RE: playground schema.org support

On Thursday, August 15, 2013 9:25 PM, David I. Lehn
> I just added a feature to the playground to use a custom
> documentLoader to map "http://schema.org[/]" to
> "https://w3id.org/schema.org". This should let schema.org examples
> [1][2] actually work instead of just complaining about an invalid
> context URL. We can remove those map entries when/if schema.org starts
> serving their own context.
 
[...]
 
> Other systems that process JSON-LD may need to use a similar hack to
> handle incoming data using a schema.org context.

I have been thinking about this for a while now but came to the conclusion
that it would be too dangerous to do so. In my opinion it sends the wrong
signal. Especially if it is done without users knowing what happens.

The danger I see is that this will become the default for large
organizations and will put a lot of pressure on implementers to do the same.
As long as those examples don't work with existing processors the pressure
is where it belongs (schema.org in this instance).

So I would prefer to revert those changes or, even better, to make the
feature a bit smarter. If the schema.org remote context is detected, we
could display a message explaining the situation (the context isn't there
yet) and provide users an option to use the w3id.org context in the
meantime. Nothing should happen automatically and the user should be made
aware of the current problem.

Would that be ok for you?


--
Markus Lanthaler
@markuslanthaler

Received on Thursday, 15 August 2013 20:38:30 UTC