From 44d619ae94d5fc2e4ce0c6bf9ca0b74327175672 Mon Sep 17 00:00:00 2001
From: Aron Roberts <aron@socrates.berkeley.edu>
Date: Thu, 26 Feb 2009 04:09:27 +0000
Subject: [PATCH] CSPACE 12: Second iteration of RELAX NG schema for defining
 and validating an entity, and also - by way of example - a CollectionObject
 payload.  This iteration now defines a set of core fields common to every
 entity object, a base definition for each field in that object, and two
 different alternatives - one using infoBlocks, one without - for enclosing
 sets of related fields.  This set of schema now successfully validates a pair
 of test entity files, also included with this iteration.  There are also
 comments about how we might perform in-line validation using Schematron
 rules.

---
 sandbox/aron/schema/CollectionObject.xml      |  64 ++++++---
 sandbox/aron/schema/CollectionObject2.xml     |  95 +++++++++----
 .../schema/collectionObject-as-entity.rng     |  25 ++++
 sandbox/aron/schema/entity.rng                | 115 +++++++++------
 sandbox/aron/schema/entityCoreFields.rng      | 115 +++++++++++++++
 sandbox/aron/schema/entityField.rng           |  81 ++++++++---
 sandbox/aron/schema/entityFieldAttributes.rng | 131 ++++++++++++++++++
 7 files changed, 520 insertions(+), 106 deletions(-)
 create mode 100644 sandbox/aron/schema/collectionObject-as-entity.rng
 create mode 100644 sandbox/aron/schema/entityCoreFields.rng
 create mode 100644 sandbox/aron/schema/entityFieldAttributes.rng

diff --git a/sandbox/aron/schema/CollectionObject.xml b/sandbox/aron/schema/CollectionObject.xml
index b53a3bb39..9ad68b88b 100644
--- a/sandbox/aron/schema/CollectionObject.xml
+++ b/sandbox/aron/schema/CollectionObject.xml
@@ -2,29 +2,53 @@
 
 <!--
 
-	CollectionObject.xml
+	collectionObject.xml
 
-	A skeletal instance of an CollectionObject, represented as an XML document.
+	A hypothetical, somewhat skeletal instance of an CollectionObject payload,
+	represented as an XML document.
 	
 	This is	created for the CollectionSpace system, http://www.collectionspace.org/
 
 -->
 
-<entity>
-	<entityName>CollectionObject</entityName>
-  <usageNotes>
-    <!-- In-depth notes about usage and meaning go in this field -->
-  </usageNotes>
-  <fields>
-    <field
-      systemName="museumId"
-      displayName="ID"
-    	usageNotes="In-depth notes about usage go here"
-    	usageHint="Tooltip-type hints go here, such as 'Primary museum ID for this item'"
-      displayed="true"
-      lengthHint="20">
-      <!-- Field contents go here -->
-      pahma-collectionname-2007-06-09-00055
-    </field>
-  </fields>
-</entity>
+<collectionObject>
+
+	<entity>
+	
+		<usageNotes>
+			<!-- Optional notes about the usage and meaning of this entity go here. -->
+		</usageNotes>
+		
+		<coreFields>
+			<id></id>
+			<created></created>
+			<createdBy></createdBy>
+			<lastModified></lastModified>
+			<lastModifiedBy></lastModifiedBy>
+		</coreFields>
+		
+		<fields>
+			<field
+				systemName="objectNumber"
+				displayName="ID"
+				usageNotes="In-depth notes about usage go here"
+				usageHint="Tooltip-type hints go here, such as 'Primary museum ID for this item'"
+				displayed="true"
+				lengthHint="20">
+				<!-- Field contents go here -->
+				pahma-collectionname-2007-06-09-00055
+			</field>
+			<field
+				systemName="title"
+				displayName="Title"
+				usageNotes="In-depth notes about usage go here"
+				usageHint="Tooltip-type hints go here"
+				displayed="true">
+				<!-- Field contents go here -->
+				Paiute Basket
+			</field>
+		</fields>
+		
+	</entity>
+	
+</collectionObject>
diff --git a/sandbox/aron/schema/CollectionObject2.xml b/sandbox/aron/schema/CollectionObject2.xml
index 09b79ce2d..7c3d2e236 100644
--- a/sandbox/aron/schema/CollectionObject2.xml
+++ b/sandbox/aron/schema/CollectionObject2.xml
@@ -2,33 +2,80 @@
 
 <!--
 
