That looks pretty good me. My only comment:
- I'd probably leave the grammar in 8.1 alone, since it is a little confusing (in this case I think the [facetValue] production of custom facets is just
Toby's change which messed up code blocks and turned them into bullet lists also still needs to get fixed. I am not sure what Toby's version actually was - looks like nothing but alignment changes, in which case we might be better off branching this change off the previous version.
On Tue, Jun 8, 2010 at 5:27 PM, <> wrote:
This is a modification of my earlier proposal based on feedback from the
group. A couple of points -
1) This change only supports custom facets, as opposed to my earlier
proposal which allowed custom object types as well. This is based on
feedback, and makes sense since custom objects can always be accommodated
via contract.
2) I restricted the data type associated with a custom facet to a subset of
available data types. It didn't seem reasonable, for example, to include
op/ref/feed etc. types since they aren't really data types.
Thanks!
Brad Benson
-- Mr. Brad Benson
The document named oBIX-1-1-spec-wd06.doc has been submitted by Mr. Brad
Benson to the OASIS Open Building Information Exchange (oBIX) TC document
repository.
Document Description:
Added proposal for supporting custom facets within the binary encoding
specification.
View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=38179
Download Document:
http://www.oasis-open.org/committees/download.php/38179/oBIX-1-1-spec-wd06.doc
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
