This also removes the early attempt of sdConformsTo structure from #154 and adds a footnote:
This is a liberal interpretation of conformsTo as it is the structured data about the workflow (this JSON-LD object) that conforms to the ComputationalWorkflow profile, not the file content of a workflow data entity (workflow/alignment.knime). Instead of introducing a sdConformsTo similar to sdPublisher, we here follow the current Bioschemas convention of indicating profile conformance when the JSON-LD is embedded within HTML pages.
Discussion in schemaorg/schemaorg#1516 schemaorg/schemaorg#2887 seems to suggest a structuredData property to another blank node entity about the metadata itself, which could then have its own creator, etc. (and in our case conformsTo). My view now is that adding a nested structuredData contextual entity in RO-Crate will get excessively verbose (particularly on the FormalParameter which is already a #nonDownloadable contextual entity).
Refer to BioSchemas 1.0-RELEASE versions without
/in their@idURIs. Example:This fixes issue #185
This also removes the early attempt of
sdConformsTostructure from #154 and adds a footnote:Discussion in schemaorg/schemaorg#1516 schemaorg/schemaorg#2887 seems to suggest a
structuredDataproperty to another blank node entity about the metadata itself, which could then have its owncreator, etc. (and in our caseconformsTo). My view now is that adding a nestedstructuredDatacontextual entity in RO-Crate will get excessively verbose (particularly on theFormalParameterwhich is already a #nonDownloadable contextual entity).