Skip to content
This repository has been archived by the owner on Aug 3, 2022. It is now read-only.

each X should be have a url based id #2

Open
nickevansuk opened this issue Jun 1, 2018 · 1 comment
Open

each X should be have a url based id #2

nickevansuk opened this issue Jun 1, 2018 · 1 comment
Labels
bug Something isn't working

Comments

@nickevansuk
Copy link
Contributor

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

@nickevansuk nickevansuk added the bug Something isn't working label Jun 1, 2018
@drchristhorpe
Copy link
Contributor

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants