Skip to content

propose that target of annotation should be composite #2

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.

Sign up for GitHub

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

Open
smrgeoinfo wants to merge 1 commit into
base: master
Choose a base branch
from
Open

propose that target of annotation should be composite #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions populate/case_study.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,8 +286,8 @@ <h4>Body, Target and Annotation</h4>
</ul>
<p>In each of these cases, the annotation (the note, the keywords or the grant) are used to supplement the information of the underlying dataset. We consider this a “data-focused” annotation system, so the data record is most commonly the object being annotated. It is possible that an annotation can itself be annotated, or the body of an annotation.</p>
<p>An annotation assumes that each body applies to each target equally. This may not be the case, for example, we may want to generate an annotation for a dataset that both links it to a record from another database, and explains why the records are being linked. In this case, neither of the body elements can be considered independent of one another with respect to the target since the text must reference the URI and the URI relationship is not clear until addressed by the text annotation.</p>
<p>The OpenAnnotation standards provide the concept of a <a href="http://www.openannotation.org/spec/core/multiplicity.html#Composite">Composite</a>. In this case, the two body elements can be bound together, indicating that they must be considered in connection to one another, and then linked to the annotation.</p>
<p><code>body:(composite:((body1)(body2)))-annotation-target:()</code></p>
<p>The OpenAnnotation standards provide the concept of a <a href="http://www.openannotation.org/spec/core/multiplicity.html#Composite">Composite</a>. In this case, the two target elements are bound together, indicating that they must be considered in connection to one another, and then linked to the annotation body that expresses the relationship.</p>
<p><code>body:()-annotation-target:(composite:((body1)(body2)))</code></p>
<div id="annotation-properties" class="section level5">
<h5>Annotation Properties</h5>
<p>The annotation requires some secondary information if we are going to manage annotations across the data lifecycle. These include the <code>creator</code>, the <code>created</code> date/time stamp, the <code>generator</code>, the agent responsible for generating the reference, the date in which the serialization was <code>generated</code>, and then, potentially, <code>modified</code>.</p>
Expand Down