| 00000 |
Groups - 2013-07-25_obix-minutes.txt modified |
Chris Bogen
|
2013-08-01 15:19 |
| 00001 |
Groups - 7/18/2013 oBIX Meeting Notes modified |
Chris Bogen
|
2013-08-01 15:19 |
| 00002 |
Groups - 2013-08-01 oBIX Meeting Notes uploaded |
Chris Bogen
|
2013-08-01 16:08 |
| 00003 |
FW: FW: Transfer of OBIX.ORG |
Toby Considine
|
2013-08-01 16:11 |
| 00004 |
Re: FW: FW: Transfer of OBIX.ORG |
Chet Ensign
|
2013-08-01 16:15 |
| 00005 |
oBIX Web Site |
Toby Considine
|
2013-08-03 14:49 |
| 00006 |
Groups - OBIX-WebSocket-v1.0-wd01.doc uploaded |
Matthias Hub
|
2013-08-05 20:29 |
| 00007 |
RE: [obix] Groups - OBIX-WebSocket-v1.0-wd01.doc uploaded |
Considine, Toby
|
2013-08-05 22:06 |
| 00008 |
Starter Document for Bindings for oBIX: Web Socket Bindings Version 1.0 |
Paul Knight
|
2013-08-07 22:33 |
| 00009 |
Groups - OBIX-WebSocket-v1.0-wd01.doc uploaded |
Toby Considine
|
2013-08-08 13:30 |
| 00010 |
Groups - obix-websocket-v1.0-wd02.doc uploaded |
Toby Considine
|
2013-08-08 13:32 |
| 00011 |
Groups - obix-websocket-v1.0-wd02.pdf uploaded |
Toby Considine
|
2013-08-08 13:33 |
| 00012 |
Groups - 2013-08-08 oBIX Workshop Meeting Notes uploaded |
Chris Bogen
|
2013-08-08 18:11 |
| 00013 |
Groups - Notes to options on Schemas.docx uploaded |
Toby Considine
|
2013-08-10 19:56 |
| 00014 |
Comment on PR01 Schemas: oBIX Schemas and backward incompatibilty |
Toby Considine
|
2013-08-10 19:57 |
| 00015 |
Obix 8/22 Liaisons and Alliances |
Toby Considine
|
2013-08-14 17:25 |
| 00016 |
Groups - obix-websocket-v1.0-wd03.pdf uploaded |
Matthias Hub
|
2013-08-14 17:57 |
| 00017 |
Re: Obix 8/22 Liaisons and Alliances |
Jamie Clark
|
2013-08-14 20:13 |
| 00018 |
[OASIS Issue Tracker] Created: (OBIX-1) UML diagram and text needs clarification line 269 |
OASIS Issues Tracker
|
2013-08-15 15:02 |
| 00019 |
[OASIS Issue Tracker] Created: (OBIX-2) Reference WS-Calendar for use of TZID in XML Alternately, reference XCAL (RFC 6321) |
OASIS Issues Tracker
|
2013-08-15 15:29 |
| 00020 |
[OASIS Issue Tracker] Updated: (OBIX-2) Reference WS-Calendar for use of TZID in XML Alternately, reference XCAL (RFC 6321) |
OASIS Issues Tracker
|
2013-08-15 15:34 |
| 00021 |
[OASIS Issue Tracker] Created: (OBIX-3) Consider DFDL issues in JSON Encoding |
OASIS Issues Tracker
|
2013-08-15 15:42 |
| 00022 |
Suggested field values for new Jira tracking items |
William Cox
|
2013-08-15 16:13 |
| 00023 |
Curse the day job |
Considine, Toby
|
2013-08-22 15:52 |
| 00024 |
[OASIS Issue Tracker] Created: (OBIX-4) Chapter 11 "Watches" - add support for transient (or non-persistent) watches |
OASIS Issues Tracker
|
2013-08-24 19:24 |
| 00025 |
[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 |
OASIS Issues Tracker
|
2013-08-24 19:28 |
| 00026 |
[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) |
OASIS Issues Tracker
|
2013-08-24 19:30 |
| 00027 |
[OASIS Issue Tracker] Created: (OBIX-7) Fix the JSON examples, especially the quotes and comma after "tag" in the second and third line |
OASIS Issues Tracker
|
2013-08-24 19:32 |
| 00028 |
[OASIS Issue Tracker] Updated: (OBIX-7) Fix the JSON examples, especially the quotes and comma after "tag" in the second and third line |
OASIS Issues Tracker
|
2013-08-24 19:38 |
| 00029 |
Re: [obix] Groups - obix-websocket-v1.0-wd03.pdf uploaded |
Markus Jung
|
2013-08-29 07:08 |
| 00030 |
RE: [obix] Groups - obix-websocket-v1.0-wd03.pdf uploaded |
Gemmill, Craig
|
2013-08-29 13:02 |
| 00031 |
Meeting today |
Toby Considine
|
2013-08-29 13:31 |
| 00032 |
Groups - oBIX Minutes 201300829 draft.txt uploaded |
Toby Considine
|
2013-08-29 17:39 |
| 00033 |
RE: [obix] Groups - obix-websocket-v1.0-wd03.pdf uploaded |
Gemmill, Craig
|
2013-08-30 11:49 |
| 00034 |
Dynamic Configuration of new Devices |
Considine, Toby
|
2013-08-30 16:54 |
| 00035 |
[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 |
OASIS Issues Tracker
|
2013-08-30 23:20 |
| 00036 |
[OASIS Issue Tracker] Created: (OBIX-9) Section 1, Line 15 - ";" should be a period "." |
OASIS Issues Tracker
|
2013-08-30 23:20 |
| 00037 |
[OASIS Issue Tracker] Updated: (OBIX-8) Section 1, Line 9 - "Design Concerns" should appear on a new line. |
OASIS Issues Tracker
|
2013-08-30 23:22 |
| 00038 |
[OASIS Issue Tracker] Created: (OBIX-10) Section 1 - Use four design points to introduce and link concepts throughout document |
OASIS Issues Tracker
|
2013-08-30 23:24 |
| 00039 |
[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) |
OASIS Issues Tracker
|
2013-08-30 23:28 |
| 00040 |
[OASIS Issue Tracker] Created: (OBIX-12) Section 2, Lines 114-115: "document" used to refer to multiple types of documents, needs clarification |
OASIS Issues Tracker
|
2013-08-30 23:30 |
| 00041 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:32 |
| 00042 |
[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." |
OASIS Issues Tracker
|
2013-08-30 23:34 |
| 00043 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:34 |
| 00044 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:36 |
| 00045 |
[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." |
OASIS Issues Tracker
|
2013-08-30 23:36 |
| 00046 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:36 |
| 00047 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:40 |
| 00048 |
[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? |
OASIS Issues Tracker
|
2013-08-30 23:40 |
| 00049 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:42 |
| 00050 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:42 |
| 00051 |
[OASIS Issue Tracker] Created: (OBIX-24) Section 4, Figure 1, Line 269 - What does "range: anyURI" mean for obix::bool? |
OASIS Issues Tracker
|
2013-08-30 23:44 |
| 00052 |
[OASIS Issue Tracker] Created: (OBIX-23) Section 4, Figure 1, Line 269 - What does "max: integer" and "min: integer" mean for obix::str? |
OASIS Issues Tracker
|
2013-08-30 23:44 |
| 00053 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:46 |
| 00054 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:46 |
| 00055 |
[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 |
OASIS Issues Tracker
|
2013-08-30 23:48 |
| 00056 |
[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. |
OASIS Issues Tracker
|
2013-08-30 23:50 |
