Open SusanBrown opened 6 years ago
This is currently what's in the ontology:
<skos:Concept rdf:about="#originalOrlandoAuthor">
<rdfs:label xml:lang="en">Members of the Orlando Project</rdfs:label>
<rdfs:label xml:lang="fr">Les membres du projet Orlando</rdfs:label>
<rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Group"/>
<foaf:name xml:lang="en">Members of the Orlando Project.</foaf:name>
<foaf:name xml:lang="fr">Les membres du projet Orlando</foaf:name>
<foaf:homepage rdf:resource="http://orlando.cambridge.org/public/svDocumentation?formname=t&d_id=CREDITSANDACKNOWLEDGEMENTS"/>
<skos:definition xml:lang="en">The collection of all persons having written entries for The Orlando Project.</skos:definition>
<skos:definition xml:lang="fr">La collection de tous les auteurs du Projet Orlando.</skos:definition>
<rdfs:isDefinedBy rdf:resource="http://sparql.cwrc.ca/ontologies/cwrc-ONTOLOGY_DATE"/>
<void:inDataset rdf:resource="#datasetdefinition"/>
</skos:Concept>
And <loc:ctb rdf:resource="#originalOrlandoAuthor"/>
of the dataset
I'm not too sure how you're intending to apply this for annotations but that might be more of a question for Joel.
What we have there seems reasonable to me, I agree that adding specific authors is better but this should be good for now.
Right now the annotations don't have a linkage to the #originalOrlandoAuthor as this wasn't handled in our annotation models, Is having the linkage to the source sufficient or do we need to add dcterms:author
or some other relation between the snippet and #originalOrlandoAuthor. @SusanBrown
I think we did mean to do this but it just got dropped from the graffles.
@joelacummings, since we're using bibframe, what would you say to using bf:author ? It can be used for orgs as well as individuals.
We could create People/Organization instances and give them a role of author and that would make sense I think.
@SusanBrown let's discuss this. Can CIDOC's Person class replace the use of FOAF? Or should we consider including both?
Let’s go with the CIDOC Person Class instead.
On Nov 12, 2021, at 2:40 PM, JasmineDW @.**@.>> wrote:
CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to @.**@.>
@SusanBrownhttps://github.com/SusanBrown let's discuss this. Can CIDOC's Person class replace the use of FOAF? Or should we consider including both?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/cwrc/ontology/issues/432#issuecomment-967406616, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAEFJIDK5DH5A4PHYHIBZH3ULVURZANCNFSM4FOVTP4Q. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
But we need to check in with @alliyya first—maybe she can show you how to update the extraction scripts when it comes to making this kind of change so that things are kept in sync?
On Nov 12, 2021, at 7:14 PM, Susan Brown @.**@.>> wrote:
Let’s go with the CIDOC Person Class instead.
On Nov 12, 2021, at 2:40 PM, JasmineDW @.**@.>> wrote:
CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to @.**@.>
@SusanBrownhttps://github.com/SusanBrown let's discuss this. Can CIDOC's Person class replace the use of FOAF? Or should we consider including both?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/cwrc/ontology/issues/432#issuecomment-967406616, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAEFJIDK5DH5A4PHYHIBZH3ULVURZANCNFSM4FOVTP4Q. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Can we create a single FOAF person entity for this that we can use for attribution for now for the sources of annotations?
Something like:
Orlando Project creators a foaf:person skos:description http://orlando.cambridge.org/public/svDocumentation?formname=t&d_id=CREDITSANDACKNOWLEDGEMENTS
Does this seem like a feasible strategy?
Longer term will be to ask all Orlando contributors if they want themselves created as persons in the ontology and probably to do so in combination with getting them to get an ORCID ID.