-	CollectionObject.xml
+	CollectionObject2.xml
 
-	A skeletal instance of an CollectionObject, represented as an XML document.
+	A hypothetical, somewhat skeletal instance of an CollectionObject payload,
+	represented as an XML document.
+	
+	(This instance uses InfoBlocks, that help group related fields into sub-sections
+	of the object schema.)
 	
 	This is	created for the CollectionSpace system, http://www.collectionspace.org/
 
 -->
 
-<entity>
-	<entityName>CollectionObject</entityName>
-  <usageNotes>
-    <!-- In-depth notes about usage and meaning go in this field -->
-  </usageNotes>
-  <infoBlocks>
-		<infoBlock>
-			<fields>
-				<field
-					systemName="museumId"
-					displayName="ID"
-					usageNotes="In-depth notes about usage go here"
-					usageHint="Tooltip-type hints go here, such as 'Primary museum ID for this item'"
-					displayed="true"
-					lengthHint="20">
-					<!-- Field contents go here -->
-					pahma-collectionname-2007-06-09-00055
-				</field>
-			</fields>
-		</infoBlock>
-  </infoBlocks>
-</entity>
+<collectionObject>
+
+	<entity>
+	
+		<usageNotes>
+			<!-- Optional notes about the usage and meaning of this entity go here. -->
+		</usageNotes>
+		
+		<coreFields>
+			<id></id>
+			<created></created>
+			<createdBy></createdBy>
+			<lastModified></lastModified>
+			<lastModifiedBy></lastModifiedBy>
+		</coreFields>
+		
+		<infoBlocks>
+		
+			<infoBlock blockName="basic">
+				<fields>
+					<field
+						systemName="objectNumber"
+						displayName="ID"
+						usageNotes="In-depth notes about usage go here"
+						usageHint="Tooltip-type hints go here, such as 'Primary museum ID for this item'"
+						displayed="true"
+						lengthHint="20">
+						<!-- Field contents go here -->
+						pahma-collectionname-2007-06-09-00055
+					</field>
+					<field
+						systemName="title"
+						displayName="Title"
+						usageNotes="In-depth notes about usage go here"
+						usageHint="Tooltip-type hints go here"
+						displayed="true">
+						<!-- Field contents go here -->
+						Paiute Basket
+					</field>
+				</fields>
+			</infoBlock>
+
+			<!--
+				Note: This infoBlock is here to test instances with multiple blocks;
+				it is *not* part of the Release 0.1 schema.
+			-->
+			<infoBlock blockName="locationAndMoveMentControl">
+				<fields>
+					<field
+						systemName="currentLocation"
+						displayName=""
+						usageNotes="In-depth notes about usage go here"
+						usageHint="Tooltip-type hints go here, such as 'Primary museum ID for this item'"
+						displayed="true"
+						lengthHint="20">
+						<!-- Field contents go here -->
+						Room 231, Shelf 5, Box 18
+					</field>
+				</fields>
+			</infoBlock>
+		</infoBlocks>
+		
+	</entity>
+	
+</collectionObject>
diff --git a/sandbox/aron/schema/collectionObject-as-entity.rng b/sandbox/aron/schema/collectionObject-as-entity.rng
new file mode 100644
index 000000000..ed6a35ca6
--- /dev/null
+++ b/sandbox/aron/schema/collectionObject-as-entity.rng
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!--
+
+	collectionObject.rng
+	
+	A schema defining the structure of an CollectionObject entity,
+	based on the generic entity schema.
+
+	This schema was created for the CollectionSpace system,
+	http://www.collectionspace.org/
+	
+	It is written in the XML syntax of the RELAX NG schema language,
+	http://relaxng.org/
+
+-->
+
+<element
+	name="collectionObject" 
+	xmlns="http://relaxng.org/ns/structure/1.0">
+	
+	<!-- Include the generic schema for all entities. -->
+	<externalRef href="entity.rng"/>
+    
+</element>
diff --git a/sandbox/aron/schema/entity.rng b/sandbox/aron/schema/entity.rng
index 29ee9632a..1cc36eed1 100644
--- a/sandbox/aron/schema/entity.rng
+++ b/sandbox/aron/schema/entity.rng
@@ -3,69 +3,86 @@
 <!--
 
 	entity.rng
-
-	A schema defining the structure of an entity.  An "entity" is a business object;
-	a "noun" within the system.
-	
-	One or more fields of this type are included within an Entity Declaration,
-	which is defined in a separate, related schema file, "Entity.rng".
 	
-	This is a schema definition, using the XML syntax of the RELAX NG schema language,
-	created for the CollectionSpace system, http://www.collectionspace.org/
+	A generic schema defining the structure of an entity.  An "entity" is a
+	business object; a "noun" within the system.
+
+	This schema was created for the CollectionSpace system,
+	http://www.collectionspace.org/
 	
-	For more information on RELAX NG, please see http://relaxng.org/
+	It is written in the XML syntax of the RELAX NG schema language,
+	http://relaxng.org/
 
 -->
 
 <element
 	name="entity" 
-	xmlns="http://relaxng.org/ns/structure/1.0">
-	
-	<!-- Name of the entity -->
-		<element name="entityName">
-			 <text/>
-		</element>
+	xmlns="http://relaxng.org/ns/structure/1.0"
+	datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
 	
-	<!-- Informational text describing the purpose and usage of this entity -->
+	<!--
+		(Optional) Informational text describing the purpose and usage
+		of this entity.  This field may be present or absent, and if
+		present, its value may be empty or contain text.
+	-->
 	<optional>
 		<element name="usageNotes">
-			 <text/>
+			<choice>
+				<empty/>
+				<text/>
+			</choice>
 		</element>
 	</optional>
-    
+	
+	<!-- Include the schema for the core fields common to all entities -->
+	<externalRef href="entityCoreFields.rng"/>
+  
   <choice>
 
-  <!--
-  	An entity may either contain one or more infoBlocks,
-  	each containing one or more fields ...
-  -->  
+		<!--
+			An entity may either contain one or more infoBlocks,
+			each containing one or more fields ...
+		-->  
   	<group>
-			<element name="infoBlocks">
-				<element name="infoBlock">
-					<element name="fields">
-						<oneOrMore>
-							<externalRef href="entityField.rng"/>
-						</oneOrMore>
-					</element>
-				</element>
-			</element>
+ 			<element name="infoBlocks">
+ 				<oneOrMore>
+					<element name="infoBlock">
+						<attribute name="blockName">
+							<data type="normalizedString" />
+						</attribute>
+						<element name="fields">
+							<oneOrMore>
+								<!--
+									Include the generic schema for a field (data element)
+									in an entity.
+								-->
+								<externalRef href="entityField.rng"/>
+							</oneOrMore>
+						</element>
+					</element> <!-- end tag for infoBlock element -->
+				</oneOrMore>
+			</element> <!-- end tag for infoBlocks element -->
 		</group>
 
-  <!--
-  	... or may simply contain one or more fields, without any infoBlocks.
-  -->
+		<!--
+			... or may simply contain one or more fields, without any infoBlocks.
+		-->
 		<group>
 			<element name="fields">
 				<oneOrMore>
+					<!--
+						Include the generic schema for a field (data element)
+						in an entity.
+					-->
 					<externalRef href="entityField.rng"/>
 				</oneOrMore>
 			</element>
 		</group>
 
 		<!--
-			Currently, there isn't an option provided to have some fields
-			contained within infoBlocks, accompanied by other fields that
-			are not contained within InfoBlocks.
+			Currently, there isn't an option provided to have a mix:
+			some fields contained within infoBlocks, accompanied by
+			other fields that are not contained within InfoBlocks.
 		-->
 		
 	</choice>
@@ -75,17 +92,31 @@
 		An entity may optionally contain validation rules.
 		
 		The content of those rules is TBD.  Conceivably, they can be
-		written in an XML-based rules language, reference in-line or
-		external JavaScript code, etc.
+		written in an XML-based rules language, or can reference in-line
+		or external JavaScript code (for use within the UI layer of
+		CollectionSpace), etc.
+		
+		One of the possible approaches to specifying validation rules
+		could be to embed Schematron rules within RELAX NG schema.
+		As noted in this article, this can be done by inserting
+		the appropriate XML markup, in the Schematron namespace:
+		either grouped together below the top-level element or,
+		throughout the document, within the elements that define
+		the contexts for the embedded rules:
+		http://www.xml.com/pub/a/2004/02/11/relaxtron.html
+		
+		This page describes the support for processing embedded Schematron
+		rules in Jing, James Clark's RELAX NG library for Java:
+		http://www.thaiopensource.com/relaxng/jing-other.html
 		
-		Also, whether we might wish to have rules that are 'attached'
+		Also, we might wish to decide whether to offer rules that are 'attached'
 		to individual fields, rather than (or in addition to being)
-		specified here on a per-entity basis here, is TBD.
+		specified here on a per-entity basis in a 'validationRules' block.
 	-->
 	<optional>
 		<element name="validationRules">
 			<oneOrMore>
-				<element name="validation-rule">
+				<element name="validationRule">
 					<!-- Define what goes here -->
 					<text/>
 				</element>
diff --git a/sandbox/aron/schema/entityCoreFields.rng b/sandbox/aron/schema/entityCoreFields.rng
new file mode 100644
index 000000000..7bf5d4771
--- /dev/null
+++ b/sandbox/aron/schema/entityCoreFields.rng
@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!--
+
+	entityCoreFields.rng
+
+	A schema defining the structure of the core fields (data elements)
+	of an entity.
+	
+	An "entity" is a business object, or a "noun" within the system,
+	defined in a separate, related schema file, "entity.rng".
+	
+	This schema was created for the CollectionSpace system,
+	http://www.collectionspace.org/
+	
+	It is written in the XML syntax of the RELAX NG schema language,
+	http://relaxng.org/
+
+-->
+
+<element
+	name="coreFields" 
+	xmlns="http://relaxng.org/ns/structure/1.0"
+	datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
+	
+
+	<!-- ######################### -->
+	<!-- ID                        -->
+	<!-- ######################### -->
+	
+	<!--
+		A unique system identifier (ID) for this entity record,
+		as distinguished from any museum-created or other
+		identifiers that might also be associated with it.
+			
+		Note: We may wish to think further about what this element name should be,
+		to help disambiguate it from other identifiers used within the system.
+	-->
+	<element name="id">
+		<!--
+			Note: We may potentially wish to specify a regex-type pattern
+			here for further validating these IDs.
+		-->
+		<choice>
+			<data type="string" />
+			<empty />
+		</choice>
+	</element>
+
+
+	<!-- ######################### -->
+	<!-- Creation                  -->
+	<!-- ######################### -->
+
+		<!--
+			A timestamp for the creation of this entity record, as specified in
+			http://www.w3.org/TR/xmlschema-2/#dateTime
+		-->
+	<element name="created">
+		<choice>
+			<data type="dateTime" />
+			<empty />
+		</choice>
+	</element>
+
+	<!-- The system Principal that created this entity record -->
+	<element name="createdBy">
+		<choice>
+			<data type="string" />
+			<empty />
+		</choice>
+	</element>
+	
+	<!-- 
+		Note: Do we also need 'acting as designate for' information here,
+		for cases where one system Principal created this entity while
+		acting as a designate for another Principal?
+	-->
+
+	<!-- ######################### -->
+	<!-- Last modification         -->
+	<!-- ######################### -->
+	
+		<!--
+			A timestamp for the last modification of this entity record, as specified in
+			http://www.w3.org/TR/xmlschema-2/#dateTime
+		-->
+	<element name="lastModified">
+		<choice>
+			<data type="dateTime" />
+			<empty />
+		</choice>
+	</element>
+
+	<!-- The system Principal that created this entity record -->
+	<element name="lastModifiedBy">
+		<choice>
+			<data type="string" />
+			<empty />
+		</choice>
+	</element>
+	
+	<!-- 
+		Note: Do we also need 'acting as designate for' information here,
+		for cases where one system Principal modified this entity while
+		acting as a designate for another Principal?
+	-->
+
+	<!--
+		Do we want multiple modification records here?  That would
+		allow us to carry entity payloads with their full (or selected)
+		modification history, with the downside of 
+	-->
+
+</element>
diff --git a/sandbox/aron/schema/entityField.rng b/sandbox/aron/schema/entityField.rng
index 11a7b2dda..5a151efdd 100644
--- a/sandbox/aron/schema/entityField.rng
+++ b/sandbox/aron/schema/entityField.rng
@@ -4,11 +4,11 @@
 
 	entityField.rng
 
-	This schema defines the structure of an individual field (or data element).
+	A schema defining structure of an individual field (or data element)
+	in an entity.
 
 	One or more of these entityFields may be included within an "entity",
-	a generic business object that is defined in a separate, related schema,
-	"entity.rng".
+	a generic business object defined in a separate, related schema, "entity.rng".
 	
 	This schema was created for the CollectionSpace system,
 	http://www.collectionspace.org/
@@ -21,15 +21,9 @@
 <element
 	name="field"
 	xmlns="http://relaxng.org/ns/structure/1.0"
-	datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
-	
-	<!-- Datatype -->
-
-	<!--
-		Currently, all entity fields are defined as xs:String datatypes.
-	-->
-	<data type="string" />
-	
+  xmlns:a="http://relaxng.org/ns/annotation/0.9"
+  datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
+		
 	<!-- Attributes -->
 
 	<!--
@@ -37,7 +31,7 @@
 		See also "displayName", below.
 	-->
 	<attribute name="systemName">
-		<text/>
+		<data type="Name" />
 	</attribute>
 	
 	<!--
@@ -45,29 +39,46 @@
 		
 		This name may be customized to meet the needs of a deployed instance,
 		internationalized, etc.
+		
+		If the value of this field is empty (blank), it is expected that the
+		systemName, above, will be displayed in the system UI.
 	-->
 	<attribute name="displayName">
-		<text/>
+		<optional>
+			<data type="normalizedString" />
+		</optional>
 	</attribute>
 	
 	<!-- Informational text describing the purpose and usage of this field -->
 	<attribute name="usageNotes">
-		 <text/>
+		<optional>
+			<data type="string" />
+		</optional>
 	</attribute>
 
 	<!-- Brief, tooltip-type help text describing the purpose and usage of this field -->
 	<attribute name="usageHint">
-		 <text/>
+		<optional>
+			<data type="string" />
+		</optional>
 	</attribute>
 	
-	<!-- A Boolean value indicating whether this field is to be displayed in system UI. -->
-	<attribute name="displayed">
+	<!--
+		A Boolean value indicating whether this field is to be displayed in system UI.
+
+		If this attribute's value is empty (blank), its default value is set to "true".
+		Since an entered value for this attribute is currently required, this default
+		value may not be necessary (or ever used), but is included here nonetheless.
+	-->
+	<attribute
+		name="displayed"
+		a:defaultValue="true">
 		<choice>
 			<value>true</value>
 			<value>false</value>
 		</choice>
 	</attribute>
-
+	
 	<!--
 		An optional hint regarding the length of this field.
 		
@@ -81,9 +92,39 @@
 	-->
 	<optional>
 		<attribute name="lengthHint">
-			<text/>
+			<data type="normalizedString" />
 		</attribute>
 	</optional>
 	
+	<!--
+		A note regarding "required fields"
+		
+		A "required field" is a data element into which valid data must be
+		entered before a new entity record, or a modification to an existing
+		entity record, can be accepted and stored.  A particular entity may
+		have one required field, or more than one such field.  In the latter
+		case, each of the required fields must contain valid data before a
+		new or modified record is stored.
+you're not
+		There isn't currently a 'required' (or similar) attribute for the
+		'field' element, because at present we're assuming that validation
+		rules will be used to define required fields.
+				
+		If this assumption isn't correct, we may wish to add such an attribute
+		to this schema.
+		
+		Apropos of this point, Patrick Schmitz wrote on 2009-02-25:
+		"We may have to separate the notion of what the system will require,
+		and what a UI interaction will require. This allows for import of
+		legacy ... data ... but can put more constraints on what folks enter."
+	-->
+
+	<!-- Value -->
+
+	<!--
+		Currently, the values of entity fields are defined as xs:String datatypes.
+	-->
+	<data type="string" />
+	
 </element>
 
