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

Re: BOXED XML (was RE: Re: Remembering the original

• To: Martin Bravenboer <martin@m...>,Don Box <dbox@m...>
• Subject: Re: BOXED XML (was RE: Re: Remembering the original XML vision)
• From: Jonathan Robie <jonathan.robie@d...>
• Date: Mon, 17 Feb 2003 09:19:24 -0500
• Cc: Sean McGrath <sean.mcgrath@p...>,xml-dev@l...
• In-reply-to: <3E509D00.2070407@m...>
• References: <57EF69AF56D92148984EDA3174082945040F995E@R...>

At 09:27 AM 2/17/2003 +0100, Martin Bravenboer wrote:

>I think W3C XML Schema doesn't fit the requirements of a "byte code" of 
>XML metadata at all. Shouldn't a bytecode contain as few irrelevant 
>details as possible? Shoudn't a bytecode be easy to process?
>
>A bytecode for xml metadata should be powerful, minimal and simple: a 
>decent programmer should be able to write some code to process the 
>bytecode in just a few days with the right tools.

I agree with Martin. And also, a byte code not have so many different ways 
of expressing the same things - this makes it much harder to process 
schemas. When I have written code to process W3C XML Schemas, the first 
thing I did was build a normalized internal format and give it an XML 
representation.

In fact, the W3C XML Schema spec gives you hints about how to normalize a 
schema into schema components, and I think most schema processors do 
something analogous to this. But it shouldn't be so difficult....

Jonathan 

• References:
  • BOXED XML (was RE: Re: Remembering the original XML vision)
    • From: "Don Box" <dbox@m...>
  • Re: BOXED XML (was RE: Re: Remembering the originalXML vision)
    • From: Martin Bravenboer <martin@m...>

• Prev by Date: Re: Anyone wanna speculate about what this means?
• Next by Date: Re: Re: How to redesign W3C XML Schema (Was: Remembering the original XML vision)
• Previous by thread: Re: BOXED XML (was RE: Re: Remembering the originalXML vision)
• Next by thread: RelaxNG problem about section 7.4. Restrictions on interleave
• Index(es):
  • Date
  • Thread