Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect transcriptions of ROI to instances of oa:TextualBody #25

Closed
arnikz opened this issue Jun 30, 2020 · 3 comments
Closed

Connect transcriptions of ROI to instances of oa:TextualBody #25

arnikz opened this issue Jun 30, 2020 · 3 comments

Comments

@arnikz
Copy link

arnikz commented Jun 30, 2020

Currently, oa:Annotation instance links directly to oa:TextualBody and dwc:Taxon instances:

<http://makingsense.liacs.nl/rdf/nc/annotation/a5b4aaa3-42b4-4046-a05b-a506e01aaf2f>
a <http://www.w3.org/ns/oa#Annotation>;
<http://purl.org/dc/terms/creator> <http://orcid.org/0000-0002-2146-4803>;
<http://purl.org/dc/terms/date> "2017-09-21";
<http://www.w3.org/ns/oa#hasBody> <http://makingsense.liacs.nl/rdf/nc/taxon1>, _:node1ec3i5nr1x861 .

@lisestork: Should we link the two instances with rdf:value predicate [1]?

@lisestork
Copy link

lisestork commented Jul 20, 2020

See also #28 (comment). I believe the dwc:Taxon instance should be directly connected to the oa:Annotation instance via the oa:hasBody property, and the "motivation": "classification".

@arnikz I agree that for the transcription of the region of interest, the transcription should indeed be attached to a blank node using the predicate rdf:value as in example 15

@arnikz
Copy link
Author

arnikz commented Aug 17, 2020

I think, using oa:TextualBody just for this

_:node1ec3i5nr1x861 a <http://www.w3.org/ns/oa#TextualBody>;
<http://purl.org/dc/terms/format> "text/plain";
<http://purl.org/dc/terms/language> "la" .

without this

<http://www.w3.org/2000/01/rdf-schema#label> "Pteropus minimus"@la .

is not that useful.

@lisestork
Copy link

lisestork commented Aug 18, 2020

Yes, I agree. In that case it is not so useful.

I think it would be good to have two bodies if a piece of text is both classified and transcribed, as we can record the two different purposes (although there is no 'transcribing' motivation tag, just 'describing'). Maybe it should be an option in the interface, so that the classification or the transcription can also be recorded separately.

textualbody: example 5 (transcribing/describing)
class from nhc: example 44 (classifying)

@arnikz arnikz changed the title Connect instances of oa:TextualBody to dwc:Taxon Connect transcriptions of ROI to instances of oa:TextualBody Aug 26, 2020
arnikz pushed a commit that referenced this issue Aug 26, 2020
arnikz pushed a commit that referenced this issue Aug 26, 2020
@arnikz arnikz closed this as completed Jan 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants