Merge pull request #550 from elichad/blog/announcing-1.3

1.3 announcement blog post

Author: elichad

docs/_blog/2026-06-23/announcing-ro-crate-1-3.md

@@ -0,0 +1,51 @@
+---
+title:  "Announcing RO-Crate 1.3"
+author: ["Eli Chadwick"]
+date: 2026-06-23
+---
+
+[RO-Crate 1.3]({{baseurl}}{% link _specification/1.3/index.md %}) has just been released!
+
+This release is extremely similar to 1.2 and upgrading will be trivial for most use cases. The changes primarily affect those describing computational workflows with RO-Crate, either using the [Workflows and Scripts]({{baseurl}}{% link _specification/1.3/workflows.md %}) chapter or the [Workflow RO-Crate](https://w3id.org/workflowhub/workflow-ro-crate/) profile and its derivatives.
+
+The [RO-Crate 1.2 Specification Quick Reference]({{baseurl}}{% link pages/resources/quick-reference.md %}) remains entirely valid for 1.3.
+
+## Updates to Bioschemas URIs in the RO-Crate JSON-LD context
+
+The [RO-Crate JSON-LD context]({{baseurl}}{% link _specification/1.3/context.jsonld %}) includes a small number of terms from the Bioschemas vocabulary that are used to describe computational workflows: `ComputationalWorkflow`, `FormalParameter`, `input`, and `output`. The Bioschemas project has now established canonical, resolvable URIs for all of these terms, and RO-Crate 1.3 updates the context accordingly.
+
+The table below shows the URIs for these terms in the last three minor versions of RO-Crate.
+
+| Term | RO-Crate 1.3 context | RO-Crate 1.2 context | RO-Crate 1.1 context |
+| --- | --- | --- | --- |
+| ComputationalWorkflow | <https://bioschemas.org/terms/ComputationalWorkflow> | https://bioschemas.org/ComputationalWorkflow | https://bioschemas.org/ComputationalWorkflow |
+| FormalParameter | <https://bioschemas.org/terms/FormalParameter> | https://bioschemas.org/FormalParameter | https://bioschemas.org/FormalParameter |
+| input | <https://bioschemas.org/terms/input> | https://bioschemas.org/properties/input | https://bioschemas.org/ComputationalWorkflow#input |
+| output | <https://bioschemas.org/terms/output> | https://bioschemas.org/properties/output | https://bioschemas.org/ComputationalWorkflow#output |
+
+Note that `ComputationalWorkflow` and `FormalParameter` did not have URI changes between 1.1 and 1.2, whereas `input` and `output` had URI changes between all three versions.
+
+The [Workflow RO-Crate](https://about.workflowhub.eu/Workflow-RO-Crate/) and [Workflow Run RO-Crate](https://www.researchobject.org/workflow-run-crate/) profiles will be updated to incorporate these changes in the coming weeks.
+
+## Schema.org version update
+
+The version of Schema.org on which the RO-Crate context is based has been updated to [v30.0](https://schema.org/docs/releases.html#v30.0) for RO-Crate 1.3. This update adds many new terms and does not remove any, so it is entirely backward compatible. 
+
+None of the new terms are used in the 1.3 specification. Some of them may however be of interest to [profile]({{baseurl}}{% link pages/resources/profiles.md %}) creators, including:
+* [AuthenticateAction](http://schema.org/AuthenticateAction)
+* [Certification](http://schema.org/Certification)
+* [Credential](http://schema.org/Credential)
+* [Error](http://schema.org/Error)
+* [InstantaneousEvent](http://schema.org/InstantaneousEvent)
+* [LoginAction](http://schema.org/LoginAction)
+* [OperatingSystem](http://schema.org/OperatingSystem)
+* [RuntimePlatform](http://schema.org/RuntimePlatform) 
+* [pronouns](http://schema.org/pronouns)
+* [various types of source for digital objects](http://schema.org/IPTCDigitalSourceEnumeration) to be used with [digitalSourceType](http://schema.org/digitalSourceType)
+* other properties associated with the classes above. 
+
+## Upgrading from 1.2 to 1.3
+
+A crate that conforms to RO-Crate 1.2 can be updated to 1.3 by simply updating the `conformsTo` and `@context`. No other changes are required to the JSON-LD metadata.
+
+RO-Crate consumers/implementers who utilize the RDF representation of crates should take note of the changes to Bioschemas term URIs and be prepared to handle the previous URIs when reading older crates.

docs/_data/sidebars/resources.yml

@@ -13,5 +13,7 @@ subitems:
     url: /vocabularies
   - title: What's changed in RO-Crate 1.2
     url: /whats-changed-in-1-2
-  - title: Specification quick reference (1.2)
+  - title: What's changed in RO-Crate 1.3
+    url: /whats-changed-in-1-3
+  - title: Specification quick reference (1.2/1.3)
     url: /quick-reference

docs/_layouts/post.html

@@ -9,4 +9,6 @@ <h1>{{ page.title }}</h1>
 
 {{ content }}
 
-{% include related_use_cases.html %}
+{% if page.related_pages and page.related_pages.use_cases and page.related_pages.use_cases.size>0  %}
+    {% include related_use_cases.html %}
+{% endif %}

docs/pages/resources/quick-reference.md

@@ -1,10 +1,12 @@
 ---
-title: RO-Crate 1.2 Specification Quick Reference
+title: RO-Crate 1.2/1.3 Specification Quick Reference
 sidebar: resources
 ---
 
 
-# RO-Crate 1.2 Specification Quick Reference
+# RO-Crate 1.2/1.3 Specification Quick Reference
+
+{% include callout.html type="note" content="This resource was developed for RO-Crate 1.2 but remains valid for 1.3 with no additional requirements."%}
 
 ## How to use this document
 
@@ -513,7 +515,7 @@ Entities with a (D) are data entities; entities with a (C) are contextual entiti
 | Script | `@id` | MUST | Must be a URI linking to the executable script | | |
 | Script | `name` | MUST | Must be present | | |
 | Script | `name` | MUST | Must be human-readable | | |
-| Workflow | `@type` | MUST | Must include all of `File`, `SoftwareSourceCode`, and `ComputationalWorkflow` | | |
+| Workflow | `@type` | MUST | Must include all of `File`, `SoftwareSourceCode`, and `ComputationalWorkflow` | In 1.3 the `ComputationalWorkflow` URI in the context was [updated](./whats-changed-in-1-3) | |
 | Workflow | `@id` | MUST | Must be a URI linking to the workflow entry-point | | |
 | Workflow | `name` | MUST | Must be present | | |
 | Workflow | `name` | MUST | Must be human-readable | | |

docs/pages/resources/whats-changed-in-1-2.md

@@ -25,6 +25,8 @@ If using the `input` and `output` properties (as in [Workflows and Scripts - Des
 * `input` has changed from `https://bioschemas.org/ComputationalWorkflow#input` to `https://bioschemas.org/properties/input` .
 * `output` has changed from `https://bioschemas.org/ComputationalWorkflow#output` to `https://bioschemas.org/properties/output`.
 
+{% include callout.html type="note" content="The URIs for these properties have been updated again in RO-Crate 1.3 - see [What's changed in RO-Crate 1.3](./whats-changed-in-1-3) for further information."%}
+
 ### Attached and Detached RO-Crate Packages
 
 The requirement in 1.1 for a RO-Crate to always be a directory has proven to be limiting in some cases. For example, in some applications it is beneficial to serve RO-Crate metadata over an API separately from the data it describes. However, separating the metadata in this way requires some changes to how you handle cross-references and finding the Root Data Entity. Therefore, 1.2 introduces a distinction between "Attached" and "Detached" RO-Crate Packages:

docs/pages/resources/whats-changed-in-1-3.md

@@ -0,0 +1,31 @@
+---
+title: What's changed in RO-Crate 1.3
+sidebar: resources
+---
+
+# What's changed in RO-Crate 1.3
+
+### JSON-LD context
+
+If using the terms `ComputationalWorkflow`, `FormalParameter`, `input`, or `output` (as in [Workflows and Scripts](specification/1.3/workflows)), be aware that their mapping in the JSON-LD context has changed.
+
+| Term | RO-Crate 1.3 context | RO-Crate 1.2 context | RO-Crate 1.1 context |
+| --- | --- | --- | --- |
+| ComputationalWorkflow | <https://bioschemas.org/terms/ComputationalWorkflow> | https://bioschemas.org/ComputationalWorkflow | https://bioschemas.org/ComputationalWorkflow |
+| FormalParameter | <https://bioschemas.org/terms/FormalParameter> | https://bioschemas.org/FormalParameter | https://bioschemas.org/FormalParameter |
+| input | <https://bioschemas.org/terms/input> | https://bioschemas.org/properties/input | https://bioschemas.org/ComputationalWorkflow#input |
+| output | <https://bioschemas.org/terms/output> | https://bioschemas.org/properties/output | https://bioschemas.org/ComputationalWorkflow#output |
+
+Note that `ComputationalWorkflow` and `FormalParameter` did not have URI changes between 1.1 and 1.2, whereas `input` and `output` had URI changes between all three versions.
+
+### To update crates from 1.2
+
+A crate that conforms to RO-Crate 1.2 can be updated to 1.3 by simply updating the `conformsTo` and `@context`. No other changes are required to the JSON-LD metadata.
+
+RO-Crate consumers/implementers who utilize the RDF representation of crates should take note of the changes to Bioschemas term URIs and be prepared to handle the previous URIs when reading older crates.
+
+### To update crates from 1.1
+
+See [What's changed in RO-Crate 1.2](./whats-changed-in-1-2) and update according to that guidance, then follow the instructions above to update from 1.2 to 1.3.
+
+{% include references.liquid %}