Re: [xml-dev] Elements have properties. What properties must beagreed to

[Stephen D Green <stephengreenubl@gmail.com>]

> If the element is "declared" in an XML Schema then it has additional properties, including nillable, abstract, substitution group affiliations.

If you want interoperability then just limiting the properties to
those declared in a single schema might not give you that.
There may be a large range of schemas required for
interoperability: With a given XML document where there may
be different senders/receivers each needing a different schema.
You might then have a 'master' schema but many 'profile'
schemas. Just like with words and their spellings. There might
be a preferred spelling such as an Oxford English Dictionary
spelling of an english word but then there might be accepted
alternatives for regions. You have to get agreement on which
spelling wil be used in a region but sometimes for any given
project. Like 'schemas' or 'schemata' for the plural of schema.
Then participants might find they have to use one spelling for
one project and simultaeously another for another project. So
with uses of a single XML vocabulary. The differences might
be declared in different schemata of using some other means.

----
Stephen D Green



On 28 March 2011 21:08, Costello, Roger L. <costello@mitre.org> wrote:
> Hi Folks,
>
> [Definition] Property: something owned; any tangible or intangible possession that is owned by someone.
>
> Consider this instance document element:
>
> <Publisher xmlns="http://www.book.org";>Wrox Press</Publisher>
>
> The element has properties, including:
>
> - name, which has the value "Publisher"
> - namespace, which has the value "http://www.book.org";
> - type, which has the value ??? (can this be determined solely by examining the instance document?)
>
> If the element is "declared" in an XML Schema then it has additional properties, including nillable, abstract, substitution group affiliations. Here's the complete list of properties:
>
> http://www.w3.org/TR/xmlschema11-1/#Element_Declaration_details
>
> So, an element has multiple properties and the properties have values.
>
> If a sender and a recipient want to interoperate, what set of properties and property values must they agree upon?
>
> I think that the sender and recipient must agree on a unique name for the element. That is, they must agree on values for the name and namespace properties. For example, they agree to this unique name:
>
> {http://www.book.org}Publisher
>
> Does the sender and recipient need to agree on the value of the type property? Suppose the sender assumes the type of the element is an enumeration list ("Wrox Press", "New Riders", "friendsofed", "Norton Press") but the recipient assumes the type of the element is an unconstrained string. Can they interoperate?
>
> Does the sender and recipient need to agree on other properties - nillable, abstract, etc?
>
> Is interoperability a sliding scale, from limited interoperability to perfect interoperability? At what point is there meaningful interoperability?
>
> /Roger
>
> _______________________________________________________________________
>
> 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
>
>