The RadioDNS suite of applications are moving away from having "brands" (RadioTAG, RadioEPG) to having descriptive names to fit in more closely with ETSI specification-style titles. I'd like to propose retitling the specification in a similar fashion, such as "Simple interaction methodology for hybrid radio".
As an extension we could begin retiring "tagging" as a term as it has been a contentious issue throughout the project. This impacts things like the /tag endpoint; we could move to describing 'tags' as 'events' and so rebrand the endpoint /event (e.g. REST'fully
POST'ing an event to /event).
The RadioDNS suite of applications are moving away from having "brands" (RadioTAG, RadioEPG) to having descriptive names to fit in more closely with ETSI specification-style titles. I'd like to propose retitling the specification in a similar fashion, such as "Simple interaction methodology for hybrid radio".
As an extension we could begin retiring "tagging" as a term as it has been a contentious issue throughout the project. This impacts things like the
/tagendpoint; we could move to describing 'tags' as 'events' and so rebrand the endpoint/event(e.g. REST'fully POST'ing an event to/event).