Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

Data model (ontology) for Data Basket

Basket Data Model


We try to reuse established ontologies as much as possible. We considered using the latest version of Open Annotation (OA) as a basis, but gave up on this idea.In order to have a simple and coherent model, Data Basket uses the same basis as Data+Image Annotation: Open Annotation Collaboration (OAC). Still, we use some approaches from OA, eg ore:Aggregation.

We map entities from the Data Basket Spec 3.5 to the following:

Entity Description Mapped to
Basket List of Bookmarks, owned by a particular user ore:Aggregation
Bookmark Pointer to an Item, made by particular user, with optional description oac:Annotation
Target Item RS URI or web URL or pure text, (in some cases) having Preview, short URL, creator see Item Types
  • Jana: why do we need a Basket?
    • Vlado1: To distinguish the bookmarks of one user from those of another
  • Jana: if Bookmark's type is oac:Annotation, how can we distinguish from other annotations, eg forum posts?
    • Vlado1: I think it can be distinguished by the fact that it's in a Basket. We never search for "all annotations", we search for annotations related to something (an Object, a Basket...)
      If we need a specific type then I'll add one. In fact OA has such: oax:Bookmark (but they oscillate between using types and using a separate field called oa:hasMotivation)


We use the following prefixes:


A Basket is a bag of Bookmarks (represented as ore:Aggregation), owned by a particular user. Fields:

Field Property
Owner dcterms:creator
Bookmarks ore:aggregates


  • A basket is created when the first bookmark is being added (on demand)
  • A basket is never deleted, even on action Clear All

Basket Example

<> a ore:Aggregation;
  dcterms:creator "username2";
  ore:aggregates <>, <>.
  • For now users are represented with a Nuxeo username, not with URI
  • TODO Jana: Can the given URI patterns be implemented?


Each bookmark resides in a basket and points to a target item (URL). Fields:

UI Field Property (path) Applicability and Notes
  rdf:type oac:Annotation (fixed value). Distinguished from other Annotations by residing in a Basket
Type oac:hasTarget/rdf:type All except Text Snippet. See Item Types
Preview rso:hasTargetPreview Image/Image Annotation: RS image URL. Web Link: URL from Web Preview service
Created by oac:hasBody/dcterms:creator  
Created on oac:hasBody/dcterms:created  
Title oac:hasBody/rso:P3_has_title Plain text. Copied from Item and shortened to 30 chars
Notes oac:hasBody/rso:P3_has_description Rich text. No default value
URL (Item) oac:hasTarget All except Text Snippet
Short URL rso:hasTargetShortURL From URL Shortening service
Item created by oac:hasTarget/dcterms:creator Only for Data/Image Annotation
Item created on oac:hasTarget/dcterms:created Only for Data/Image Annotation


  • Applicability describes for which item types that field is applicable, and gives extra notes
  • The following fields shown on Data Basket UI design don't really exist: Sent by, Tags, Last updated


  • oac:hasBody/dcterms:creator and created are set from the current user and datetime when the bookmark is created.
    They are preserved if the bookmark is copied to another basket.
  • oac:hasTarget/dcterms:creator and created are present only for 2 item types. They alraedy exist, they are not added when the bookmark is created.

Bookmark Example

<> a oac:Annotation;
  oac:hasTarget <>;
  rso:hasTargetShortURL <>;
  rso:hasTargetPreview <>;
  oac:hasBody <>.

<> a foaf:Document. ## Note1

<> a oac:Body;
  dcterms:creator <>;
  dcterms:created "2012-10-08T12:34:56"^^xsd:dateTime;
  rso:P3_has_title "Wikipedia";
  rso:P3_has_description "Wikipedia is a world-wide collaboratively-created encyclopedia".

In the graphical examples below, a green circle indicates a pre-existing statement. All others are created when a bookmark is created.

Item Types

Target Items can have one of the following types.

  • Vlado1: It's important that we use the normal rdf:type property, since the type is attached to the item (target node) and not to the bookmark through a customproperty
Type Name Type Icon Comments
Data Annotation rso:DataAnnotation see Annotation with OAC and Reification
New subclass of oac:Annotation that allows the Basket code to recognize more easily the item type.
TODO Mitac & Stanislav: Change the Data & Image Annotation backend to use rso:DataAnnotation and rso:ImageAnnotation
Forum   Not in RS3.5
Image crm:E38_Image Dominic: we don't have a display of the image only, so do we need this? Vlado: Yes - we will need this soon
TODO Vlado: if we need it, change RKD mapping to make explicit image URL instead of has_image_file and attach E38 (BM mapping does that)
Image Annotation rso:ImageAnnotation see Image Annotation Design#Example.
New subclass of oac:Annotation: see comment of Data Annotation
Object rso:FC70_Thing This class is set by a rule in FR Implementation
Object Field rdf:Statement see Annotation with OAC and Reification.
When an AP is added to Basket, this Statement is created, same as making annotation or a link to AP
Search rso:Search new class. It has one field P3_has_note storing the textual representation of the search
Text Snippet (none) Does not have item URI, therefore no type. Its title and content (rich-text description) are saved in Bookmark's body
TODO Svetoslav & Stanislav: assume that no type means Text Snippet
Web Link foaf:Document New class with no fields.
TODO Svetoslav: add statement as per ## Note1 above

Re Search:

  • Vlado: should the rso:Search node be created when the Search is put in history, or only when it's put in basket?
  • Jana: History is currently stored in Nuxeo
  • Vlado1: I understand, but I thought we'd be storing the history same as the bookmarks? The question is who & when will create the node


Dominic: The specification is written specific according to existing tools. However, the way that the data basket works should be generic for existing and new tools to come. The production version of research space will require an API that means that all tools that adhere to it can be accessed and inetgrated with the databasket tool. This means that there must be a consistent type of URI / URL with tool parameter so that tools can be launched and placed in the appropriate state. These links should be ones that could be used as a normal web link in a browser (RESTful) so that the links could be used outside the databasket using a simple browser address box. To this end the specification should also have a technical specification outlining the way in which the databasket would interact with the ResearchSpace environment


  • I agree that bookmarking should be more in the style of using "browser address box". However, our URIs are currently not resolvable, see RS URLs and URIs.
    Adding a new item type ("tool") to the basket is a matter of adding it to the table above, and to frontend handling code (different types have somewhat different handling behavior).
  • For full extensibility the Basket should be able to figure out the item's type from the item URI alone. That is the case above, except for Web Link (for which we need to add a type statement upon adding to basket).
    • I've used "a foaf:Document" above (that's the range of foaf:homePage)
    • OA recommends using "a dcmitype:Text; dc:format "text/html" which I don't find very nice (and may change)
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.