[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [obix] RE: Press release of OBIX documents - WebSocket orthography
|
It's singular.
The RFC as cited in "AMQP WebSocket Binding" is [RFC6455] Fette, I., and Melinkov, A., “The WebSocket Protocol”, December 2011. RFC 6455, December 2011. http://tools.ietf.org/html/rfc6455.which uses "WebSocket" (one word, singular). In the MQTT document it says Which is correct per the RFC. Thanks! bill -- William Cox Email: wtcox@CoxSoftwareArchitects.com Web: http://www.CoxSoftwareArchitects.com +1 862 485 3696 mobile
Is the doc title "WebSocket" or "WebSockets"? I seem to recall a question by Matthias about this. -----Original Message----- From: obix@lists.oasis-open.org [mailto:obix@lists.oasis-open.org] On Behalf Of William Cox Sent: Thursday, November 13, 2014 11:17 AM To: obix@lists.oasis-open.org; Toby Considine Subject: [obix] RE: Press release of OBIX documents Resending due to mail glitch...I'd say rather "the relationship between Websockets and MQTT." Agree on the heating up, and I'd definitely mention the connection, which appears to me to be using Web sockets as a transport (http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_T oc398718127 in the OASIS Standard). I'd also mention AMQP has a relationship as well (the work is actually in the separate but overlapping membership AMQP-BINDMAP TC) - see the June 2014 CSPRD of the AMQP Web socket Binding at http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/csprd01/amqp-wsb -v1.0-csprd01.html . This is slightly more challenging IMO than the MQTT approach because the AMQP tunneling raises additional issues and isn't as straightforward as a transport layering. Thanks! bill On 11/13/14 10:57 AM, Considine, Toby wrote:I have the boilerplate I have been using for the last two PRs. We can still modify it if we work quickly...With how MQTT is heating up, we may wish to point out the attachment between WebSocket and MQTT. Specification Overview: OBIX v1.1 provides the core information model (expressed as an XDM) and interaction pattern for interactions with building control systems, or any control systems. The document specifies an object model used for machine-to-machine (M2M) communication which we name the Open Building Information eXchange (OBIX). It also describes the default XML encoding for OBIX. Encodings for OBIX: Common Encodings v1.0 specifies different encodings for OBIX objects adhering to the OBIX object model. OBIX provides the core information model and interaction pattern for communication with building control systems. Specific implementations of OBIX must choose how to encode OBIX Information. The core specification describes an XML encoding, which is used in all examples in that document. The document specifies common alternate encodings, including CoAP, EXI, and JSON. Bindings for OBIX: REST Bindings v1.0 specifies REST bindings for OBIX. The document describes the REST Binding, an interaction pattern that can be used in conjunction with XML, EXI, CoAP, and JSON encodings, as well as other encodings that may be specified elsewhere. Bindings for OBIX: SOAP Bindings v1.0 specifies SOAP protocol bindings for OBIX. The document describes the SOAP Binding and includes a WSDL artifact. Bindings for OBIX: WebSockets Bindings v1.0 specifies Web Socket protocol bindings for OBIX. The OBIX Binding for WebSockets was of particular interest to consumer electronics and smart televisions. "It is the theory that decides what can be observed." -- Albert Einstein Toby Considine Email: Toby.Considine@ unc.edu Phone: (919)962-9073 Information Technology Services University of North Carolina Chapel Hill, NC Chair, OASIS OBIX Technical Committee Chair, OASIS WS-Calendar Technical Committee Editor, OASIS EMIX, Energy Interoperation http://www.oasis-open.org http://www.NewDaedalus.com http://TheEnergyMashupLab.org -----Original Message----- From: Ludo Bertsch [mailto:ludob@horizontec.com] Sent: Thursday, November 13, 2014 10:26 AM To: Considine, Toby Subject: Press release of OBIX documents Toby, Do you have some wording for the release of the OBIX documents that we could use as a core to massage into a press release that we could send out through CABA? Cheers, Ludo -- Ludo Bertsch, P.Eng. Horizon Technologies www.horizontec.com ludob@horizontec.com (250) 592-1488 This email may contain confidential information and is directed at the recipient only and is not to be disclosed to anyone else without permission. If you have received this email in error, please inform us and delete this email and attachments. Please let us know if you no longer wish to receive emails from us. --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]