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
This is because earlier versions of the Workflow RO-Crate profile did not suggest global identifiers for these. However these can still be spotted by having the same identifier and/or url.
So the current graph will make it complicated to query for workflows in a given language as the absolute identifiers (from #1) will vary for each crate.
As it may be tricky to replace each use of programmingLanguage and the declared entity perhaps it's better to add glue statements:
Here sameAs is stated both with OWL and http://schema.org/sameAs as we're not using OWL otherwise but owl:sameAs is very much more common than s:sameAs.
Many RO-Crates in WorkflowHub use identifiers like
#cwl
for identifying a workflow language rather than the now global identifiers https://w3id.org/workflowhub/workflow-ro-crate#cwl -- see https://about.workflowhub.eu/Workflow-RO-Crate/#supported-workflow-typesThis is because earlier versions of the Workflow RO-Crate profile did not suggest global identifiers for these. However these can still be spotted by having the same
identifier
and/orurl
.So the current graph will make it complicated to query for workflows in a given language as the absolute identifiers (from #1) will vary for each crate.
As it may be tricky to replace each use of
programmingLanguage
and the declared entity perhaps it's better to add glue statements:Here
sameAs
is stated both with OWL and http://schema.org/sameAs as we're not using OWL otherwise butowl:sameAs
is very much more common thans:sameAs
.This would need to match each of the languages in https://about.workflowhub.eu/Workflow-RO-Crate/ro-crate-metadata.json but not other unknown languages.
The text was updated successfully, but these errors were encountered: