Create RO-Crate C++ library which can create green metric RO-Crates #319

Activity

1. ianhinder

   assigned

   OliverWoolland

   on Aug 20, 2026
2. ianhinder

   added a parent issue on Aug 20, 2026

   • STEERS WP3 (D3.2) - Green/Resource RO-Crate Profile #239
3. OliverWoolland commented on Sep 3, 2026

   

   OliverWoolland

   on Sep 3, 2026

   More actions

   James Croft has reviewed and I opened a PR implementing his changes eScienceLab/ro-crate-cpp#8 (awaiting review review)
4. OliverWoolland commented on Sep 3, 2026

   

   OliverWoolland

   on Sep 3, 2026

   More actions

   Eli suggested changes 4 5 6
5. OliverWoolland commented on Sep 3, 2026

   

   OliverWoolland

   on Sep 3, 2026

   More actions

   Paul S has reviewed and is going to write an issue on the repo summarising his suggestions
6. OliverWoolland commented on Sep 3, 2026

   

   OliverWoolland

   on Sep 3, 2026

   More actions

   I plan on releasing v0.[1-3].0 on applying these changes and v1 once I've used the lib in the slurm issue
7. elichad

   added sub-issues on Sep 7, 2026

   • Links are flat strings ro-crate-cpp#1
   • Root data entity has not hasParts ro-crate-cpp#2
   • Root metadata entity is missing about ro-crate-cpp#3
   • Support creating detached crates ro-crate-cpp#4
   • Consider allowing vectors of properties ro-crate-cpp#5
   • Move to RO-Crate 1.3 spec ro-crate-cpp#6
8. elichad

   marked this as blocking on Sep 7, 2026

   • STEERS WP3 (D3.2) - Green/Resource RO-Crate Profile #239
9. elichad

   removed a parent issue on Sep 7, 2026

   • STEERS WP3 (D3.2) - Green/Resource RO-Crate Profile #239
10. elichad

    added a sub-issue on Sep 9, 2026

    • Observation and Discussion from Review ro-crate-cpp#9
11. pmslavin commented on Sep 9, 2026

    

    pmslavin

    on Sep 9, 2026

    More actions

    Paul S has reviewed and is going to write an issue on the repo summarising his suggestions

    I made a start on this here which collects all of the comments in one issue - if any particular observation seems useful enough to be implemented then a separate issue can be created for that change.

    I'll add some more points as they occur to me, but I would note that these are just suggestions and/or topics for discussion - the code builds, runs, and works well for me so the suggestions are minor and less important than the maintainer being comfortable with the code.