You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Today one can either create a document type to constrain RDF triples into a shared lifecycle, or create a subdocument to add a "layer" of information to a type (JSON-LD).
An elegant solution for bi-directional links would be to have a reference-counted linked relationship between two objects. Imagine the concept of friendship, being between two persons, seeing it as directional gives a skewed view of reality, a bi-directional link as a reference-counted third object that connects the individiual would be quite handy.
Another similar instance is a configuration of items into an offering. It could of course be modelled as a type with a set of links, either as individual properties, or as a set of link with a Cardinality. However, if any of the parts of the offering is removed, the offering could be relevant to automatically delete as well (as a design choice).
Describe the solution you'd like
Having reference counted type properties (if one of the property linked is removed, the entire object should be removed too) would enable a significant opportunity to avoid having to write custom logic and instead have more operations possible to perform over the REST and GraphQL interface.
Describe alternatives you've considered
WOQL logic for it, but would be hard for the use case.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Today one can either create a document type to constrain RDF triples into a shared lifecycle, or create a subdocument to add a "layer" of information to a type (JSON-LD).
An elegant solution for bi-directional links would be to have a reference-counted linked relationship between two objects. Imagine the concept of friendship, being between two persons, seeing it as directional gives a skewed view of reality, a bi-directional link as a reference-counted third object that connects the individiual would be quite handy.
Another similar instance is a configuration of items into an offering. It could of course be modelled as a type with a set of links, either as individual properties, or as a set of link with a Cardinality. However, if any of the parts of the offering is removed, the offering could be relevant to automatically delete as well (as a design choice).
Describe the solution you'd like
Having reference counted type properties (if one of the property linked is removed, the entire object should be removed too) would enable a significant opportunity to avoid having to write custom logic and instead have more operations possible to perform over the REST and GraphQL interface.
Describe alternatives you've considered
WOQL logic for it, but would be hard for the use case.
Additional context
N/A
The text was updated successfully, but these errors were encountered: