Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Versioning of XML Schema and namespaces

From: Dan Vint <dvint@-----.--->
To: Eliot Kimber <ekimber@---------------.--->,John.Hockaday@--.---.--
Date: 5/10/2005 12:57:00 AM
At 07:26 AM 5/10/2005, Eliot Kimber wrote:
>- What abstract "application" the document applies to. This is indicated 
>by the namespace. There is no analog of this in DTD-land. People *tried* 
>to use public identifiers in this way, but that's not what they were 
>intended to mean. This declaration can be *reliably* used by processors to 
>associate documents with both validation rules (schemas) and business 
>rules (e.g., XSLTs, Java classes, import/export rules for content 
>management systems, etc.).

I agree with the idea that namespaces could provide this functionality, 
except that most folks recommend not versioning the namespace. I believe 
you or someone in this thread suggested using the version attribute for 
this function. Well that might work if the parsers actually did something 
with the version attribute. The only mechanism that I can be sure will be 
caught by the parser is to use the namespace with a version to indicate 
that the document conforms to a different version of the standard than 
someone else might be using.

..dan
---------------------------------------------------------------------------
Danny Vint

Specializing in Panoramic Images of California and the West
http://www.dvint.com

voice: 510-522-4703


     



From ekimber@i... Tue May 10 15:21:12 2005
Recei


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent