search

oldm / OldMan

Python OLDM (Object Linked Data Mapper)
Other
15 stars 3 forks source link

Supported reversed properties #2

Closed bcogrel closed 10 years ago

bcogrel commented 10 years ago

Common with JSON-LD context

Not yet supported in Hydra but may be added soon : https://github.com/HydraCG/Specifications/issues/40

It could looks like a hydra:reversed property for hydra:supportedProperty

bcogrel commented 10 years ago

Support added at the JSON-LD level (see https://github.com/oldm/OldMan/commit/91404d95da2aebba69fc313fe465086f90eb79a7).

However the situation needs to be clarified at the Hydra level. Currently, a hydra:supportedProperty indicates that a given property should be considered for instances of a given RDFS class.

We currently make no difference between a reversed property and a regular one using the same RDF predicate at the Hydra-level. This is not good if, for instance, one property is required but not the second one.

bcogrel commented 10 years ago

An OMProperty must now be hydra:reversed for supporting @reverse JSON-LD terms.

Last problem: some triples are now related to two Resource objects. Example: employer and employee (if employer is the reversed property of schema:employee). In such a case, the cache must be invalidated.

bcogrel commented 10 years ago

Cache invalidation added.