diff --git a/schemas/biocomputeobject.json b/schemas/biocomputeobject.json index 6668f44..7430f7a 100755 --- a/schemas/biocomputeobject.json +++ b/schemas/biocomputeobject.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/biocomputeobject.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/biocomputeobject.json", "type": "object", "title": "Base type for all BioCompute Objects", "description": "All BioCompute object types must adhear to this type in order to be compliant with BioCompute specification", @@ -42,7 +42,7 @@ "type": "string", "format": "date-time" }, - "sha1_chksum": { + "sha1_checksum": { "type": "string", "description": "value of sha1 checksum of file", "pattern": "[A-Za-z0-9]+" diff --git a/schemas/description_domain.json b/schemas/description_domain.json index 6e2908e..9d763c4 100755 --- a/schemas/description_domain.json +++ b/schemas/description_domain.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/description_domain.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/description_domain.json", "type": "object", "title": "Description Domain", "description": "Structured field for description of external references, the pipeline steps, and the relationship of I/O objects.", diff --git a/schemas/error_domain.json b/schemas/error_domain.json index 6e48328..aec9a8a 100644 --- a/schemas/error_domain.json +++ b/schemas/error_domain.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/error_domain.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/error_domain.json", "type": "object", "title": "Error Domain", "description": "", diff --git a/schemas/execution_domain.json b/schemas/execution_domain.json index 861e776..97c7d0e 100755 --- a/schemas/execution_domain.json +++ b/schemas/execution_domain.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/execution_domain.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/execution_domain.json", "type": "object", "title": "Execution Domain", "description": "The fields required for execution of the BCO are herein encapsulated together in order to clearly separate information needed for deployment, software configuration, and running applications in a dependent environment", diff --git a/schemas/extension_domain/fhir_extension.json b/schemas/extension_domain/fhir_extension.json index 7352a0f..9cdc7fb 100644 --- a/schemas/extension_domain/fhir_extension.json +++ b/schemas/extension_domain/fhir_extension.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/extension_domain/fhir_extension.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/extension_domain/fhir_extension.json", "type": "object", "required": [ "fhir_endpoint", diff --git a/schemas/extension_domain/scm_extension.json b/schemas/extension_domain/scm_extension.json index 8457656..577fcd0 100644 --- a/schemas/extension_domain/scm_extension.json +++ b/schemas/extension_domain/scm_extension.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/extension_domain/scm_extension.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/extension_domain/scm_extension.json", "type": "object", "required": [ "scm_repository", diff --git a/schemas/io_domain.json b/schemas/io_domain.json index 3f2c00b..2a01cb9 100755 --- a/schemas/io_domain.json +++ b/schemas/io_domain.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/io_domain.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/io_domain.json", "type": "object", "title": "Input and Output Domain", "description": "The list of global input and output files created by the computational workflow, excluding the intermediate files. Custom to every specific BCO implementation, these fields are pointers to objects that can reside in the system performing the computation or any other accessible system.", diff --git a/schemas/parametric_domain.json b/schemas/parametric_domain.json index 943cbae..2c64400 100755 --- a/schemas/parametric_domain.json +++ b/schemas/parametric_domain.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/parametric_domain", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/parametric_domain", "type": "array", "title": "Parametric Domain", "description": "This represents the list of NON-default parameters customizing the computational flow which can affect the output of the calculations. These fields can be custom to each kind of analysis and are tied to a particular pipeline implementation", diff --git a/schemas/provenance_domain.json b/schemas/provenance_domain.json index 4919624..ec8d09c 100755 --- a/schemas/provenance_domain.json +++ b/schemas/provenance_domain.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/provenance_domain.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/provenance_domain.json", "type": "object", "title": "Provenance Domain", "description": "Structured field for tracking data through transformations, including contributors, reviewers, and versioning.", diff --git a/schemas/usability_domain.json b/schemas/usability_domain.json index df993b2..e99c712 100755 --- a/schemas/usability_domain.json +++ b/schemas/usability_domain.json @@ -1,6 +1,6 @@ { "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "http://biocomputeobject.org/1.3.0/schemas/usability_domain.json", + "$id": "http://www.w3id.org/biocompute/1.3.0/schemas/usability_domain.json", "type": "array", "title": "Usability Domain", "description": "Author-defined usability domain of the BCO. This field is to aid in search-ability and provide a specific description of the function of the object. It is recommended that a novel use of the BCO could result in the creation of a new entry with a new usability domain",