Skip to content

Shouldn't the content file for the CTDL include the vocabulary terms? #380

@stuartasutton

Description

@stuartasutton

I think we may have a conceptual issue with the jsonld context file.

Currently, we have a context file for "CTDL" and then separate context files for each of the controlled vocabularies. However, I can imagine no instance data using CTDL for describing a credential that does not also use some concepts from the controlled vocabularies? Therefore, shouldn't the CTDL context file also include all of the concept terms? Otherwise, how can such instances reference a single context file and cover everything in their instance data?

The schema.org context file includes concepts (enumerations) in its context file. Granted, schema.org constrains everything to one namespace, but nevertheless, I'm wondering whether all of our classes (including concepts in concept schemes) shouldn't everything be in one grand context file.

Could this possibly account for older data in WorkIt that had no context declarations of prefixes for controlled vocabularies...they weren't in the master context file?

Related issue at schemaorg/schemaorg#990

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions