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] RE: List of differences between XML and JSON?

At 2015-05-01 21:01 +0000, Costello, Roger L. wrote:
Ø  the syntax of XML enforces the "hasA" view

I'm not one to put words into Walter's mouth as I
defer to and have always looked up to his sage
thoughts, so what I say here is my own interpretation.

what is it in the XML syntax that enforces the
“hasA” view”? (Please be specific)
Is it not, simply, the hierarchy?

If I were to design a new data format language,
what would I put in the language to enforce the “hasA” view?
Elements that contain other elements.  If you
have only a document element and then a serial
list of children without grandchildren, then you
only have the one "hasA" relationship, but not at each branch of the tree.

However, the more hierarchy (branches) you
introduce, the more "hasA" relationships are being described.

What’s the principle at work?

How did the XML founding fathers sneak that into
the XML language? By design or by accident?
I suppose by design, choosing to preserve the
SGML concept of expressing hierarchy and containership.

What is the advantage of the “hasA” view?
It is unambiguous.  Anyone gets to interpret
"isA" any way they wish, but in the syntax
(remember, that is what Walter said, it is the
syntax) the start and end tags contain ("hasA") their descendants.

Is it something that one should strive for when
designing a data format language? Or is it something that is to be avoided?
Simply use hierarchy where hierarchy makes sense.

For example, this invoice does not exploit "hasA":

   <sellto-street>123 Main St.</sellto-street>
   <buyfrom-street>234 Fornt St.</buyfrom-street>

... whereas this invoice does exploit "hasA":

       <street>123 Main St</street>
       <street>234 Front St</street>

The invoice "has a seller" and "has a
buyer".  Both the buyer and seller "has a name"
and "has an address".  Every name has two
components, every address has two
components.  This is inherent in the syntax as a representation of a tree.

This is what I believe Walter is
highlighting.  As always, I applaud his insight.

I hope this helps.

. . . . . . . . .  Ken

Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Free 5-hour lecture:  http://www.CraneSoftwrights.com/links/video.htm |
Crane Softwrights Ltd.             http://www.CraneSoftwrights.com/x/ |
G. Ken Holman                    mailto:gkholman@CraneSoftwrights.com |
Google+ profile:       http://plus.google.com/+GKenHolman-Crane/about |
Legal business disclaimers:     http://www.CraneSoftwrights.com/legal |

This email has been checked for viruses by Avast antivirus software.

[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