CSPACE-2671: Clarified note re contentDate field to confirm that no work related...

diff --git a/services/collectionobject/3rdparty/nuxeo-platform-cs-collectionobject/src/main/resources/schemas/collectionobjects_common.xsd b/services/collectionobject/3rdparty/nuxeo-platform-cs-collectionobject/src/main/resources/schemas/collectionobjects_common.xsd
index d5587c7220e33c969ecb63360bb090377bfac6ec..33dff6582b2ba09f5d42d5a27c5dbe80ce50c0db 100644 (file)
--- a/services/collectionobject/3rdparty/nuxeo-platform-cs-collectionobject/src/main/resources/schemas/collectionobjects_common.xsd
+++ b/services/collectionobject/3rdparty/nuxeo-platform-cs-collectionobject/src/main/resources/schemas/collectionobjects_common.xsd
@@ -92,10 +92,12 @@
             </xs:sequence>\r
         </xs:complexType>\r
     </xs:element>\r
+    <!-- Note: Penelope's repeatability spreadsheet identifies a Content Date -->\r
+    <!-- repeatable group, containing contentDate and dateAssociation fields. -->\r
+    <!-- Did not find the dateAssociation field in the wiki schemas, however.  -->\r
+    <!-- contentDate is itself a structured date field, containing a dateAssociation -->\r
+    <!-- field, so perhaps this may merely be a product of some confusion. -->\r
     <xs:element name="contentDate" type="xs:string"/>\r
-    <!-- FIXME [1.0 alpha] Penelope's repeatability spreadsheet describes a Content Date -->\r
-    <!-- repeatable field, with contentDate and dateAssociation fields.  Did not -->\r
-    <!-- find the latter in the wiki schemas, however.  contentDate is a structured date field. -->\r
     <xs:element name="contentDescription" type="xs:string"/>\r
 \r
     <!-- FIXME Start of Content event name repeatable group -->\r