Changes between Version 15 and Version 16 of MDServiceImpl

Timestamp:

08/16/10 09:27:30 (14 years ago)

Author:

vronk

Comment:

--

MDServiceImpl

@@ -91 +91 @@
    * provide the RelationSets to the user
    * perform query expansion based on the relations provided by the RelationRegistry
+ * implement a simple ResourceViewer (just handle the ResourceRefs -> open in iframe or new window)
 
 === Open questions ===
@@ -96 +97 @@
   * search any substring in any field
   * exact match on selected fields
- * handling of data-categories (they have to be resolved to Element-names as MDRepository is unaware of Datacategories)
-   -> MDRecords should have the usual schema-reference in the root-element, (at least those produced by Avril) and the schema references the used components via `ComponentId` so it should be possible to work with identities (instead of just element-names). However the schema-reference is not present yet in the test-data and is also hardly to be guaranteed from other data-providers. Furthermore this would make the querying a lot more complexer, so we have to find intelligent ways to employ it (eg using the identity-based querying only when dealing with ambiguity).
+ * handling of data-categories - they have to be resolved to Element-names as MDRepository is unaware of Datacategories
+   This is not exactly true. MDRecords should have the usual schema-reference in the root-element, (at least those produced by Avril) and the schema references the used components via `ComponentId` so '''it should be possible to work with identities''' (instead of just element-names). However the schema-reference is not present yet in the test-data and is also hardly to be guaranteed from other data-providers. Furthermore this would make the querying a lot more complex, so we have to find intelligent ways to employ it (eg using the identity-based querying only when dealing with ambiguous queries).