"RadioDNS" and "the RadioDNS Project" - some useful definitions
James Cridland
Boštjan Jerko
I totally agree.
I've created a RadioVIS addition to radio scheduling program and wrongly
named the tech behind it as RadioDNS.
The only addition I have is (since I plan to add RadioEPG) when you use two
or more technologies from the RadioDNS spectrum you can say you are using
RadioDNS technologies.
Do you agree or should I name the technologies specifically?
Regards,
Boštjan
On Tuesday, October 4, 2011, James Cridland <ja...@radiodns.org> wrote:
> Hello,
> In the steering board last week, some board members noted
confusion about RadioDNS (the core specification), RadioDNS (the
project), and "those visuals from RadioDNS". We agreed to
make some ever so slight changes to lessen confusion in this area -
changes we'd already begun to unconsciously make anyway. I'm sharing
these with the dev list first, and would be grateful for any feedback
before we put this in our announce list.
> The RadioDNS ProjectThat's you and me! If you're working on
anything that needs RadioDNS to work, you're working within the
RadioDNS Project. The people at the end of feedback(at)radiodns.org
are the RadioDNS Project Office.
> RadioDNSThat's the spec! RadioDNS provides the link between
broadcast and IP. We sometimes call this "the core RadioDNS
spec" to be clearer.
> RadioVIS, RadioEPG, RadioTAGThese are the applications! They work
with RadioDNS, but don't need it. (The STOMP-based specification for
RadioVIS is in use in many IP-only smartphones, where RadioDNS isn't
required, for example.)
>
> So, it's not right to say "the PURE Sensia has pretty
pictures from RadioDNS in it": the RadioDNS project doesn't
control the images, we're not involved with their generation: and the
core RadioDNS spec is only used once, when the device is tuned in.
Better to say "the PURE Sensia has pretty pictures using
RadioVIS".
> Hopefully this'll help eradicate some confusion: and you'll see
that our Twitter feed and our website have both changed subtly to
reflect this. Shout if it's not clear (and when you've finished
shouting, be so kind as to write it down and contact me, since I can't
hear you from here.)
> -- James CridlandSecretary, RadioDNS Project
>
>
>
> --
> You received this message because you are subscribed to the
RadioDNS developers group. RadioDNS is at http://radiodns.org/
> To post to this group, send email to
> radiodns-...@googlegroups.com
> To unsubscribe from this group, send email to
> radiodns-develo...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/radiodns-developers?hl=en
James Cridland (RadioDNS)
I've created a RadioVIS addition to radio scheduling program and wrongly
named the tech behind it as RadioDNS.
The only addition I have is (since I plan to add RadioEPG) when you use two
or more technologies from the RadioDNS spectrum you can say you are using
RadioDNS technologies.
Do you agree or should I name the technologies specifically?
James Cridland, Secretary, RadioDNS Project http://radiodns.org/
Where new platforms and radio collide: http://james.cridland.net/blog/
Boštjan Jerko
Regarding my RadioVIS solution I will be implementing it at one of Slovene radio broadcasters in the weeks to come and also present it at conference by Sourcefabric or better at their workshop and I'll probably open source core of the solution.
I just need to work on the licensing since I want to be able to use derivative work for commercial solution without need to provide the source code.
I'll check the links you provided and see if it's already time for me to be mentioned there. I am sure at the end of October I'll have something to show and I'll send all the data.
Thanks,
Boštjan
On Tuesday, October 4, 2011, James Cridland (RadioDNS) <james.c...@radiodns.org> wrote:
> 2011/10/4 Boštjan Jerko <bos...@japina.eu>
>>
>> I've created a RadioVIS addition to radio scheduling program and wrongly
>> named the tech behind it as RadioDNS.
>> The only addition I have is (since I plan to add RadioEPG) when you use two
>> or more technologies from the RadioDNS spectrum you can say you are using
>> RadioDNS technologies.
>> Do you agree or should I name the technologies specifically?
>
> Interesting one, Boštjan - my own personal view would be "RadioDNS Project applications" (since as I understand it, a software product can support RadioVIS and RadioEPG but not specifically the core RadioDNS spec).
> That said, you might want to specifically mention both applications, since that's probably better marketing for you.
> Thanks for your understanding - one of the nice effects of the rapid growth of RadioDNS means we need to be a little more careful of the way we talk about ourselves.
> A reminder that if your software is in use by a broadcaster, you can appear in http://radiodns.org/software-solution-providers/ (if you offer customer service), or http://radiodns.org/software/ (if it's an open-source tool).
> --
> James Cridland, Secretary, RadioDNS Project http://radiodns.org/
> Twitter: @jamescridland | Web: http://james.cridland.net/
> Where new platforms and radio collide: http://james.cridland.net/blog/
>
> You received this message because you are subscribed to the RadioDNS developers group. RadioDNS is at http://radiodns.org/
> To unsubscribe from this group, send email to
> For more options, visit this group at