Changes between Version 11 and Version 12 of DASISH/Compliance with Open Annotation Data Model


Ignore:
Timestamp:
05/17/13 14:02:22 (11 years ago)
Author:
olhsha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DASISH/Compliance with Open Annotation Data Model

    v11 v12  
    1818= Target Sources =
    1919
    20 Single target sources are represented as instances of {{{oa:SpecificResource}}}.
     20Single target sources are represented as instances of {{{oa:SpecificResource}}}. Example:
    2121
    2222[[Image(source.png)]]
    … …  
    2626= Users =
    2727
    28 A user or a group of user is an agent, and for agents "Open Annotation" standart recommends to use {{{foaf}}} namespace, see [http://xmlns.com/foaf/spec/]. This data model is designed for social networks, and in principle suits DASISH schema for a user and permission lists. There is one little technical inconvenience: {{{foaf}}} agents  do not have a property which can be used to define permission types  (owner, reader, writer) directly. For now, permissions are represented via property {{{foaf:topic_interest}}}.
     28A user or a group of user is an agent, and for agents "Open Annotation" standart recommends to use {{{foaf}}} namespace, see [http://xmlns.com/foaf/spec/]. This data model is designed for social networks, and in principle suits DASISH schema for a user and permission lists. There is one little technical inconvenience: {{{foaf}}} agents  do not have a property which can be used to define permission types  (owner, reader, writer) directly. For now, permissions are represented via property {{{foaf:topic_interest}}}. Example:
    2929
    3030[[Image(users.png)]]
    … …  
    3232= Bodies =
    3333
    34 An annotation body in DASISH can be any correct xml. A generic way to present such bodies in "Open Annotation" is to consider a body, which (typically) has attributes and elements, as instances of {{{oa:Composite}}}. Any element and any attribute of the body becomes an {{{oa:item}}} of the body. If an element  has sub-elements, it is an instance of {{{oa:composite}}} as well, etc. An attribute or an element with now sub-elements has one of the {{{dctypes}}} and one of the {{{dc:formtat}}}s, and possibly additional relevant properties, such as {{{cnt:chars}}} for text values.
     34An annotation body in DASISH can be any correct xml. A generic way to present such bodies in "Open Annotation" is to consider a body, which (typically) has attributes and elements, as instances of {{{oa:Composite}}}. Any element and any attribute of the body becomes an {{{oa:item}}} of the body. If an element  has sub-elements, it is an instance of {{{oa:composite}}} as well, etc. An attribute or an element with now sub-elements has one of the {{{dctypes}}} and one of the {{{dc:formtat}}}s, and possibly additional relevant properties, such as {{{cnt:chars}}} for text values. Example:
     35
     36[[Image(annotation.png)]]
     37
     38Another example:
     39
     40[[Image(AnnotationUGOT.png)]]
    3541
    3642= Headlines =
    … …  
    4046= Notebooks =
    4147
    42 Open Annotation does not define structures like "notebook" or "annotations collection", or similar. Nevertheless,  a notebook can be presented as an annotation which body is {{{title}}} and target {{{Annotations}}} is an instance of {{{oa:Composite}}}. Any annotation in the notebook becomes an {{{oa"item}}} of {{{Annotations}}}.
     48Open Annotation does not define structures like "notebook" or "annotations collection", or similar. Nevertheless,  a notebook can be presented as an annotation which body is {{{title}}} and target {{{Annotations}}} is an instance of {{{oa:Composite}}}. Any annotation in the notebook becomes an {{{oa"item}}} of {{{Annotations}}}. Example:
    4349
     50[[Image(notebooks.png)]]