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

Re: Re: Where does the "nothing left but toolkits" myth come f

• To: David Lyon <david.lyon@c...>
• Subject: Re: Re: Where does the "nothing left but toolkits" myth come from?
• From: Chris Burdess <dog@b...>
• Date: Mon, 7 Feb 2005 13:16:33 +0000
• Cc: xml-dev@l...
• In-reply-to: <200502072203.32140.david.lyon@c...>
• References: <Pine.LNX.4.44L0.0501280904130.20504-100000@s...> <e3a5cb2c05020609516779e7d6@m...> <6fa681b1050206105274c18b2b@m...> <200502072203.32140.david.lyon@c...>

David Lyon wrote:
> but I'm only advocating adding an encoding strategy for dealing with
> business data from the data-centric database world. To giver faster
> throughput and reduce the capacity for xml data processing errors.

Your non-XML language, example:

  <parts>
   <Carparts Item>
    Product_Name&="Selespede gearbox"
   </Carparts Item>
  </parts>

XML, example:

  <parts>
   <carparts-item product-name='Selespede gearbox'/>
  </parts>

An example XML Schema definition that provides the datatype information:

  <xsd:schema xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
   <xsd:complexType name='Parts'>
    <xsd:sequence>
     <xsd:element name='carparts-item' minOccurs='0' 
maxOccurs='unbounded'>
      <xsd:complexType>
       <xsd:attribute name='product-name' type='xsd:normalizedString' 
use='required'/>
      </xsd:complexType>
     </xsd:element>
    </xsd:sequence>
   </xsd:complexType>
   <xsd:element name='parts' type='Parts'/>
  </xsd:schema>

David's non-XML: 65 significant non-whitespace characters per car-part 
entry.
XML: 50 significant non-whitespace characters per car-part entry.

Note that the length of the element and attribute names is the same in 
each case.

Granted, the XSD does take up a bit of space. However, it's constant 
for all car-parts entries and therefore only needs to be transferred 
once (ever). There are also less verbose schema languages. And besides, 
we only need 30 car-parts entries to negate the cost of the XSD. In 
your data-centric database world, you have LOTS more car-parts entries 
that that, right?
-- 
Chris Burdess

• Follow-Ups:
  • Re: Re: Where does the "nothing left but toolkits" myth come from?
    • From: David Lyon <david.lyon@c...>

• References:
  • Re: Where does the "nothing left but toolkits" myth come from?
    • From: Michael Champion <michaelc.champion@g...>
  • Re: Re: Where does the "nothing left but toolkits" myth come from?
    • From: Kurt Cagle <kurt.cagle@g...>
  • Re: Re: Where does the "nothing left but toolkits" myth come from?
    • From: David Lyon <david.lyon@c...>

• Prev by Date: Re: Re: Where does the "nothing left but toolkits" myth come from?
• Next by Date: Re: Re: Where does the "nothing left but toolkits" myth come from?
• Previous by thread: Re: Re: Where does the "nothing left but toolkits" myth come from?
• Next by thread: Re: Re: Where does the "nothing left but toolkits" myth come from?
• Index(es):
  • Date
  • Thread