-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace the subidentifier field with a Relationship object #108
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Replace the subidentifier field with a Relationship object
The specification currently uses the road_events.subidentifier field as a foreign key to relate objects. However, the field does not explicitly describe how linked features are related. Replacing road_events.subidentifier with a Relation object, like the one used in JSCalendar, will relate road event features and explicitly describe how features are related.
The Relationship object as defined in the JSCalendar Specification.
A Relation object defines the relation to other objects, using a possibly empty set of relation types. The object that defines this relation is the linking object, while the other object is the linked object.
The Relation object has the following properties:
Specifies the type of this object. This MUST be "Relation".
Describes how the linked object is related to the linking object. The relation is defined as a set of relation types. If empty, the relationship between the two objects is unspecified. Keys in the set MUST be one of the following values, or specified in the property definition where the Relation object is used, or a value registered in the IANA JSCalendar Enum Registry, or a vendor-specific value:
The value for each key in the set MUST be true.
The Relationship object used in the Work Zone Data Specification.
Hierarchical Example
Sequential Example
The text was updated successfully, but these errors were encountered: