- From: Gregg Kellogg <gregg@kellogg-assoc.com>
- Date: Thu, 5 Apr 2012 18:57:18 -0400
- To: Gregg Kellogg <gregg@kellogg-assoc.com>
- CC: Niklas Lindström <lindstream@gmail.com>, Markus Lanthaler <markus.lanthaler@gmx.net>, Linked JSON <public-linked-json@w3.org>
Then again, they need to relate other information based on language, for example a video or audio clip, so I think they may need to create per-language resources to contain text as well as other such resources. It might be modeled better using frbr:Manifestation. Gregg On Apr 5, 2012, at 3:21 PM, Gregg Kellogg wrote: > This actually might make sense. I suggested the following markup, but find it doesn't really work: > > { > "@id" : "q7", > "titles" : { > "en" : { > "@context": {"@language" : "en"}, > "value" : "Georgia_(country)" > }, > "de" : { > "@context": {"@language" : "de"}, > "value" : "Georgien" > } > } > } > > It seems that our processing rules don't provide for @context within a value object. > > If we had something like you suggest, with @container: @langmap, this would expand to the following: > > { > "@id": "q7", > "titles": [ > {"@value": "Georgia_(country)", "@language": "en"}, > {"@value": "Georgien", "@language": "de"} > ] > } > > It's important for them to have a simple selector path, such as titles.en.value. > > There's quite a bit of interest in using JSON-LD, if it can work. This would allow them to use a single representation, rather than one for RDF and another for JSON. Also, it seems that named graphs may be an important use case for them. > > It might also be interesting to think if framing could come in handy, if there was a way to frame the data for "@language": "en", say, so that a developer could get the representation they want to work with. > > Gregg > > On Apr 5, 2012, at 10:51 AM, Niklas Lindström wrote: > >> Great! I also stumbled across it, and noted the use of language as >> keys. We've discussed that previously, with possible support by using >> a special "@container": "@langmap" directive for a property. In case >> they're convinced that this form is valuable for consumers, I think we >> should revisit it. >> >> In any case, it'll be interesting and great to see their usage align >> and hopefully adopt JSON-LD! >> >> Best regards, >> Niklas >> >> >> On Thu, Apr 5, 2012 at 4:41 PM, Gregg Kellogg <gregg@kellogg-assoc.com> wrote: >>> I'll do that. As it happens, I'm talking with Wikia this month anyway, so they're somewhat related. >>> >>> Gregg >>> >>> On Apr 5, 2012, at 7:31 AM, Markus Lanthaler wrote: >>> >>>> Hey guys, >>>> >>>> I just stumbled across this: >>>> http://meta.wikimedia.org/wiki/Wikidata/Data_model_in_JSON >>>> >>>> Looks quite familiar :-) Unfortunately I currently don't have the time to >>>> follow that up and introduce them JSON-LD, maybe someone of you has a bit of >>>> time to do that. >>>> >>>> >>>> Cheers, >>>> Markus >>>> >>>> >>>> -- >>>> Markus Lanthaler >>>> @markuslanthaler >>>> >>>> >>>> >>>> >>>> >>> >>> > >
Received on Thursday, 5 April 2012 22:57:55 UTC