W3C home > Mailing lists > Public > public-xg-lld@w3.org > November 2010

Curating the Goals of Use Cases

From: Mark van Assem <mark@cs.vu.nl>
Date: Tue, 02 Nov 2010 16:04:59 +0100
Message-ID: <4CD0289B.9020308@cs.vu.nl>
To: public-xg-lld <public-xg-lld@w3.org>

I noticed that the description of goals tend to overlap, and worded 
completely different.

Can't we curate the different goals just as we did for Requirements and 
Topics? And then assign them "by code" to the UCs?

I went through the UCs in the Digital Objects cluster and came up with 
these Goals, see details below.

Would you agree this is useful?



URIS: provide URIs for entities in the UC [INSERT ENTITY NAMES]

RELATIONS: represent relationships between the entities that already 
existed in the data

RELATIONS-NEW: add relationships between the entities that did not exist 
yet in the original data

AGGREGATE: add aggregation relations between entities

PUBLISH: publish the data as {RDF, RDFa, HTML, ...}

SEARCH/BROWSE: provide search and browse facilities over the RDF data

REUSE-SCHEMAS: reuse of existing schemas {FOAF, ORE, ...} in publishing 
the data as RDF

REUSE-VOCABS: reuse existing vocabularies already published as LOD 
{LCSH, GTAA, ...} in publishing the data as RDF, i.e. replacing internal 
identifiers with URIs from these vocabularies.

LINK-VOCABS: link the published data to other LOD vocabulaires, i.e. 

API: provide an API to access / change the data.


Below follow the goal descriptions of the UCs in the DO cluster as they 
are now on the wiki, below that the goal(s) I would suggest it gets 
replaced with



(1) link scientific publications to material related to the publication, 
including data, models, additional illustrations, algorithms and other 
publications -- also known as enhanced publications. Allow search over 
and reuse of these materials.


(2) reuse of schemas and vocabularies simplifies publishing, searching 
and reuse of enhanced publications and materials associated with them.



    1. To give each and every collection, folder, document, page and 
even search result set a persistent identifier for citation and linking. 
To provide context from metadata and link to other data relevant to the 
domain. To support the use of a standard image and metadata viewer based 

--> URIS

    2. Combine Linked Data and REST principles to implement an 
application based on RDFa for presentation and OAI-ORE to structure and 
access the deeply nested aggregations.



    1. To give each newspaper title, issue and page a unique URL to 
enable citation.

--> URIS

    2. To contextualize newspaper content by associating it with other 
content on the web.


    3. To allow digital objects (titles, issued and pages) and their 
associated bitstreams (pdf, jp2, ocr/xml) to be meaningfully harvested 
out of the web application, so that the data can be re-purposed, and 
preserved elsewhere.

--> (something else depending of meaning of harvesting)

    4. To provide an API for third parties to use the content in their 
own environments without needing to harvest the actual content.

--> API


    1. Explore the text repository through rich interlinks between 
works, authors, and topics.


    2. Describe and catalog holdings of digital text repositories 
quickly (i.e. without much original research) and efficiently (i.e. 
without replication of much metadata)


    3. Expose and share entities from digital text repositories ensuring 
maximal discoverability and ease of delivery.

--> URIS



(1) In this scenario a student finds all the material directly related 
to their course/module as well as supplementary material based on direct 
links, cross-repositories such as subject classifications, as well as 
based on indirect (and possibly external) links such as “the people 
involved in the creation of the resources”


(2) This is realized by publishing relevant data sets as linked, where 
standardised URI schemes are used to connect Open University resources 
across repositories, as well as through external links, e.g. to datasets 
at the BBC, UK government, DBPedia and other publication/library 
resources. Common resources include subject classifications which are 
used to classify courses/modules, publications, A/V material and othes, 
which are expressed in SKOS and mapped to each other. We expect 
resources such as people, courses, topics and publications to play a 
central role in connecting Open University datasets to each other, and 
to external resources.

--> URIS

  Mark van Assem - Vrije Universiteit Amsterdam
Received on Tuesday, 2 November 2010 15:05:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:55 UTC