> ok - this approach more or less replicates the release id approach > already in use, but converts it to a URL.
Except, this is a change that occurs in all xml _instances_, not just the schema files. So every reference model document in every system in existence now has to handle two different schemas and convert between them. We have to decide whether this is what we want.. do the xml schemas aggressively track the exact spec versions, or do we only increment xml schema versions when necessary (and therefore should the xml schemas have a separate version) > We already have the URL > pattern http://www.openehr.org/releases/N.M.P, so we could do > http://www.openehr.org/releases/N.M.P/schemas > > Apparently it is not always expected that the URL mentioned in a schema > actually exists so http://schemas.openehr.org/v1.0.2 could be used as > well. Or we could create it for real. (What are the requirements here?) The schema identifier is a URI - there is no requirement that it is accessible at the same identifier, and in fact it seems like there is a trend towards using other URN syntaxes rather than URLs. > Starting from Composition.xsd, there is a cascade of nested inclusions > down to Basic_types.xsd. If an XML document representing a Composition > is to correctly indicate its schema, it should point to e.g. > http://www.openehr.org/releases/1.0.2/schemas/Composition.xsd or > http://schemas.openehr.org/1.0.2/Composition.xsd > > Inclusions are curently done with a statement like > > <xs:include schemaLocation="Content.xsd"/> > > which does not mention the version of the included schema, so one > assumes it is from the same release, which is the effect we want. Is > this the orthodox way to do this in XML land? There was a decision by Heath (and others at Ocean) to have a single namespace for all the openehr XML classes around the time of the 1.0 release. The schemaLocation of XSD files is a separate issue and one that I would not worry about - assume that all XSD files bundled together in the same directory belong to the same "release set" (as is currently the case) Andrew
