Changes between Version 5 and Version 6 of proposals/SubTemplates

Timestamp:

May 31, 2011, 2:11:34 AM (13 years ago)

Author:

fxp

Comment:

--

proposals/SubTemplates

@@ -102 +102 @@
  * do we need more than full text indexing ? 
  * Sub template for simple element ? eg. gmd:abstract
- * Root element : how-to manage same types ? eg. gmd:pointOfContact, gmd:contact, gmd:citedResponsibleParty, gmd:distributorContact elements are all gmd:CI_ResponsibleParty. Root element is not enough to be able to decide where a sub-template could be inserted. For the contact gmd:CI_ResponsibleParty would be a better type identifier.
+ * Root element : 
+  * how-to manage same types ? eg. gmd:pointOfContact, gmd:contact, gmd:citedResponsibleParty, gmd:distributorContact elements are all gmd:CI_ResponsibleParty. Root element is not enough to be able to decide where a sub-template could be inserted. For the contact gmd:CI_ResponsibleParty would be a better type identifier.
+  * qualifiedName in the root column : maybe namespace is better ?
  * When adding a contact as sub-template, editor want to set his role (which could be different according to the record) ? How to set this as a parameter to the sub-template ?
  * should we use metadata import page to import sub template ? or a custom one ?