search

niso-standards / cpld

Content Profile / Linked Document Standard
MIT License
4 stars 0 forks source link

What to do with `@import` for CPLD and OA context. #81

Closed RinkeHoekstra closed 1 year ago

RinkeHoekstra commented 2 years ago

There's an issue with JSON-LD context includes in that they only go one level deep.

If I have a document that includes the CPLD context that includes OA, then the OA context will not be imported by a parser.

See https://www.w3.org/TR/json-ld11-api/#context-processing-algorithm section 4.1.5, step 5.6.7.

So, either we should state that every document should @import both the CPLD context and the OA context, or we should copy over the OA context into the CPLD context.

NB this is not an issue for JSON-LD documents that refer to the CPLD context using @context but it is likely that they will want to extend the definitions, which requires an @import map.

RinkeHoekstra commented 1 year ago

Just use all contexts as an array in the Linked Document directly.