diff --git a/sandbox/aron/schema/entityFieldAttributes.rng b/sandbox/aron/schema/entityFieldAttributes.rng
new file mode 100644
index 000000000..98e298a23
--- /dev/null
+++ b/sandbox/aron/schema/entityFieldAttributes.rng
@@ -0,0 +1,131 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!--
+
+	entityFieldAttributes.rng
+
+	A schema defining structure of the attributes of an individual field
+	(or data element) in an entity.
+
+	These entityFieldAttributes may be included within an "entityField",
+	a generic business object defined in a separate, related schema, "entity.rng".
+	
+	This schema was created for the CollectionSpace system,
+	http://www.collectionspace.org/
+	
+	It is written in the XML syntax of the RELAX NG schema language,
+	http://relaxng.org/
+
+-->
+
+<element
+	name="field"
+	xmlns="http://relaxng.org/ns/structure/1.0"
+  xmlns:a="http://relaxng.org/ns/annotation/0.9"
+  datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
+		
+	<!-- Attributes -->
+
+	<!--
+		The name of this field/data element, as used internally by the system.
+		See also "displayName", below.
+	-->
+	<attribute name="systemName"
+		xmlns="http://relaxng.org/ns/structure/1.0">
+		<data type="Name" />
+	</attribute>
+	
+	<!--
+		The name of this field/data element, as displayed in the system UI.
+		
+		This name may be customized to meet the needs of a deployed instance,
+		internationalized, etc.
+		
+		If the value of this field is empty (blank), it is expected that the
+		systemName, above, will be displayed in the system UI.
+	-->
+	<attribute name="displayName">
+		<optional>
+			<data type="normalizedString" />
+		</optional>
+	</attribute>
+	
+	<!-- Informational text describing the purpose and usage of this field -->
+	<attribute name="usageNotes">
+		<optional>
+			<data type="string" />
+		</optional>
+	</attribute>
+
+	<!-- Brief, tooltip-type help text describing the purpose and usage of this field -->
+	<attribute name="usageHint">
+		<optional>
+			<data type="string" />
+		</optional>
+	</attribute>
+	
+	<!--
+		A Boolean value indicating whether this field is to be displayed in system UI.
+
+		If this attribute's value is empty (blank), its default value is set to "true".
+		Since an entered value for this attribute is currently required, this default
+		value may not be necessary (or ever used), but is included here nonetheless.
+	-->
+	<attribute
+		name="displayed"
+		a:defaultValue="true">
+		<choice>
+			<value>true</value>
+			<value>false</value>
+		</choice>
+	</attribute>
+	
+	<!--
+		An optional hint regarding the length of this field.
+		
+		This may be used for dynamically laying out fields within a forms-based
+		user interface, or for similar purposes.
+		
+		The meaning of this field is instance-dependent, and may refer
+		to a typical length, or an expected maximum length, for instance.
+		It may also refer to any arbitrary measurement system, such as US-ASCII
+		characters, em units or pixels.
+	-->
+	<optional>
+		<attribute name="lengthHint">
+			<data type="normalizedString" />
+		</attribute>
+	</optional>
+	
+	<!--
+		A note regarding "required fields"
+		
+		A "required field" is a data element into which valid data must be
+		entered before a new entity record, or a modification to an existing
+		entity record, can be accepted and stored.  A particular entity may
+		have one required field, or more than one such field.  In the latter
+		case, each of the required fields must contain valid data before a
+		new or modified record is stored.
+you're not
+		There isn't currently a 'required' (or similar) attribute for the
+		'field' element, because at present we're assuming that validation
+		rules will be used to define required fields.
+				
+		If this assumption isn't correct, we may wish to add such an attribute
+		to this schema.
+		
+		Apropos of this point, Patrick Schmitz wrote on 2009-02-25:
+		"We may have to separate the notion of what the system will require,
+		and what a UI interaction will require. This allows for import of
+		legacy ... data ... but can put more constraints on what folks enter."
+	-->
+
+	<!-- Value -->
+
+	<!--
+		Currently, the values of entity fields are defined as xs:String datatypes.
+	-->
+	<data type="string" />
+	
+</element>
+
-- 
2.47.3