-
Notifications
You must be signed in to change notification settings - Fork 0
Support for complex types #28
Copy link
Copy link
Open
Labels
breaking changeIntroduce a needed breaking changeIntroduce a needed breaking changeenhancementNew feature or requestNew feature or requesthigh energyRepresents a task which need a lot of energyRepresents a task which need a lot of energy
Milestone
Metadata
Metadata
Assignees
Labels
breaking changeIntroduce a needed breaking changeIntroduce a needed breaking changeenhancementNew feature or requestNew feature or requesthigh energyRepresents a task which need a lot of energyRepresents a task which need a lot of energy
Similar and prior to #7 , it may be useful to enable the usage of complex types on a schema:
Complex types are embedded in the enclosing schema and does not need a separate repository, this is purely for convenience to avoid a big flat structure and the representation in the triple will still be standard.
This feature will introduce a needed breaking change, the
Schema.typeshould be moved to theRepository(and thetypebecomes mandatory in the repository options), I think it makes more sense after all, only the repository cares about a Thing type after all, the schema is here only to map JS <-> Thing