address review comments

Author: a-mile

episodes/05-metadata-descriptor.md

@@ -17,7 +17,7 @@ exercises: 2
 
 ## RO-Crate Metadata descriptor 
 
-The first JSON-LD _entity_ to add in the `@graph` array has the `@id` value of `ro-crate-metadata.json` to describe the JSON file itself:
+Next, we'll add another _entity_ to the `@graph` array has the `@id` value of `ro-crate-metadata.json` to describe the JSON file itself:
 
 
 ```json

episodes/06-cross-references.md

@@ -4,7 +4,7 @@ teaching: 3
 exercises: 4
 ---
 :::::::::::::::::::::::::::::::::::::::: questions
-- How does RO Crate use flattened JSON-LD?
+- How can I describe an entity further?
 - How can I cross-reference different entities?
 ::::::::::::::::::::::::::::::::::::::::::::::::::
 

episodes/07-data-entities.md

@@ -59,12 +59,32 @@ as shown in the above example, this does not need to match the filename/identifi
 The `encodingFormat` indicates the media file type so that consumers of the crate can open `data.csv` in an appropriate program,
 and can be particularly important for less common file extensions frequently encountered in outputs from research software and instruments.
 
-You can override the license for the root data entity by specifying a `license` property on the data entity itself.
-
 For more information on describing files and folders,
 including their recommended and required attributes,
 see section on [data entities](https://www.researchobject.org/ro-crate/specification/1.2/data-entities.html).
 
+:::::::::::::::::::::::::::::::::::::::: challenge
+## Override the licence
+
+1. Consider if the file content of `data.csv` is not covered by our overall license (CC0), 
+   but [Creative Commons BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/)
+   (which only permits non-commercial use)
+2. To override, add an  `license` cross-reference property on this particular data entity
+
+:::::::::::::::  solution
+```json
+{
+    "@id": "data.csv",
+    "@type": "File",
+    "name": "Rainfall Katoomba 2022-02",
+    "description": "Rainfall data for Katoomba, NSW Australia February 2022",
+    "encodingFormat": "text/csv",
+    "license": { "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/" }
+},  
+```
+:::::::::::::::::::::::::
+::::::::::::::::::::::::::::::::::::::::::::::::::
+
 
 :::::::::::::::::::::::::::::::::::::::: keypoints
 - Data entities are files & folders within the root, as well as external Web references

episodes/08-contextual-entities.md

@@ -37,6 +37,45 @@ for instance how to link to authors and their affiliations.
 Simplifying slightly, a data entity is referenced from `hasPart` in a `Dataset`,
 while a contextual entity is referenced using any other defined property.
 
+## Detailing licenses
+
+We have previously declared two different `license` cross-references.
+While following the URLs in this case explain the licenses well,
+it is also best practice to include a very brief summary of contextual entities in the RO-Crate Metadata Document.
+This is more important if the cross-reference do not use a permalink and may change over time.
+As a minimum, each referenced entity should have a `@type` and `name` property.
+It is also possible to add `url` for more information.
+
+:::::::::::::::::::::::::::::::::::::::: challenge
+## Add licence entities
+
+Add a contextual entity for each of the two licenses,
+see the [licensing](https://www.researchobject.org/ro-crate/1.1/contextual-entities.html#licensing-access-control-and-copyright) section for details:
+ 
+:::::::::::::::  solution
+```json
+{
+   "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/",
+   "@type": "CreativeWork",
+   "name": "CC BY-NC-SA 4.0 International",
+   "description": "Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International"
+},    
+{
+   "@id": "http://spdx.org/licenses/CC0-1.0",
+   "@type": "CreativeWork",
+   "name": "CC0-1.0",
+   "description": "Creative Commons Zero v1.0 Universal",
+   "url": "https://creativecommons.org/publicdomain/zero/1.0/"
+},  
+```
+:::::::::::::::::::::::::
+::::::::::::::::::::::::::::::::::::::::::::::::::
+
+
+An additional exercise is to try to unify the two entities so that both use spdx identifiers,
+remembering to update the corresponding `license` cross-references when changing the `@id`.
+However, not all licenses have a direct SPDX identifier.
+
 ## Instrument details
 
 For example, the instrument used to capture weather data is not itself part of the dataset, but knowing what device created the measurements helps the data consumer interpret and validate the data.

episodes/13-complete.md

@@ -52,6 +52,7 @@ The final RO-Crate Metadata Document constructed in this tutorial should look so
      "name": "Rainfall Katoomba 2022-02",
      "description": "Rainfall data for Katoomba, NSW Australia February 2022",
      "encodingFormat": "text/csv",
+     "license": {"@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/"},
      "instrument": { "@id": "https://example.org/instrument/ws-2000" }
    },
    {
@@ -60,14 +61,20 @@ The final RO-Crate Metadata Document constructed in this tutorial should look so
      "name": "WS-2000 Weather Station",
      "description": "Automated weather station used to record temperature and rainfall data.",
      "url": "https://example.org/instrument/ws-2000"
-   },    
+   },
+   {
+     "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/",
+     "@type": "CreativeWork",
+     "name": "CC BY-NC-SA 4.0 International",
+     "description": "Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International"
+   },
    {
      "@id": "http://spdx.org/licenses/CC0-1.0",
      "@type": "CreativeWork",
      "name": "CC0-1.0",
      "description": "Creative Commons Zero v1.0 Universal",
      "url": "https://creativecommons.org/publicdomain/zero/1.0/"
-   },    
+   },
    {
      "@id": "https://orcid.org/0000-0002-1825-0097",
      "@type": "Person", 

episodes/14-common-pitfalls.md

@@ -91,7 +91,8 @@ Here's an incorrect metadata example. Identify and fix the issues.
 3. The data.csv entity should be defined separately in the @graph.
 4. The encodingFormat should be a valid IANA media type (e.g., "text/csv").
 5. Missing required properties (description, datePublished, license) on the root dataset.
-::::::::::::::::::::::::::::::::::::::::
+:::::::::::::::::::::::::
+::::::::::::::::::::::::::::::::::::::::::::::::::
 
 ## RO-Crate validation tools
 

episodes/15-next-steps.md

@@ -23,10 +23,10 @@ You have completed making a basic RO-Crate. You may try any of the following:
 
 - **RO-Crate Profiles**: Delve into [RO-Crate Profiles](https://www.researchobject.org/ro-crate/profiles.html), which are community-defined content checklists that extend the base specification to meet the specific needs of a domain or data type. Profiles impose conventions and may add domain specific terms/vocabularies, effectively making RO-Crates typed and machine-actionable for specific use cases. Examples include the [Workflow RO-Crate profile](https://about.workflowhub.eu/Workflow-RO-Crate/) used by WorkflowHub and the [Five Safes RO-Crate profile](https://trefx.uk/5s-crate/) for trusted workflow execution in Trusted Research Environments (TREs).
 
-- **FAIR Signposting**: Understand how [FAIR Signposting](https://catalogue.fair-impact.eu/resources/fair-signposting) can be used in combination with RO-Crate to guide machine agents through metadata space. It re-uses existing web standards (HTTP Link headers or HTML `<link>` tags tags) to make machine navigation explicit, helping automated agents locate an object's identifier, data records, and metadata records.
+- **FAIR Signposting**: Understand how [FAIR Signposting](https://catalogue.fair-impact.eu/resources/fair-signposting) can be used in combination with RO-Crate to guide machine agents through metadata space.
 
-- **Bioschemas**: Explore [Bioschemas](https://bioschemas.org/), a community initiative built on schema.org that defines domain-specific profiles (e.g., Dataset, ComputationalWorkflow, ChemicalSubstance) to add structured metadata to web resources, improving findability and interoperability, particularly in the life sciences.
+- **Bioschemas**: Explore [Bioschemas](https://bioschemas.org/), a life sciences community initiative built on schema.org that defines domain-specific profiles (e.g., Dataset, ComputationalWorkflow, ChemicalSubstance).
 
-- **Community and Tools**: Join the open [RO-Crate community](https://www.researchobject.org/ro-crate/community) on GitHub, participate in drop-in sessions, and explore available tools like Crate-O, RO-Crate Playground, and libraries for various programming languages (Python, JavaScript). This active community and the developer-friendly tools are key to RO-Crate's adoption and sustainability.
+- **Community and Tools**: Join the open [RO-Crate community](https://www.researchobject.org/ro-crate/community) on GitHub, participate in drop-in sessions, and explore the tools and libraries for various programming languages.
 
-- **Real-world Use Cases**: Gain inspiration from how RO-Crates are being [used in practice](https://www.researchobject.org/ro-crate/use_cases) across various domains, such as in ELIXIR resources for life sciences, WorkflowHub for computational workflows, for Electronic Lab Notebooks (ELN) provenance, and for packaging earth observation data. RO-Crate enables exchange between services and data repositories, fostering an ecosystem of research infrastructure.
+- **Real-world Use Cases**: Explore how RO-Crates are being [used in practice](https://www.researchobject.org/ro-crate/use_cases) across various domains.

index.md

@@ -10,6 +10,7 @@ packaging research data.
 :::::::::::::::::::::::::::::::::::::::::: prereq
 ## Prerequisites
 - Files and folder organization and using a text editor or IDE such as [Visual Studio Code](https://code.visualstudio.com/)
+- Familiarity with [JSON](https://www.json.org/) file format
 ::::::::::::::::::::::::::::::::::::::::::::::::::
 
 ### Target Audience