Skip to content
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

Closed
floWetzels opened this issue Mar 5, 2024 · 5 comments
Closed

Integration of Data Fragment Selectors #21

floWetzels opened this issue Mar 5, 2024 · 5 comments
Assignees

Comments

@floWetzels
Copy link
Collaborator

floWetzels commented Mar 5, 2024

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 the DataSelectorFormat column as a URL) is added through the usageInfo property. Information on the data format (given in the DataFormat column as a URL) is added through the encodingFormat property.

Example

For example, consider the following process table:

Input [Sample Name] Output [Data] Data Format Data Selector Format
input1 result.csv#col=1 text/csv https://datatracker.ietf.org/doc/html/rfc7111
input2 result.csv#col=2 text/csv https://datatracker.ietf.org/doc/html/rfc7111

The corresponding jsonld objects should look like this:

{
  "@id": "#some_process_id",
  "@type": "LabProcess",
  "object": ["#Sample_input1","#Sample_input2"],
  "result": ["result.csv#col=1","result.csv#col=2"]
},
{
  "@id": "#result.csv#col=1",
  "@type": "MediaObject",
  "encodingFormat": "text/csv",
  "usageInfo": "https://datatracker.ietf.org/doc/html/rfc711"
},
{
  "@id": "#result.csv#col=2",
  "@type": "MediaObject",
  "encodingFormat": "text/csv",
  "usageInfo": "https://datatracker.ietf.org/doc/html/rfc711"
},
{
  "@id": "#Sample_input1",
  "@type": "Sample"
},
{
  "@id": "#Sample_input2",
  "@type": "Sample"
}
@kMutagene kMutagene added the Status: Needs Triage This item is up for investigation. label Jun 18, 2024
@HLWeil HLWeil removed the Status: Needs Triage This item is up for investigation. label Jun 27, 2024
@HLWeil HLWeil transferred this issue from nfdi4plants/arc-to-rocrate Jun 27, 2024
@github-actions github-actions bot added the Status: Needs Triage This item is up for investigation. label Jun 27, 2024
@HLWeil HLWeil changed the title Integration of Data Fragment Selectors Integration of Data Fragment Selectors and Datamap Jun 27, 2024
@HLWeil
Copy link
Member

HLWeil commented Jun 27, 2024

@HLWeil HLWeil changed the title Integration of Data Fragment Selectors and Datamap Integration of Data Fragment Selectors Jun 27, 2024
@HLWeil HLWeil assigned HLWeil and floWetzels and unassigned HLWeil Jun 27, 2024
@HLWeil HLWeil moved this from In discussion to Backlog in ARCStack Jun 27, 2024
@HLWeil HLWeil removed the Status: Needs Triage This item is up for investigation. label Jun 27, 2024
@HLWeil
Copy link
Member

HLWeil commented Sep 11, 2024

I think this is ready to be incorporated? @floWetzels

@HLWeil
Copy link
Member

HLWeil commented Sep 20, 2024

Actually, maybe we could model this more closely to Web Annotation Model:
https://www.w3.org/TR/annotation-model/#selectors

@HLWeil
Copy link
Member

HLWeil commented Sep 20, 2024

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"
    }    
  }
}

@floWetzels
Copy link
Collaborator Author

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
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants