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

Re: Venetian Blinds vs Garden of Eden patterns for industry st

  • From: "Pete Cordell" <petexmldev@codalogic.com>
  • To: <xml-dev@lists.xml.org>
  • Date: Thu, 28 Oct 2010 11:16:28 +0100

Re:  Venetian Blinds vs Garden of Eden patterns for industry st
One thing I'm surprised is not more popular is to always use Venetian Blind, 
even across namespaces, BUT make local elements unqualified, i.e. use 
elementFormDefault="unqualified".

That way you only ever have one namespace declaration (ignoring QName 
issues) irrespective of the types you use from other namespaces, and you 
only have the root element as qualified.  So your XML instance looks like:

<myNS:root xmlns:myNS="abc">
    <element1>
        <elementWithTypeDefinedInAnotherNamespace>
        </elementWithTypeDefinedInAnotherNamespace>
    </element1>
</myNS>

The instance is appropriately tagged with it's namespace, but it's all 
clearly done in one place and there's no other namespace gotchas to worry 
about.

The approach mirrors JSON's response to "there's nothing like XML namespaces 
in JSON."

I think the issue is that the interpretation of a element depends on the 
context provided by the parent and XSLT and other XPath technologies have 
difficulty with that.

Spot the outsider!

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using C++ XML
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
for more info
----- Original Message ----- 
From: "Pete Cordell" <petexmldev@codalogic.com>
To: <xml-dev@lists.xml.org>
Sent: Thursday, October 28, 2010 10:58 AM
Subject: Re:  Venetian Blinds vs Garden of Eden patterns for 
industry standards XML Schemas


> FWIW I would use:
>
> <xs:element name="" type=""/>
>
> (i.e. Venetian Blind) where type is within the same namespace/schema as 
> the element, and:
>
> <xs:element ref=""/>
>
> (i.e. Salami Slice) when the element(/type) being accessed is in a 
> different namespace.
>
> To give it a name I'll call it Venetian Slice!
>
> By analogy to a class interface, I see the global elements as the public 
> members of an interface, and the global types as the private members.  The 
> interface should only publically expose what it has to, and Venetian Blind 
> provides a non-narrative way to express that.  Accessing a new namespace 
> is analogous to accessing a new class, and so the public interface (i.e. 
> global elements) of that namespace have to be used.
>
> That should open up the discussion!
>
> Pete Cordell
> Codalogic Ltd
> Interface XML to C++ the easy way using C++ XML
> data binding to convert XSD schemas to C++ classes.
> Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
> for more info
> ----- Original Message ----- 
> From: "Dennis Sosnoski" <dms@sosnoski.com>
> To: <xml-dev@lists.xml.org>
> Sent: Thursday, October 28, 2010 6:41 AM
> Subject: Re:  Venetian Blinds vs Garden of Eden patterns for 
> industry standards XML Schemas
>
>
>>
>> If you're thinking of using data binding for working with the data in
>> applications I'd strongly recommend a Venetian Blinds approach. Most
>> data binding approaches turn Garden of Eden into an amorphous foam of
>> tiny classes - which is, after all, exactly what Garden of Eden
>> represents in XML terms.
>>
>> Associating the name "Garden of Eden" with this concept of pureed
>> structure was excellent marketing, but doesn't really give the right
>> impression. I'd suggest "Element Soup" as an alternative. :-)
>>
>>  - Dennis
>>
>>
>> On 10/28/2010 05:31 AM, Lech Rzedzicki wrote:
>>> Hi all.
>>>
>>> I am now involved in developing the next iteration of schemas to
>>> standardise information storage and exchange for trademarks and design
>>> (there is also some cooperation with patent people).
>>> The current standards (TM-XML and DS-XML) use a venetian blind pattern
>>> because it nicely mimics OO model, so it's easy to generate classes
>>> and objects, also it hides element definitions so there's no conflicts
>>> when processing them. Finally the naming convention (not my idea)
>>> means that the element names are not reusable anyway.
>>> Some people are now proposing that we move to "Garden of Eden" design
>>> patter, but I don't see that as a particularly smart move in the
>>> context of our domain.
>>> I have noticed that many of the schemas in the industry, for instance
>>> UBL have gone for Garden of Eden first and and later reverted to
>>> Venetian Blinds.
>>> I am very interested in some thoughts from the trenches as to why one
>>> or the other approach might be more useful in a committee driven
>>> standards with contributors from different domains.
>>>
>>> No need to point me to google either - I have read all the articles
>>> about it [1,2,3] and authored schemas that are in production now both
>>> ways, but still unconvinced either way...
>>>
>>>
>>> References:
>>>
>>> [1] A slideshows on various approaches:
>>> http://dret.net/lectures/xml-fall08/xsd-2#(11)
>>> [2] http://www.xfront.com/GlobalVersusLocal.html - schema best practices
>>> [3] http://www.ibm.com/developerworks/xml/library/x-schemascope/
>>> etc...
>>>
>>> _______________________________________________________________________
>>>
>>> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>>> to support XML implementation and development. To minimize
>>> spam in the archives, you must subscribe before posting.
>>>
>>> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>>> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
>>> subscribe: xml-dev-subscribe@lists.xml.org
>>> List archive: http://lists.xml.org/archives/xml-dev/
>>> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>>>
>>>
>>
>> _______________________________________________________________________
>>
>> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>> to support XML implementation and development. To minimize
>> spam in the archives, you must subscribe before posting.
>>
>> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
>> subscribe: xml-dev-subscribe@lists.xml.org
>> List archive: http://lists.xml.org/archives/xml-dev/
>> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>>
>>
> 





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.