[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: PSVI formalization

• To: 'Alaric Snell' <alaric@a...>, "Thomas B. Passin" <tpassin@c...>, xml-dev@l...
• Subject: RE: PSVI formalization
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Fri, 10 May 2002 08:20:55 -0500

Some have.  Versioning threads started a few years ago. 

It seems so strange to read the PSVI and XPath/XQuery 
threads and see XML (posed originally to make a programmer's
job easy) becoming not only something hard for a programmer 
to learn, but close to impossible for the rest of the 
web community.  This is progress?  Someone should write a book 
outlining all the easy and straightforward ways to use 
ASP, JScript/Javascript, and cheap relational dbs that 
enable web services and basic XML/HTML to do 99% of the 
practical jobs and skip the rest:

"XML:  On Time and Under Budget"

len

-----Original Message-----
From: Alaric Snell [mailto:alaric@a...]


That reminds me... extensibility. In the XML world, the 'extensible' really 
just means 'you can define your own vocabularies'. There's no explicit 
support for different versions of vocabularies to try to interact beyond what 
is intrinsically provided by having tagged values that can be skipped if 
unknown like in BER. ASN.1 has an explicit versioning mechanism for revisions 
of schemas that allows one to control the interoperability between them, 
explicitly marking the changes so processors can deal with different versions 
well.

Is this a requirement XML schema languages other than ASN.1 are going to 
stumble into in a few year's time and make XML-DEV writhe with curses and 
debates?

• Follow-Ups:
  • Re: PSVI formalization
    • From: Alaric Snell <alaric@a...>

• Prev by Date: Re: PSVI formalization
• Next by Date: Web Services Mapping Capabilities?
• Previous by thread: RE: PSVI formalization
• Next by thread: Re: PSVI formalization
• Index(es):
  • Date
  • Thread