Join the team (post here to be added) #1
Comments
|
Happy to join |
|
Me too! |
|
Count me in too! |
also added @rap3wk to RO-Lite team in GitHub - see #1
Hi, in @kylechard asked me to have a look at this, as in https://researchobject.github.io/ro-lite/ we are trying to formalize exactly what you are trying to do. This patch is aligning the `manifest.json` closer to https://researchobject.github.io/ro-lite/0.1.0/ draft but without the suggested relocation it to `/manifest.jsonld` so that this is still valid according to existing BDBag. * `Description` typo -> `description` (for http://schema.org/description) * Use http://schema.org/ context, avoids `"@type": "@id"` mapping and `schema:` prefix * Modified `license` (as we're not so interested in license of the license file) - express on the overall RO * Use schema.org over foaf * schema.org JSON-LD blocks can be used directly as in examples * Fixed missing URI escaping in `folder` (good example!) * Fixed `@id` of the person so it's an actual URI - here using ORCID (as in RO-lite directly rather than with `orcid` property) * http://schema.org/keywords instead of http://schema.org/category as `category` does not apply to http://schema.org/CreativeWork (alternative: relate it to https://schema.org/exampleOfWork if there's something it's an example of) * http://schema.org/creator http://schema.org/createdDate instead of `pav:createdBy` and `pav:createdDate` * Use http://schema.org/dataset as main holder, which makes the `ro:ResearchObject` also be a http://schema.org/DataCatalog and implicit `@type: Dataset` * "duplicate" `dataset` relation in `aggregate` so that the doi `Dataset` instance is also part of the RO Try the JSON-LD in https://json-ld.org/playground/ and click **Table** to check the triples are in the correct namespaces etc. https://search.google.com/structured-data/testing-tool is not ideal as it gets upset on properties from non-schema.org vocabularies (which are harmless according to @b) - but at least it flags mistakes like `Description` vs `description` In the RO-Lite work we want to move towards formalizing this approach, so we would likely make a new JSON-LD context to avoids the tricky "@context: [...]" hacks above. If you are interested you can join ResearchObject/ro-crate#1 and help us shape RO Lite. Alternative 1 - all schema.org: https://gist.github.com/stain/2673f4c920a86d1b257cc0a696b32df4 (RO and bdbag tools does not know this yet) Alternative 2 - schema: prefix only: https://gist.github.com/stain/93686e8e557f13e8edccc15a767e8499 (works just as well in https://search.google.com/structured-data/testing-tool - but JSON looks more noisy as `schema:` properties become more "imported" This patch is a "middle ground" of those two approaches, preserving in particular the OAI-ORE aggregation aspect of research objects.
|
Time for first call next week is being voted on in https://doodle.com/poll/z7r8vzaz575xrq7y |
First ROLite call will be on 2019-03-28T21:00Z Telcon: https://zoom.us/j/938672241 Agenda: https://docs.google.com/document/d/1vg805CJ4QXY6CCBNR-8ETgkbOCAMqSKJPCKOTNxrIbk/ |
|
hi |
|
Hello |
|
Hi everyone! |
|
Hi all. |
|
Happy to join. |
Joining the team from #1: @frederikcoppens @CaroleGoble @jmfernandez @kylechard @josemanuelgp
|
Everyone welcome to join the RO Lite meetings. Next scheduled meetings:
Join call at https://zoom.us/j/189405531 See rolling agenda at https://s.apache.org/ro-lite-minutes |
|
I'd like to at least observe, thanks! |
|
HI, I would also like to join, thanks! |
|
hello world! |
from #1 Also tidied some language around ROLite/RO-Crate.
|
Everyone welcome to join the RO Crate meetings. Next scheduled meetings:
Join call at https://zoom.us/j/189405531 See rolling agenda at https://s.apache.org/ro-crate-minutes |
|
Oh, I have a conflicting meeting starting at 12:30pm. Will try to join later or follow up on the minutes. |
|
Hi @stain - thanks for setting this up. I am a bit late to the discussion, but look forward to learning more about the work happening in the group. I'll try to catch up via notes. Cheers. |
|
Friendly reminder of RO-Crate call tomorrow or so. Everyone welcome to join the RO Crate meetings. Next scheduled meetings:
Join call at https://zoom.us/j/189405531 |
|
Happy to join to the RO-crew! |
|
Happy to join the effort! |
|
Happy to help think about the validation challenges |
|
welcome jake!! |
|
Hello, |
|
Hi there! Bruno from BSC. Planning to improve how Autosubmit handles provenance, looking at all the great stuff here. I would like to join too, please. Thanks! |
|
Hi everyone! I'd like to join the team |
|
Hi. I'd like to join the team. Thanks. |
|
I would like to join as well please. Thank you. |
|
I would like to join :) |
|
Hello everyone! I'm Toshiyuki from the National Institute of Informatics (ORCID: https://orcid.org/0000-0001-6712-6335). We're planning to use RO-Crates as packages of metadata, provenances of analysis, etc. I would like to join the team. Thank you in advance :-) |
|
Hi, I would like to be included as well. |
|
Sign me up, please! |
|
Would also love to join :) |
|
Would love to join the team please :) |
|
There is still an issue with anyone signing up to https://lists.elixir-europe.org/mailman/listinfo/ro-crate_elixir-europe.org independently - basically we get >1000 spam request per day. Please reply here if you are NOT signed up to the mailing list and I can add you. This is a low-traffic list that mainly notifies you of RO-Crte meetings!. |
|
I think I've already got through the spam filter on that one as I do get the weekly meeting updates (useful for minutes as they are at my 4am)
…________________________________
From: Stian Soiland-Reyes ***@***.***>
Sent: Tuesday, April 23, 2024 12:01 AM
To: ResearchObject/ro-crate ***@***.***>
Cc: James Love ***@***.***>; Comment ***@***.***>
Subject: Re: [ResearchObject/ro-crate] Join the team (post here to be added) (#1)
There is still an issue with anyone signing up to https://lists.elixir-europe.org/mailman/listinfo/ro-crate_elixir-europe.org<https://lists.elixir-europe.org/mailman/listinfo/ro-crate_elixir-europe.org> independently - basically we get >1000 spam request per day. Please reply here if you are NOT signed up to the mailing list and I can add you. This is a low-traffic list that mainly notifies you of RO-Crte meetings!.
—
Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEJLFDLOET7RNKRRSJJ7BWTY6T3ZBAVCNFSM4GXE4AC2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBWHEZDCNRQGEZA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Would love to join the team and the meetings. I am not signed up to the mailing list. @stain pls add me if you can, thanks! |
|
I didn't realize how long I'd been missing the party! 🥳 @stain, I'd like to be added as well. Many thanks. |
|
Hi! I'm Andreas from Scientific IT Services of ETH Zürich. |
and others
Add a comment to this issue to join the https://github.com/ResearchObject/ro-crate team.
It is helpful if you include your ORCID. We will then add you to the Slack and mailing list.
There are no obligations in being a contributor except abiding by our code of conduct.
The text was updated successfully, but these errors were encountered: