[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (OBIX-39) Section 6 - Simple editorial comments
Section 6 - Simple editorial comments
-------------------------------------
Key: OBIX-39
URL: http://tools.oasis-open.org/issues/browse/OBIX-39
Project: OASIS Open Building Information Exchange (oBIX) TC
Issue Type: Improvement
Components: OBIX 1.1 Specification
Affects Versions: oBIX PR01
Environment: Toby Considine
Reporter: Toby Considine
Assignee: Toby Considine
Priority: Minor
638-641: OBIX Contracts are used to define inheritance in OBIX points. A Contract is a template that is referenced by other objects. These templates are referenced using the "is" attribute".
Contracts solve many problems in OBIX:
652-654: Eliminate first two sentences.
659-670: Do not use "a couple of" to introduce a list of four items. Consider:
"Common Terms useful for discussing Contracts" and then placing the terms in a numbered table captioned "Contract Terminology"
687: "Syntactic Sugar?
702-703 "Formally defined in XML"? consider other language that distinguishes between information model and encoding.
694-709: It is unclear what a coder should do when encountering "Implicit Contracts"
797: Are these the rules used for alternate encodings? Perhaps in
"In XML, flattening is done by...." Other encodings MUST either define the rules for expressing flattening or explicitly forbid flattening to conform with this specification.
804: Here we slide back from URLs to URIs. Pick one.
827 "Diamond Inheritance Pattern" may confuse more than enlighten without more words.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]