Re: [Linking-open-data] watchdog.net and LOD best practices

Michael Smethurst wrote:
> Hi Aaron / everyone
>
> Apologies for the dumb question but i guess from your "enter zip code" homepage we're talking US politics here?!?
>
> Since this is connected to politics of the UK kind the rest of this will probably be spam:
>
> As many of you know we're going to be making BBC programmes available as linked open (meta) data - sorry we don't have rights for programmes themselves, except....
>
> ...we do have full rights for at least some BBC Parliament content. For some reason this disappears from iPlayer and hence /programmes after 7 days. We're currently working our way through the BBC hierarchy to work out why. It's a tiring journey but with luck on our side we'll be able to make some programmes permanently available online at persistent urls with rdf available.
>
> So i guess my question is: is there anyone out there that would be interested in a semantic erm mashup from a UK politics perspective? Maybe someone from http://www.theyworkforyou.com/ with an rdf bent? or maybe even someone from parliament?
>
> sorry to take up your time... worth a punt perhaps
>   

Micheal,

Sure!!

Ironically, I've just been testing our Sponger Cartridge for 
<http://www.theyworkforyou.com/>  :-) 

I''ll post a browser demo link and a URI once I am happy with the Cartridge.


Kingsley
>
>
> -----Original Message-----
> From: linking-open-data-bounces@simile.mit.edu on behalf of Aaron Swartz
> Sent: Tue 4/15/2008 5:42 PM
> To: Linking Open Data
> Subject: [Linking-open-data] watchdog.net and LOD best practices
>  
> Hi there,
>
> I'm launching a new site, watchdog.net, to bring together various
> sorts of political data. As part of this, we want to make it very easy
> for developers and LOD people to take advantage of the data.
>
> What we're currently doing is described at:
>
> http://watchdog.net/about/api
>
> Basically, we support URL and content negotiation to return N3,
> RDF/XML, or JSON on each page.
>
> Open questions: Are there better ways to expose this? What do we do
> for our query APIs?
>
> For example, we have an ability to take a zip code and return back a
> list of matching districts. What's the best way to expose this as RDF.
> Should we just say:
>
> [ :zipcode "s98dfu89sdif" ] :districts ( ) .
>
> ?
>
> Anyway, take a look and let me know what you think.
> _______________________________________________
> Linking-open-data mailing list
> Linking-open-data@simile.mit.edu
> http://simile.mit.edu/mailman/listinfo/linking-open-data
>
>
> http://www.bbc.co.uk/
> This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> 					
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linking-open-data mailing list
> Linking-open-data@simile.mit.edu
> http://simile.mit.edu/mailman/listinfo/linking-open-data
>   


-- 


Regards,

Kingsley Idehen	      Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO 
OpenLink Software     Web: http://www.openlinksw.com

Received on Tuesday, 15 April 2008 18:21:18 UTC