Changes between Version 4 and Version 5 of CmdiOverview


Ignore:
Timestamp:
07/16/09 20:50:59 (15 years ago)
Author:
vronk
Comment:

revised the issue of semantic mapping

Legend:

Unmodified
Added
Removed
Modified
  • CmdiOverview

    v4 v5  
    2222== 3. Metadata Search & Browsing Service ==
    2323
    24 The metadata search service & browsing is offered to users via (1) a GUI allowing users to create queries on the basis of the elements and vocabularies available in the repository and (2) a web service. The service can make use of the references to the concept registry and relation registries to make different components interoperable if their semantics overlap. It is at this moment not clear if this should be implemented by having a semantic normalization step before storing the metadata descriptions in the repository or (as is depicted in the figure) having a translation of a metadata query into different component-specific ones. The first possibility places more emphasis on correct description and being able to retrieve that description using a familiar vocabulary and while the second places more emphasis on harmonizing all semantic content by having a well chosen normalized vocabulary.
     24The metadata search service & browsing is offered to users via (1) a GUI allowing users to create queries on the basis of the elements and vocabularies available in the repository and (2) a web service. The service can make use of the references to the concept registry and relation registries to make different components interoperable if their semantics overlap. ~~It is at this moment not clear if this should be implemented by having a semantic normalization step before storing the metadata descriptions in the repository~~ or (as is depicted in the figure) having a translation of a metadata query into different component-specific ones. The first possibility places more emphasis on correct description and being able to retrieve that description using a familiar vocabulary and while the second places more emphasis on harmonizing all semantic content by having a well chosen normalized vocabulary. ''(As discussed in Nijmegen 2009-05-14, metadata must be stored in the [wiki:CmdiRepository] as provided by the metadata providers. Any semantic mapping will be the sole competency of [wiki:CmdiRelationRegistry] used by [wiki:CmdiMetadataServices] when resolving/expanding queries.)''
     25
    2526
    2627This text is derived from the CLARIN EU WP2 workdocument: [http://www.clarin.eu/node/2553 CLARIN metadata infrastructure]