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
{{ message }}
This repository has been archived by the owner on Aug 3, 2022. It is now read-only.
Does this mean that sub-models such as Place, Organisation, Person don't have the requirement for URL based ID?
In our documentation we state - "Information about Events, Places, Organizations and other types of resources should already have been published online to make that information accessible to users. Using existing URLs as identifiers avoids the need to define a new identifier scheme for resources described in opportunity data."
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There's an over-sensitivity here, as only the Event requires a url based id, and only if the booking specification is also being implemented
The text was updated successfully, but these errors were encountered: