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
As noted in this comment, our usage of universal resource locators/references is not really aligned over our json schemas and markdown docs. We should decide on what format to use and then make sure it is updated in the relevant files
The text was updated successfully, but these errors were encountered:
I don't think there is any misalignment in the usage of URI and URI refs - however, the JSON schema does not enforce URI/URI-ref yet. This is only because I didn't realise it was possible in jsonschema - I will add it as part of this issue.
We already indicate URI as the recommended format:
source (context)
Type: [URI-Reference][typesystem]
- Description: defines the context in which an event happened. The main purpose
of the source is to provide global uniqueness for source + id.
(...)
Constraints:
- REQUIRED
- MUST be a non-empty URI-reference
- An absolute URI is RECOMMENDED
As noted in this comment, our usage of universal resource locators/references is not really aligned over our json schemas and markdown docs. We should decide on what format to use and then make sure it is updated in the relevant files
The text was updated successfully, but these errors were encountered: