Critical Following a conversation about the notation shift, we need to discuss the need to support XDI-graph versioning.
There is a version defined at the Messaging level but it is probably preferable to have a separate one for XDI graph definitions.
Pre-1.0 versions of the standard are identified by working draft number.
We still need to add versioning starting 1.0 (to prepare for subsequent releases).
BTW how do we expect 2 implementations that use different pre-1.0 versions to interoperate...?
We've discussed this in TC meeting - if we can avoid having to support pre-1.0 versions that would be better.
In any case I don't think this is a bug against the spec - it may be for XDI itself.
Isn't this a bug for 1.0 though?
In other words, aren't we going to address graph versioning in 1.0?
ED: to clarify the comment a bit, "We need a mechanism to express the version of the serialization and XDI graph model. I would expect this to have an initial value of 1.0". See proposed resolution in https://lists.oasis-open.org/archives/xdi/201407/msg00107.html
Agree that Core should include details on how Graph and serialization version is expressed.
Messaging will need additional material (esp. wrt messaging versions)
To be clear, I'm talking about the versioning of the XDI standard, not versioning of data (e.g. collection).
For instance to differentiate pre and post notation shift XDI standard.