RE: How to mitigate accidental/unwelcome IRI expansion?

On Saturday, December 19, 2015 1:31 AM, Robert Sanderson wrote:
> How about this scenario:
> 
> In an extension to a well used vocabulary (such as AS, but substitute
> for anything you like), an attacker puts in a context of:
> 
>     {"http": "http://track.me/tracker/", "https": "https://tracke.me/tracker/"}

How would the attacker put that in the context?

Even if those definitions would be in the context, nothing would happen because

  4.2) If prefix is underscore (_) or suffix begins with double-forward-slash (//),
  return value as it is already an absolute IRI or a blank node identifier.

  http://www.w3.org/TR/json-ld-api/#iri-expansion


Cheers,
Markus


--
Markus Lanthaler
@markuslanthaler