XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Service Constraints

Andrew Welch scripsit:

> The extreme flip side is an XSD where everything is optional, which
> doesn't do anyone any good,

Actually, it can.  $EMPLOYER provides an interface of the form "Tell me
all you know about a real-world entity with the following properties".
Both request and reply use the same all-is-optional schema.  Obviously,
if the request contains only obscure properties, you may get back no
results; likewise, it's possible that the properties you supply are all
we know, so we echo them back to you.

But without the schema, there would be no agreement about which
properties are available, or how they are denoted.

-- 
What asininity could I have uttered     John Cowan <cowan@ccil.org>
that they applaud me thus?              http://www.ccil.org/~cowan
        --Phocion, Greek orator


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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS