Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Schemas and the open world assumption.

From: "Michael Kay" <mike@--------.--->
To: "'Olivier Rossel'" <olivier.rossel@-----.--->, <xml-dev@-----.---.--->
Date: 10/5/2009 9:13:00 PM
I'm not really sure that open-world/closed-world is the right way to
characterize this question. I see that as being more about whether or not
one can assume one has access to all instances of a type (for example, all
employees) or only to selected instances.

It's true that derivation-by-extension poses problems for substitutability.
But there is an OO analogy: adding new methods/fields in a subclass does not
invalidate callers who only use the methods/fields defined in the
superclass. Applications that use the paths a/b or a/c will continue to work
when a subtype is defined that also permits a/d.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 
 

> -----Original Message-----
> From: Olivier Rossel [mailto:olivier.rossel@g...] 
> Sent: 05 October 2009 10:04
> To: xml-dev@l...
> Subject: [xml-dev] Schemas and the open world assumption.
> 
> Hello everyone.
> 
> Sorry to be 5 years late, but it is just today that I 
> question myself about derivation by extension and closed 
> world assumption.
> 
> Please do not hesitate to comment the following points:
> 
> If I define "a" as being a sequence of b,c:
> <a>
>  <b/>
>  <c/>
> </a>
> 
> and i extend "a" into "aa" that extends that sequence with d:
> <aa>
>  <b/>
>  <c/>
>  <d/>
> </aa>
> 
> then any "aa" will not validate against the definition of "a".
> right?
> this sounds like a MAJOR difference with OO paradigm (where 
> any "aa" is also a "a").
> 
> that is what i call the closed world assumption in xml validation.
> 
> considering i need a more open world approach, i plan to 
> relax my schema by defining "a" in this way:
> <a>
>  <b/>
>  <c/>
>  <xsd:any>
> </a>
> 
> then i feel like i could extend my "a" definition  without 
> breaking the "subclass" philosophy.
> 
> can anyone comment that point of view?
> i am especially interested in possible pitfalls i could have 
> missed in using the "any" statement.
> i am also interested in best practices when defining modular 
> expandable models.
> 
> any help is very welcome.
> 
> ______________________________________________________________
> _________
> 
> 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@l...
> subscribe: xml-dev-subscribe@l... 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@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



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