Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Interesting pair of comments (was Re: [xml-dev] Schema Experience Workshop minutes online)

From: Paul Downey <paul.downey@----------.--->
To: "Rick Jelliffe" <ricko@-------.---.-->
Date: 7/14/2005 10:37:00 AM
On 14 Jul 2005, at 05:02, Rick Jelliffe wrote:

> "There appeared to be no obvious way to split the XML Schema 
> specification
> into layers or sub-languages"
>
> So XML Schemas is such spaghetti that it cannot be untangled? Yikes.
> But I don't believe it.

The difficulty in splitting the spec into layers or shells is that
there isn't consensus on which features are core and which are
esoteric. You're 80 is my 20 was order of the day and highlighted
in Paul Biron's summary of the experience reports.

> One problem with a monolithic spec is that it gives little
> guidance about what is core and non-core. Everything is
> core. A more layered spec such as I suggest would clarify
> that, for example, mixed content is a core feature but xsi:nill
> is not.

Which I think, proves my point. Whilst I agree that mixed content is
core - from my perspective it's what XML is all about, but for many
people serialising their data, it's a nuisance and definitely not as
core as xsi:nill.

--
http://blog.whatfettle.com


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