Skip to topic | Skip to bottom
Home

RDFTM
RDFTM.RequirementsUseCasesr1.4 - 27 Apr 2005 - 18:02 - FabioVitalitopic end

Start of topic | Skip to actions

This is Valentina's proposed approach for the definition of a (side) document containing the description of a set of use cases and requirements. Basically, the idea is to motivate the identified requirements using some possible real scenarios. There are two analogous W3C documents that can be used as a reference: OWL Use Cases and Requirements and RDF Data Access Use Cases and Requirements.

Use Cases and Requirements

This document presents a number of use cases which motivate the identified requirements that need to be supported by the RDFTM Guidelines?.

1 Use Cases

1.1 Web portals and search tools

A web portal is a web site that provides information content on a common topic and is a starting place for locating interesting content on a specific domain of interest. This content can be in part collected by a set of other sites considered authoritatives. The use of Semantic web ontologies helps, among the other things, to support one of the most important and used services that a web information portal provides: the search tool. A very important aspect that a semantic/conceptual search tool has to support is ontology interoperability. In fact, a web portal representing a wide domain of knowledge can rely on more than one ontologies which could be also defined either with RDF or TM.

Motivates: Queries, Advises for authors, Full translation

1.2 Migration and compliance

An information system the content of which is decorated with meta-information using one of the two paradigms, that needs to become available on the Semantic web and that wants to maintain the compatibility with the query languages related to both paradigms.

Motivates: Merge of data, Reuse of vocabularies, Queries, Use of RDF, RDFS, OWL and TMDM, Single vocabulary

1.3 Developers of tools and users

A company which develops a tool supporting the management of documents written using either RDF or TM, their editing, navigation, conversion and storing. The users of this type of tool, both experts and not, should be supported in creating and managing contents in order to ensure interoperability compliance.

Motivates: Unguided translation, Guided translation, Problematic issues, Advises for authors, Full translation, Round tripping

2 Requirements

2.1 MUST
Merge of data
2.1.1 Merge of data
Data originating in one paradigm must merge cleanly with data originating in the other.

2.1.2 Reuse of vocabularies
Vocabularies must be reusable across the two paradigms.

2.1.3 Queries
Queries written against one model must be usable with data translated from the other.

2.1.4 Unguided translation
Useful translations must be possible in the absence of mapping information specifically intended to guide the translation.

2.1.5 Guided translation
It must be possible to provide specific mapping information in order to achieve an optimal (guided) translation.

2.1.6 Problematic issues
Constructs that cannot be handled by the translation mechanism (if any) must be specified in the Guidelines.

2.1.7 Advises for authors
Advice must be given to authors on how to ensure maximum interoperability.

2.1.8 Determinism
The results of a translation must be deterministic.

2.2 SHOULD

2.2.1 Round tripping
Round-tripping should be possible with both guided and unguided translations.

2.2.2 Event-based processing
It should be possible to implement the translation using event-based processing.

2.2.3 Use of RDF, RDFS, OWL and TMDM
Properties and classes defined in RDF, RDFS, OWL, and TMDM should be used where possible in order to aid and guide translations.

2.2.4 Single vocabulary
There should be just one vocabulary that covers both directions and can be expressed in either RDF or Topic Maps.

2.2.5 Guided translation vs. unguided translation
The results of a guided and an unguided translation should be as similar as possible.

2.2.6 Full translation
The translation mechanism should be capable of handling every possible construct in the source paradigm.
to top

You are here: RDFTM > RDFTMMappingGuidelines > RDFTMInteroperabilityGuidelines > RequirementsUseCases

to top

Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Fabio's Wiki? Send feedback