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

Add default metadata fields #214

Open
mr-c opened this issue May 19, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@mr-c
Copy link
Member

commented May 19, 2016

And document its use.

By default, the following is assumed in every draft-4 CWL document unless overridden by the user

$namespace:
  ro: http://purl.org/wf4ever/ro#

$schemas:
- http://wf4ever.github.com/ro/ro.owl
  • pull request against the community workflow repository migrating an existing tool's metadata to use this schema
  • get versioned URL for the schema from @stain
  • PR to add text to draft-4
  • PR to add support to cwltool's draft-4 support
@stain

This comment has been minimized.

Copy link
Member

commented May 19, 2016

I don't think the RO ontology, which deals with aggregation and annotations, makes sense for metadata. We re-use existing vocabularies, e.g. using a JSON-LD context that maps to existing vocabularies like ORE, PROV, PAV, etc.

What would make more sense is to select certain provenance properties, e.g. retrievedFrom and authoredBy and add them to the core CWL JSON-LD context so they can be used without prefixes.

Using http://schema.org/ terms for project definition probably makes sense, but it's a bit too weak for my liking for provenance, e.g. if a tool description JSON was downloaded from somewhere, I would want to see that stated explicitly with pav:retrievedFrom (if the file is the same), or pav:importedFrom a resource in a different form (e.g. a http://bio.tools/ page), or pav:derivedFrom if further edits have been done.

@mr-c mr-c changed the title Make ResearchObject.org default metadata ontology Add default metadata fields May 20, 2016

@mr-c mr-c modified the milestone: unscheduled Dec 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.