OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xliff] proposed solutions for CSPRD 138 (Unique Particle Attribution) - version attribute

Hi all,

One last question to close that specific topic.
(just making sure we have a clear path forward).

Now that we have a solution for the schemas/spec what will happened to the version number when we have a new specification?

Let's say we add a new module:

- We have to change the spec document since we add the module there I presume.
- But none of the namespaces changes, so they all stay at 2.0 (including the core).
- Does the spec document goes to 2.1? or something like 2.0.a?
- and the version attribute changes to the spec version.
--> one issue: that attribute is part of the core, if we change it we change the core schema...

My question I suppose is: do we need a version attribute at all? Since that info now would make sense only per namespace. The
overall version of the spec is rather moot since it can have modules defined on previous versions.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]