DiSCO, Distributed Scholarly Communicated Object, is simple semantics for grouping entities together for the purpose of creating a "Research Object." A research object is any collection of entities pertaining to a research activity.
We needn't adopt Disco itself, merely the ability to designate a collection of entities as belonging to a research object.
For background on DiSCO, see
Hanson, K.L., DiLauro, T., Donoghue, M. (2015). The RMap Project:
Capturing and Preserving Associations amongst Multi-Part Distributed
Publications. In Proceedings of the 15th ACM/IEEE-CS Joint Conference on
Digital Libraries, pp. 281-282. ACM.
[https://urldefense.proofpoint.com/v2/url?u=https-3A__doi.org_10.1145_2756406.2756952&d=DwIFAg&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0KAeOm4xReLRjGI8tqzw-A&m=YdbzJgLynnmG8OvlMF98opmp_dKHDXA7Gg5pWnpIJMc&s=IpaBsLk1alKAO2Ij-2la4IbfaYnnvN-P6ieQgfoRiKo&e=]
It would be desirable to provide an interface to the RO to provide functionality – create, delete, manage contents (add and delete entities), but this would be a separate ticket and not required for adding the entity to the ontology.
Questions:
Q: How is this different from foaf:Group?
A: A foaf:Group is a collection of foaf:Agents
Q: How is this different from bibo:Collection?
A: A bibo:Collection is a collection of Information Resources. Perhaps everything in a research object (DiSCO) is an information resource, but this needs discussion.
Q: Can this be implemented without new software?
A: Yes. We can have entities in the ontology that are not directly manipulable by the software.
Mike Conlon (Migrated from VIVO-1621) said:
DiSCO, Distributed Scholarly Communicated Object, is simple semantics for grouping entities together for the purpose of creating a "Research Object." A research object is any collection of entities pertaining to a research activity.
We needn't adopt Disco itself, merely the ability to designate a collection of entities as belonging to a research object.
For background on DiSCO, see
Hanson, K.L., DiLauro, T., Donoghue, M. (2015). The RMap Project: Capturing and Preserving Associations amongst Multi-Part Distributed Publications. In Proceedings of the 15th ACM/IEEE-CS Joint Conference on Digital Libraries, pp. 281-282. ACM. [https://urldefense.proofpoint.com/v2/url?u=https-3A__doi.org_10.1145_2756406.2756952&d=DwIFAg&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0KAeOm4xReLRjGI8tqzw-A&m=YdbzJgLynnmG8OvlMF98opmp_dKHDXA7Gg5pWnpIJMc&s=IpaBsLk1alKAO2Ij-2la4IbfaYnnvN-P6ieQgfoRiKo&e=] It would be desirable to provide an interface to the RO to provide functionality – create, delete, manage contents (add and delete entities), but this would be a separate ticket and not required for adding the entity to the ontology. Questions: Q: How is this different from foaf:Group? A: A foaf:Group is a collection of foaf:Agents Q: How is this different from bibo:Collection? A: A bibo:Collection is a collection of Information Resources. Perhaps everything in a research object (DiSCO) is an information resource, but this needs discussion. Q: Can this be implemented without new software? A: Yes. We can have entities in the ontology that are not directly manipulable by the software.