[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [obix] Binary encoding (was: [obix] Groups -oBIX-1-1-spec-wd05.pdf uploaded)
The description of the binary encoding details specifically does not account for custom namespaces/elements/attributes as stated in section 8 para 2, which certainly seems reasonable. However, it is wise to not provide a mechanism for such extensions to occur since they likely will anyway? Conceptually, could we reserve a binary constant within the table in section 8.2 as a marker for a custom namespace/element/tag? For example, binary constant 31 ( 31 << 2, using the notation in the aforementioned table) might be defined as the marker for a custom element or attribute, the name of which is encoded as a string immediately following the constant. There are of course additional details to be worked here, but I think the concept is worth examining.
If there are no objections to this idea, I'd be happy to write up a more formal description as a proposal.
Side note - is it just my system or are several pages missing (or perhaps the table of contents is munged) - lines 259 through 285 within the TOC have undefined bookmarks, for example.
Trane /Ingersoll Rand
firstname.lastname@example.org / 651-407-4285
"The way to get started is to quit talking and begin doing." - Walter Elias "Walt" Disney
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Wednesday, June 02, 2010 8:39 AM
Subject: [obix] Groups - oBIX-1-1-spec-wd05.pdf uploaded
Several committee members have asked me about getting this to a standards vote soon - this will only happen with some participation and comments.
I have adopted a convention here that has proved useful in other TCs. There are multiple versions of this document. The most recent, or reference version, is a PDF with line numbers turned on. This makes for the easiest comments. An earlier version is a clean (changes accepted) word doc. To get to the earlier version, look at document properties in the libary, and see all versions.
In work going forward, I propose that we have an even earlier doc, that is a document with changes shown. This multi-versioon approach has helped focus and clarify work in other committees. The review copy with lines is a PDF because changes in printer can change line numbers....
-- Toby Considine
The document revision named oBIX-1-1-spec-wd05.pdf has been submitted by Toby Considine to the OASIS Open Building Information Exchange (oBIX) TC document repository. This document is revision #1 of oBIX-1-1-spec-wd05.doc.
Updated document to current template used for OASIS standards. For the most part, document was untouched, although I added references and acknowledgements.
There is now a blank chapter at the end for conformance statements. Current OASIS process dictates that the last normative chapter of a specification document must be conformance section.Appendices are for all non-normative material, i.e., background or explanatory. So far, I can't see a chapter to move in that direction.
View Document Details:
This document is revision #1 of oBIX-1-1-spec-wd05.doc. The document details page referenced above will show the complete revision history.
PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
-OASIS Open Administration
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at: