LORC vs. SHARE

[pdurbin]

Under "How is it different than related projects?" it says, "You tell us 😉 " but I don't find this especially satisfying so I thought I'd open this issue to see if I can learn how the Linked Open Research Cloud is different than SHARE which is described at https://osf.io/cpsin/wiki/home/ as follows.

SHARE is a higher education initiative whose mission is to maximize research impact by making a comprehensive inventory of research widely discoverable, accessible, and reusable.
...
SHARE Notify generates a normalized feed of research release events from diverse sources and with varied schema.

They're both inboxes, right?

p.s. "To this end, this article announce its inbox to receive" should be "announces" or "is announcing", right? I'm looking at https://linkedresearch.org/cloud

[csarven]

Some differences as I understand it:

• There is no registration
• Notifications can come from anyone
• Notification payload contains all there is needed to know
• Notifications are available as Linked Data
• LORC wants to only know about free and full "data" (as opposed to "metadata") available as Linked Data

[pdurbin]

@csarven thanks! I just linked to this issue in a post to the SHARE community to see if they can also help tease apart the differences: https://groups.google.com/d/msg/openscienceframework/7eYs-G-7eHU/w-5FsCAhDgAJ

[pdurbin]

• Notifications can come from anyone

• Notification payload contains all there is needed to know

• Notifications are available as Linked Data

@csarven I'm glad I reached out at https://gitter.im/linkedresearch/chat?at=5cfa9dae6fc5846bab7bb4c1 because I had kind of forgotten about Linked Data Notifications (LDN) and it's seems quite related to some new ideas from @michbarsinai about maybe someday using ActivityPub to "follow" (Twitter-style) datasets: IQSS/dataverse#5883

@rigelk joined the discussion and later posted about a new draft vocabulary called SciFed, "a standard for federation of scientific activities and content using ActivityPub" at https://synalp.frama.io/olki/scifed/

Looking again at https://www.w3.org/TR/ldn/ I see "Linked Data Notifications is a protocol that describes how servers (receivers) can have messages pushed to them by applications (senders), as well as how other applications (consumers) may retrieve those messages. Any resource can advertise a receiving endpoint (Inbox) for the messages. Messages are expressed in RDF, and can contain any data." It all seems highly related to me, so I hope this comment helps introduce everybody. 😄

[rigelk]

@pdurbin there is a note in the ActivityPub specification answering your question, actually 🙂

[…] it is worth noting that ActivityPub's targeting and delivery mechanism overlaps with the Linked Data Notifications specification, and the two specifications may interoperably combined. In particular, the inbox property is the same between ActivityPub and Linked Data Notifications, and the targeting and delivery systems described in this document are supported by Linked Data Notifications. In addition to JSON-LD compacted ActivityStreams documents, Linked Data Notifications also supports a number of RDF serializations which are not required for ActivityPub implementations. However, ActivityPub implementations which wish to be more broadly compatible with Linked Data Notifications implementations may wish to support other RDF representations.