Clarification: Example 45, expansion of interest.name

[Zonker2]

In Example 45, interest.name expands to http://schema.org/name despite interest having a property-scoped context with vocabulary set to http://xmlns.com/foaf/0.1 (and foaf defining a property name.)

Is this because the domain of foaf:interest is foaf:person and foaf:person is not in the domain of foaf:name, (but e.g. of foaf:first_name)? This seems illogical, since it requires the JSON-LD processor to understand RDF schema (at least), everything else up to now has been self-contained.

I think actually this is because @vocab acts as a fall back for terms not defined elsewhere (here name in the outer @context) but perhaps a notice would be helpful.

[BigBlueHat]

I think actually this is because @vocab acts as a fall back for terms not defined elsewhere (here name in the outer @context) but perhaps a notice would be helpful.

That's correct. There is not any "knowledge" of RDF Schema in a JSON-LD processor...and, in fact, the processor isn't being given the necessary RDFS even in cases where it might exist.

Essentially, explicit term definitions outweigh the @vocab fallback, so the earlier name definition wins over the more "local" @vocab addition in the scoped vocab.

If one wanted to override name, a more direct definition for it could be added to the scoped context with a new IRI:

{
  "@context": {
    "@version": 1.1,
    "name": "http://schema.org/name",
    "interest": {
      "@id": "http://xmlns.com/foaf/0.1/interest",
      "@context": {
        "@vocab": "http://xmlns.com/foaf/0.1/",
        "name": "http://xmlns.com/foaf/0.1/"
      }
   }
}

Hope that helps!