Re: The Great Public Linked Data Use Case Register for Non-Technical End User Applications

Barry 


The sort of thing that I might envisage recording on the register is this (if not too onerous). Please suggesta different format if this is too rigid.


User Requirement: A description of the general requirement that would be addressed by an RDF application approach.

Audience: The main user groups for an application. 


Particular Benefit of using RDF: Why RDF enhances or makes the initiative possible  


Domain: The sector in which the requirement is needed.

Current Status: What progress has been made in addressing the requirement using Linked 'RDF' Data.

Approach and Techniques: What additional elements are needed along with RDF to achieve the requirement.


Related Initiatives: Projects or initiatives that have some relationship to this requirement.

Contacts: People involved in satisfying the requirement

I will start off with one of my own examples.


User Requirement: The ability to harmonise different cultural heritage catalogue (object) records (using a set of agreed generalisations) so that they can searched as a single collection. This can then be used to co-reference terminology, people and places, infer new information and expose potential relationships between different cultural heritage (or other) objects. An application that supported this type of analysis would be of huge benefit to cultural heritage organisations (curators) and humanities researchers (High Eduication) and would challenge exisiting work and conclusions that has relied on traditional manual methods of enquiry. It could also be used for highly innovative general engagement or education applications. It would also support a range of other applications covering a wide range of audience type. 


Audience: The interface must be usable for people who are basic computer users but which understand basic cultural heritage terminology.


Particular Benefit of RDF: The particular benefit is that data can be brought together without losing important institutional metadata (squeezing data into a common set of fields) 

and the contextual nature of the original source is preserved in the RDF triples. The system makes heavy use of inference and reasoning. 


Domain: Cultural Heritage with wider implications.


Currrent Status: A working prototype of the search system has been created and different RDFdatasets are being loaded (see www.researchspace.org). A specification for co-referencing is in draft and due for development during 2013. 


Approach and techniques: Context is provided using the CIDOC-CRM ontology. The system uses the OWLIM SE triplestore. Backend uses JAVA and the user interface mainly uses Javascript. 


Related Initiatives: Not known

Contacts: Dominic Oldman, British Museum, ResearchSpace (www.ResearchSpace.org).

I should find a place to display the harvested posts...



Dominic









________________________________
 From: Barry Norton <barry.norton@ontotext.com>
To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> 
Cc: public-lod <public-lod@w3.org> 
Sent: Sunday, 23 June 2013, 12:46
Subject: Re: The Great Public Linked Data Use Case Register for Non-Technical  End User Applications
 


Not published yet - exemplar applications go in EUCLID's Module 5, which we'll consult the list on, as we did for Modules 3 and 4.

We'll also include it in an endpoint for the SKOS/schema.org version of the syllabus, which I'm now honour-bound to publicly release now our project review's done.

Stand by for a message from Maria Maleshkova at KIT, where they compile the syllabus...

Barry



On 23/06/13 12:41, ☮ elf Pavlik ☮ wrote:
> Excerpts from Barry Norton's message of 2013-06-23 11:16:16 +0000:
>> Dominic, I think this is a great idea - the W3C lists suffer both from
>> senescence and fatigue (i.e., they're out-of-date and seem not to get
>> refreshed with new examples).
>> 
>> May I be presumptuous enough to offer to help/steal from the EUCLID
>> project, where we're already compiling such a list (and ResearchSpace is
>> already on it ;) )?
> where do we find this list? :)