Re: Curating the Goals of Use Cases

Hi Mark,

Sorry for the lag.
But--lo and behold!-- I'm going now to try and play my shepherd role, and react to your mail.


> ----------------------------------------------------------------------
> http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Publishing_20th_Century_Press_Archives
>
> 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 on METS/MODS.
>
> --> URIS
> --> REUSE-SCHEMAS (METS/MODS)
> --> SEARCH/BROWSE
> --> LINK-VOCABS
>
> 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.
>
> --> PUBLISH RDFa, HTML
> --> SEARCH/BROWSE


I think the P20 case really has aggregation of resources high on its agenda: there are "folders" (but they already exist prior to the use case) and even, serving aggregations of search results is mentioned) so I think it should mention ASSOCIATE--or at least RELATE-- (in your new terminology at [2]) somewhere.


> ----------------------------------------------------------------------
> http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Digital_Text_Repository
>
> 1. Explore the text repository through rich interlinks between works, authors, and topics.
>
> --> SEARCH/BROWSE
>
> 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)
>
> --> SEARCH/BROWSE ??
>
> 3. Expose and share entities from digital text repositories ensuring maximal discoverability and ease of delivery.
>
> --> URIS
> --> PUBLISH RDF


I think you captured 1 and 3 properly. 2 is more orentied towards the production of data. As said, they want to prepare new digital editions of texts, new "Manifestations (in FRBR terms)". The description then mentions "related items" and "authority data" as two specific foci. I would thus categorize this second goal aspect using REUSE-VALUE-VOCABS and ASSOCIATE from [2].

Hoping this is useful,

Antoine

[2] http://www.w3.org/2005/Incubator/lld/wiki/Goals


> Hi,
>
> 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?
>
> Best,
> Mark
>
> ----------------------------------------------------------------------
>
> 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. mappings.
>
> 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
>
> ----------------------------------------------------------------------
>
> http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Enhanced_Publications
>
> (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.
>
> --> PUBLISH RDF
> --> RELATIONS-NEW
>
> (2) reuse of schemas and vocabularies simplifies publishing, searching and reuse of enhanced publications and materials associated with them.
>
> --> REUSE-SCHEMAS
> --> SEARCH/BROWSE
>
> ----------------------------------------------------------------------
> http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Publishing_20th_Century_Press_Archives
>
> 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 on METS/MODS.
>
> --> URIS
> --> REUSE-SCHEMAS (METS/MODS)
> --> SEARCH/BROWSE
> --> LINK-VOCABS
>
> 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.
>
> --> PUBLISH RDFa, HTML
> --> SEARCH/BROWSE
>
> ----------------------------------------------------------------------
> http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_NDNP
>
> 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.
>
> --> LINK-VOCABS
>
> 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.
>
> --> PUBLISH RDF
> --> (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
>
> ----------------------------------------------------------------------
> http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Digital_Text_Repository
>
> 1. Explore the text repository through rich interlinks between works, authors, and topics.
>
> --> SEARCH/BROWSE
>
> 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)
>
> --> SEARCH/BROWSE ??
>
> 3. Expose and share entities from digital text repositories ensuring maximal discoverability and ease of delivery.
>
> --> URIS
> --> PUBLISH RDF
>
> ----------------------------------------------------------------------
>
> http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Collecting_material_related_to_courses_at_The_Open_University
>
> (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”
>
> --> SEARCH/BROWSE
>
> (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
> --> PUBLISH RDF
> --> LINK-VOCABS
>
>

Received on Thursday, 11 November 2010 11:18:28 UTC