Looks good.
Consider appropriate use of SHALL (caps) when needed.
"When one door closes, another opens; but we often look so long and so regretfully upon the closed door that we do not see the one which has opened for us."
-- Alexander Graham Bell
Toby Considine
Chair, OASIS oBIX TC
Editor, OASIS EMIX, Energy Interoperation
Campus Services Information Technology
University of North Carolina
Chapel Hill, NC
Email:
Toby.Considine@ unc.edu
Phone: (919)962-9073
http://www.oasis-open.org
http://www.NewDaedalus.com
From: [mailto:]
On Behalf Of Gemmill, Craig
Sent: Tuesday, April 30, 2013 2:56 PM
To:
Subject: [obix] potential language for Section 3
Obixers-
I think we agreed to discuss on the email list for the language in section 3. I don’t think much is needed, but in the interest of starting the discussion,
How about simply:
for the ‘Architecture’ section:
Encoding: a set of rules for representing the object model in certain common formats.
For the XML section 3.2 – retitled ‘Encoding’:
A necessary facet of oBIX is set of simple syntax rules to represent the underlying object model. XML is a widely used language with well-defined and well-understood syntax that maps nicely to the oBIX object model.
The rest of this document will use XML as the example encoding, because it is easily human-readable, and serves to clearly demonstrate the concepts presented. The syntax used shall be considered normative. Implementations using an XML encoding MUST conform
to this syntax and representation of elements.
When encoding oBIX objects in XML, eachoBIX is all about a simple XML syntax to represent its underlying object model. Each of the object types map to one type of element.
Craig
