> [Heath Frankel]
> I understand your point here but if we cannot have some kind of schema
> migration mechanism we will need a new schema per release, which is
> something that I don't think anyone wants.

Yes - I don't want that either. I bring it up because if we are allowing
minor schema changes as well as major ones, we need two versioning
mechanisms.

For the major releases the schema namespace is the indicator.

For minor releases, we have no information about what minor release
the instance was designed for, unless we mandate a mechanism
such as the one you suggested with rm_version in archetype_details.

> [Heath Frankel]
> So your suggesting moving to a date oriented namespace so that there is no
> tie to the release number?

Well, the tie would be through documentation - the 1.1.3 release would say
something like - we are using the 2009/01 schemas. It then puts them
on a separate release trajectory. Of course, this would only be useful
if we think there will actually be divergence between the XML schema
changes needed, and the major releases needed.

> [Heath Frankel]
> All archetyped locatables can have this and I would expect all top-level
> objects to be archetyped otherwise they have no domain semantics.

What about actual ARCHETYPE objects? Some tools or systems may
persist the xml serialization of the AOM rather than the ADL. Same
with templates. I'm saying that every XML instance that might ever be
in the wild using the openehr schemas should have some clear mechanism
to tie it to the actual schema files that it _strictly_ conforms to.

> [Heath Frankel]
> I can see the utility of this, but I am not sure that we should mandate it,
> seems a bit of a hack.

It does feel hackish. But it is the only attributes you can add to an xml
instance without needing to change schema, and the xsi:schemaLocation
field is actually roughly designed for this purpose.

The other option is to add a mandatory fixed "meta" attribute for Composition,
Archetype etc that is explicitly in the XML ITS, that holds the full
schema release version number.

Andrew

Reply via email to