RadioVIS Specification V1.1.0 FINAL (hopefully)

24 views
Skip to first unread message

Ben Poor

unread,
Apr 10, 2012, 10:49:27 AM4/10/12
to radiovis-...@googlegroups.com
Dear All,

I'm glad to say I've had some good feedback from the last draft, which I've incorporated into a new document. Its only fair I circulate this first as there are one or two functional changes, although its on new functionality. The rest are mainly corrections:

* Have corrected references to FQDN and RadioVIS host and port to make them more distinct.
* Clarified restriction on ServiceIdentifier field to be maximum characters
* Clarified distinction between headers with a RadioVIS frame and HTTP headers
* Reversed time-direction of frames to be from older->newer. This made more sense with the restriction on number of frames and total response size.
* Corrected 4.5.1 where the trigger-time header was stated as being mandatory. This should have been optional. Whoops.
* Loosened up requirements on Stomp version to allow support for versions of Stomp later than 1.0, given the version negotiation in version 1.1.
* Clarified that a Stomp frame in its entirety be UTF-8, rather than just the message body

You can find this version of the specification here:


Since I've changed the meaning in some places I feel it only fair I post it here for your review. Please do check this over - I suspect many of you are getting draft spec fatigue by now, but I think we're nearly there...

I'm gonna say any feedback should be received by 09:00 GMT Friday 13th April. If you need more time then please say.

Ben


Ben Poor

unread,
Apr 13, 2012, 5:24:26 AM4/13/12
to radiovis-...@googlegroups.com
Hello All,

Last one from me to say that there has been no sustained objection to this specification and so this will be sent to the Steering Board for ratification.

This version of the specification has actually been in formation for longer than I can remember - must be over 2 years now - so its great to finally get it completed.

Once adopted, I'm looking forward to seeing takeup of the HTTP transport, and also larger slide sizings on devices, especially non-traditional radio devices.

I'll post the release version of the specification on the radiodns.org site soon and let you all know.

There are some things coming up that make the future of RadioVIS as a whole look really good - such as the 3D project (Hi Paolo), and also the Interactivity demos that were shown at the EBU in February (Hi Frontier, Hi Robin). Both of these innovations show that due to the open nature of our work, we allow people to take the base of the project and take it in a new and exciting direction. I'm looking forward to seeing more of this in the future, as well as more devices openly supporting RadioVIS.

Many thanks to all of you for participating,

Ben Poor
Reply all
Reply to author
Forward
0 new messages