| [OASIS Issue Tracker] Commented: (OBIX-10) Section 1 - Use four design points to introduce and link concepts throughout document |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-11) Section 2 - Suggest examples follow through on each of four design points from section 1, making sure to use those four words (XML, Networking, Normalization, Foundation) |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-13) Section 2, Line 109 - It is stated that ". . . there are three element types." It is suggested that the three element types be listed at this point. |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-12) Section 2, Lines 114-115: "document" used to refer to multiple types of documents, needs clarification |
2 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-14) Section 2, Line 115 - "Child" has not been used up to this point in the document, and is used in line 115 without any explanation. |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-15) Section 2, Line 115 - It is stated that "There are three child objects for each of the thermostat's variables." Should it not say something like: "There are child objects to describe each of the three thermostat's variables." |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-16) Section 2, Line 122 - It is suggested that it might be appropriate to introduce this section with the "Normalization" term used in section 1, so that the reader can follow through with the example using terms introduced in section 1. |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-19) Line 148, Line 161, Line 212 - Are words such as "slick", "cleverly", "nifty" appropriate words to use along with the connotations they imply? |
2 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-21) Section 4 - While Figure 1 shows the supported attributes for each object type, the same attributes do not appear in the text. |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-24) Section 4, Figure 1, Line 269 - What does "range: anyURI" mean for obix::bool? |
3 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-23) Section 4, Figure 1, Line 269 - What does "max: integer" and "min: integer" mean for obix::str? |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-25) Section 4.1, Lines 272-3: It may be helpful to explain the significance or consequence of "Every XML element in oBIX is a derivative of the obj element" - e.g. in that each of the other objects contain those attributes. |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-27) Section 4.1, Line 283: "Contract definition" is used for the first time in this document, but there is no explanation. |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (OBIX-1) UML diagram and text needs clarification line 269 |
2 |
2013-09-05 |
| [OASIS Issue Tracker] Commented: (OBIX-7) Fix the JSON examples, especially the quotes and comma after "tag" in the second and third line |
2 |
2013-09-05 |
| [OASIS Issue Tracker] Commented: (OBIX-5) Call the structural element "items" instead of "nodes" because of the semantic meaning of the term "node" / "nodes" in HTML context (where JSON is usually used |
1 |
2013-09-05 |
| [OASIS Issue Tracker] Commented: (OBIX-6) Call the tag element "type" instead of "tag" - as it seems to be more like a type than a tag (although "type" already used in edge cases) |
1 |
2013-09-05 |
| [OASIS Issue Tracker] Created: (OBIX-28) Fix Acknowledgment Section |
1 |
2013-09-05 |
| [OASIS Issue Tracker] Created: (OBIX-29) Code example format |
1 |
2013-09-05 |
| Regrets for the September 5 meeting |
1 |
2013-09-05 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOS0wNV9vYml4?= =?UTF-8?B?TWludXRlcy50eHQgdXBsb2FkZWQ=?= |
1 |
2013-09-05 |
| Handling of JIRA issues |
2 |
2013-09-05 |
| Comments on oBIX 1.1 PR01 |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-30) General: Document should indicate more clearly what is normative, what is illustrative. |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-31) General: Consider a table of tables, and a table of examples following the table of contents. Many of the bulleted lists in this specification should be re-cast as tables. |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-32) Section 2 - This section should be labeled non-normative |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Updated: (OBIX-32) Section 2 - This section should be labeled non-normative |
2 |
2013-09-09 |
| [OASIS Issue Tracker] Updated: (OBIX-31) General: Consider a table of tables, and a table of examples following the table of contents. Many of the bulleted lists in this specification should be re-cast as tables. |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-33) Sections 1-2: Simple Editorial Comments |
1 |
2013-09-09 |
| Comments on Common Encodings, PR01 |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-34) Section 3 - Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-35) Detailed comment on URIs |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-36) Detailed discussion of REST |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-38) Section 5 - Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-39) Section 6 - Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-37) Section 4 - Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-40) Section 7 - "Akin to methonds in OO" |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Updated: (OBIX-40) Section 7 - "Akin to methonds in OO" |
1 |
2013-09-09 |
| Comments on REST Bindings for oBIX PR01 |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-41) Section 8 - Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-42) Section 8.5 - Alternate Hierarchies does not represent the notion of metainformation well. Suggest we use "Tagging" as a title. |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-44) Section 11 - Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-43) Section 9 - Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-45) Section 12 - Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-46) Line 1692 - Format values |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-47) Sections 13-14: Simple editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-48) General: Simple Editorial comments |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-49) Move XML encoding rules from Core to Common Encodings |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Updated: (OBIX-49) XML Headers - Move XML encoding rules from Core to Common Encodings |
2 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-50) Localization - Move XML encoding rules from Core to Common Encodings |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-51) Simple Editorial Issues |
1 |
2013-09-09 |
| Comments on SOAP Bindings for oBIX PR01 |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Updated: (OBIX-48) Encodings: Simple Editorial comments |
1 |
2013-09-09 |
| Comments on Web Socket binding for oBIX WD02 |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Updated: (OBIX-50) Localization - Move XML encoding rules from Core to Common Encodings |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Updated: (OBIX-51) REST: Simple Editorial Issues |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-53) SOAP - Namespaces throughout document |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-52) SOAP: Simple editorial issues |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-54) SOAP: XML Namespaces in examples |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Updated: (OBIX-52) SOAP: Simple editorial issues |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Created: (OBIX-55) Localization |
1 |
2013-09-09 |
| [OASIS Issue Tracker] Commented: (OBIX-49) XML Headers - Move XML encoding rules from Core to Common Encodings |
2 |
2013-09-12 |
| [OASIS Issue Tracker] Created: (OBIX-56) Editorial: Tables and Figures need to be identified, have separate tables of... in the front matter |
1 |
2013-09-12 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOS0xMiBvQklY?= =?UTF-8?B?IG1lZXRpbmcgbWludXRlcyB1cGxvYWRl?= =?UTF-8?B?ZA==?= |
1 |
2013-09-12 |
| [OASIS Issue Tracker] Updated: (OBIX-2) Reference WS-Calendar for use of TZID in XML Alternately, reference XCAL (RFC 6321) |
1 |
2013-09-13 |
| [OASIS Issue Tracker] Updated: (OBIX-4) Chapter 11 "Watches" - add support for transient (or non-persistent) watches |
1 |
2013-09-13 |
| [OASIS Issue Tracker] Updated: (OBIX-8) Section 1, Line 9 - "Design Concerns" should appear on a new line. |
1 |
2013-09-13 |
| Web Sockets |
1 |
2013-09-15 |
| RE: [obix] Groups - obix-websocket-v1.0-wd03.pdf uploaded |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-12) Section 2, Lines 114-115: "document" used to refer to multiple types of documents, needs clarification |
1 |
2013-09-16 |
| assigning issues to non-listed commenters |
2 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-14) Section 2, Line 115 - "Child" has not been used up to this point in the document, and is used in line 115 without any explanation. |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-20) Section 3.2, Line 177 - With the special meaning for "facet" within the oBIX specification, it is suggested that a different word than "facet" be used in this sentence so as not to cause confusion. |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-16) Section 2, Line 122 - It is suggested that it might be appropriate to introduce this section with the "Normalization" term used in section 1, so that the reader can follow through with the example using terms introduced in section 1. |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-23) Section 4, Figure 1, Line 269 - What does "max: integer" and "min: integer" mean for obix::str? |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-24) Section 4, Figure 1, Line 269 - What does "range: anyURI" mean for obix::bool? |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-25) Section 4.1, Lines 272-3: It may be helpful to explain the significance or consequence of "Every XML element in oBIX is a derivative of the obj element" - e.g. in that each of the other objects contain those attributes. |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-26) Section 4, Figure 1, Line 269 & Section 4.1, Line 279 & Section 4.18, Lines 424-550: "Facets" needs better organization and more explanation |
1 |
2013-09-16 |
| OBIX-26 |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-27) Section 4.1, Line 283: "Contract definition" is used for the first time in this document, but there is no explanation. |
1 |
2013-09-16 |
| [OASIS Issue Tracker] Updated: (OBIX-28) Fix Acknowledgment Section |
1 |
2013-09-16 |
| Today's meeting |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gb0JJWC12MS4xLXNjaGVt?= =?UTF-8?B?YS13c2RsLXdkMTQuemlwIHVwbG9hZGVk?= |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOC0wMSBvQklY?= =?UTF-8?B?IE1lZXRpbmcgTm90ZXMgbW9kaWZpZWQ=?= |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOC0wOCBvQklY?= =?UTF-8?B?IFdvcmtzaG9wIE1lZXRpbmcgTm90ZXMg?= =?UTF-8?B?bW9kaWZpZWQ=?= |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOS0xMiBvQklY?= =?UTF-8?B?IG1lZXRpbmcgbWludXRlcyBtb2RpZmll?= =?UTF-8?B?ZA==?= |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOS0wNV9vYml4?= =?UTF-8?B?TWludXRlcy50eHQgbW9kaWZpZWQ=?= |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wNi0yNy1vYml4?= =?UTF-8?B?LW1pbnV0ZXMudHh0IG1vZGlmaWVk?= |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOS0xOSBvQklY?= =?UTF-8?B?IG1lZXRpbmcgbWludXRlcyB1cGxvYWRl?= =?UTF-8?B?ZA==?= |
1 |
2013-09-19 |
| [OASIS Issue Tracker] Commented: (OBIX-31) General: Consider a table of tables, and a table of examples following the table of contents. Many of the bulleted lists in this specification should be re-cast as tables. |
2 |
2013-09-24 |
| Figure 4-1 needs an update |
6 |
2013-09-24 |
| WebSocket Binding Discussion |
2 |
2013-09-26 |
| =?UTF-8?B?R3JvdXBzIC0gT0JJWC12MS4xLVdEMTQg?= =?UTF-8?B?dXBsb2FkZWQ=?= |
1 |
2013-09-26 |
| RE: [obix] Groups - OBIX-v1.1-WD14 uploaded |
3 |
2013-09-26 |
| Suggested convention for uploading obix working drafts |
1 |
2013-09-26 |
| [OASIS Issue Tracker] Commented: (OBIX-46) Line 1692 - Format values |
2 |
2013-09-26 |
| [OASIS Issue Tracker] Updated: (OBIX-10) Section 1 - Use four design points to introduce and link concepts throughout document |
1 |
2013-09-26 |
| OBIX-22 |
1 |
2013-09-26 |
| [OASIS Issue Tracker] Commented: (OBIX-22) Section 4, Figure 1, Line 269 - It may be useful to include the chapter number for each object type in the Figure 1 for easy reference lookup. |
1 |
2013-09-26 |
| [OASIS Issue Tracker] Commented: (OBIX-34) Section 3 - Simple editorial comments |
1 |
2013-09-26 |
| REST vs. CRUD in 1.1 spec |
2 |
2013-09-26 |
| [OASIS Issue Tracker] Commented: (OBIX-56) Editorial: Tables and Figures need to be identified, have separate tables of... in the front matter |
1 |
2013-09-27 |
| [OASIS Issue Tracker] Commented: (OBIX-36) Detailed discussion of REST |
1 |
2013-09-27 |
| [OASIS Issue Tracker] Commented: (OBIX-4) Chapter 11 "Watches" - add support for transient (or non-persistent) watches |
1 |
2013-09-27 |
