| Need a Meeting Host again this week - and Call for Agenda |
6 |
2014-02-05 |
| RE: [obix] Need a Meeting Host again this week - and Call for Agenda (UNCLASSIFIED) |
1 |
2014-02-06 |
| Get your Comments in |
1 |
2014-02-15 |
| [OASIS Issue Tracker] Commented: (OBIX-71) Table 4-2 - Unacked Alarm Confusion |
1 |
2014-02-18 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxNC0wMi0yMC1vYml4?= =?UTF-8?B?TWludXRlcy50eHQgdXBsb2FkZWQ=?= |
1 |
2014-02-20 |
| Missed out today (UNCLASSIFIED) |
1 |
2014-02-20 |
| [OASIS Issue Tracker] Created: (OBIX-87) Mix of should and SHOULD |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-88) Conformance clause inadequate in SOAP binding |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-89) conformance clause inadequate in REST binding |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-90) mix of SHALL and MUST keywords |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-91) COnformance clause for Encodings is inadequate |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-92) SHOULD statements in conformance clause belong to specification body |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-95) conformance clause repeats normative statement |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-93) Normative contract text not referred in conformance clause |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-94) Narrative style not appropriate for a standard |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-97) underspecified and/or under-referenced Negotiation mechanisms in conformance clause |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-96) imprecise reference from conformance clause |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-100) Confusing organization |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-99) Response to invalid XML? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-98) Support for Encodings is optional in specification narrative, but seems always requried for Servers |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-101) Normative vs. non-normative text |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-102) Normative vs. non-normative text? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-103) Examples as normative? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-104) Improper outlining |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-106) Table of Contents display issue |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-105) Improper outlining |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-107) Hanging paragraphs (4 cases) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-110) Hanging paragraphs (9) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-108) Hanging paragraphs (2 cases) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-109) Hanging paragraphs (4 cases) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-112) Support for Bindings is optional in specification narrative, but seems always requried for Servers. |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-113) detailed requirements ishould be in specification body instead of Conformance clause |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-111) Hanging paragraphs (33 cases) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-114) Lobby Conformance Clause undefined |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-115) Normative general considerations belong outside the Conformance section |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-116) OBIX implementation(s) not well defined |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-117) Missing References - RFC 4346/2246 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-120) 1.2 Normative References RFC6455 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-118) 2.2 Requests - vague references |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-119) 1.3 Non-Normative References - empty |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-122) WSDL schema error - cannot resolve obix:obj |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-121) 1.2 Normative References RFC3986 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-123) WSDL schema error |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-124) 3. Conformance - null and void |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-126) 1.2 Normative References - SOAP not cited |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-127) 1.3 Normative References - delete its empty |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-128) 1.2 Normative References |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-125) 3. Conformance - violates TC process |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-131) 1.2 Normative References COAP |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-129) 1.3 Non-Normative References CoAP-OBSERVE |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-130) 1.2 Normative References OBIX Encodings |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-134) 1.2 Normative References OBIX 1.1 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-135) Section headers inconsistent |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-132) 1.2 Normative References RFC2246 and RFC4346 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-133) 1.2 Normative References - RFC2618 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-138) 5.2 Schema-informed EXI |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-137) 4.1.4 Other types and facets: above, below, following |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-136) Examples are unnumbered |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-140) Encoding - Overloading terminology |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-139) 5.2 Non-schema-informed EXI |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-142) 3.3.7 Time Encodings |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-144) 3.3.2 Int Encodings Unknown abbreviations |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-141) 6 Conformance |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-143) 3.3.4 Str Encodings |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-147) 2.2 XML Syntax |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-146) 2. XML Encoding - redundant |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-145) 3.3 Value Encodings |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-148) 2.1 Design Philosophy |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-149) 1.3 Non-Normative References EXI BP |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-152) 1.2 Normative References RFC4627 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-151) 1.2 Normative References - RFC768 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-153) 1.2 Normative References EXI |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-150) 1.3 Non-Normative References EXI MR |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-154) 6.3 URI Normalization |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-156) 3.3 URIs -Normative? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-157) Confusing normative and non-normative text, ending in ambiguity |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-155) 6.2 Href |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-159) keywords? required and should |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-158) We 9 times and we 60 times? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-160) 17. Conformance - Interaction with SHOULD and MAY following implementations |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-161) 6.2 Href, 6.3 URI Normalization, 6.4 Fragment URIs |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-166) 4.1.14 of - repetition |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-163) Examples - unlabeled |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-165) 1.6 Editing Conventions |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-164) 1.6 Editing Conventions - examples |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-162) 17 Conformance |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-169) 4.1 obj - derivative? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-167) 4.1.1 Null |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-170) Camel Case in XML? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-168) 4.1 obj - cross-references |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-171) 1.5 Naming Conventions - Lower Camel Case? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-173) Non-Normative References - XML-ns |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-174) 1.3 Non-Normative References - UML |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-175) Non-Normative References REST |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-172) 1.4 Namespace |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-181) Normative References - RFC 2246 - Superseded RFC |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-178) 1.2 Normative References - XLINK |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-177) Normative References 1.2 - XPointer |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-180) 1.2 Normative References - RFC 3986 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-179) 1.2 Normative References - SI Units - not a NIST reference |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-176) 1.2 Normative References XML Schema |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-185) Redirects (7) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-182) 1.2 Normative References - superseded reference PNG |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-184) 2.3 Security - Missing Normative References (2), superseded normative references |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-183) 1.2 Normative References - PNG |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-187) Redirects (7) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-188) Redirects (7) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-189) Redirects (7) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-186) Broken Fragment (2) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-191) 404 link (1) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-190) Redirects (8) |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-192) CamelCase reference Lines 43-44 and other locations |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-193) Table 1-3, section 1.9, 133-134 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-196) 3.6 There is a lot of We Want here. |
1 |
2014-02-21 |
| =?utf-8?q?=5BOASIS_Issue_Tracker=5D_Created=3A_=28OBIX-194=29__S?= =?utf-8?q?everal_areas_of_this_specification_are_overly_conversational?= =?utf-8?q?=E2=80=94particularly_topic_sentences=2E?= |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-195) 276:279: This is an important transition and it is muddled |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-197) Section 4: 296: The first sentence cannot decide whether it is a specification or not. |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-198) Multiple locations, the use of the word "Concept" in this specification is nearly always in muddled expressions of intent |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-200) Line 642 uses a recursive definition of "batch" |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-199) Section 5.1: Should there be a general discussion of securing the lobby? |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-201) Consider whether each use of "Vendors" should be replaced by "implementers", "systems" or similar words as appropriate. |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-203) 7.6.2 Lines 1009-1010. Mixins should either be more or less defined. |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-202) Line 721-722: "it is recommended that servers SHOULD protect" is duplicative. |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-204) General Comment: The usage WebSocket is always preferred to WebSockets. Fix wherever it is found. |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-207) 16 Security: 2270-2273 |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-205) 14.2.5 Compact Histories. Proper handling of missing time intervals is more implicit than explicit. |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-208) Non-Standard Formatting |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-206) 2177-2178. Language for PointAlarm definition is muddy |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-210) Line 464: suggest "according to" be changed to "in conformance with" |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-209) Document Consistency |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Created: (OBIX-211) Conformance |
1 |
2014-02-21 |
| [OASIS Issue Tracker] Updated: (OBIX-88) Conformance clause inadequate in SOAP binding |
1 |
2014-02-23 |
| [OASIS Issue Tracker] Updated: (OBIX-89) conformance clause inadequate in REST binding |
1 |
2014-02-23 |
| Jira and Assignments |
1 |
2014-02-23 |
| =?UTF-8?B?R3JvdXBzIC0gMjAxNC0wMi0yNy1vYml4?= =?UTF-8?B?TWludXRlcy50eHQgdXBsb2FkZWQ=?= |
1 |
2014-02-27 |
