Re: Schema.org site updates: Added RDFa and JSON-LD incoming properties

I should probably have realized that, while the general suggestion of
linking terms to the vocabulary, discovery etc. was also on the table, your
suggestion Gregg, for rel="describedby", was for alleviating the now
missing structured data within the term pages, right? For that, it
certainly seems like a good idea.

Cheers,
Niklas


On Sat, Apr 5, 2014 at 11:15 AM, Niklas Lindström <lindstream@gmail.com>wrote:

>
> On Sat, Apr 5, 2014 at 11:04 AM, Niklas Lindström <lindstream@gmail.com>wrote:
>
>> Hi,
>>
>> First off, I'd like to join in complimenting the addition of this to
>> schema.org. Great stuff!
>>
>> On Sat, Apr 5, 2014 at 2:48 AM, Gregg Kellogg <gregg@greggkellogg.net>wrote:
>>
>>> On Apr 4, 2014, at 2:48 PM, Dan Brickley <danbri@google.com> wrote:
>>>
>>> > On 4 April 2014 22:05, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>>> >> On 4/4/14 8:49 AM, Dan Brickley wrote:
>>> >>>
>>> >>> The bad news is only temporary: There are a few glitches that we're
>>> >>> working to fix asap.
>>> >>
>>> >> Dan,
>>> >>
>>> >> Please look at [1]. I don't know if this is a glitch or intentional.
>>> >
>>> > Thanks. I think you're the first person to have shown interest in the
>>> > RDFa+RDFS that we used to have in per-term pages. It's on the list of
>>> > things to add back in, but there are some other things that need to
>>> > get done first.
>>> >
>>> > Note that the entire schema is available at
>>> > http://schema.org/docs/datamodel.html ->
>>> > http://schema.org/docs/schema_org_rdfa.html
>>> >
>>> > Do you have some particular use in mind for in-page schema
>>> > declarations, or it's just appealing for general Linked Data usage?
>>>
>>> For me, I would think that each term might reference the vocabulary
>>> document somehow (perhaps rel=describedBy?). It would also be useful if
>>> going to http://schema.org/ would somehow allow discovery of the
>>> vocabulary.
>>
>>
>> I agree, that would be nice. I'm sure rdfs:isDefinedBy [1] is the right
>> property for that. :)
>>
>>
>>> Perhaps when you get a JSON-LD context there (through
>>> content-negotiation), it could also include the JSON-LD serialization of
>>> the RDFS definition? Alternatively, link to it through a suitable
>>> relationship.
>>>
>>
>> That is a good idea. I think an rdfs:seeAlso [2] link from the context
>> document to a full serialization would be enough. So a nice start for <
>> http://schema.org/index.jsonld> could be:
>>
>>     {
>>       "@context": {"@vocab": "http://schema.org/"},
>>       "http://www.w3.org/2000/01/rdf-schema#seeAlso": "
>> http://schema.org/docs/schema_org.jsonld"
>>     }
>>
>
> Or more properly:
>
>     {
>       "@context": {"@vocab": "http://schema.org/"},
>       "http://www.w3.org/2000/01/rdf-schema#seeAlso": {"@id": "
> http://schema.org/docs/schema_org.jsonld"}
>     }
>
> :)
>
>
>> Cheers,
>> Niklas
>>
>> [1]: http://www.w3.org/TR/rdf-schema/#ch_isdefinedby
>>  [2]: http://www.w3.org/TR/rdf-schema/#ch_seealso
>>
>>
>> The Structured Data linter [1] (among other tools) makes use of the
>>> RDFa+RDFS to perform basic validation services. Right now, I have to build
>>> in a special case to fetch the vocabulary from
>>> http://schema.org/docs/schema_org_rdfa.html; it would be nice if that
>>> could simply be discovered.
>>>
>>> (By the way, I've updated the linter to use the updated vocabulary. I
>>> expect to update the examples used in the linter to be based on [2] (with
>>> attribution). This seems like the best source for those examples; correct
>>> me if I've got it wrong, though, please.
>>>
>>> Gregg
>>>
>>> [1] http://linter.structured-data.org/
>>> [2] https://github.com/rvguha/schemaorg/blob/master/data/examples.txt
>>>
>>> > Dan
>>> >
>>> >> [1]
>>> >>
>>> http://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Fschema.org%2FVehicle
>>> >> -- Note: the object of the rdfs:subClassOf relation is a literal
>>> rather than
>>> >> a URI
>>> >>
>>> >>
>>> >> --
>>> >>
>>> >> Regards,
>>> >>
>>> >> Kingsley Idehen
>>> >> Founder & CEO
>>> >> OpenLink Software
>>> >> Company Web: http://www.openlinksw.com
>>> >> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
>>> >> Twitter Profile: https://twitter.com/kidehen
>>> >> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
>>> >> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >
>>>
>>>
>>>
>>
>