• From: "Johnson, Matthew C. (LNG-HBE)" <Matthew.C.Johnson@l...>
• To: Frank Manola <fmanola@a...>, "Costello, Roger L." <costello@m...>
• Date: Tue, 27 Sep 2011 13:37:18 +0000

As with RelaxNG, the focus on the underlying model which can then be serialized in multiple ways.  For RDF, RDF/XML is just one of those options.  And using RDF/XML then enforces the striping pattern described.  Using something like Turtle (another option) is not based on XML and, therefore, does not serialize using elements/attributes.



> -----Original Message-----
> From: Frank Manola [mailto:fmanola@a...]
> Sent: Monday, September 26, 2011 10:18 PM
> To: Costello, Roger L.
> Cc: xml-dev@l...
> Subject: Re:  RE: When you create a markup language, what do
> your parent elements mean? What do your children elements mean?
> 
> Roger--
> 
> You need to distinguish between RDF and RDF/XML.  RDF is not a markup
> language, and has no notions of parent and child elements (or any other
> kind of elements, for that matter).
> 
> --Frank
> 
> 
> On Sep 26, 2011, at 6:49 PM, Costello, Roger L. wrote:
> 
> > Hi Folks,
> >
> > These two markup languages have a consistent definition of what parent
> elements and child elements mean:
> >
> > 1. RDF
> > 2. GML
> >
> > Both languages specify that parent elements represent a resource or
> object and child elements represent properties or attributes.
> >
> > Are those the only markup languages that have a consistent definition
> of what parent elements and child elements mean?
> >
> > If one is creating a markup language and wants to adopt a consistent
> definition for parent elements and child elements, is resource/object
> and property/attribute the only way to accomplish it?
> >
> > Is an Object-Oriented approach to markup the only viable approach when
> one wants to have a consistent definition for parent elements and child
> elements? That would be quite astonishing, given that people such as Tim
> Bray argue that "XML is 180 degrees apart from OO".
> >
> > /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@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

• References:
  • When you create a markup language, what do your parent elementsmean? What do your children elements mean?
    • From: "Costello, Roger L." <costello@m...>
  • RE: When you create a markup language, what do your parent elementsmean? What do your children elements mean?
    • From: "Costello, Roger L." <costello@m...>
  • Re: RE: When you create a markup language,what do your parent elements mean? What do your children elements mean?
    • From: Frank Manola <fmanola@a...>