[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: potential language for Section 3
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
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, each