search

LINNAE-project / SFB-Annotator

This web app is intended for demo purposes only!
https://www.research-software.nl/software/sfb-annotator
Apache License 2.0
1 stars 0 forks source link

Update documentation of use cases #18

Closed arnikz closed 3 years ago

arnikz commented 4 years ago

Update in 5b83310a54256ce5d8962036deb7fc59f0bc9aa5.

lisestork commented 3 years ago

Update use case (minimal mandatory triples created for each annotation example + optional triples) in 4543f66959fbe7166094c2686e25700532b2f4e6

arnikz commented 3 years ago

@lisestork: please replace dummy instances of:

in example_1_2 with real values if possible.

arnikz commented 3 years ago

@lisestork: TYPEs must be established prior making links between them (via GUI) in so-called OBSERVATION RECORDs. Is my assumption correct?

lisestork commented 3 years ago

@lisestork: TYPEs must be established prior making links between them (via GUI) in so-called OBSERVATION RECORDs. Is my assumption correct?

True, although technically links can also be established first as properties have a fixed domain and range. Unless an entity is annotated with only a type.

arnikz commented 3 years ago

Somewhat related: if you make this distinction (i.e., TYPE vs. OBSERVATION RECORD) then you have to draw a bounding box for a TYPE(s) but not for the OBSERVATION RECORD(s) that connects two TYPEs (e.g., taxon & location). Moreover, this translates to different input forms that shouldn't overlap as it is now.

lisestork commented 3 years ago

@lisestork: please replace dummy instances of:

in example_1_2 with real values if possible.

Reason sfor minting URIs for abstract concepts

The instances can serve as anchor points to which resources [...] may be linked. Because of this cross-institutional and cross-community anchoring function, DSW expects that most resources will be identified by persistent HTTP URIs or HTTP-proxied versions of globally unique identifiers in accordance with the TDWG GUID Applicability Statement Standard (https://www.tdwg.org/standards/guid-as/, https://github.com/tdwg/guid-as/blob/master/guid/tdwg_guid_applicability_statement.pdf). (Baskauf, S. J., & Webb, C. O. (2016). Darwin-SW: Darwin Core-based terms for expressing biodiversity data as RDF. Semantic Web, 7(6), 629–643. https://doi.org/10.3233/SW-150203)

Primary goal of the DSW is to facilitate the linking of real data. Globally unique URIs should be generated for abstract concepts, such that metadata related to these concepts can be found in the text and attached to these concepts, in line with the Darwin Core specifications (https://dwc.tdwg.org/list/).

e.g.: ex:organism1 dwc:organismRemarks "Wir erhielten sie met den Jungen"

The entities of the ontology serve as a backbone for such metadata, and should be generated during annotation of entities that can be found explicitly on the page, such as a taxonomic name, location, person name, anatomical entity, and property or fact.

README.md will be updated to reflect this

arnikz commented 3 years ago

Reason sfor minting URIs for abstract concepts...

I agree with this, however, please provide concrete examples for the remaining instances rather than

e.g.: ex:organism1 dwc:organismRemarks "Wir erhielten sie met den Jungen".

lisestork commented 3 years ago

Reason sfor minting URIs for abstract concepts...

I agree with this, however, please provide concrete examples for the remaining instances rather than

e.g.: ex:organism1 dwc:organismRemarks "Wir erhielten sie met den Jungen".

See: iss18-URI-annotations

arnikz commented 3 years ago

Btw dwc:*Remarksare written here in English but the corresponding pages.are written in German. @lisestork: I think, these should be verbatim (in iso:ger). Could you provide the transcriptions to update the input JSON files and/or RDF data models accordingly (related to #81)?

arnikz commented 3 years ago

Could you provide the transcriptions to update the input JSON files and/or RDF data models accordingly (related to #81)?

This won't be necessary.