Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
RadioDNS and RadioEPG Specification releases: v1.0.0-DRAFT
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ben Poor  
View profile  
 More options Aug 11 2011, 7:12 am
From: Ben Poor <ben.p...@radiodns.org>
Date: Thu, 11 Aug 2011 12:12:23 +0100
Local: Thurs, Aug 11 2011 7:12 am
Subject: RadioDNS and RadioEPG Specification releases: v1.0.0-DRAFT
Dear All,

We are pleased to announce the release of draft specifications v1.0.0
for RadioDNS and RadioEPG.

This is a significant step forward for the RadioDNS project, as it
adds the functionality necessary to enable RadioDNS application
discovery from IP-based audio services.

Both are being released as a package as RadioEPG provides support for
the discovery process, as well as detailing methods for supporting
Service Following on devices, enabling Hybrid Radio behaviour.

These changes to the RadioDNS specification are key to the success of
the RadioDNS project as a whole and so I would strongly urge you to
give it close consideration. All changes are highlighted and comments
explaining the change are attached as PDF comments.

In particular, the following questions will need to be considered:

* Are the methods of transporting in in-band metadata compatible with
the way you currently stream audio?
* Is the use of the 'icy-url' HTTP response for transporting in-band
metadata for the Shoutcast protocol likely to cause issues for
particular encoders / client devices?
* What additional streaming protocols should be considered in this, or
future specifications?

It is vitally important that we all examine the implications these
changes would have, as well as whether they fully support our
ambitions.

The proposed documentation can be found at:
http://radiodns.org/documentation#proposed

Please reply to this mail with any feedback.

Kind Regards,

Ben Poor
ben.p...@radiodns.org


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »