Thanks.
That’s what the meeting notes said, but they were a little unclear at that point, and I wanted to be sure I was getting the documents started correctly.
tc
"If something is not worth doing, it`s not worth doing well " -- Peter Drucker
Toby Considine TC9, Inc OASIS TC Chair: oBIX & WS-Calendar OASIS TC Editor: EMIX, Energy Interoperation SGIP Smart Grid Architecture Committee | | Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.tcnine.com blog: http://www.NewDaedalus.com |
From: obix@lists.oasis-open.org [mailto:obix@lists.oasis-open.org] On Behalf Of Markus Jung
Sent: Friday, February 22, 2013 4:06 AM
To: obix@lists.oasis-open.org
Subject: Re: [obix] To clarify intent - Encodings
Hi,
CoAP is protocol binding, since it is a similar protocol like HTTP, with the main difference being based on UDP instead of TCP. Since a REST binding for CoAP is straightforward I would consider it wihin the planned REST protocol bindings document.
Regarding the message encodings, I would have a single document for all encodings. Currently, the encodings in the 1.1 WD06 document are XML (application/xml) and oBIX binary (application/x-obix-binary). Further encodings would be the _javascript_ Object Notation (application/json) and the standardized efficient XML interchange format (appplication/exi). For the oBIX binary encoding, the XML encoding and maybe the JSON encoding it is required to describe the mapping of oBIX documents expressed with the oBIX object model to the specific encoding, but for EXI it will be straightforward since it works on the XML encoding.
The current encoding sections have just 2 to 4 pages, so I would prefer having one document with maybe 20 pages instead of splitting it on several small documents.
Finally, at the end of such a document an overview should be included stating which encoding makes sense for which protocol binding. For the REST bindings all encodings can be used, but for the SOAP bindings only XML and maybe EXI make sense.
BR
Markus
Am 21.02.2013 23:07, schrieb Toby Considine:
Oh – a further clarification
Do we consider CoAP as an Encoding [of REST] or as a binding…
tc
"If something is not worth doing, it`s not worth doing well " -- Peter Drucker
Did we want one general purpose encodings document
"Encodings for OBIX v1.0"
OBIX-Encoding-v1.0
Or did we want several Encodings Documents
"Encodings for OBIX: EXI Encodings v1.0"
OBIX-EXI-v1.0
"Encodings for OBIX: FIE Encodings v1.0"
OBIX-FOO-v1.0
"Encodings for OBIX: FIE Encodings v1.0"
OBIX-FIE-v1.0
If we wanted several, what are they.
Thanks
tc
“It is the theory that decides what can be observed." -- Albert Einstein
--
Dipl.-Ing. Markus Jung
Projektassistent
mjung@auto.tuwien.ac.at
Tel. +43 1 58801-18322
Fax +43 1 58801-18391
Institut für Rechnergestützte Automation
Treitlstr. 1-3/4. Stock/E183-1
TU Wien