-
Notifications
You must be signed in to change notification settings - Fork 0
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
Integration of Data Fragment Selectors #21
Comments
github-actions
bot
added
the
Status: Needs Triage
This item is up for investigation.
label
Jun 27, 2024
HLWeil
changed the title
Integration of Data Fragment Selectors
Integration of Data Fragment Selectors and Datamap
Jun 27, 2024
HLWeil
changed the title
Integration of Data Fragment Selectors and Datamap
Integration of Data Fragment Selectors
Jun 27, 2024
I think this is ready to be incorporated? @floWetzels |
Actually, maybe we could model this more closely to Web Annotation Model: |
Something like: {
"@id": "#result.csv#col=2",
"@type": {"MediaObject","Annotation"}
"encodingFormat": "text/csv",
"body": {
"source" : "result.csv",
"selector" : {
"type" : "FragmentSelector",
"conformsTo" : "https://datatracker.ietf.org/doc/html/rfc711",
"value" : "col=2"
}
}
} |
Integrated the initial version (without the json model from Web Annotation Model) in PR #28 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Data Fragment Selectors for data outputs of processes can be represented in the RO-Crate by adding the data format and data selector format information to the json object representing the output.
The output is a schema.org/MediaObject, with its
@id
being the URL of a file or a directory containing the data selector. Information on how to interpret the data selector (given in theDataSelectorFormat
column as a URL) is added through theusageInfo
property. Information on the data format (given in theDataFormat
column as a URL) is added through theencodingFormat
property.Example
For example, consider the following process table:
The corresponding jsonld objects should look like this:
The text was updated successfully, but these errors were encountered: