Annotation
Names
Annotation, Web Annotation, Semantic Annotation
(es) Anotación, Anotación Web, Anotación Semántica
Definition
A Web Annotation/Semantic Annotation is information added on an original text or resource. The original resource itself is not altered.
Examples
- A comment in a blog entry/forum
- A categorization (attaching a label to a content)
- Linking to complementary resources (transcripts, translations, content dissection, etc)
- Moderation/Evaluation scores (readers telling whether it is worthy reading)
- Linking to centralized reference for that work / concept / etc
Observations
- An annotation itself might be subject to annotation
Analysis
W3C Annotea/Amaya implement RDF annotations. @@@ CHECKPOINT: Consider whether that is adequate @@@
Data
- (field) annotation subject
- resource URI
- locator in resource
- propagation (to alternate media types, languages, rephrasings)
- (field) annotation type : As in RDF properties, might be an URL
- (field) annotation payload (might contain the rest/many of the other fields)
- (field) annotation id (might refer to a RDF object with the payload and the rest of
- (field) annotation permisions (who can display,edit)
- (field) annotation owner(s), followers.
- (field) timestamps
- (field) flags/system tags (e.g. pending revision, schedulled for deletion)
Observations
- We might enforce for the annotations to be done on a resource's reference (with an internal URI) rather than on the resource URI itself. Then the only annotation on the resource itself might be the reference annotation.
- ? Any problems if many annotations of the same type are made on the resource
Types of Annotation
- Reference Related
- Reference Annotation. If part of a resource, then provide the range within the complete reference
- Summary
- Equals/Equivalent To: Repetition of content. Applied annotations might be merged
- AlternativeMedia: Different language or media type
- Text Comment related
- Untyped Comment
- Question: Ask the author (or other readers) for clarification
- Answer: Propose an answer to a (non-rethoric) question
- Objection: Report bad data or argumentation
- Antagonist: Expose an alternative hypothesis/proposal
- AlternativeExpression: Same concept in different words
- Review Related
- Review
- Review Call/Seal of Approval: Ask authorized peers/authority to check
- Minor correction/Whisper to author
- CertaintyValoration: Certain,Consensus,EvenCertainty,Dubious,Discounted (based on the consensus, the state of objections, antagonists)
- ReadersValoration: Like/Dislike, Score out of 5. Might be as well an score in different categories (informative,readerFriendly,...)
- ValorationTags: As is Slashdot (Inspired,Informative,Funny ...).
- Content Extension
- Follow-up: Provide further detail on a point
- Spread: Introduce more concepts
- Weave: Interlink with other concepts
- Dive: Provide further detail about the topic
- TopicReference: The topic developed in a reference work (like an Enciclopedia)
- PrimarySource: Give credit of the concept from the source (primary research, historic chronicles, factual databases)
- Example
- Proof
- Because/Therefore? (Causality)
- Follow-up: Provide further detail on a point
- Link related
- Untyped (incoming) Link
- Categorization (As in Delicious bookmarks)
- Bibliographic link (what about a flag indicating that source is a peer-reviewed publication?)
Any user/application might provide additional annotations.
An annotation might have multiple types? (if infrequent, then might have a "compound" type, or non-core types specified on annotations on the annotation).
If many types are specified, it might be easy to use a wrong type. Power/Trusted user might be enabled/encouraged to edit the annotation metadata (including type).
Amaya provides types: Advice,Change,Comment,Example,Explanation,Question,SeeAlso