- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Wed, 20 Feb 2013 17:20:48 +0100
- To: "'David Rogers'" <david.rogers@bbc.co.uk>
- Cc: <public-linked-json@w3.org>
Thanks a lot Dave! Please keep us posted. -- Markus Lanthaler @markuslanthaler > -----Original Message----- > From: David Rogers [mailto:david.rogers@bbc.co.uk] > Sent: Wednesday, February 20, 2013 5:18 PM > To: Markus Lanthaler > Cc: public-linked-json@w3.org > Subject: Re: Inverse properties in JSON-LD > > Here's a high-level description of the project: > > http://www.bbc.co.uk/blogs/internet/posts/Linked-Data-Connecting- > together-th > e-BBCs-Online-Content > > I'll be talking about the project at QCon London in a couple of weeks, > so > watch this space for some slides with more detail: > > http://qconlondon.com/london- > 2013/presentation/Introducing%20the%20BBC%27s%2 > 0Linked%20Data%20Platform%20and%20APIs > > Cheers, > > Dave > > > On 20/02/2013 16:14, "Markus Lanthaler" <markus.lanthaler@gmx.net> > wrote: > > >> We would need a predicable way of generating inverse property names, > so > >> presumably we could prefix properties with '^' to indicate inverse > for > >> our > >> APIs? And simply make a reference to this in the context. It would > >> therefore > >> no longer be micro-syntax, simply a convention in our APIs. > > > > Sure, there are no restrictions on term names. > > > > > >> We're building a set of APIs at the BBC which are powered by > CONSTRUCT > >> queries on our triple store. We want to provide this data in ways > that > >> are > >> more familiar to developers not so familiar with RDF, whilst not > losing > >> the > >> 'linked' aspect of the data. JSON-LD was the best fit. > > > > Great to hear. Does there exist a blog post or something similar > describing > > it? The reason why I'm asking is because I try to maintain a list of > early > > adopters of JSON-LD. > > > > > > Thanks, > > Markus > > > > > > > > -- > > Markus Lanthaler > > @markuslanthaler > > > > > 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. >
Received on Wednesday, 20 February 2013 16:21:21 UTC