Re: [uf-discuss] Marking up radio stations

[Alex Mayrhofer]

On 25.07.2010 07:42, Corey Mwamba wrote:


Heart FM (Sussex)
102.4 MHz


However, such a URI scheme does not exist. It could be registered with
IANA, or you could bypass that requirement by using a specialised HTTP
prefix instead, a la.


side note:

A URI scheme for "geo" does now exists - it is standardized in RFC 5870, 
so the following example:



Short of specialised URIs to identify radio signals, the most
appropriate construct in hCard would probably be class="note". e.g.:


Heart FM (Sussex)

102.4 MHz
(Eastbourne)




... could also include a

  102.4 MHz
 (Eastbourne)
 

(Disclaimer: I'm one of the authors of the "geo" URI scheme, so my view 
might be biased ;)


Alex
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] Marking up radio stations

[Corey Mwamba]

Hello,

I suffered from span-itis in my last mock-up. And it might be easier to read 
with some spacing. Here it is corrected.


   Morning
   9:00+08
   12:00+08
   
   SW: 
   9660, 
   15230, 
   15240, 
   21725
   



http://www.coreymwamba.co.uk
http://trio.coreymwamba.co.uk/

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] Marking up radio stations

[Corey Mwamba]

Hello again,

I had not realised that Andy Mabbett didn't post a reply here - so here's a 
reference to his blog post on this:

http://pigsonthewing.wordpress.com/2010/07/24/measurement-microformat-for-radio-station-frequencies

There's discussion in the comments. Having had some sleep, I'm feeling more 
that "frequency" should be able to act as either

1. a property, as proposed in the broadcast examples page:
http://microformats.org/wiki/broadcast-examples

OR

2. a sub-property of "adr".

Am I correct in thinking that this would be similar to how "tel" or "geo" 
work?

If this were to happen I think "frequency" should have additional 
sub-properties:
* band [I think this should be required] - FM, SW, LW, MW, et al.

It should be enough to just write 


Rádio Nacional do Alto Solimões


Amazonas
Brazil


FM: 96.1


AM: 670 



But as quite a few radio stations are located over a range of frequencies, 
you'd need 

* low - the lowest frequency at which the station can be heard
* high - the highest frequency at which the station can be heard

This is from my gigs page for Radio 3 and shows the range:



http://www.bbc.co.uk/radio3/jazzon3"; class="url">BBC Radio 3


90.2 - 92.6
FM: 


UK



and you could use value for discrete frequencies.


Heart Radio in Sussex

102.4  and 
103.5
FM

(Eastbourne)


If you wanted to or needed to refer to units [note that when using a radio, 
most people will not need the units as the reception range for each band is 
already set] then you could use hMeasure;


Rádio Nacional do Alto Solimões

Amazonas
Brazil


FM 

96.1
MHz



AM 

670
kHz 




But I feel this is easier to read and type:


Rádio Nacional do Alto Solimões

Amazonas
Brazil


FM: 96.1MHz


AM: 670kHz



Shortwave radio reception can be dependent on the time of day: should/can this 
be handled with hCalendar?

For example, looking at 

http://www.radioaustralia.net.au/waystolisten/australia.htm

The morning frequencies might be marked up as: 



Morning
9:00 
+08

12:00
+08


SW: 
9660, 
15230, 
15240, 
21725



Any thoughts?

C.


http://www.coreymwamba.co.uk
http://trio.coreymwamba.co.uk/

music = science + magic

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] Marking up radio stations

[Corey Mwamba]

> Interesting question. hCard is probably a good start:
>
>   
>   Heart FM (Sussex)
>   102.4 MHz
>   
>

That's what I thought too. That's what I'm doing at the moment. The frequency 
I see as a form of location. Except on the electromagnetic spectrum.


> Now, how to encode the frequency? It is an address of sorts, or at
> least a locator. Not the kind of address that is suitable for marking
> up with class="adr" though. If there were a URI scheme for radio wave
> frequencies this would be a little easier:
>
>   
>   Heart FM (Sussex)
> class="url" >102.4 MHz
>   
>
> Radio stations are very geography-specific. 50 miles away a completely
> different organisation could be broadcasting on the same frequency. So
> our hypothetical "radio:" URI scheme would probably need a geographic
> signifier to be attached:
>
>   
>   Heart FM (Sussex)
> class="url">102.4 MHz
>   
>
> However, such a URI scheme does not exist. It could be registered with
> IANA, or you could bypass that requirement by using a specialised HTTP
> prefix instead, a la .
>
> Short of specialised URIs to identify radio signals, the most
> appropriate construct in hCard would probably be class="note". e.g.:
>
>   
>   Heart FM (Sussex)
>   
>   102.4 MHz
>class="geo">(Eastbourne)
>   
>   

I read Andy's post and went looking for the hMeasure draft which looked 
promising - but then ran across 

http://microformats.org/wiki/broadcast-examples

which would define exactly what I need [and has the class name "frequency"]. 
However it is worth noting that some radio stations are not placed at one 
frequency, but a range: however the idea doesn't deal with that as it stands.

So, bearing in mind my bias towards frequency being a location [albeit a fuzzy 
one], I'm thinking on the lines of


BBC Radio 3
radio station

90  - 92
FM



I'm ignoring the Hertz units because:
1. As far as I can recall, no one has ever mentioned them while speaking; and
2. the band [FM/UKV, AM, SW, LW, MW] is more important for physically finding 
the station on a radio.

If you DID want to use the units [which from a scientific point of view would 
be correct] then this could be like this:


Heart FM (Sussex)
102.4
MHz

(Eastbourne)



I do agree that stations are very geography specific, though. But to my 
thinking, the geo block does not need to be inside the frequency class if the 
information is contained in a hCard [although it could be].

So for the Sussex Heart FM example, it'd look like this:


Heart FM (Sussex)
102.4FM

(Eastbourne)


Or more formally:


Heart Radio in Sussex

102.4  and 
103.5
FM
(Eastbourne)



What do you think?

C. 




http://www.coreymwamba.co.uk
http://trio.coreymwamba.co.uk/

music = science + magic



___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] Marking up radio stations

[Toby Inkster]

On Sat, 24 Jul 2010 05:04:50 +0100
Corey Mwamba  wrote:

> I was wondering if anyone had any suggestions as to how to mark up a
> radio station using microformats, especially in relation to the
> frequencies - which I see as a type of address! Any thoughts?

Interesting question. hCard is probably a good start:


Heart FM (Sussex)
102.4 MHz


Now, how to encode the frequency? It is an address of sorts, or at
least a locator. Not the kind of address that is suitable for marking
up with class="adr" though. If there were a URI scheme for radio wave
frequencies this would be a little easier:


Heart FM (Sussex)
102.4 MHz


Radio stations are very geography-specific. 50 miles away a completely
different organisation could be broadcasting on the same frequency. So
our hypothetical "radio:" URI scheme would probably need a geographic
signifier to be attached:


Heart FM (Sussex)
102.4 MHz


However, such a URI scheme does not exist. It could be registered with
IANA, or you could bypass that requirement by using a specialised HTTP
prefix instead, a la .

Short of specialised URIs to identify radio signals, the most
appropriate construct in hCard would probably be class="note". e.g.:


Heart FM (Sussex)

102.4 MHz
(Eastbourne)



-- 
Toby A Inkster




___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss