Hi Sandro,
Any thoughts on where they should go?
>>>
>> If the context is part of a JSON-LD encoding of the vocabulary, then
>> retrieving the vocabulary from it's published location with
>> content-negotiation for JSON-LD will also retrieve the context.
>>
>
> Hmmm. I would have thought the context use in a vocabulary description
> document would be a context that was good for describing vocabularies. But
> now you're saying it should actually be one that's good for describing
> whatever the vocabulary describes. How do we make this work?
You would just need to include owl, rdf, rdfs, skos (as appropriate) in the
context along with whatever LDP needs.
Do we have the context include stuff not needed by LDP?
Yes.
> Do we have the LDP namespace document be written so that it doesn't
> actually make any use of the context provided?
You could do this -- just include the full URIs for all of the predicates
needed, and then no need to include even prefix mapping in the context. I'm
not sure that there's any benefit to doing this though.
> Do we use multiple contexts?
>
No (see previous discussion about multiple contexts and framing /
compaction)
Rob
--
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305