| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wNy0yNV9vYml4?= =?UTF-8?B?LW1pbnV0ZXMudHh0IG1vZGlmaWVk?= |
1 |
2013-08-01 |
| =?UTF-8?B?R3JvdXBzIC0gNy8xOC8yMDEzIG9CSVgg?= =?UTF-8?B?TWVldGluZyBOb3RlcyBtb2RpZmllZA==?= |
1 |
2013-08-01 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOC0wMSBvQklY?= =?UTF-8?B?IE1lZXRpbmcgTm90ZXMgdXBsb2FkZWQ=?= |
1 |
2013-08-01 |
| FW: FW: Transfer of OBIX.ORG |
2 |
2013-08-01 |
| oBIX Web Site |
1 |
2013-08-03 |
| =?UTF-8?B?R3JvdXBzIC0gT0JJWC1XZWJTb2NrZXQt?= =?UTF-8?B?djEuMC13ZDAxLmRvYyB1cGxvYWRlZA==?= |
2 |
2013-08-05 |
| RE: [obix] Groups - OBIX-WebSocket-v1.0-wd01.doc uploaded |
1 |
2013-08-05 |
| Starter Document for Bindings for oBIX: Web Socket Bindings Version 1.0 |
1 |
2013-08-07 |
| =?UTF-8?B?R3JvdXBzIC0gb2JpeC13ZWJzb2NrZXQt?= =?UTF-8?B?djEuMC13ZDAyLmRvYyB1cGxvYWRlZA==?= |
1 |
2013-08-08 |
| =?UTF-8?B?R3JvdXBzIC0gb2JpeC13ZWJzb2NrZXQt?= =?UTF-8?B?djEuMC13ZDAyLnBkZiB1cGxvYWRlZA==?= |
1 |
2013-08-08 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxMy0wOC0wOCBvQklY?= =?UTF-8?B?IFdvcmtzaG9wIE1lZXRpbmcgTm90ZXMg?= =?UTF-8?B?dXBsb2FkZWQ=?= |
1 |
2013-08-08 |
| =?UTF-8?B?R3JvdXBzIC0gTm90ZXMgdG8gb3B0aW9u?= =?UTF-8?B?cyBvbiBTY2hlbWFzLmRvY3ggdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-08-10 |
| Comment on PR01 Schemas: oBIX Schemas and backward incompatibilty |
1 |
2013-08-10 |
| Obix 8/22 Liaisons and Alliances |
2 |
2013-08-14 |
| =?UTF-8?B?R3JvdXBzIC0gb2JpeC13ZWJzb2NrZXQt?= =?UTF-8?B?djEuMC13ZDAzLnBkZiB1cGxvYWRlZA==?= |
1 |
2013-08-14 |
| [OASIS Issue Tracker] Created: (OBIX-1) UML diagram and text needs clarification line 269 |
1 |
2013-08-15 |
| [OASIS Issue Tracker] Created: (OBIX-2) Reference WS-Calendar for use of TZID in XML Alternately, reference XCAL (RFC 6321) |
1 |
2013-08-15 |
| [OASIS Issue Tracker] Updated: (OBIX-2) Reference WS-Calendar for use of TZID in XML Alternately, reference XCAL (RFC 6321) |
1 |
2013-08-15 |
| [OASIS Issue Tracker] Created: (OBIX-3) Consider DFDL issues in JSON Encoding |
1 |
2013-08-15 |
| Suggested field values for new Jira tracking items |
1 |
2013-08-15 |
| Curse the day job |
1 |
2013-08-22 |
| [OASIS Issue Tracker] Created: (OBIX-4) Chapter 11 "Watches" - add support for transient (or non-persistent) watches |
1 |
2013-08-24 |
| [OASIS Issue Tracker] Created: (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-08-24 |
| [OASIS Issue Tracker] Created: (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-08-24 |
| [OASIS Issue Tracker] Created: (OBIX-7) Fix the JSON examples, especially the quotes and comma after "tag" in the second and third line |
1 |
2013-08-24 |
| [OASIS Issue Tracker] Updated: (OBIX-7) Fix the JSON examples, especially the quotes and comma after "tag" in the second and third line |
1 |
2013-08-24 |
| Re: [obix] Groups - obix-websocket-v1.0-wd03.pdf uploaded |
3 |
2013-08-29 |
| Meeting today |
1 |
2013-08-29 |
| =?UTF-8?B?R3JvdXBzIC0gb0JJWCBNaW51dGVzIDIw?= =?UTF-8?B?MTMwMDgyOSBkcmFmdC50eHQgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-08-29 |
| Dynamic Configuration of new Devices |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (OBIX-8) Section 1, Line 9 - I thought of walking round and round a space Utterly empty, utterly a source Where the decked chestnut tree had lost its place In our front hedge above the wallflowers. The white chips jumped and jumped and skited high. I heard the hat |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (OBIX-9) Section 1, Line 15 - ";" should be a period "." |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Updated: (OBIX-8) Section 1, Line 9 - "Design Concerns" should appear on a new line. |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (OBIX-10) Section 1 - Use four design points to introduce and link concepts throughout document |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (OBIX-12) Section 2, Lines 114-115: "document" used to refer to multiple types of documents, needs clarification |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (OBIX-18) Section 2, Lines 125-7 - The use of the words "we should" is somewhat vague about what device is doing the reporting. It is suggested that clarification be given. |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (OBIX-17) Section 2, Line 122 - It is suggested that an example be given at this point of what might be "more semantics than a simple scalar value." |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (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? |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (OBIX-24) Section 4, Figure 1, Line 269 - What does "range: anyURI" mean for obix::bool? |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (OBIX-23) Section 4, Figure 1, Line 269 - What does "max: integer" and "min: integer" mean for obix::str? |
1 |
2013-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [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-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
| [OASIS Issue Tracker] Created: (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-08-30 |
