W3C home > Mailing lists > Public > public-linked-json@w3.org > February 2013

Re: Open Annotation / Default Context Location?

From: Robert Sanderson <azaroth42@gmail.com>
Date: Wed, 27 Feb 2013 13:53:33 -0700
Message-ID: <CABevsUERbwEyDueHMx3ObMwz3NijmCH4qV4GURA+JhQt0C-S5A@mail.gmail.com>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Cc: public-linked-json@w3.org
Hi Markus and all,

>> As the W3C (thank you Ivan) lets us
>> publish our namespace documents, we figured that they'd also let us
>> publish the JSON-LD context file, but they don't have anything in
>> place for doing that yet.
> I didn't know that. If that's the case, why don't combine your namespace
> document with your external context? The external context would end up being
> slightly bigger, but that shouldn't really matter. That even has the
> advantage that your namespace document is available as JSON-LD and there
> won't be an additional round-trip to fetch its definitions.

This is a great idea, which we're implementing at least until there's
a better solution.

The remaining question is whether it should be the recommended best practice?

Ivan Herman said (quoted with permission), with regards to having
somewhere on the W3C site to collect context documents from different

RDFa has the notion of initial contexts. They are much simpler and
less powerful than @context, and they are essentially static files
assigned to RDFa host languages, but they are more similar to @context
files than vocabularies are. Those files are stored in

Taking that example, we can set up, say,
as a more general resource where such files can be stored.

This would fit more neatly with how we were expecting things to work,
but certainly is not in the Open Annotation CGs remit to request :)
Either this CG or the RDF WG would seem appropriate, if it's deemed to
be the correct way forwards.

Many thanks for your engagement with the issue, and the merged
ontology/context suggestion :)

Received on Wednesday, 27 February 2013 20:54:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:36 UTC