Changes between Version 1 and Version 2 of CmdiMetadataServices

Timestamp:

07/27/09 11:05:52 (15 years ago)

Author:

vronk

Comment:

--

CmdiMetadataServices

@@ -2 +2 @@
 
 It interacts with:
-* Metadata Repository (as consumer)
-* Relation Registry (as consumer)
-* Metadata Browser (as provider)
-* Virtual Collection Registry (? as consumer/provider?) 
-* external Applications (as provider)
+ * Metadata Repository (as consumer)
+ * Relation Registry (as consumer)
+ * Metadata Browser (as provider)
+ * Virtual Collection Registry (? as consumer/provider?) 
+ * external Applications (as provider)
 
 MDService accepts queries about metadata from MetadataBrowser (and external Applications) and passes them to the Metadata Repository(ies) (MDRep) and/or to the Virtual Collection Registry, optionally making use of the Semantic Mapping service provided by the Relation Registry, receiving results and passing them back to the requesting node.
 
 The main competencies/tasks/functions are:
-provide Vocabularies:: 
+ provide Vocabularies:: 
   (out of existing schemas)   
   for the end-user (and user-agent)   
   needed to be able to formulate a query
-translate::
+ translate::
   from Vocabulary-based user query to XPath/XQuery for the MDRepository
   (and consequently communicate with MDRepository)
@@ -21 +21 @@
 
 Further possible functionality:
-publish VirtualCollections::
+ publish VirtualCollections::
   one natural place for creating VirtualCollections seems to be the MD Browser 
   some components needs to care for passing the Metadata about the newly created Virtual Collection to the Virtual Collection Registry. As MDService will be very well informed about the user queries and data, it seems to be a good candidate for handling this, ie register user's VirtualCollection in the VCR.
 
-
-
 There seem to be following alternatives for the deployment mode/node for MDService:
-1. MD-Repository (near to data, good for computings)
-1. CMDIPortal  
-1. Client (could skip web-UI (CmdiPortal) and talk directly to MetadataRepository)
+ 1. MD-Repository (near to data, good for computings)
+ 1. CmdiPortal  
+ 1. Client (could skip web-UI (CmdiPortal) and talk directly to MetadataRepository)
 
 == Interface Definition ==
 This is a first shot on methods MDService has to provide on its query-API:
+{{{
  .listRepositories()
  .listSchemas()
@@ -40 +39 @@
  .stats(Repository)
    .countMetadataEntries()
- 
+}}}
+
 An optional separate interface for publishing Resources (not the OAI-PMH way, so MetadataRepository would have to provide something corresponding).
+{{{
  .publishResource(Repository,MD,Schema)
+}}}
+
 Relevant resources could be 
-1. VirtualCollections, 
-1. users' "private" Resources she wants to share or 
-1. new Resources as results of some processing of existing ones.
+ 1. VirtualCollections, 
+ 1. user's "private" Resources she wants to share or 
+ 1. new Resources as results of processing existing ones.