Make it clear that @id is URIpath with / seperators #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added below Core Metadata for Data Entities to clarify #77
Encoding file paths
Note that all
@id
identifiers must be valid URI references, care must be taken to express any relative paths using/
separator, correct casing, and escape special characters like space (%20
) and percent (%25
), for instance a File Data Entity from the Windows pathResults and Diagrams\almost-50%.png
becomes"@id": "Results%20and%20Diagrams/almost-50%25.png"
in the RO-Crate JSON-LD.In this document the term URI includes international _IRI_s; the RO-Crate Metadata File is always UTF-8 and international characters in identifiers SHOULD be written using native UTF-8 characters (_IRI_s), however traditional URL encoding of Unicode characters with
%
MAY appear in@id
strings. Example:"@id": "面试.mp4"
is preferred over the equivalent"@id": "%E9%9D%A2%E8%AF%95.mp4"