So could just as easily make your namespaces "http://apples" and "http://autocannons", bind them to a: and b: respectively then use that as a thought exercise :)
If your database queries are not intended to be scoped by version, then you might want to look at your schema versioning scheme. The "semantic versioning" concept might be a good point of reference for that activity, eg. only bump up the version number in the namespace URL if your schema update makes incompatible changes with the previous version of the schema.
In the case of incompatible schema updates, you might then want to make a conscious decision to either upgrade the entire database to the new schema or instead update all your query code to handle the new schema version (this second option is what you question in your email below). The easy (and slighty scary) option would be to just ignore namespaces. Hard to recommend an approach without knowing more about the data and application.
It does occur to me however that if both the 2.4.1 and 2.4.2 schemas are compatible with each other then it doesn't seem like a great idea to use a different namespace for each version as that will complicate the query code and any other downstream consumers of the XML.
Hi All,
I don't recall my specific reasons now but I have been reusing a namespace prefix in schemas and instance data 'mlhim2' to reference different versions of a schema reference model.
For example:
Now I think this is a mistake when I need to have multiple versions of instance data in a single database and run queries across them.
Should I change to start using:
to be more explicit and avoid any problems?
Thanks In Advance,
Tim
