<xs:element name="allow" type="AccessRule">
- <xs:annotation>
- <xs:documentation>tooltip: Allow rule summary: A rule that grants a permission type. description: The allow element indicates that a particular user or group is granted the defined permission. example: allow</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -701,25 +657,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="principal" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: User or group summary: The user or group (principal) for which the access control applies. description: The principal element defines the user or group to which the access control rule applies. The users and groups must be defined in the authentication system described in the authSystem element. The special principal 'public' can be used to indicate that any user or group has a particular access permission, thereby making it easier to specify that anonymous access is allowed. example: public example: uid=alice,o=LTER,dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -819,40 +756,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="permission" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Type of permission summary: The type of permission being granted or denied. description: The permission that is being granted or denied to a particular user or group for a given resource. The list of permissions come from a predetermined list: 'read' - allow or deny viewing of the resource, 'write' - allow or deny modification of the resource (except for access rules), 'changePermission' - modifications including access rules, and 'all' - all of the above. This element also allows other permission values that may be applicable to some other authentication systems but are not defined in this specification (if these other values are used, access rule enforcement is indeterminate outside of the originating system). example: read</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:union>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="read"/>
- <xs:enumeration value="write"/>
- <xs:enumeration value="changePermission"/>
- <xs:enumeration value="all"/>
- </xs:restriction>
- </xs:simpleType>
- <xs:simpleType>
- <xs:restriction base="xs:string"/>
- </xs:simpleType>
- </xs:union>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -966,25 +869,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="deny" type="AccessRule">
- <xs:annotation>
- <xs:documentation>tooltip: Deny rule summary: A rule that revokes a permission type. description: The deny element indicates that a particular user or group is not granted the defined permission. example: deny</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1214,25 +1098,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="access" type="AccessType">
- <xs:annotation>
- <xs:documentation>tooltip: Access control rules summary: The rules defined in this element will determine the level of access to a resource for the defined users and groups. description: The access element contains a list of rules defining permissions for this resource. For descriptions of the individual elements, see the AccessType.The permission rules defined here can be overridden by rules added to an access tree in the PhysicalDistributionType at the entity level. example: See the description of the AccessType.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="AccessType">
- <xs:annotation>
- <xs:documentation>tooltip: Access control rules summary: The rules defined in this element will determine the level of access to a resource for the defined users and groups. description: The access element contains a list of rules that define the level of access for a resource. There are two uses of access trees: to control access to either metadata or data. To control access to metadata use the eml/access tree. By default, these rules will also apply to the contained data. To override the default controls for specific data entities, use the access element available in the entity's physical/distribution tree. A combination of access trees and their "order rules" (see description of the "order" attribute) allows EML authors to have fine control over permissions for individuals and groups.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="allow" type="AccessRule">
- <xs:annotation>
- <xs:documentation>tooltip: Allow rule summary: A rule that grants a permission type. description: The allow element indicates that a particular user or group is granted the defined permission. example: allow</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="deny" type="AccessRule">
- <xs:annotation>
- <xs:documentation>tooltip: Deny rule summary: A rule that revokes a permission type. description: The deny element indicates that a particular user or group is not granted the defined permission. example: deny</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
- <xs:attribute name="order" use="optional" default="allowFirst">
- <xs:annotation>
- <xs:documentation>tooltip: Rule order summary: The order in which the allow and deny rules should be applied. description: To obtain the desired access control, use the order attribute to define which rules should be applied first. The acceptable values are 'allowFirst' and 'denyFirst'. If 'allowFirst' is specified, then all 'allow' rules are processed, and then overridden by all 'deny' rules. If 'denyFirst' is specified, then all 'deny' rules are processed, and then overridden by all 'allow' rules. example: allowFirst</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="allowFirst"/>
- <xs:enumeration value="denyFirst"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:attribute>
- <xs:attribute name="authSystem" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Authentication system summary: The authentication system is used to verify the user or group to whom access is allowed or denied. description: The authentication system determines the set of principals (users + groups) that can be used in the access control list, and the membership of users in groups. This element is intended to provide a reference to the authentication system that is used to verify the user or group. This reference is typically in the form of a URI, which includes the connection protocol, Internet host, and path to the authentication mechanism. example: ldap://ldap.ecoinformatics.org:389/dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
- </xs:attribute>
-</xs:complexType>
<xs:complexType name="AccessRule">
- <xs:annotation>
- <xs:documentation>tooltip: Access Rule summary: Access Rules define a user's access to a resource. description: The AccessRule type defines a list of users that are derived from a particular authentication system (such as an LDAP directory), whether the user or group is allowed or denied access, the extent of their access (read, write , or changePermission access).</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="principal" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: User or group summary: The user or group (principal) for which the access control applies. description: The principal element defines the user or group to which the access control rule applies. The users and groups must be defined in the authentication system described in the authSystem element. The special principal 'public' can be used to indicate that any user or group has a particular access permission, thereby making it easier to specify that anonymous access is allowed. example: public example: uid=alice,o=LTER,dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="permission" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Type of permission summary: The type of permission being granted or denied. description: The permission that is being granted or denied to a particular user or group for a given resource. The list of permissions come from a predetermined list: 'read' - allow or deny viewing of the resource, 'write' - allow or deny modification of the resource (except for access rules), 'changePermission' - modifications including access rules, and 'all' - all of the above. This element also allows other permission values that may be applicable to some other authentication systems but are not defined in this specification (if these other values are used, access rule enforcement is indeterminate outside of the originating system). example: read</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:union>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="read"/>
- <xs:enumeration value="write"/>
- <xs:enumeration value="changePermission"/>
- <xs:enumeration value="all"/>
- </xs:restriction>
- </xs:simpleType>
- <xs:simpleType>
- <xs:restriction base="xs:string"/>
- </xs:simpleType>
- </xs:union>
- </xs:simpleType>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:attribute name="order" use="optional" default="allowFirst">
- <xs:annotation>
- <xs:documentation>tooltip: Rule order summary: The order in which the allow and deny rules should be applied. description: To obtain the desired access control, use the order attribute to define which rules should be applied first. The acceptable values are 'allowFirst' and 'denyFirst'. If 'allowFirst' is specified, then all 'allow' rules are processed, and then overridden by all 'deny' rules. If 'denyFirst' is specified, then all 'deny' rules are processed, and then overridden by all 'allow' rules. example: allowFirst</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="allowFirst"/>
- <xs:enumeration value="denyFirst"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:attribute>
<xs:attribute name="authSystem" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Authentication system summary: The authentication system is used to verify the user or group to whom access is allowed or denied. description: The authentication system determines the set of principals (users + groups) that can be used in the access control list, and the membership of users in groups. This element is intended to provide a reference to the authentication system that is used to verify the user or group. This reference is typically in the form of a URI, which includes the connection protocol, Internet host, and path to the authentication mechanism. example: ldap://ldap.ecoinformatics.org:389/dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:element name="attributeName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute name summary: The name of the attribute description: Attribute name is official name of the attribute. This is usually a short, sometimes cryptic name that is used to refer to the attribute. Many systems have restrictions on the length of attribute names, and on the use of special characters like spaces in the name, so the attribute name is often not particularly useful for display (use attributeLabel for display). The attributeName is usually the name of the variable that is found in the header of a data file. example: spden example: spatialden example: site example: spcode</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1289,25 +1137,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeLabel" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute label summary: A label for displaying an attribute name. description: A descriptive label that can be used to display the name of an attribute. This is often a longer, possibly multiple word name for the attribute than the attributeName. It is not constrained by system limitations on length or special characters. For example, an attribute with a name of 'spcode' might have an attributeLabel of 'Species Code'. example: Species Density example: Spatial Density example: Name of Site example: Species Code</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1422,25 +1251,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeDefinition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute definition summary: Precise definition of the attribute description: This element gives a precise definition of attribute in the data entity (dataTable, spatialRaster, spatialVector, storedProcedure, view or otherEntity) being documented. It explains the contents of the attribute fully so that a data user could interpret the attribute accurately. Some additional information may also be found in the methods element as well. example: "spden" is the number of individuals of all macro invertebrate species found in the plot</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1603,36 +1413,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="storageType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Storage Type summary: Storage type hint for this field description: This element describes the storage type, for data in a RDBMS (or other data management system) field. As many systems do not provide for fine-grained restrictions on types, this type will often be a superset of the allowed domain defined in attributeDomain. Values for this field are by default drawn from the XML Schema Datatypes standard values, such as: integer, double, string, etc. If the XML Schema Datatypes are not used, the type system from which the values are derived should be listed in the 'typeSystem' attribute described below. This field represents a 'hint' to processing systems as to how the attribute might be represented in a system or language, but is distinct from the actual expression of the domain of the attribute. The field is repeatable so that the storageType can be indicated for multiple type systems (e.g., Oracle data types and Java data types). example: integer example: int</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="typeSystem" type="xs:string" use="optional" default="http://www.w3.org/2001/XMLSchema-datatypes">
- <xs:annotation>
- <xs:documentation>tooltip: Storage Type System summary: The system used to define the storage types. This should be an identifier of a well known and published typing system. description: The typeSystem attribute is the system used to define the storage types. This should be an identifier of a well known and published typing system. The default and recommended system is the XML Schema data type system. For details go to http://www.w3.org. If another system is used (such as Java or C++ types), typeSystem should be changed to match the system. example: http://www.w3.org/2001/XMLSchema-datatypes example: java example: C example: Oracle 8i</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1771,97 +1551,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="measurementScale">
- <xs:annotation>
- <xs:documentation>tooltip: Measurement Scale summary: The measurement scale for the attribute. description: The measurementScale element indicates the type of scale from which values are drawn for the attribute. This provides information about the scale in which the data was collected. example: Nominal is used when numbers have only been assigned to a variable for the purpose of categorizing the variable. An example of a nominal scale is assigning the number 1 for male and 2 for female. example: Ordinal is used when the categories have a logical or ordered relationship to each other. These types of scale allow one to distinguish the order of values, but not the magnitude of the difference between values. An example of an ordinal scale is a categorical survey where you rank a variable 1=good, 2=fair, 3=poor. example: Interval is used for data which consist of equidistant points on a scale. The Celsius scale is an interval scale, since each degree is equal but there is no natural zero point (so, 20 C is not twice as hot as 10 C). example: Ratio is used for data which consists not only of equidistant points but also has a meaningful zero point, which allows ratios to have meaning. An example of a ratio scale would be the Kelvin temperature scale (200K is half as hot as 400K), and length in meters (e.g., 10 meters is twice as long as 5 meters).</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="nominal">
- <xs:annotation>
- <xs:documentation>tooltip: Nominal scale summary: Characteristics used to define nominal (categorical) scale attributes description: This field is used for defining the characteristics of this variable if it is a nominal scale variable, which are variables that are categorical in nature. Nominal is used when numbers have only been assigned to a variable for the purpose of categorizing the variable. An example of a nominal scale is assigning the number 1 for male and 2 for female.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="ordinal">
- <xs:annotation>
- <xs:documentation>tooltip: Ordinal scale summary: Characteristics used to define ordinal (ordered) scale attributes description: This field is used for defining the characteristics of this variable if it is an ordinal scale variable, which specify ordered values without specifying the magnitude of the difference between values. Ordinal is used when the categories have a logical or ordered relationship to each other. These types of scale allow one to distinguish the order of values, but not the magnitude of the difference between values. An example of an ordinal scale is a categorical survey where you rank a variable 1=good, 2=fair, 3=poor.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="interval">
- <xs:annotation>
- <xs:documentation>tooltip: Interval scale summary: Characteristics used to define interval scale attributes description: This field is used for defining the characteristics of this variable if it is an interval scale variable, which specifies both the order and magnitude of values, but has no natural zero point. Interval is used for data which consist of equidistant points on a scale. The Celsius scale is an interval scale, since each degree is equal but there is no natural zero point (so, 20 C is not twice as hot as 10 C). zero point (so, 20 C is not twice as hot as 10 C).</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="unit" type="UnitType"/>
- <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
- <xs:element name="numericDomain" type="NumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="ratio">
- <xs:annotation>
- <xs:documentation>tooltip: Ratio scale summary: Characteristics used to define ratio scale attributes description: This field is used for defining the characteristics of this variable if it is a ratio scale variable, which specifies the order and magnitude of values and has a natural zero point, allowing for ratio comparisons to be valid. Ratio is used for data which consists not only of equidistant points but also has a meaningful zero point, which allows ratios to have meaning. An example of a ratio scale would be the Kelvin temperature scale (200K is half as hot as 400K), and length in meters (e.g., 10 meters is twice as long as 5 meters).</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="unit" type="UnitType"/>
- <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
- <xs:element name="numericDomain" type="NumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="dateTime">
- <xs:annotation>
- <xs:documentation>tooltip: Date/Time scale summary: Characteristics used to define date and time attributes description: The dateTime field is used for defining the characteristics of the attribute if it contains date and time values. DateTime is used when the values fall on the Gregorian calendar system. DateTime values are special because they have properties of interval values (most of the time it is legitimate to treat them as interval values by converting them to a duration from a fixed point) but they sometimes only behave as ordinals (because the calendar is not predetermined, for some dateTime values one can only find out the order of the points and not the magnitude of the duration between those points). Thus, the dateTime scale provides the information necessary to properly understand and parse date and time values without improperly labeling them under one of the more traditional scales. Date and time values are unlike any other measured values. Note that the dateTime field would not be used if one is recording time durations. In that case, one should use a standard unit such as seconds, nominalMinute or nominalDay, or a customUnit that defines the unit in terms of its relationship to SI second.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="formatString" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Date/Time Format summary: A format string that describes the format for a date-time value from the Gregorian calendar. description: A format string that describes the format for a dateTime value from the Gregorian calendar. DateTime values should be expressed in a format that conforms to the ISO 8601 standard. This field allows one to specify the format string that should be used to decode the date or time value. To describe the format of an attribute containing dateTime values, construct a string representation of the format using the following symbols: Y year M month W month abbreviation (e.g., JAN) D day h hour m minute s second T time designator (demarcates date and time parts of date-time) Z UTC designator, indicating value is in UTC time . indicates a decimal fraction of a unit +/- indicates a positive or negative number, or a positive or negative time zone adjustment relative to UTC - indicates a separator between date components A/P am or pm designator Any other character in the format string is interpreted as a separator character. Here are some examples of the format strings that can be constructed. Format string Example value ------------------- ------------------ ISO Date YYYY-MM-DD 2002-10-14 ISO Datetime YYYY-MM-DDThh:mm:ss 2002-10-14T09:13:45 ISO Time hh:mm:ss 17:13:45 ISO Time hh:mm:ss.sss 09:13:45.432 ISO Time hh:mm.mm 09:13.42 Non-standard DD/MM/YYYY 14/10/2002 Non-standard MM/DD/YYYY 10/14/2002 Non-standard MM/DD/YY 10/14/02 Non-standard YYYY-MMM-DD 2002-OCT-14 Non-standard YYYYMMMDD 2002OCT14 Non-standard YYYY-MM-DD hh:mm:ss 2002-10-14 09:13:45 Some notes about these examples. First, the ISO 8601 standard is strict about the date components, their order, and the separators; e.g., date parts are upper case, and time parts are lower case. If no UTC relation information is given, the time is assumed to be in local time. Assuming local time is ambiguous even when communicating within a single time zone, given variations in Daylight Saving Time. Best practice is to follow the ISO 8601 format precisely and accurately. In particular, please note that these are all non-standard according to ISO: use of a slash (/) to separate date components, a space to separate date and time components, using a twelve-hour time with am/pm designator, placing any of the components out of descending order However, we recognize that existing data contain non-standard dates, and existing equipment (e.g., sensors) may still be producing non-standard dates. Further, data parsers often apply individual interpretations. E.g., Java interprets HH on a 24-hr clock and hh on a 12-hr clock, and MM as a padded integer for month but MMM as a 3-letter abbreviation. Consequently, the formatting string can contain characters as needed to accommodate existing data. Decimal dateTime values can be extended by indicating in the format that additional decimals can be used. Only the final unit (e.g., seconds in a time value) can use the extended digits according to the ISO 8601 standard. For example, to show indicate that seconds are represented to the nearest 1/1000 of a second, the format string would be "hh:mm:ss.sss". Note that this only indicates the number of decimals used to record the value, and not the precision of the measurement (see dateTimePrecision for that). Date and time values are from an interval scale, but it is extremely complex because of the vagaries of the calendar (e.g., leap years, and leap seconds). The duration between date and time values in the future is not even deterministic because leap seconds are based on current measurements of the earth's orbit. Consequently, date and time values are unlike any other measured values. The format string for dateTime values allows one to accurately calculate the duration in SI second units between two measured dateTime values, assuming that the conversion software has a detailed knowledge of the Gregorian calendar. example: YYYY-MM-DDThh:mm:ss example: YYYY-MM-DD example: YYYY example: hh:mm:ss example: hh:mm:ss.sss</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dateTimePrecision" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Precision summary: An indication of the precision of a date or time value description: A quantitative indication of the precision of a date or time measurement. The precision should be interpreted in the smallest units represented by the dateTime format. For example, if a dateTime value has a format of "hh:mm:ss.sss", then "seconds" are the smallest unit and the precision should be expressed in seconds. Thus, a precision value of "0.01" would mean that measurements were precise to the nearest hundredth of a second, even though the format string might indicate that values were written down with 3 decimal places. example: 0.1 example: 0.01</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dateTimeDomain" type="DateTimeDomainType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Domain summary: See the summary for the type: DateTimeDomainType description: See the description for the type: DateTimeDomainType</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1971,30 +1660,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="nominal">
- <xs:annotation>
- <xs:documentation>tooltip: Nominal scale summary: Characteristics used to define nominal (categorical) scale attributes description: This field is used for defining the characteristics of this variable if it is a nominal scale variable, which are variables that are categorical in nature. Nominal is used when numbers have only been assigned to a variable for the purpose of categorizing the variable. An example of a nominal scale is assigning the number 1 for male and 2 for female.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
<xs:element name="enumeratedDomain">
- <xs:annotation>
- <xs:documentation>tooltip: Enumerated domain summary: Description of any coded values associated with the attribute. description: The enumeratedDomain element describes any code that is used as a value of an attribute. These codes can be defined here in the metadata as a list with definitions (preferred), can be referenced by pointing to an external citation or URL where the codes are defined, or can be referenced by pointing at an entity that contains the code value and code definition as two attributes. For example, data might have a variable named 'site' with values 'A', 'B', and 'C', and the enumeratedDomain would explain how to interpret those codes.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="codeDefinition" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Code Definition summary: A codes and its definition description: This element gives the value of a particular code and its definition. It is repeatable to allow for a list of codes to be provided.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="code" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code summary: Code value allowed in the domain description: The code element specifies a code value that can be used in the domain example: 1 example: HIGH example: BEPA example: 24</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="definition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code definition summary: Definition of the associated code description: The definition describes the code with which it is associated in enough detail for scientists to interpret the meaning of the coded values. example: high density, above 10 per square meter</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Source of code summary: The name of the source for this code and its definition description: The source element is the name of the source from which this code and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be the researcher's customized way of recording and classifying their data, and no external "source" would exist. example: ISO country codes</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="order" type="xs:long" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Order summary: Mechanism for specifying what the order of the code-definitions included should be description: Ordinal scale measurements have a discrete list of values with a specific ordering of those values. This attributes specifies that order from low to high. For example, for LOW, MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and HIGH=3".</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="externalCodeSet">
- <xs:annotation>
- <xs:documentation>tooltip: External code set summary: A reference to an externally defined set of codes used in this attribute description: The externalCodeSet element is a reference to an externally defined set of codes used in this attribute. This can either be a citation (using the eml-citation module) or a URL. Using an externally defined codeset (rather than a codeDefinition) means that interpretation of the data is dependent upon future users being able to obtain the code definitions, so care should be taken to only use highly standardized external code sets that will be available for many years. If at all possible, it is preferable to define the codes inline using the codeDefinition element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="codesetName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code Set Name summary: The name of an externally defined code set description: The codesetName element is the name of an externally defined code set. example: FIPS State Abbreviation Codes</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="citation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Citation summary: A citation for the code set reference description: The citation element is a citation for the code set reference</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="codesetURL" type="xs:anyURI">
- <xs:annotation>
- <xs:documentation>tooltip: Code set URL summary: A URL for the code set reference description: The codesetURL element is a URL for the code set reference.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="entityCodeList">
- <xs:annotation>
- <xs:documentation>tooltip: Entity Code List summary: A code list that is defined in a data table description: The entityCodeList is a list of codes and their definitions in a data entity that is present in this dataset. The fields specify exactly which entity it is, and which attributes of that entity contain the codes, their definitions, and the order of the values.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="entityReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Entity Reference summary: A reference to the id of the entity in which the code list has been defined description: The entityReference element is a reference to the id of the entity in which the code list has been defined. This entity must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="valueAttributeReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Value Attribute Reference summary: A reference to the id of the attribute that contains the list of codes description: The valueAttributeReference element is a reference to the id of the attribute that contains the list of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="definitionAttributeReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Definition Attribute Reference summary: A reference to the id of the attribute that contains the definition of codes description: The definitionAttributeReference element is a reference to the id of the attribute that contains the definition of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="orderAttributeReference" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Order Attribute Reference summary: A reference to the id of the attribute that contains the order of codes description: The orderAttributeReference element is a reference to the id of the attribute that contains the order of codes. The values in this attribute are integers indicating increasing values of the categories. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:attribute name="enforced" use="optional" default="yes">
- <xs:annotation>
- <xs:documentation>tooltip: Enforced Domain summary: Indicates whether the enumerated domain values enforced. description: Indicates whether the enumerated domain values are the only allowable values for the domain. In some exceedingly rare cases, users may wish to present a list of value codes in enumeratedDomain but not formally restrict the value space for the attribute to those values. If so, they can indicate this by setting the enforced attribute to the value no. Acceptable values are yes and no, and the default value is yes.</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2569,49 +2101,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="codeDefinition" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Code Definition summary: A codes and its definition description: This element gives the value of a particular code and its definition. It is repeatable to allow for a list of codes to be provided.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="code" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code summary: Code value allowed in the domain description: The code element specifies a code value that can be used in the domain example: 1 example: HIGH example: BEPA example: 24</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="definition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code definition summary: Definition of the associated code description: The definition describes the code with which it is associated in enough detail for scientists to interpret the meaning of the coded values. example: high density, above 10 per square meter</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Source of code summary: The name of the source for this code and its definition description: The source element is the name of the source from which this code and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be the researcher's customized way of recording and classifying their data, and no external "source" would exist. example: ISO country codes</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="order" type="xs:long" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Order summary: Mechanism for specifying what the order of the code-definitions included should be description: Ordinal scale measurements have a discrete list of values with a specific ordering of those values. This attributes specifies that order from low to high. For example, for LOW, MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and HIGH=3".</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2726,25 +2215,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="code" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code summary: Code value allowed in the domain description: The code element specifies a code value that can be used in the domain example: 1 example: HIGH example: BEPA example: 24</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2855,25 +2325,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="definition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code definition summary: Definition of the associated code description: The definition describes the code with which it is associated in enough detail for scientists to interpret the meaning of the coded values. example: high density, above 10 per square meter</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2993,25 +2444,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Source of code summary: The name of the source for this code and its definition description: The source element is the name of the source from which this code and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be the researcher's customized way of recording and classifying their data, and no external "source" would exist. example: ISO country codes</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3130,46 +2562,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="externalCodeSet">
- <xs:annotation>
- <xs:documentation>tooltip: External code set summary: A reference to an externally defined set of codes used in this attribute description: The externalCodeSet element is a reference to an externally defined set of codes used in this attribute. This can either be a citation (using the eml-citation module) or a URL. Using an externally defined codeset (rather than a codeDefinition) means that interpretation of the data is dependent upon future users being able to obtain the code definitions, so care should be taken to only use highly standardized external code sets that will be available for many years. If at all possible, it is preferable to define the codes inline using the codeDefinition element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="codesetName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code Set Name summary: The name of an externally defined code set description: The codesetName element is the name of an externally defined code set. example: FIPS State Abbreviation Codes</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="citation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Citation summary: A citation for the code set reference description: The citation element is a citation for the code set reference</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="codesetURL" type="xs:anyURI">
- <xs:annotation>
- <xs:documentation>tooltip: Code set URL summary: A URL for the code set reference description: The codesetURL element is a URL for the code set reference.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3279,25 +2671,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="codesetName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code Set Name summary: The name of an externally defined code set description: The codesetName element is the name of an externally defined code set. example: FIPS State Abbreviation Codes</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3525,25 +2898,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Citation summary: A citation for the code set reference description: The citation element is a citation for the code set reference</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3623,25 +2977,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="codesetURL" type="xs:anyURI">
- <xs:annotation>
- <xs:documentation>tooltip: Code set URL summary: A URL for the code set reference description: The codesetURL element is a URL for the code set reference.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3755,49 +3090,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="entityCodeList">
- <xs:annotation>
- <xs:documentation>tooltip: Entity Code List summary: A code list that is defined in a data table description: The entityCodeList is a list of codes and their definitions in a data entity that is present in this dataset. The fields specify exactly which entity it is, and which attributes of that entity contain the codes, their definitions, and the order of the values.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="entityReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Entity Reference summary: A reference to the id of the entity in which the code list has been defined description: The entityReference element is a reference to the id of the entity in which the code list has been defined. This entity must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="valueAttributeReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Value Attribute Reference summary: A reference to the id of the attribute that contains the list of codes description: The valueAttributeReference element is a reference to the id of the attribute that contains the list of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="definitionAttributeReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Definition Attribute Reference summary: A reference to the id of the attribute that contains the definition of codes description: The definitionAttributeReference element is a reference to the id of the attribute that contains the definition of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="orderAttributeReference" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Order Attribute Reference summary: A reference to the id of the attribute that contains the order of codes description: The orderAttributeReference element is a reference to the id of the attribute that contains the order of codes. The values in this attribute are integers indicating increasing values of the categories. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3908,25 +3200,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="entityReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Entity Reference summary: A reference to the id of the entity in which the code list has been defined description: The entityReference element is a reference to the id of the entity in which the code list has been defined. This entity must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4038,25 +3311,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="valueAttributeReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Value Attribute Reference summary: A reference to the id of the attribute that contains the list of codes description: The valueAttributeReference element is a reference to the id of the attribute that contains the list of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4169,25 +3423,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="definitionAttributeReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Definition Attribute Reference summary: A reference to the id of the attribute that contains the definition of codes description: The definitionAttributeReference element is a reference to the id of the attribute that contains the definition of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4304,25 +3539,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="orderAttributeReference" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Order Attribute Reference summary: A reference to the id of the attribute that contains the order of codes description: The orderAttributeReference element is a reference to the id of the attribute that contains the order of codes. The values in this attribute are integers indicating increasing values of the categories. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4444,44 +3660,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="textDomain">
- <xs:annotation>
- <xs:documentation>tooltip: Text domain summary: Description of a free-text domain pattern for the attribute description: The textDomain element describes a free text domain for the attribute. By default, if a pattern is missing or empty, then any text is allowed. If a pattern is present, then it is interpreted as a regular expression constraining the allowable character sequences for the attribute. This domain type is most useful for describing extensive text domains that match a pattern but do not have a finite set of values. Another use is for describing the domain of textual fields like comments that allow any legal string value. example: Typically, a text domain will have an empty pattern or one that constrains allowable values. For example, '[0-9]{3}-[0-9]{3}-[0-9]{4}' allows for only numeric digits in the pattern of a US phone number.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="definition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Text domain definition summary: Definition of what this text domain represents description: The element definition provides the text domain definition, that is, what kinds of text expressions are allowed for this attribute. If there is a pattern supplied, the definition element expresses the meaning of the pattern, For example, a particular pattern may be meant to represent phone numbers in the US phone system format. A definition element may also be used to extend an enumerated domain. example: US telephone numbers in the format "(999) 888-7777"</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pattern" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Text pattern summary: Regular expression pattern constraining the attribute description: The pattern element specifies a regular expression pattern that constrains the set of allowable values for the attribute. This is commonly used to define template patterns for data such as phone numbers where the attribute is text but the values are not drawn from an enumeration. If the pattern field is empty or missing, it defaults to '.*', which matches any string, including the empty string. Repeated pattern elements are combined using logical OR. The regular expression syntax is the same as that used in the XML Schema Datatypes Recommendation from the W3C. example: '[0-9a-zA-Z]' matches simple alphanumeric strings and '(\d\d\d) \d\d\d-\d\d\d\d' represents telephone strings in the US of the form '(704) 876-1734'</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Source of text domain summary: The name of the source for this text domain. description: The source element is the name of the source from which this text domain and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be a researcher's custom way of recording and classifying their data, and no external "source" would exist. example: ISO country codes</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -4597,25 +3775,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="definition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Text domain definition summary: Definition of what this text domain represents description: The element definition provides the text domain definition, that is, what kinds of text expressions are allowed for this attribute. If there is a pattern supplied, the definition element expresses the meaning of the pattern, For example, a particular pattern may be meant to represent phone numbers in the US phone system format. A definition element may also be used to extend an enumerated domain. example: US telephone numbers in the format "(999) 888-7777"</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4744,25 +3903,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="pattern" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Text pattern summary: Regular expression pattern constraining the attribute description: The pattern element specifies a regular expression pattern that constrains the set of allowable values for the attribute. This is commonly used to define template patterns for data such as phone numbers where the attribute is text but the values are not drawn from an enumeration. If the pattern field is empty or missing, it defaults to '.*', which matches any string, including the empty string. Repeated pattern elements are combined using logical OR. The regular expression syntax is the same as that used in the XML Schema Datatypes Recommendation from the W3C. example: '[0-9a-zA-Z]' matches simple alphanumeric strings and '(\d\d\d) \d\d\d-\d\d\d\d' represents telephone strings in the US of the form '(704) 876-1734'</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4881,25 +4021,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Source of text domain summary: The name of the source for this text domain. description: The source element is the name of the source from which this text domain and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be a researcher's custom way of recording and classifying their data, and no external "source" would exist. example: ISO country codes</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5012,30 +4133,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="ordinal">
- <xs:annotation>
- <xs:documentation>tooltip: Ordinal scale summary: Characteristics used to define ordinal (ordered) scale attributes description: This field is used for defining the characteristics of this variable if it is an ordinal scale variable, which specify ordered values without specifying the magnitude of the difference between values. Ordinal is used when the categories have a logical or ordered relationship to each other. These types of scale allow one to distinguish the order of values, but not the magnitude of the difference between values. An example of an ordinal scale is a categorical survey where you rank a variable 1=good, 2=fair, 3=poor.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
<xs:element name="interval">
- <xs:annotation>
- <xs:documentation>tooltip: Interval scale summary: Characteristics used to define interval scale attributes description: This field is used for defining the characteristics of this variable if it is an interval scale variable, which specifies both the order and magnitude of values, but has no natural zero point. Interval is used for data which consist of equidistant points on a scale. The Celsius scale is an interval scale, since each degree is equal but there is no natural zero point (so, 20 C is not twice as hot as 10 C). zero point (so, 20 C is not twice as hot as 10 C).</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="unit" type="UnitType"/>
- <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
- <xs:element name="numericDomain" type="NumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -5399,21 +4455,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="unit" type="UnitType"/>
-
-
-
-
-
@@ -5504,25 +4545,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="standardUnit" type="unit:StandardUnitDictionary">
- <xs:annotation>
- <xs:documentation>tooltip: Standard Unit summary: The name of a standard unit used to make this measurement description: Use the standardUnit element if the unit for this attribute has been defined in the Standard Unit Dictionary. The list of "standard" units includes the SI base units and many compound units based on SI, plus and some commonly used units which are not SI. The list is by no means exhaustive. If the unit you need is not part of this list, then the customUnit field should be used instead. Standard units have been described using STMML. See the documentation for the Type for more information. example: meter example: second example: joule</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5634,25 +4656,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="customUnit" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Custom Unit summary: The name of a custom unit used to make this measurement. description: The customUnit element is for units that are not part of the standard list provided with EML. The customUnit must correspond to an id in the document where its definition is provided using the STMML syntax. The customUnit definition will most likely be in the additionalMetadata section. example: gramsPerOneThirdMeter</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:element name="bounds" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Bounds summary: Elements for specifying allowed values range. description: The bounds element in the BoundsGroup contains the minimum and maximum values of a numeric attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). Either or both a minimum and maximum may be set, and each has an attribute "exclusive" to define how the value should be interpreted.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="minimum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum numeric bound summary: Minimum numeric bound of attribute description: The minimum element specifies the minimum permitted value of a numeric attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:float">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="maximum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum numeric bound summary: Maximum numeric bound of attribute description: The maximum element specifies the maximum permitted value of a numeric attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:float">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -6364,36 +5263,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="minimum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum numeric bound summary: Minimum numeric bound of attribute description: The minimum element specifies the minimum permitted value of a numeric attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:float">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -6528,36 +5397,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="maximum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum numeric bound summary: Maximum numeric bound of attribute description: The maximum element specifies the maximum permitted value of a numeric attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:float">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -6674,32 +5513,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="ratio">
- <xs:annotation>
- <xs:documentation>tooltip: Ratio scale summary: Characteristics used to define ratio scale attributes description: This field is used for defining the characteristics of this variable if it is a ratio scale variable, which specifies the order and magnitude of values and has a natural zero point, allowing for ratio comparisons to be valid. Ratio is used for data which consists not only of equidistant points but also has a meaningful zero point, which allows ratios to have meaning. An example of a ratio scale would be the Kelvin temperature scale (200K is half as hot as 400K), and length in meters (e.g., 10 meters is twice as long as 5 meters).</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="unit" type="UnitType"/>
- <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
- <xs:element name="numericDomain" type="NumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
<xs:element name="dateTime">
- <xs:annotation>
- <xs:documentation>tooltip: Date/Time scale summary: Characteristics used to define date and time attributes description: The dateTime field is used for defining the characteristics of the attribute if it contains date and time values. DateTime is used when the values fall on the Gregorian calendar system. DateTime values are special because they have properties of interval values (most of the time it is legitimate to treat them as interval values by converting them to a duration from a fixed point) but they sometimes only behave as ordinals (because the calendar is not predetermined, for some dateTime values one can only find out the order of the points and not the magnitude of the duration between those points). Thus, the dateTime scale provides the information necessary to properly understand and parse date and time values without improperly labeling them under one of the more traditional scales. Date and time values are unlike any other measured values. Note that the dateTime field would not be used if one is recording time durations. In that case, one should use a standard unit such as seconds, nominalMinute or nominalDay, or a customUnit that defines the unit in terms of its relationship to SI second.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="formatString" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Date/Time Format summary: A format string that describes the format for a date-time value from the Gregorian calendar. description: A format string that describes the format for a dateTime value from the Gregorian calendar. DateTime values should be expressed in a format that conforms to the ISO 8601 standard. This field allows one to specify the format string that should be used to decode the date or time value. To describe the format of an attribute containing dateTime values, construct a string representation of the format using the following symbols: Y year M month W month abbreviation (e.g., JAN) D day h hour m minute s second T time designator (demarcates date and time parts of date-time) Z UTC designator, indicating value is in UTC time . indicates a decimal fraction of a unit +/- indicates a positive or negative number, or a positive or negative time zone adjustment relative to UTC - indicates a separator between date components A/P am or pm designator Any other character in the format string is interpreted as a separator character. Here are some examples of the format strings that can be constructed. Format string Example value ------------------- ------------------ ISO Date YYYY-MM-DD 2002-10-14 ISO Datetime YYYY-MM-DDThh:mm:ss 2002-10-14T09:13:45 ISO Time hh:mm:ss 17:13:45 ISO Time hh:mm:ss.sss 09:13:45.432 ISO Time hh:mm.mm 09:13.42 Non-standard DD/MM/YYYY 14/10/2002 Non-standard MM/DD/YYYY 10/14/2002 Non-standard MM/DD/YY 10/14/02 Non-standard YYYY-MMM-DD 2002-OCT-14 Non-standard YYYYMMMDD 2002OCT14 Non-standard YYYY-MM-DD hh:mm:ss 2002-10-14 09:13:45 Some notes about these examples. First, the ISO 8601 standard is strict about the date components, their order, and the separators; e.g., date parts are upper case, and time parts are lower case. If no UTC relation information is given, the time is assumed to be in local time. Assuming local time is ambiguous even when communicating within a single time zone, given variations in Daylight Saving Time. Best practice is to follow the ISO 8601 format precisely and accurately. In particular, please note that these are all non-standard according to ISO: use of a slash (/) to separate date components, a space to separate date and time components, using a twelve-hour time with am/pm designator, placing any of the components out of descending order However, we recognize that existing data contain non-standard dates, and existing equipment (e.g., sensors) may still be producing non-standard dates. Further, data parsers often apply individual interpretations. E.g., Java interprets HH on a 24-hr clock and hh on a 12-hr clock, and MM as a padded integer for month but MMM as a 3-letter abbreviation. Consequently, the formatting string can contain characters as needed to accommodate existing data. Decimal dateTime values can be extended by indicating in the format that additional decimals can be used. Only the final unit (e.g., seconds in a time value) can use the extended digits according to the ISO 8601 standard. For example, to show indicate that seconds are represented to the nearest 1/1000 of a second, the format string would be "hh:mm:ss.sss". Note that this only indicates the number of decimals used to record the value, and not the precision of the measurement (see dateTimePrecision for that). Date and time values are from an interval scale, but it is extremely complex because of the vagaries of the calendar (e.g., leap years, and leap seconds). The duration between date and time values in the future is not even deterministic because leap seconds are based on current measurements of the earth's orbit. Consequently, date and time values are unlike any other measured values. The format string for dateTime values allows one to accurately calculate the duration in SI second units between two measured dateTime values, assuming that the conversion software has a detailed knowledge of the Gregorian calendar. example: YYYY-MM-DDThh:mm:ss example: YYYY-MM-DD example: YYYY example: hh:mm:ss example: hh:mm:ss.sss</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dateTimePrecision" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Precision summary: An indication of the precision of a date or time value description: A quantitative indication of the precision of a date or time measurement. The precision should be interpreted in the smallest units represented by the dateTime format. For example, if a dateTime value has a format of "hh:mm:ss.sss", then "seconds" are the smallest unit and the precision should be expressed in seconds. Thus, a precision value of "0.01" would mean that measurements were precise to the nearest hundredth of a second, even though the format string might indicate that values were written down with 3 decimal places. example: 0.1 example: 0.01</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dateTimeDomain" type="DateTimeDomainType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Domain summary: See the summary for the type: DateTimeDomainType description: See the description for the type: DateTimeDomainType</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -7398,25 +6128,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="formatString" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Date/Time Format summary: A format string that describes the format for a date-time value from the Gregorian calendar. description: A format string that describes the format for a dateTime value from the Gregorian calendar. DateTime values should be expressed in a format that conforms to the ISO 8601 standard. This field allows one to specify the format string that should be used to decode the date or time value. To describe the format of an attribute containing dateTime values, construct a string representation of the format using the following symbols: Y year M month W month abbreviation (e.g., JAN) D day h hour m minute s second T time designator (demarcates date and time parts of date-time) Z UTC designator, indicating value is in UTC time . indicates a decimal fraction of a unit +/- indicates a positive or negative number, or a positive or negative time zone adjustment relative to UTC - indicates a separator between date components A/P am or pm designator Any other character in the format string is interpreted as a separator character. Here are some examples of the format strings that can be constructed. Format string Example value ------------------- ------------------ ISO Date YYYY-MM-DD 2002-10-14 ISO Datetime YYYY-MM-DDThh:mm:ss 2002-10-14T09:13:45 ISO Time hh:mm:ss 17:13:45 ISO Time hh:mm:ss.sss 09:13:45.432 ISO Time hh:mm.mm 09:13.42 Non-standard DD/MM/YYYY 14/10/2002 Non-standard MM/DD/YYYY 10/14/2002 Non-standard MM/DD/YY 10/14/02 Non-standard YYYY-MMM-DD 2002-OCT-14 Non-standard YYYYMMMDD 2002OCT14 Non-standard YYYY-MM-DD hh:mm:ss 2002-10-14 09:13:45 Some notes about these examples. First, the ISO 8601 standard is strict about the date components, their order, and the separators; e.g., date parts are upper case, and time parts are lower case. If no UTC relation information is given, the time is assumed to be in local time. Assuming local time is ambiguous even when communicating within a single time zone, given variations in Daylight Saving Time. Best practice is to follow the ISO 8601 format precisely and accurately. In particular, please note that these are all non-standard according to ISO: use of a slash (/) to separate date components, a space to separate date and time components, using a twelve-hour time with am/pm designator, placing any of the components out of descending order However, we recognize that existing data contain non-standard dates, and existing equipment (e.g., sensors) may still be producing non-standard dates. Further, data parsers often apply individual interpretations. E.g., Java interprets HH on a 24-hr clock and hh on a 12-hr clock, and MM as a padded integer for month but MMM as a 3-letter abbreviation. Consequently, the formatting string can contain characters as needed to accommodate existing data. Decimal dateTime values can be extended by indicating in the format that additional decimals can be used. Only the final unit (e.g., seconds in a time value) can use the extended digits according to the ISO 8601 standard. For example, to show indicate that seconds are represented to the nearest 1/1000 of a second, the format string would be "hh:mm:ss.sss". Note that this only indicates the number of decimals used to record the value, and not the precision of the measurement (see dateTimePrecision for that). Date and time values are from an interval scale, but it is extremely complex because of the vagaries of the calendar (e.g., leap years, and leap seconds). The duration between date and time values in the future is not even deterministic because leap seconds are based on current measurements of the earth's orbit. Consequently, date and time values are unlike any other measured values. The format string for dateTime values allows one to accurately calculate the duration in SI second units between two measured dateTime values, assuming that the conversion software has a detailed knowledge of the Gregorian calendar. example: YYYY-MM-DDThh:mm:ss example: YYYY-MM-DD example: YYYY example: hh:mm:ss example: hh:mm:ss.sss</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7540,25 +6251,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dateTimePrecision" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Precision summary: An indication of the precision of a date or time value description: A quantitative indication of the precision of a date or time measurement. The precision should be interpreted in the smallest units represented by the dateTime format. For example, if a dateTime value has a format of "hh:mm:ss.sss", then "seconds" are the smallest unit and the precision should be expressed in seconds. Thus, a precision value of "0.01" would mean that measurements were precise to the nearest hundredth of a second, even though the format string might indicate that values were written down with 3 decimal places. example: 0.1 example: 0.01</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7703,25 +6395,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dateTimeDomain" type="DateTimeDomainType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Domain summary: See the summary for the type: DateTimeDomainType description: See the description for the type: DateTimeDomainType</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7840,61 +6513,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="bounds" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Bounds summary: Elements for specifying allowed date range. description: The bounds element in the BoundsDateGroup contains the minimum and maximum dates of a dateTime attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). Either or both a minimum and maximum may be set, and each has an attribute "exclusive" to define how the value should be interpreted.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="minimum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum date bound summary: Minimum date bound of attribute description: The minimum element specifies the minimum permitted value of a date attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="maximum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum date bound summary: Maximum date bound of attribute description: The maximum element specifies the maximum permitted value of a date attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -8029,36 +6647,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="minimum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum date bound summary: Minimum date bound of attribute description: The minimum element specifies the minimum permitted value of a date attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -8193,36 +6781,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="maximum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum date bound summary: Maximum date bound of attribute description: The maximum element specifies the maximum permitted value of a date attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -8342,39 +6900,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="missingValueCode" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Character for missing value summary: Character for missing value in the data of the field description: This element is to specify missing value in the data of the field. It is repeatable to allow for multiple different codes to be present in the attribute. Note that missing value codes should not be considered when determining if the observed values of an attribute all fall within the domain of the attribute (i.e., missing value codes should be parsed out of the data stream before examining the data for domain violations.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="code" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: The missing value code itself. summary: The missing value code itself. description: The code element is the missing value code itself. Each missing value code should be entered in a separate element instance. The value entered is what is placed into a data grid if the value is missing for some reason. example: -9999 example: -1 example: N/A example: MISSING</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="codeExplanation" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Explanation of Missing value Code summary: An explanation of what the missing value code means. description: The codeExplanation element is an explanation of the meaning of the missing value code that was used, that is, the reason that there is a missing value. For example, an attribute might have a missing value code of '-99' to indicate that the data observation was not actually taken, and a code of '-88' to indicate that the data value was removed because of calibration errors. example: Sensor down time. example: Technician error.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -8490,25 +7015,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="code" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: The missing value code itself. summary: The missing value code itself. description: The code element is the missing value code itself. Each missing value code should be entered in a separate element instance. The value entered is what is placed into a data grid if the value is missing for some reason. example: -9999 example: -1 example: N/A example: MISSING</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8624,25 +7130,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="codeExplanation" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Explanation of Missing value Code summary: An explanation of what the missing value code means. description: The codeExplanation element is an explanation of the meaning of the missing value code that was used, that is, the reason that there is a missing value. For example, an attribute might have a missing value code of '-99' to indicate that the data observation was not actually taken, and a code of '-88' to indicate that the data value was removed because of calibration errors. example: Sensor down time. example: Technician error.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8764,25 +7251,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="accuracy" type="Accuracy" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: The accuracy of the measured attribute summary: The accuracy of the attribute. This information should describe any accuracy information that is known about the collection of this data attribute. description: The accuracy element represents the accuracy of the attribute. This information should describe any accuracy information that is known about the collection of this data attribute. The content model of this metadata is taken directly from FGDC FGDC-STD-001-1998 section 2 with the exception of processContact, sourceCitation, and timePeriodInformation which either user XMLSchema types or use predefined EML types for these purposes.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8892,25 +7360,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeAccuracyReport" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Accuracy Report summary: An explanatory report of the accuracy of the attribute. description: The attributeAccuracyReport element is an explanation of the accuracy of the observation recorded in this attribute. It will often include a description of the tests used to determine the accuracy of the observation. These reports are generally prepared for remote sensing or other measurement devices.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9027,39 +7476,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quantitativeAttributeAccuracyAssessment" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Attribute Accuracy Assessment summary: A value assigned to summarize the accuracy of the attribute. description: The quantitativeAttributeAccuracyAssessment element is composed of two parts, a value that represents the accuracy of the recorded observation an explanation of the tests used to determine the accuracy.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Accuracy Value summary: A value assigned to estimate the accuracy of the attribute. description: The attributeAccuracyValue element is an estimate of the accuracy of the identification of the entities and assignments of attribute values in the data set.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="attributeAccuracyExplanation" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Accuracy Explanation summary: The test which yields the Attribute Accuracy Value. description: The attributeAccuracyExplanation element is the identification of the test that yielded the Attribute Accuracy Value.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -9166,25 +7582,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Accuracy Value summary: A value assigned to estimate the accuracy of the attribute. description: The attributeAccuracyValue element is an estimate of the accuracy of the identification of the entities and assignments of attribute values in the data set.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9291,25 +7688,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeAccuracyExplanation" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Accuracy Explanation summary: The test which yields the Attribute Accuracy Value. description: The attributeAccuracyExplanation element is the identification of the test that yielded the Attribute Accuracy Value.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9485,25 +7863,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="coverage" type="cov:Coverage" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute coverage summary: An explanation of the coverage of the attribute. description: An explanation of the coverage of the attribute. This specifically indicates the spatial, temporal, and taxonomic coverage of the attribute in question when that coverage deviates from coverages expressed at a higher level (e.g., entity or dataset). Please see the eml-coverage module for complete documentation.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9623,25 +7982,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="methods" type="md:MethodsType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute methods summary: An explanation of the methods involved in the collection of this attribute. description: An explanation of the methods involved in the collection of this attribute. These specifically supplement or possibly override methods provided at a higher level such as entity or dataset. Please see the eml-methods module for complete documentation.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9824,25 +8164,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="annotation" type="sem:SemanticAnnotation" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement for this attribute. description: An annotation represents a precisely-defined semantic statement that applies to this attribute. This semantic statement is used to associate precise measurement semantics with the attribute, such as the property that is being measured (e.g., oboe:Characteristic), the entity that is being measured (e.g., oboe:Entity), and the measurement standard for interpreting values for this attribute (e.g., oboe:Standard). Each annotation consists of a propertyURI and valueURI that define the property and value of the statement. The subject of the statement is the eml:attribute that contains the annotation. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10038,25 +8359,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attribute" type="AttributeType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute summary: Characteristics of a 'field' or 'variable' in a data entity (ie. dataTable). description: The content model for attribute is a CHOICE between "references" and all of the elements that let you describe the attribute (e.g., attributeName, attributeDefinition, precision). The attribute element allows a user to document the characteristics that describe a 'field' or 'variable' in a data entity (e.g. dataTable). Complete attribute descriptions are perhaps the most important aspect to making data understandable to others. An attribute element describes a single attribute or an attribute element can contain a reference to an attribute defined elsewhere. Using a reference means that the referenced attribute is (semantically) identical, not just in name but identical in its complete description. For example, if attribute "measurement1" in dataTable "survey1" has a precision of 0.1 and you are documenting dataTable survey2 which has an attribute called "measurement1" but the survey2's measurement1 has a precision of 0.001 then these are different attributes and must be described separately.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10199,25 +8501,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeList" type="AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute list summary: A list of attributes description: This is the root element of the eml-attribute module. It is mainly used for testing, but can also be used for creating stand-alone eml-attribute modules where a list of attributes is needed.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: List of attributes description: This complexType defines the structure of the attributeList element. The content model is a choice between one or more attribute elements, and references. References links to an attribute list defined elsewhere.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:element name="attribute" type="AttributeType" maxOccurs="unbounded"/>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
-</xs:complexType>
<xs:complexType name="AttributeType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Type summary: Type definition for the content of an attribute (variable) that can be part of an entity. description: Type definition for the content of an attribute (variable) that can be part of an entity.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="attributeName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute name summary: The name of the attribute description: Attribute name is official name of the attribute. This is usually a short, sometimes cryptic name that is used to refer to the attribute. Many systems have restrictions on the length of attribute names, and on the use of special characters like spaces in the name, so the attribute name is often not particularly useful for display (use attributeLabel for display). The attributeName is usually the name of the variable that is found in the header of a data file. example: spden example: spatialden example: site example: spcode</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="attributeLabel" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute label summary: A label for displaying an attribute name. description: A descriptive label that can be used to display the name of an attribute. This is often a longer, possibly multiple word name for the attribute than the attributeName. It is not constrained by system limitations on length or special characters. For example, an attribute with a name of 'spcode' might have an attributeLabel of 'Species Code'. example: Species Density example: Spatial Density example: Name of Site example: Species Code</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="attributeDefinition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute definition summary: Precise definition of the attribute description: This element gives a precise definition of attribute in the data entity (dataTable, spatialRaster, spatialVector, storedProcedure, view or otherEntity) being documented. It explains the contents of the attribute fully so that a data user could interpret the attribute accurately. Some additional information may also be found in the methods element as well. example: "spden" is the number of individuals of all macro invertebrate species found in the plot</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="storageType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Storage Type summary: Storage type hint for this field description: This element describes the storage type, for data in a RDBMS (or other data management system) field. As many systems do not provide for fine-grained restrictions on types, this type will often be a superset of the allowed domain defined in attributeDomain. Values for this field are by default drawn from the XML Schema Datatypes standard values, such as: integer, double, string, etc. If the XML Schema Datatypes are not used, the type system from which the values are derived should be listed in the 'typeSystem' attribute described below. This field represents a 'hint' to processing systems as to how the attribute might be represented in a system or language, but is distinct from the actual expression of the domain of the attribute. The field is repeatable so that the storageType can be indicated for multiple type systems (e.g., Oracle data types and Java data types). example: integer example: int</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="typeSystem" type="xs:string" use="optional" default="http://www.w3.org/2001/XMLSchema-datatypes">
- <xs:annotation>
- <xs:documentation>tooltip: Storage Type System summary: The system used to define the storage types. This should be an identifier of a well known and published typing system. description: The typeSystem attribute is the system used to define the storage types. This should be an identifier of a well known and published typing system. The default and recommended system is the XML Schema data type system. For details go to http://www.w3.org. If another system is used (such as Java or C++ types), typeSystem should be changed to match the system. example: http://www.w3.org/2001/XMLSchema-datatypes example: java example: C example: Oracle 8i</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="measurementScale">
- <xs:annotation>
- <xs:documentation>tooltip: Measurement Scale summary: The measurement scale for the attribute. description: The measurementScale element indicates the type of scale from which values are drawn for the attribute. This provides information about the scale in which the data was collected. example: Nominal is used when numbers have only been assigned to a variable for the purpose of categorizing the variable. An example of a nominal scale is assigning the number 1 for male and 2 for female. example: Ordinal is used when the categories have a logical or ordered relationship to each other. These types of scale allow one to distinguish the order of values, but not the magnitude of the difference between values. An example of an ordinal scale is a categorical survey where you rank a variable 1=good, 2=fair, 3=poor. example: Interval is used for data which consist of equidistant points on a scale. The Celsius scale is an interval scale, since each degree is equal but there is no natural zero point (so, 20 C is not twice as hot as 10 C). example: Ratio is used for data which consists not only of equidistant points but also has a meaningful zero point, which allows ratios to have meaning. An example of a ratio scale would be the Kelvin temperature scale (200K is half as hot as 400K), and length in meters (e.g., 10 meters is twice as long as 5 meters).</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="nominal">
- <xs:annotation>
- <xs:documentation>tooltip: Nominal scale summary: Characteristics used to define nominal (categorical) scale attributes description: This field is used for defining the characteristics of this variable if it is a nominal scale variable, which are variables that are categorical in nature. Nominal is used when numbers have only been assigned to a variable for the purpose of categorizing the variable. An example of a nominal scale is assigning the number 1 for male and 2 for female.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="ordinal">
- <xs:annotation>
- <xs:documentation>tooltip: Ordinal scale summary: Characteristics used to define ordinal (ordered) scale attributes description: This field is used for defining the characteristics of this variable if it is an ordinal scale variable, which specify ordered values without specifying the magnitude of the difference between values. Ordinal is used when the categories have a logical or ordered relationship to each other. These types of scale allow one to distinguish the order of values, but not the magnitude of the difference between values. An example of an ordinal scale is a categorical survey where you rank a variable 1=good, 2=fair, 3=poor.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="interval">
- <xs:annotation>
- <xs:documentation>tooltip: Interval scale summary: Characteristics used to define interval scale attributes description: This field is used for defining the characteristics of this variable if it is an interval scale variable, which specifies both the order and magnitude of values, but has no natural zero point. Interval is used for data which consist of equidistant points on a scale. The Celsius scale is an interval scale, since each degree is equal but there is no natural zero point (so, 20 C is not twice as hot as 10 C). zero point (so, 20 C is not twice as hot as 10 C).</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="unit" type="UnitType"/>
- <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
- <xs:element name="numericDomain" type="NumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="ratio">
- <xs:annotation>
- <xs:documentation>tooltip: Ratio scale summary: Characteristics used to define ratio scale attributes description: This field is used for defining the characteristics of this variable if it is a ratio scale variable, which specifies the order and magnitude of values and has a natural zero point, allowing for ratio comparisons to be valid. Ratio is used for data which consists not only of equidistant points but also has a meaningful zero point, which allows ratios to have meaning. An example of a ratio scale would be the Kelvin temperature scale (200K is half as hot as 400K), and length in meters (e.g., 10 meters is twice as long as 5 meters).</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="unit" type="UnitType"/>
- <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
- <xs:element name="numericDomain" type="NumericDomainType"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="dateTime">
- <xs:annotation>
- <xs:documentation>tooltip: Date/Time scale summary: Characteristics used to define date and time attributes description: The dateTime field is used for defining the characteristics of the attribute if it contains date and time values. DateTime is used when the values fall on the Gregorian calendar system. DateTime values are special because they have properties of interval values (most of the time it is legitimate to treat them as interval values by converting them to a duration from a fixed point) but they sometimes only behave as ordinals (because the calendar is not predetermined, for some dateTime values one can only find out the order of the points and not the magnitude of the duration between those points). Thus, the dateTime scale provides the information necessary to properly understand and parse date and time values without improperly labeling them under one of the more traditional scales. Date and time values are unlike any other measured values. Note that the dateTime field would not be used if one is recording time durations. In that case, one should use a standard unit such as seconds, nominalMinute or nominalDay, or a customUnit that defines the unit in terms of its relationship to SI second.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="formatString" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Date/Time Format summary: A format string that describes the format for a date-time value from the Gregorian calendar. description: A format string that describes the format for a dateTime value from the Gregorian calendar. DateTime values should be expressed in a format that conforms to the ISO 8601 standard. This field allows one to specify the format string that should be used to decode the date or time value. To describe the format of an attribute containing dateTime values, construct a string representation of the format using the following symbols: Y year M month W month abbreviation (e.g., JAN) D day h hour m minute s second T time designator (demarcates date and time parts of date-time) Z UTC designator, indicating value is in UTC time . indicates a decimal fraction of a unit +/- indicates a positive or negative number, or a positive or negative time zone adjustment relative to UTC - indicates a separator between date components A/P am or pm designator Any other character in the format string is interpreted as a separator character. Here are some examples of the format strings that can be constructed. Format string Example value ------------------- ------------------ ISO Date YYYY-MM-DD 2002-10-14 ISO Datetime YYYY-MM-DDThh:mm:ss 2002-10-14T09:13:45 ISO Time hh:mm:ss 17:13:45 ISO Time hh:mm:ss.sss 09:13:45.432 ISO Time hh:mm.mm 09:13.42 Non-standard DD/MM/YYYY 14/10/2002 Non-standard MM/DD/YYYY 10/14/2002 Non-standard MM/DD/YY 10/14/02 Non-standard YYYY-MMM-DD 2002-OCT-14 Non-standard YYYYMMMDD 2002OCT14 Non-standard YYYY-MM-DD hh:mm:ss 2002-10-14 09:13:45 Some notes about these examples. First, the ISO 8601 standard is strict about the date components, their order, and the separators; e.g., date parts are upper case, and time parts are lower case. If no UTC relation information is given, the time is assumed to be in local time. Assuming local time is ambiguous even when communicating within a single time zone, given variations in Daylight Saving Time. Best practice is to follow the ISO 8601 format precisely and accurately. In particular, please note that these are all non-standard according to ISO: use of a slash (/) to separate date components, a space to separate date and time components, using a twelve-hour time with am/pm designator, placing any of the components out of descending order However, we recognize that existing data contain non-standard dates, and existing equipment (e.g., sensors) may still be producing non-standard dates. Further, data parsers often apply individual interpretations. E.g., Java interprets HH on a 24-hr clock and hh on a 12-hr clock, and MM as a padded integer for month but MMM as a 3-letter abbreviation. Consequently, the formatting string can contain characters as needed to accommodate existing data. Decimal dateTime values can be extended by indicating in the format that additional decimals can be used. Only the final unit (e.g., seconds in a time value) can use the extended digits according to the ISO 8601 standard. For example, to show indicate that seconds are represented to the nearest 1/1000 of a second, the format string would be "hh:mm:ss.sss". Note that this only indicates the number of decimals used to record the value, and not the precision of the measurement (see dateTimePrecision for that). Date and time values are from an interval scale, but it is extremely complex because of the vagaries of the calendar (e.g., leap years, and leap seconds). The duration between date and time values in the future is not even deterministic because leap seconds are based on current measurements of the earth's orbit. Consequently, date and time values are unlike any other measured values. The format string for dateTime values allows one to accurately calculate the duration in SI second units between two measured dateTime values, assuming that the conversion software has a detailed knowledge of the Gregorian calendar. example: YYYY-MM-DDThh:mm:ss example: YYYY-MM-DD example: YYYY example: hh:mm:ss example: hh:mm:ss.sss</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dateTimePrecision" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Precision summary: An indication of the precision of a date or time value description: A quantitative indication of the precision of a date or time measurement. The precision should be interpreted in the smallest units represented by the dateTime format. For example, if a dateTime value has a format of "hh:mm:ss.sss", then "seconds" are the smallest unit and the precision should be expressed in seconds. Thus, a precision value of "0.01" would mean that measurements were precise to the nearest hundredth of a second, even though the format string might indicate that values were written down with 3 decimal places. example: 0.1 example: 0.01</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dateTimeDomain" type="DateTimeDomainType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Domain summary: See the summary for the type: DateTimeDomainType description: See the description for the type: DateTimeDomainType</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="missingValueCode" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Character for missing value summary: Character for missing value in the data of the field description: This element is to specify missing value in the data of the field. It is repeatable to allow for multiple different codes to be present in the attribute. Note that missing value codes should not be considered when determining if the observed values of an attribute all fall within the domain of the attribute (i.e., missing value codes should be parsed out of the data stream before examining the data for domain violations.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="code" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: The missing value code itself. summary: The missing value code itself. description: The code element is the missing value code itself. Each missing value code should be entered in a separate element instance. The value entered is what is placed into a data grid if the value is missing for some reason. example: -9999 example: -1 example: N/A example: MISSING</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="codeExplanation" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Explanation of Missing value Code summary: An explanation of what the missing value code means. description: The codeExplanation element is an explanation of the meaning of the missing value code that was used, that is, the reason that there is a missing value. For example, an attribute might have a missing value code of '-99' to indicate that the data observation was not actually taken, and a code of '-88' to indicate that the data value was removed because of calibration errors. example: Sensor down time. example: Technician error.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="accuracy" type="Accuracy" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: The accuracy of the measured attribute summary: The accuracy of the attribute. This information should describe any accuracy information that is known about the collection of this data attribute. description: The accuracy element represents the accuracy of the attribute. This information should describe any accuracy information that is known about the collection of this data attribute. The content model of this metadata is taken directly from FGDC FGDC-STD-001-1998 section 2 with the exception of processContact, sourceCitation, and timePeriodInformation which either user XMLSchema types or use predefined EML types for these purposes.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="coverage" type="cov:Coverage" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute coverage summary: An explanation of the coverage of the attribute. description: An explanation of the coverage of the attribute. This specifically indicates the spatial, temporal, and taxonomic coverage of the attribute in question when that coverage deviates from coverages expressed at a higher level (e.g., entity or dataset). Please see the eml-coverage module for complete documentation.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="methods" type="md:MethodsType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute methods summary: An explanation of the methods involved in the collection of this attribute. description: An explanation of the methods involved in the collection of this attribute. These specifically supplement or possibly override methods provided at a higher level such as entity or dataset. Please see the eml-methods module for complete documentation.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="annotation" type="sem:SemanticAnnotation" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement for this attribute. description: An annotation represents a precisely-defined semantic statement that applies to this attribute. This semantic statement is used to associate precise measurement semantics with the attribute, such as the property that is being measured (e.g., oboe:Characteristic), the entity that is being measured (e.g., oboe:Entity), and the measurement standard for interpreting values for this attribute (e.g., oboe:Standard). Each annotation consists of a propertyURI and valueURI that define the property and value of the statement. The subject of the statement is the eml:attribute that contains the annotation. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="NonNumericDomainType">
- <xs:annotation>
- <xs:documentation>tooltip: Non-numeric domain summary: description: The non-numeric domain field describes the domain of the attribute being documented. It can describe two different types of domains: enumerated and text. Enumerated domains are lists of values that are explicitly provided as legitimate values. Only values from that list should occur in the attribute. They are often used for response codes such as "HIGH" and "LOW". Text domains are used for attributes that allow more free-form text fields, but still permit some specification of the value-space through pattern matching. A text domain is usually used for comment and notes attributes, and other character attributes that don't have a precise set of constrained values. This is an important field for post processing and error checking of the dataset. It represents a formal specification of the value space for the attribute, and so there should never be a value for the attribute that falls outside of the set of values prescribed by the domain.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="enumeratedDomain">
- <xs:annotation>
- <xs:documentation>tooltip: Enumerated domain summary: Description of any coded values associated with the attribute. description: The enumeratedDomain element describes any code that is used as a value of an attribute. These codes can be defined here in the metadata as a list with definitions (preferred), can be referenced by pointing to an external citation or URL where the codes are defined, or can be referenced by pointing at an entity that contains the code value and code definition as two attributes. For example, data might have a variable named 'site' with values 'A', 'B', and 'C', and the enumeratedDomain would explain how to interpret those codes.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="codeDefinition" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Code Definition summary: A codes and its definition description: This element gives the value of a particular code and its definition. It is repeatable to allow for a list of codes to be provided.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="code" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code summary: Code value allowed in the domain description: The code element specifies a code value that can be used in the domain example: 1 example: HIGH example: BEPA example: 24</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="definition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code definition summary: Definition of the associated code description: The definition describes the code with which it is associated in enough detail for scientists to interpret the meaning of the coded values. example: high density, above 10 per square meter</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Source of code summary: The name of the source for this code and its definition description: The source element is the name of the source from which this code and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be the researcher's customized way of recording and classifying their data, and no external "source" would exist. example: ISO country codes</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="order" type="xs:long" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Order summary: Mechanism for specifying what the order of the code-definitions included should be description: Ordinal scale measurements have a discrete list of values with a specific ordering of those values. This attributes specifies that order from low to high. For example, for LOW, MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and HIGH=3".</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="externalCodeSet">
- <xs:annotation>
- <xs:documentation>tooltip: External code set summary: A reference to an externally defined set of codes used in this attribute description: The externalCodeSet element is a reference to an externally defined set of codes used in this attribute. This can either be a citation (using the eml-citation module) or a URL. Using an externally defined codeset (rather than a codeDefinition) means that interpretation of the data is dependent upon future users being able to obtain the code definitions, so care should be taken to only use highly standardized external code sets that will be available for many years. If at all possible, it is preferable to define the codes inline using the codeDefinition element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="codesetName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Code Set Name summary: The name of an externally defined code set description: The codesetName element is the name of an externally defined code set. example: FIPS State Abbreviation Codes</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="citation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Citation summary: A citation for the code set reference description: The citation element is a citation for the code set reference</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="codesetURL" type="xs:anyURI">
- <xs:annotation>
- <xs:documentation>tooltip: Code set URL summary: A URL for the code set reference description: The codesetURL element is a URL for the code set reference.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="entityCodeList">
- <xs:annotation>
- <xs:documentation>tooltip: Entity Code List summary: A code list that is defined in a data table description: The entityCodeList is a list of codes and their definitions in a data entity that is present in this dataset. The fields specify exactly which entity it is, and which attributes of that entity contain the codes, their definitions, and the order of the values.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="entityReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Entity Reference summary: A reference to the id of the entity in which the code list has been defined description: The entityReference element is a reference to the id of the entity in which the code list has been defined. This entity must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="valueAttributeReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Value Attribute Reference summary: A reference to the id of the attribute that contains the list of codes description: The valueAttributeReference element is a reference to the id of the attribute that contains the list of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="definitionAttributeReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Definition Attribute Reference summary: A reference to the id of the attribute that contains the definition of codes description: The definitionAttributeReference element is a reference to the id of the attribute that contains the definition of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="orderAttributeReference" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Order Attribute Reference summary: A reference to the id of the attribute that contains the order of codes description: The orderAttributeReference element is a reference to the id of the attribute that contains the order of codes. The values in this attribute are integers indicating increasing values of the categories. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:attribute name="enforced" use="optional" default="yes">
- <xs:annotation>
- <xs:documentation>tooltip: Enforced Domain summary: Indicates whether the enumerated domain values enforced. description: Indicates whether the enumerated domain values are the only allowable values for the domain. In some exceedingly rare cases, users may wish to present a list of value codes in enumeratedDomain but not formally restrict the value space for the attribute to those values. If so, they can indicate this by setting the enforced attribute to the value no. Acceptable values are yes and no, and the default value is yes.</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="textDomain">
- <xs:annotation>
- <xs:documentation>tooltip: Text domain summary: Description of a free-text domain pattern for the attribute description: The textDomain element describes a free text domain for the attribute. By default, if a pattern is missing or empty, then any text is allowed. If a pattern is present, then it is interpreted as a regular expression constraining the allowable character sequences for the attribute. This domain type is most useful for describing extensive text domains that match a pattern but do not have a finite set of values. Another use is for describing the domain of textual fields like comments that allow any legal string value. example: Typically, a text domain will have an empty pattern or one that constrains allowable values. For example, '[0-9]{3}-[0-9]{3}-[0-9]{4}' allows for only numeric digits in the pattern of a US phone number.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="definition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Text domain definition summary: Definition of what this text domain represents description: The element definition provides the text domain definition, that is, what kinds of text expressions are allowed for this attribute. If there is a pattern supplied, the definition element expresses the meaning of the pattern, For example, a particular pattern may be meant to represent phone numbers in the US phone system format. A definition element may also be used to extend an enumerated domain. example: US telephone numbers in the format "(999) 888-7777"</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pattern" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Text pattern summary: Regular expression pattern constraining the attribute description: The pattern element specifies a regular expression pattern that constrains the set of allowable values for the attribute. This is commonly used to define template patterns for data such as phone numbers where the attribute is text but the values are not drawn from an enumeration. If the pattern field is empty or missing, it defaults to '.*', which matches any string, including the empty string. Repeated pattern elements are combined using logical OR. The regular expression syntax is the same as that used in the XML Schema Datatypes Recommendation from the W3C. example: '[0-9a-zA-Z]' matches simple alphanumeric strings and '(\d\d\d) \d\d\d-\d\d\d\d' represents telephone strings in the US of the form '(704) 876-1734'</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Source of text domain summary: The name of the source for this text domain. description: The source element is the name of the source from which this text domain and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be a researcher's custom way of recording and classifying their data, and no external "source" would exist. example: ISO country codes</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
-</xs:complexType>
<xs:complexType name="UnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Unit of measurement summary: Unit of measurement for data in the field description: This field identifies the unit of measurement for this attribute. It is a choice of either a standard unit, or a custom unit. If it is a custom unit, the definition of the unit must be provided in the document using the STMML syntax, and the name provided in the customUnit element must reference the id of its associated STMML definition precisely. For further information on STMML (http://www.xml-cml.org/stmml/) or see stmml.xsd which is included with the EML 2.0 distribution for details.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:element name="standardUnit" type="unit:StandardUnitDictionary">
- <xs:annotation>
- <xs:documentation>tooltip: Standard Unit summary: The name of a standard unit used to make this measurement description: Use the standardUnit element if the unit for this attribute has been defined in the Standard Unit Dictionary. The list of "standard" units includes the SI base units and many compound units based on SI, plus and some commonly used units which are not SI. The list is by no means exhaustive. If the unit you need is not part of this list, then the customUnit field should be used instead. Standard units have been described using STMML. See the documentation for the Type for more information. example: meter example: second example: joule</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="customUnit" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Custom Unit summary: The name of a custom unit used to make this measurement. description: The customUnit element is for units that are not part of the standard list provided with EML. The customUnit must correspond to an id in the document where its definition is provided using the STMML syntax. The customUnit definition will most likely be in the additionalMetadata section. example: gramsPerOneThirdMeter</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
-</xs:complexType>
<xs:complexType name="PrecisionType">
- <xs:annotation>
- <xs:documentation>tooltip: Precision summary: The precision of the measurement. description: Precision indicates how close together or how repeatable measurements are. A precise measuring instrument will give very nearly the same result each time it is used. This means that someone interpreting the data should expect that if a measurement were repeated, most measured values would fall within the interval specified by the precision. The value of precision should be expressed in the same unit as the measurement. For example, for an attribute with unit "meter", a precision of "0.1" would be interpreted to mean that most repeat measurements would fall within an interval of 1/10th of a meter. example: 0.1 example: 0.5 example: 1</xs:documentation>
- </xs:annotation>
- <xs:simpleContent>
- <xs:extension base="xs:float"/>
- </xs:simpleContent>
-</xs:complexType>
<xs:complexType name="NumericDomainType">
- <xs:annotation>
- <xs:documentation>tooltip: Numeric Domain summary: Numeric domain of attribute specifying allowed values. description: The numericDomain element specifies the minimum and maximum values of a numeric attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). The information in numericDomain and in precision together constitute sufficient information to decide upon an appropriate system specific data type for representing a particular attribute. For example, an attribute with a numeric domain from 0-50,000 and a precision of 1 could be represented in the C language using a 'long' value, but if the precision is changed to '0.5' then a 'float' type would be needed.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="numberType" type="NumberType">
- <xs:annotation>
- <xs:documentation>tooltip: number type</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:group ref="BoundsGroup"/>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
-</xs:complexType>
<xs:simpleType name="NumberType">
- <xs:annotation>
- <xs:documentation>description: This is the enumeration for the allowed values of the element numberType.</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:enumeration value="natural">
- <xs:annotation>
- <xs:documentation>tooltip: Natural numbers summary: Natural numbers description: The number type for this attribute consists of the 'natural' numbers, otherwise known as the counting numbers: 1, 2, 3, 4, ...</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- <xs:enumeration value="whole">
- <xs:annotation>
- <xs:documentation>tooltip: Whole numbers summary: Whole numbers description: The number type for this attribute consists of the 'whole' numbers, which are the natural numbers plus the zero value: 0, 1, 2, 3, 4, ...</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- <xs:enumeration value="integer">
- <xs:annotation>
- <xs:documentation>tooltip: Integer numbers summary: Integer numbers description: The number type for this attribute consists of the 'integer' numbers, which are the natural numbers, plus the zero value, plus the negatives of the natural numbers: ..., -4, -3, -2, -1, 0, 1, 2, 3, 4, ...</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- <xs:enumeration value="real">
- <xs:annotation>
- <xs:documentation>tooltip: Real numbers summary: Real numbers description: The number type for this attribute consists of the 'real' numbers, which contains both the rational numbers that can be expressed as fractions and the irrational numbers that can not be expressed as fractions (such as the square root of 2). example: 4.1516 example: 2.5 example: .3333333...</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- </xs:restriction>
-</xs:simpleType>
<xs:complexType name="DateTimeDomainType">
- <xs:annotation>
- <xs:documentation>tooltip: DateTime Domain summary: DateTime domain of attribute specifying allowed values. description: The DateTimeDomain specifies the minimum and maximum values of a dateTime attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). The domain expressions should be in the same dateTime format as is used in the "formatString" description for the attribute. For example, if the format string is "YYYY-MM-DD", then a valid minimum in the domain would be "2001-05-29". The "bounds" element is optional, and if it is missing then any legitimate value from the Gregorian calendar system is allowed in the attribute as long as its representation matches its corresponding formatString.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:group ref="BoundsDateGroup"/>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
-</xs:complexType>
<xs:complexType name="Accuracy">
- <xs:sequence>
- <xs:element name="attributeAccuracyReport" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Accuracy Report summary: An explanatory report of the accuracy of the attribute. description: The attributeAccuracyReport element is an explanation of the accuracy of the observation recorded in this attribute. It will often include a description of the tests used to determine the accuracy of the observation. These reports are generally prepared for remote sensing or other measurement devices.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quantitativeAttributeAccuracyAssessment" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Attribute Accuracy Assessment summary: A value assigned to summarize the accuracy of the attribute. description: The quantitativeAttributeAccuracyAssessment element is composed of two parts, a value that represents the accuracy of the recorded observation an explanation of the tests used to determine the accuracy.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Accuracy Value summary: A value assigned to estimate the accuracy of the attribute. description: The attributeAccuracyValue element is an estimate of the accuracy of the identification of the entities and assignments of attribute values in the data set.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="attributeAccuracyExplanation" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Accuracy Explanation summary: The test which yields the Attribute Accuracy Value. description: The attributeAccuracyExplanation element is the identification of the test that yielded the Attribute Accuracy Value.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:attribute name="typeSystem" type="xs:string" use="optional" default="http://www.w3.org/2001/XMLSchema-datatypes">
- <xs:annotation>
- <xs:documentation>tooltip: Storage Type System summary: The system used to define the storage types. This should be an identifier of a well known and published typing system. description: The typeSystem attribute is the system used to define the storage types. This should be an identifier of a well known and published typing system. The default and recommended system is the XML Schema data type system. For details go to http://www.w3.org. If another system is used (such as Java or C++ types), typeSystem should be changed to match the system. example: http://www.w3.org/2001/XMLSchema-datatypes example: java example: C example: Oracle 8i</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="order" type="xs:long" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Order summary: Mechanism for specifying what the order of the code-definitions included should be description: Ordinal scale measurements have a discrete list of values with a specific ordering of those values. This attributes specifies that order from low to high. For example, for LOW, MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and HIGH=3".</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="enforced" use="optional" default="yes">
- <xs:annotation>
- <xs:documentation>tooltip: Enforced Domain summary: Indicates whether the enumerated domain values enforced. description: Indicates whether the enumerated domain values are the only allowable values for the domain. In some exceedingly rare cases, users may wish to present a list of value codes in enumeratedDomain but not formally restrict the value space for the attribute to those values. If so, they can indicate this by setting the enforced attribute to the value no. Acceptable values are yes and no, and the default value is yes.</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:attribute>
<xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:group name="BoundsGroup">
- <xs:annotation>
- <xs:documentation>tooltip: Bounds summary: Elements for specifying allowed values range. description: The bounds element contains the minimum and maximum values of a numeric attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive).</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="bounds" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Bounds summary: Elements for specifying allowed values range. description: The bounds element in the BoundsGroup contains the minimum and maximum values of a numeric attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). Either or both a minimum and maximum may be set, and each has an attribute "exclusive" to define how the value should be interpreted.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="minimum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum numeric bound summary: Minimum numeric bound of attribute description: The minimum element specifies the minimum permitted value of a numeric attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:float">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="maximum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum numeric bound summary: Maximum numeric bound of attribute description: The maximum element specifies the maximum permitted value of a numeric attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:float">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:group>
<xs:group name="BoundsDateGroup">
- <xs:annotation>
- <xs:documentation>tooltip: BoundsDateGroup summary: Elements for specifying allowed value ranges. description: The BoundsDateGroup specifies the minimum and maximum dates allowed for a dateTime attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). The domain expressions should be in the same dateTime format as is used in the attribute's "formatString". For example, if the format string is "YYYY-MM-DD", then a valid minimum in the domain would be "2001-05-29". The "bounds" element is optional, and if it is missing then any legitimate value from the Gregorian calendar system is allowed in the attribute as long as its representation matches its corresponding formatString.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="bounds" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Bounds summary: Elements for specifying allowed date range. description: The bounds element in the BoundsDateGroup contains the minimum and maximum dates of a dateTime attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). Either or both a minimum and maximum may be set, and each has an attribute "exclusive" to define how the value should be interpreted.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="minimum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum date bound summary: Minimum date bound of attribute description: The minimum element specifies the minimum permitted value of a date attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="maximum" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum date bound summary: Maximum date bound of attribute description: The maximum element specifies the maximum permitted value of a date attribute.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="exclusive" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:group>
<xs:element name="primaryKey">
- <xs:annotation>
- <xs:documentation>tooltip: Primary Key summary: The primary key in the entity description: The primaryKey element declares the primary key in the entity to which the defined constraint pertains. example: date example: site</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null. example: site example: plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -815,25 +731,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="constraintName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Name of the constraint summary: A meaningfull name of the constraint. description: The constraintName element is a name which represents a human readable and meaningful name for the constraint. example: PrimaryKey_birdSurvey</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -916,25 +813,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="constraintDescription" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Description of the constraint summary: Descibes the purpose of the constraint. description: The constraintDescription element describes the nature of the constraint. It might be a description of a check condition, or a statement about the composition of a primary key or the nature of the relationship between two database tables or two ascii files. example: 1.Must be greater than 0 but less than 100 2. "The primary key of the table BIRD_SURVEY is composed of two attributes:speciesCode and observationDate 3. The species name associated with the species code in survey.txt can be found in the file speciesList.txt</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1047,34 +925,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null. example: site example: plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1189,25 +1039,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1320,44 +1151,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="uniqueKey">
- <xs:annotation>
- <xs:documentation>tooltip: Unique Key summary: A unique key in the entity description: The uniqueKey element represents a unique key within the referenced entity. This is different from a primary key in that it does not form any implicit foreign key relationships to other entities, however it is required to be unique within the entity. example: date</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null. example: date, site, plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1468,34 +1261,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null. example: date, site, plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1610,25 +1375,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1788,40 +1534,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="checkConstraint">
- <xs:annotation>
- <xs:documentation>tooltip: Check Constraint summary: A constraint which checks a conditional clause within an entity. description: The checkConstraint element defines a constraint which checks a conditional clause within an entity. example: if site>1 then plot>10</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="checkCondition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Check Condition summary: An SQL statement or other language implementation of the condition for a check constraint. description: The checkCondition element defines an SQL statement or other language implementation of the condition for a check constraint. Generally this provides a means for constraining the values within and among entities. example: (year > 1900 and year < 1990)</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="language" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Language summary: The language that the is used to express or implement the check constraint. description: The language element declares the language that is used to implement the check constraint. This is typically the name and version of a programming language such as Java, C, Perl, Basic, or other. Sometime it is the name and version of a scriptable analysis system such as SAS, Matlab, R, or SPlus. example: Perl 5.6.1</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1934,25 +1646,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="checkCondition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Check Condition summary: An SQL statement or other language implementation of the condition for a check constraint. description: The checkCondition element defines an SQL statement or other language implementation of the condition for a check constraint. Generally this provides a means for constraining the values within and among entities. example: (year > 1900 and year < 1990)</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2068,28 +1761,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="foreignKey">
- <xs:annotation>
- <xs:documentation>tooltip: Foreign Key summary: A foreign key relationship among entities description: The foreignKey element defines a foreign key relationship among entities which relates this entity to another's primary key.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:group ref="ForeignKeyGroup"/>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2197,34 +1868,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2339,25 +1982,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2468,25 +2092,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="entityReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Referenced Entity ID summary: The id of the parent-entity in a foreign key constraint. description: The entityReference element contains the id of the entity to which a foreign key refers, otherwise known as the parent-entity or parent-table. This should be an identifier that matches one of the "identifier" elements for an entity. example: knb.79.4</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2601,31 +2206,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="relationshipType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Relationship type: Identifying or non-identifying summary: Relationship type: Identifying or non-identifying description: The relationshipType element defines identifying relationships that propagate from the parent entity's primary key to the child's primary key. Non-identifying relationships propagate the parent's primary key as a non-key attribute of the child entity. example: relationshipType code</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="identifying"/>
- <xs:enumeration value="non-identifying"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -2748,45 +2328,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="cardinality" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Cardinality of the relationship between two entities. summary: Cardinality of the relationship between a parent entity and a child entity. description: The cardinality element represents a statement of the relationship between parent and child entities. Cardinality is expressed as the ratio of related parent and child entities. Cardinality 1 to N is a specific form of cardinality in which zero or one parent records are related to a specified number of child records. The cardinality ratio for the parent entity depends on whether the "existence" is mandatory (one or more) or optional (zero to ...). example: One to many example: One to 10 example: Zero or One to Many</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="parentOccurences">
- <xs:annotation>
- <xs:documentation>tooltip: Parent portion of a 1 to exactly N cardinality summary: Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. description: The parentOccurences element describes the Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. Value of 0 implies that the "existence" of a child record is optional. Value of 1 implies that the "existence" of a child record is mandatory. example: One to 10, Zero or One to Many</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:integer">
- <xs:enumeration value="0"/>
- <xs:enumeration value="1"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="childOccurences" type="CardinalityChildOccurancesType">
- <xs:annotation>
- <xs:documentation>tooltip: Child portion of the cardinality expression summary: Child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many". description: The childOccurences element describes the child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many" example: 2, 15, many</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2898,31 +2439,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="parentOccurences">
- <xs:annotation>
- <xs:documentation>tooltip: Parent portion of a 1 to exactly N cardinality summary: Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. description: The parentOccurences element describes the Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. Value of 0 implies that the "existence" of a child record is optional. Value of 1 implies that the "existence" of a child record is mandatory. example: One to 10, Zero or One to Many</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:integer">
- <xs:enumeration value="0"/>
- <xs:enumeration value="1"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -3008,25 +2524,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="childOccurences" type="CardinalityChildOccurancesType">
- <xs:annotation>
- <xs:documentation>tooltip: Child portion of the cardinality expression summary: Child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many". description: The childOccurences element describes the child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many" example: 2, 15, many</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3146,44 +2643,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="joinCondition">
- <xs:annotation>
- <xs:documentation>tooltip: Join Condition summary: A non primary/foreign key join description: The joinCondition element describes any join of two tables that is not done with a primary/foreign key relationship. example: JOIN code</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ForeignKeyGroup"/>
- <xs:element name="referencedKey">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which a foreign key constraint refers. description: The referencedKey element defines set of attributes to which a foreign key constraint refers. If the key refers to the primary key in the referenced entity, then the "referencedKey" is optional. For a foreign key, the set of attributes must match an identifying key in the referenced entity. example: site, plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3293,34 +2752,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="referencedKey">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which a foreign key constraint refers. description: The referencedKey element defines set of attributes to which a foreign key constraint refers. If the key refers to the primary key in the referenced entity, then the "referencedKey" is optional. For a foreign key, the set of attributes must match an identifying key in the referenced entity. example: site, plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3435,25 +2866,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3563,44 +2975,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="notNullConstraint">
- <xs:annotation>
- <xs:documentation>tooltip: Not Null Constraint summary: A constraint that indicates that no null values should be present for an attribute. description: The notNullConstraint element defines a constraint that indicates that no null values should be present for an attribute in this entity.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3709,34 +3083,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3851,25 +3197,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="ConstraintType">
- <xs:annotation>
- <xs:documentation>tooltip: Relational integrity constraint descriptors summary: Describes the relational integrity constraints of a relational database. description: The ConstraintType type describes the relational integrity constraints of a relational database. This includes primary keys, foreign keys, unique keys, etc. When an eml-constraint module is created, it should be linked into a dataset using the "triple" element, and all of the entities that are referenced in the constraints should be accessible within that same package.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:element name="primaryKey">
- <xs:annotation>
- <xs:documentation>tooltip: Primary Key summary: The primary key in the entity description: The primaryKey element declares the primary key in the entity to which the defined constraint pertains. example: date example: site</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null. example: site example: plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="uniqueKey">
- <xs:annotation>
- <xs:documentation>tooltip: Unique Key summary: A unique key in the entity description: The uniqueKey element represents a unique key within the referenced entity. This is different from a primary key in that it does not form any implicit foreign key relationships to other entities, however it is required to be unique within the entity. example: date</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null. example: date, site, plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="checkConstraint">
- <xs:annotation>
- <xs:documentation>tooltip: Check Constraint summary: A constraint which checks a conditional clause within an entity. description: The checkConstraint element defines a constraint which checks a conditional clause within an entity. example: if site>1 then plot>10</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="checkCondition" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Check Condition summary: An SQL statement or other language implementation of the condition for a check constraint. description: The checkCondition element defines an SQL statement or other language implementation of the condition for a check constraint. Generally this provides a means for constraining the values within and among entities. example: (year > 1900 and year < 1990)</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="language" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Language summary: The language that the is used to express or implement the check constraint. description: The language element declares the language that is used to implement the check constraint. This is typically the name and version of a programming language such as Java, C, Perl, Basic, or other. Sometime it is the name and version of a scriptable analysis system such as SAS, Matlab, R, or SPlus. example: Perl 5.6.1</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="foreignKey">
- <xs:annotation>
- <xs:documentation>tooltip: Foreign Key summary: A foreign key relationship among entities description: The foreignKey element defines a foreign key relationship among entities which relates this entity to another's primary key.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:group ref="ForeignKeyGroup"/>
- </xs:complexType>
- </xs:element>
- <xs:element name="joinCondition">
- <xs:annotation>
- <xs:documentation>tooltip: Join Condition summary: A non primary/foreign key join description: The joinCondition element describes any join of two tables that is not done with a primary/foreign key relationship. example: JOIN code</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ForeignKeyGroup"/>
- <xs:element name="referencedKey">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which a foreign key constraint refers. description: The referencedKey element defines set of attributes to which a foreign key constraint refers. If the key refers to the primary key in the referenced entity, then the "referencedKey" is optional. For a foreign key, the set of attributes must match an identifying key in the referenced entity. example: site, plot</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="notNullConstraint">
- <xs:annotation>
- <xs:documentation>tooltip: Not Null Constraint summary: A constraint that indicates that no null values should be present for an attribute. description: The notNullConstraint element defines a constraint that indicates that no null values should be present for an attribute in this entity.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:simpleType name="CardinalityChildOccurancesType">
- <xs:annotation>
- <xs:documentation>tooltip: Child portion of a cardinality expression summary: Child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many". description: The CardinalityChildOccurancesType element defines the child portion of a cardinality expression. Allowed values are positive integers including zero or the string value "many". example: 0,1, 2, 15,many</xs:documentation>
- </xs:annotation>
- <xs:union memberTypes="xs:integer">
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="many"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:union>
-</xs:simpleType>
<xs:attribute name="language" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Language summary: The language that the is used to express or implement the check constraint. description: The language element declares the language that is used to implement the check constraint. This is typically the name and version of a programming language such as Java, C, Perl, Basic, or other. Sometime it is the name and version of a scriptable analysis system such as SAS, Matlab, R, or SPlus. example: Perl 5.6.1</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:group name="ConstraintBaseGroup">
- <xs:sequence>
- <xs:element name="constraintName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Name of the constraint summary: A meaningfull name of the constraint. description: The constraintName element is a name which represents a human readable and meaningful name for the constraint. example: PrimaryKey_birdSurvey</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="constraintDescription" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Description of the constraint summary: Descibes the purpose of the constraint. description: The constraintDescription element describes the nature of the constraint. It might be a description of a check condition, or a statement about the composition of a primary key or the nature of the relationship between two database tables or two ascii files. example: 1.Must be greater than 0 but less than 100 2. "The primary key of the table BIRD_SURVEY is composed of two attributes:speciesCode and observationDate 3. The species name associated with the species code in survey.txt can be found in the file speciesList.txt</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:group>
<xs:group name="ForeignKeyGroup">
- <xs:sequence>
- <xs:group ref="ConstraintBaseGroup"/>
- <xs:element name="key">
- <xs:annotation>
- <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined. example: site</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="entityReference" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Referenced Entity ID summary: The id of the parent-entity in a foreign key constraint. description: The entityReference element contains the id of the entity to which a foreign key refers, otherwise known as the parent-entity or parent-table. This should be an identifier that matches one of the "identifier" elements for an entity. example: knb.79.4</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="relationshipType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Relationship type: Identifying or non-identifying summary: Relationship type: Identifying or non-identifying description: The relationshipType element defines identifying relationships that propagate from the parent entity's primary key to the child's primary key. Non-identifying relationships propagate the parent's primary key as a non-key attribute of the child entity. example: relationshipType code</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="identifying"/>
- <xs:enumeration value="non-identifying"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="cardinality" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Cardinality of the relationship between two entities. summary: Cardinality of the relationship between a parent entity and a child entity. description: The cardinality element represents a statement of the relationship between parent and child entities. Cardinality is expressed as the ratio of related parent and child entities. Cardinality 1 to N is a specific form of cardinality in which zero or one parent records are related to a specified number of child records. The cardinality ratio for the parent entity depends on whether the "existence" is mandatory (one or more) or optional (zero to ...). example: One to many example: One to 10 example: Zero or One to Many</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="parentOccurences">
- <xs:annotation>
- <xs:documentation>tooltip: Parent portion of a 1 to exactly N cardinality summary: Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. description: The parentOccurences element describes the Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. Value of 0 implies that the "existence" of a child record is optional. Value of 1 implies that the "existence" of a child record is mandatory. example: One to 10, Zero or One to Many</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:integer">
- <xs:enumeration value="0"/>
- <xs:enumeration value="1"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="childOccurences" type="CardinalityChildOccurancesType">
- <xs:annotation>
- <xs:documentation>tooltip: Child portion of the cardinality expression summary: Child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many". description: The childOccurences element describes the child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many" example: 2, 15, many</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:group>
<xs:element name="geographicCoverage" type="GeographicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic coverage summary: Geographic coverage information. description: Geographic Coverage is a container for spatial information about a project, a resource, or an entity within a resource. It allows a bounding box for the overall coverage (in lat long), and also allows description of arbitrary polygons with exclusions. example: Please see the individual sub fields for specific examples.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1089,25 +967,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="geographicDescription" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Description of geographic extent summary: Short text description of the geographic areal domain of the data set. description: geographicDescription is a short text description of a dataset's geographic areal domain. A text description is especially important to provide a geographic setting when the extent of the data set cannot be well described by the "boundingCoordinates", or in the case of data which are not specifically geospatial. Assuming the "boundingCoordinates" do not adequately describe the extent of the data set, the discrepancy can be identified and described here. The coordinates may define a rectangle around a country, with this geographicDescription element containing a disclaimer and/or further details concerning the border. A study of the diseases of salmon may not have a specific geographic extent associated with it, but the salmon were collected in the states of Washington and Oregon. The "boundingCoordinates" might form a general rectangle around the states of Washington and Oregon, but the "geographicDescription" might describe the fact that the study took place only along certain rivers within those states. This data element differs from the standard data element "Place_Keyword" in that it allows a free text description of the geographic extent, rather than just a list of words or phrases useful as an index of location names associated with the data set. This element can also contain information about the collection of the boundingCoordinates, e.g., an altitude value that is referenced to Mean Lower Low Water, or the projection system that the latitude and longitude coordinates were taken from. example: "Manistee River watershed" example: "extent of 7 1/2 minute quads containing any property belonging to Yellowstone National Park" example: "ponds and reservoirs larger than 2 acres in Jefferson County, Colorado".</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1248,97 +1107,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="boundingCoordinates">
- <xs:annotation>
- <xs:documentation>tooltip: Bounding coordinates summary: The four margins (N, S, E, W) of a bounding box on the earth's surface, or when considered in lat-lon pairs, the corners of the box. To define a single point, use the same value in each lat or lon pair. These elements are meant to convey general information and are not for accurate mapping. More specific information may be included by using the elements in the spatialReference schema. description: Bounding Coordinates are the four margins (N, S, E, W) of a bounding box, or when considered in lat-lon pairs, the corners of the box. These elements are meant to convey general information and are not for accurate mapping. More specific information may be included by using the elements in the spatialReference schema. The limits of coverage of a data set should be expressed as decimal latitudes and longitudes, and in the order western-most, eastern-most, northern-most, and southern-most. By convention, latitudes and longitudes are referenced to the Equator and to the Prime Meridian (the datums), respectively. By definition, the 0 and 180 meridians themselves do not belong in either hemisphere, but local conventions may place them in either. All coordinates are typed as decimals. Since all four elements are required, a bounding area that is a single point should use the same values for northBoundingCoordinate and southBoundingCoordinate, and likewise for westBoundingCoordinate and eastBoundingCoordinate. In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended example: Please see the individual sub-fields.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="westBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: West bounding coordinate, in decimal degrees summary: Western-most limit of a bounding box, expressed in degrees of longitude. description: The westBoundingCoordinate field defines the longitude of the western-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended. example: -118.25 example: +25 example: 45.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-180.0"/>
- <xs:maxInclusive value="180.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="eastBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: East bounding coordinate summary: Eastern-most limit of a bounding box, expressed in degrees of longitude. description: The eastBoundingCoordinate field defines the longitude of the eastern-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended. example: -118.25 example: +25 example: 45.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-180.0"/>
- <xs:maxInclusive value="180.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="northBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: North bounding coordinate summary: Northern-most lilmit of a bounding box expressed in latitude. description: The northBoundingCoordinate field defines the latitude of the northern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively. example: -18.25 example: +25 example: 65.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-90.0"/>
- <xs:maxInclusive value="90.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="southBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: South bounding coordinate summary: Southern-most limit of the bounding box expressed in latitude. description: The southBoundingCoordinate field defines the latitude of the southern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively. example: -118.25 example: +25 example: 84.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-90.0"/>
- <xs:maxInclusive value="90.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="boundingAltitudes" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bounding altitudes summary: The vertical limits of a data set expressed by altitude. description: The bounding altitude field is intended to contain altitudinal (elevation) measurements for the bounding box being described. It allows for minimum and maximum altitude fields, as well as a field for the units of measure. The combination of these fields provide the vertical extent information for the bounding box. example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="altitudeMinimum" type="xs:decimal">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum altitude summary: The minimum altitude extent of coverage. description: The minimum altitude extent of coverage for the bounding box that is being described. The minimum altitude should be in reference to a known datum (e.g., Mean Sea Level), which should be part of the geographicDescription. example: 100.6 example: -12</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeMaximum" type="xs:decimal">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum altitude summary: The maximum altitude extent of coverage. description: The maximum altitude extent of coverage for the bounding box that is being described. The maximum altitude should be in reference to a known datum, which should be part of the geographicDescription. example: 100.6 example: -10</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeUnits" type="unit:LengthUnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Units summary: The unit of altitude description: The unit that the altitude is expressed in. See the description under the Type definition</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1462,31 +1230,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="westBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: West bounding coordinate, in decimal degrees summary: Western-most limit of a bounding box, expressed in degrees of longitude. description: The westBoundingCoordinate field defines the longitude of the western-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended. example: -118.25 example: +25 example: 45.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-180.0"/>
- <xs:maxInclusive value="180.0"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -1610,31 +1353,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="eastBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: East bounding coordinate summary: Eastern-most limit of a bounding box, expressed in degrees of longitude. description: The eastBoundingCoordinate field defines the longitude of the eastern-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended. example: -118.25 example: +25 example: 45.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-180.0"/>
- <xs:maxInclusive value="180.0"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -1754,31 +1472,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="northBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: North bounding coordinate summary: Northern-most lilmit of a bounding box expressed in latitude. description: The northBoundingCoordinate field defines the latitude of the northern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively. example: -18.25 example: +25 example: 65.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-90.0"/>
- <xs:maxInclusive value="90.0"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -1898,31 +1591,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="southBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: South bounding coordinate summary: Southern-most limit of the bounding box expressed in latitude. description: The southBoundingCoordinate field defines the latitude of the southern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively. example: -118.25 example: +25 example: 84.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-90.0"/>
- <xs:maxInclusive value="90.0"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -2040,44 +1708,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="boundingAltitudes" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bounding altitudes summary: The vertical limits of a data set expressed by altitude. description: The bounding altitude field is intended to contain altitudinal (elevation) measurements for the bounding box being described. It allows for minimum and maximum altitude fields, as well as a field for the units of measure. The combination of these fields provide the vertical extent information for the bounding box. example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="altitudeMinimum" type="xs:decimal">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum altitude summary: The minimum altitude extent of coverage. description: The minimum altitude extent of coverage for the bounding box that is being described. The minimum altitude should be in reference to a known datum (e.g., Mean Sea Level), which should be part of the geographicDescription. example: 100.6 example: -12</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeMaximum" type="xs:decimal">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum altitude summary: The maximum altitude extent of coverage. description: The maximum altitude extent of coverage for the bounding box that is being described. The maximum altitude should be in reference to a known datum, which should be part of the geographicDescription. example: 100.6 example: -10</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeUnits" type="unit:LengthUnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Units summary: The unit of altitude description: The unit that the altitude is expressed in. See the description under the Type definition</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2161,25 +1791,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="altitudeMinimum" type="xs:decimal">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum altitude summary: The minimum altitude extent of coverage. description: The minimum altitude extent of coverage for the bounding box that is being described. The minimum altitude should be in reference to a known datum (e.g., Mean Sea Level), which should be part of the geographicDescription. example: 100.6 example: -12</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2263,25 +1874,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="altitudeMaximum" type="xs:decimal">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum altitude summary: The maximum altitude extent of coverage. description: The maximum altitude extent of coverage for the bounding box that is being described. The maximum altitude should be in reference to a known datum, which should be part of the geographicDescription. example: 100.6 example: -10</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2533,25 +2125,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="altitudeUnits" type="unit:LengthUnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Units summary: The unit of altitude description: The unit that the altitude is expressed in. See the description under the Type definition</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2670,69 +2243,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="datasetGPolygon" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Polygon data set summary: This construct creates a spatial ring with a hollow center. description: This construct creates a spatial ring with a hollow center. This doughnut shape is specified by the outer ring (datasetGPolygonOuterRing) and the inner exclusion zone (datasetGPolygonExclusionGRing) which can be thought of as the hole in the center of a doughnut. This is useful for defining areas such as the shores of a pond where you only want to specify the shore excluding the pond itself. example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="datasetGPolygonOuterGRing">
- <xs:annotation>
- <xs:documentation>tooltip: Outer polygon summary: The outer containment loop of a datasetGPolygon. description: The outer containment loop of a datasetGPolygon. This is the outer part of the doughnut shape that encompasses the broadest area of coverage. It can be created either by a gRing (list of points) or 3 or more gRingPoints. See the sub-elements and their Type definitions for more specific information. This element is generally analogous to the FGDC outer ring although somewhat differently specified. Documentation for an FGDC G-Ring states that 4 points are required to define a polygon, and the first and last should be identical. However this is not enforceable in XML Schema, and so in EML a minimum of 3 <gRingPoint>s is required to define a polygon, and it can be assumed that a polygon is closed by joining the last point to the first. XSL stylesheets that transform EML instances to the FGDC specification should repeat the first gRingPoint node as the last when creating a list of points.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:sequence>
- <xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. As a child of <datasetGPolygonOuterGRing> a minimum of 3 are required to define a polygon. The polygon is presumed to be closed. Please see the sub elements and the Type description for more information about creating a point location.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:element name="gRing" type="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, The number of points in the string is not enforced by EML. However, authors should note that in order for this field is to be directly translated to FGDC, 4 points should be included in the string. See the Type for more information on constructing the string.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="datasetGPolygonExclusionGRing" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusion polygon summary: Data Set G-Polygon Exclusion G-Ring, the closed nonintersecting boundary of a void area (or hole in an interior area). description: the closed nonintersecting boundary of a void area (or hole in an interior area). This is the center of the doughnut shape created by the datasetGPolygon. It can be created either by a gRing (list of points) or one or more gRingPoints. See the sub-elements and their Type definitions for more information. This element is generally analogous to an FGDC exclusion ring "Data Set G-Polygon Exclusion G-Ring", although it's children are somewhat differently described. Documentation for the FGDC component states that 4 points are required to define a polygon, and the first and last should be identical. However this EML element requires only one point so that a single point can be excluded, presumably, a single station. If multiple single stations are to be excluded, then authors should include multiple <datasetGPolygonExclusionGRing>s.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. This is useful if you register your datasets by a single geospatial point, such as the lat/long of your research station. Please see the sub elements and the Type description for more information on constructing a gRingPoint</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="gRing" type="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, See the Type for more information</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2851,41 +2361,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="datasetGPolygonOuterGRing">
- <xs:annotation>
- <xs:documentation>tooltip: Outer polygon summary: The outer containment loop of a datasetGPolygon. description: The outer containment loop of a datasetGPolygon. This is the outer part of the doughnut shape that encompasses the broadest area of coverage. It can be created either by a gRing (list of points) or 3 or more gRingPoints. See the sub-elements and their Type definitions for more specific information. This element is generally analogous to the FGDC outer ring although somewhat differently specified. Documentation for an FGDC G-Ring states that 4 points are required to define a polygon, and the first and last should be identical. However this is not enforceable in XML Schema, and so in EML a minimum of 3 <gRingPoint>s is required to define a polygon, and it can be assumed that a polygon is closed by joining the last point to the first. XSL stylesheets that transform EML instances to the FGDC specification should repeat the first gRingPoint node as the last when creating a list of points.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:sequence>
- <xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. As a child of <datasetGPolygonOuterGRing> a minimum of 3 are required to define a polygon. The polygon is presumed to be closed. Please see the sub elements and the Type description for more information about creating a point location.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:element name="gRing" type="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, The number of points in the string is not enforced by EML. However, authors should note that in order for this field is to be directly translated to FGDC, 4 points should be included in the string. See the Type for more information on constructing the string.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3006,25 +2481,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. As a child of <datasetGPolygonOuterGRing> a minimum of 3 are required to define a polygon. The polygon is presumed to be closed. Please see the sub elements and the Type description for more information about creating a point location.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3139,31 +2595,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="gRingLatitude">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring Latitude summary: The latitude of a point of the g-ring. description: A latitude coordinate is typed as a decimal, i.e., decimal degrees from -90 to 90, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'S' or 'south') are not allowed. Latitudes north of the equator must be specified by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). example: 34.123 example: -18.25 example: +78.25</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-90.0"/>
- <xs:maxInclusive value="90.0"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -3278,31 +2709,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="gRingLongitude">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring Longitude summary: description: The longitude of a point of the g-ring A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). example: -118.25 example: +25 example: 45.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-180.0"/>
- <xs:maxInclusive value="180.0"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -3382,25 +2788,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="gRing" type="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, The number of points in the string is not enforced by EML. However, authors should note that in order for this field is to be directly translated to FGDC, 4 points should be included in the string. See the Type for more information on constructing the string.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3527,39 +2914,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="datasetGPolygonExclusionGRing" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusion polygon summary: Data Set G-Polygon Exclusion G-Ring, the closed nonintersecting boundary of a void area (or hole in an interior area). description: the closed nonintersecting boundary of a void area (or hole in an interior area). This is the center of the doughnut shape created by the datasetGPolygon. It can be created either by a gRing (list of points) or one or more gRingPoints. See the sub-elements and their Type definitions for more information. This element is generally analogous to an FGDC exclusion ring "Data Set G-Polygon Exclusion G-Ring", although it's children are somewhat differently described. Documentation for the FGDC component states that 4 points are required to define a polygon, and the first and last should be identical. However this EML element requires only one point so that a single point can be excluded, presumably, a single station. If multiple single stations are to be excluded, then authors should include multiple <datasetGPolygonExclusionGRing>s.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. This is useful if you register your datasets by a single geospatial point, such as the lat/long of your research station. Please see the sub elements and the Type description for more information on constructing a gRingPoint</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="gRing" type="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, See the Type for more information</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3676,25 +3030,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. This is useful if you register your datasets by a single geospatial point, such as the lat/long of your research station. Please see the sub elements and the Type description for more information on constructing a gRingPoint</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3771,25 +3106,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="gRing" type="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, See the Type for more information</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3966,33 +3282,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="temporalCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Temporal coverage summary: Temporal coverage information. description: This field specifies temporal coverage, and allows coverages to be a single point in time, multiple points in time, or a range of dates. Dates can be expressed in terms of both calendar dates and geologic dating systems. example: Please see the individual sub fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="TemporalCoverage">
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -4111,25 +3400,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="singleDateTime" type="SingleDateTimeType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Single Date/Time summary: Means of encoding a single date and time description: The singleDateTime field is intended to describe a single date and time for an event. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4220,25 +3490,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="calendarDate" type="res:yearDate">
- <xs:annotation>
- <xs:documentation>tooltip: Calendar date summary: The calendar date for an event. description: The calendar date field is used to express a date, giving the year, month, and day. The format should be one that complies with the International Standards Organization's standard 8601. The recommended format for EML is YYYY-MM-DD, where Y is the four digit year, M is the two digit month code (01 - 12, where January = 01), and D is the two digit day of the month (01 - 31). This field can also be used to enter just the year portion of a date. example: 2001-01-01 example: 2001-10-12 example: 2001 example: 1895</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4335,25 +3586,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="time" type="xs:time" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Time of day summary: The time of day for an event. description: The time field is used to express the hour (and optionally minute, or minute and second) of the day for an event, and should comply with the International Standards Organization's standard 8601. The recommended format for EML is hh:mm:ssTZD, where hh is the two digit hour of the day, mm is the two digit minute of the hour, and ss is the two digit second of the minute. TZD stands for Time Zone Designator which is used to handle time zone offsets. Times may be expressed in two ways: 1) UTC (Coordinated Universal Time, also known as Greenwich Mean Time, or GMT), with a special UTC designator ("Z"), 2) local time, together with a time zone offset in hours and minutes. A time zone offset of "+hh:mm" indicates that the date or time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC. A time zone offset of "-hh:mm" indicates a local time zone which is "hh" hours and "mm" minutes behind UTC. example: 1) 08:31:22Z , which means eight thirty one and 22 seconds in the morning at Coordinated Universal Time (Greenwich Mean Time). 2) 14:06:09-08:00 , which means six minutes, nine seconds past two o'clock p.m., Pacific Standard Time (which is offset eight hours behind UTC)</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4480,54 +3712,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="alternativeTimeScale">
- <xs:annotation>
- <xs:documentation>tooltip: Alternative Time Scale summary: A name, code, or date describing an event or period in an alternative time scale, such as one of the geologic time scales. description: A name, code, or date describing an event or period in an alternative time scale, for instance as an absolute date calculated using a named dating method, or as a relative date that is drawn from stratigraphy or biostratigraphy. Calendar dates as provided in the ISO 8601 dating system used in the standard CSDGM are not adequate to describe geologic time periods. Absolute geologic time is usually measured in millions of years before present, but may use different units and relative base times. Relative geologic time is measured by subdivisions of the earth's geology. in an order based upon relative age, most commonly, vertical or stratigraphic position. The actual dating systems used in geologic studies often tie relative times measured through stratigraphy or biostratigraphy to a particular absolute time using radioisotope dating techniques, among others. As these methods for absolute dating have improved, the estimates of the dates for strata have changed, consequently, it would be inaccurate to record absolute dates in situations where relative dates were measured. This structure is provided as an optional alternative to the standard calendar dates provided by ISO 8601. example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="timeScaleName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: alternative time scale summary: Name of a recognized alternative time scale. description: Name of a recognized alternative time scale. This includes 'Absolute' as the name of the time scale for measuring geologic dates before the present and names of geologic dating systems that are arrangements of symbols or names in order of relative geologic time. example: 'Absolute', 'Geomagnetic Polarity Time Scale', 'International Geological Time Scale', 'Oxygen-Isotope'</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="timeScaleAgeEstimate" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age estimate summary: description: Either an absolute date or a relative age name describing an event or period in an alternative time scale such as the Geologic Time Scale. example: For example, '300 Ma' (300 million years before present) is a Geologic_Age_Estimate based on the Absolute Geologic_Time_Scale, 'C28r' is a chron name from the Geomagnetic Polarity Time Scale, and 'Maastrichtian' and 'Jurassic' are names from the International Geological Time Scale. Since different relative geologic time scales are often not aligned, multiple geologic dates may need to be specified. For example, the Geomagnetic Polarity Time Scale chron 'C29r', at the K/T boundary lies in both the 'Maastrichtian' and the 'Danian' stages from the International Geological Time Scale, thus if you were documenting this event using the International Geological Time Scale, both 'Maastrichtian' and 'Danian' should be included here.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="timeScaleAgeUncertainty" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age uncertainty summary: The error estimate for the alternative time scale. description: The error estimate for the alternative time. This should include the units of measure, a description of what the error estimate represents and how it was calculated. example: +/- 5 Ma (Million Years)</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="timeScaleAgeExplanation" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age explanation summary: The name and/or description of the method used to calculate the time scale age estimate. description: The name and/or description of the method used to calculate the age estimate. Detailed information about the method may be provided through references contained in the Time Scale Citation field.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="timeScaleCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Time Scale citation summary: Citation for works providing detailed information about any element of the time scale age. description: Citation for works providing detailed information about any element of the time scale age. example: For example, a publication describing the methodology used for carbon dating or describing the basic geologic time scale in more detail could be cited here.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -4637,25 +3821,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="timeScaleName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: alternative time scale summary: Name of a recognized alternative time scale. description: Name of a recognized alternative time scale. This includes 'Absolute' as the name of the time scale for measuring geologic dates before the present and names of geologic dating systems that are arrangements of symbols or names in order of relative geologic time. example: 'Absolute', 'Geomagnetic Polarity Time Scale', 'International Geological Time Scale', 'Oxygen-Isotope'</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4772,25 +3937,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="timeScaleAgeEstimate" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age estimate summary: description: Either an absolute date or a relative age name describing an event or period in an alternative time scale such as the Geologic Time Scale. example: For example, '300 Ma' (300 million years before present) is a Geologic_Age_Estimate based on the Absolute Geologic_Time_Scale, 'C28r' is a chron name from the Geomagnetic Polarity Time Scale, and 'Maastrichtian' and 'Jurassic' are names from the International Geological Time Scale. Since different relative geologic time scales are often not aligned, multiple geologic dates may need to be specified. For example, the Geomagnetic Polarity Time Scale chron 'C29r', at the K/T boundary lies in both the 'Maastrichtian' and the 'Danian' stages from the International Geological Time Scale, thus if you were documenting this event using the International Geological Time Scale, both 'Maastrichtian' and 'Danian' should be included here.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4902,25 +4048,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="timeScaleAgeUncertainty" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age uncertainty summary: The error estimate for the alternative time scale. description: The error estimate for the alternative time. This should include the units of measure, a description of what the error estimate represents and how it was calculated. example: +/- 5 Ma (Million Years)</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5031,25 +4158,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="timeScaleAgeExplanation" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age explanation summary: The name and/or description of the method used to calculate the time scale age estimate. description: The name and/or description of the method used to calculate the age estimate. Detailed information about the method may be provided through references contained in the Time Scale Citation field.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5288,25 +4396,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="timeScaleCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Time Scale citation summary: Citation for works providing detailed information about any element of the time scale age. description: Citation for works providing detailed information about any element of the time scale age. example: For example, a publication describing the methodology used for carbon dating or describing the basic geologic time scale in more detail could be cited here.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5417,39 +4506,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="rangeOfDates">
- <xs:annotation>
- <xs:documentation>tooltip: Range of dates/times summary: Means of encoding a range of dates and times. description: The 'RangeOfDatesType' field is intended to be used for describing a range of dates and/or times. It may be used multiple times to document multiple date ranges. It allows for two 'singleDateTime' fields, the first to be used as the beginning dateTime, and the second to be used as the ending dateTime of the range. example: Please see the examples from the 'singleDateTime' field for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="beginDate" type="SingleDateTimeType">
- <xs:annotation>
- <xs:documentation>tooltip: Begin Date summary: A single time stamp signifying the beginning of some time period description: A single time stamp signifying the beginning of some time period. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="endDate" type="SingleDateTimeType">
- <xs:annotation>
- <xs:documentation>tooltip: End Date summary: A single time stamp signifying the end of some time period description: A single time stamp signifying the end of some time period. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -5565,25 +4621,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="beginDate" type="SingleDateTimeType">
- <xs:annotation>
- <xs:documentation>tooltip: Begin Date summary: A single time stamp signifying the beginning of some time period description: A single time stamp signifying the beginning of some time period. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5699,25 +4736,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="endDate" type="SingleDateTimeType">
- <xs:annotation>
- <xs:documentation>tooltip: End Date summary: A single time stamp signifying the end of some time period description: A single time stamp signifying the end of some time period. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5896,33 +4914,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonomicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic coverage summary: Taxonomic coverage information. description: Taxonomic Coverage is a container for Taxonomic information about a project, a resource, or an entity within a resource. It includes a list of species names (or higher level ranks) from one or more classification systems. example: Please see the individual sub fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="TaxonomicCoverage">
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -6040,96 +5031,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonomicSystem" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic system summary: Documentation of taxonomic sources, procedures, and treatments. description: Documentation of taxonomic sources, procedures, and treatments.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="classificationSystem" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Classification system/authority summary: Information about the classification system or authority used. description: Information about the classification system or authority used. example: Flora of North America</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="classificationSystemCitation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic citation summary: description: Relevant literature for documenting the used classification system.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="classificationSystemModifications" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Classification system modification summary: description: A description of any modifications or exceptions made to the classification system or authority used.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="identificationReference" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Non-authoritative citation summary: description: Information on any non-authoritative materials (e.g. field guides) useful for reconstructing the actual identification process.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="identifierName" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Identifier's Name summary: description: Information about the individual(s) responsible for the identification(s) of the specimens or sightings, etc.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="taxonomicProcedures" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic procedures summary: description: Description of the methods used for the taxonomic identification. example: specimen processing, comparison with museum materials, keys and key characters, chemical or genetic analyses</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="taxonomicCompleteness" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic completeness summary: description: Information concerning the proportions and treatment of unidentified materials, estimates of the importance and possible identities of uncertain determinations, synonyms or other incorrect usages, taxa not well treated or requiring further work, and expertise of field workers. example: materials sent to experts, and not yet determined</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="vouchers" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Specimen information summary: description: Information on the types of specimen, the repository, and the individuals who identified the vouchers.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="specimen" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Specimen type summary: description: A word or phrase describing the type of specimen collected. example: herbarium specimens, blood samples, photographs, individuals, or batches</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="repository">
- <xs:annotation>
- <xs:documentation>tooltip: Storage location of specimen summary: description: Information about the curator or contact person and/or agency responsible for the specimens.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided. example: Please see the examples within the sub fields for the responsible party.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -6241,39 +5142,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="classificationSystem" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Classification system/authority summary: Information about the classification system or authority used. description: Information about the classification system or authority used. example: Flora of North America</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="classificationSystemCitation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic citation summary: description: Relevant literature for documenting the used classification system.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="classificationSystemModifications" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Classification system modification summary: description: A description of any modifications or exceptions made to the classification system or authority used.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -6499,25 +5367,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="classificationSystemCitation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic citation summary: description: Relevant literature for documenting the used classification system.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6626,25 +5475,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="classificationSystemModifications" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Classification system modification summary: description: A description of any modifications or exceptions made to the classification system or authority used.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6879,25 +5709,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="identificationReference" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Non-authoritative citation summary: description: Information on any non-authoritative materials (e.g. field guides) useful for reconstructing the actual identification process.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7078,25 +5889,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="identifierName" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Identifier's Name summary: description: Information about the individual(s) responsible for the identification(s) of the specimens or sightings, etc.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7204,25 +5996,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonomicProcedures" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic procedures summary: description: Description of the methods used for the taxonomic identification. example: specimen processing, comparison with museum materials, keys and key characters, chemical or genetic analyses</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7336,25 +6109,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonomicCompleteness" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic completeness summary: description: Information concerning the proportions and treatment of unidentified materials, estimates of the importance and possible identities of uncertain determinations, synonyms or other incorrect usages, taxa not well treated or requiring further work, and expertise of field workers. example: materials sent to experts, and not yet determined</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7467,48 +6221,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="vouchers" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Specimen information summary: description: Information on the types of specimen, the repository, and the individuals who identified the vouchers.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="specimen" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Specimen type summary: description: A word or phrase describing the type of specimen collected. example: herbarium specimens, blood samples, photographs, individuals, or batches</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="repository">
- <xs:annotation>
- <xs:documentation>tooltip: Storage location of specimen summary: description: Information about the curator or contact person and/or agency responsible for the specimens.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided. example: Please see the examples within the sub fields for the responsible party.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -7616,25 +6328,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="specimen" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Specimen type summary: description: A word or phrase describing the type of specimen collected. example: herbarium specimens, blood samples, photographs, individuals, or batches</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7737,34 +6430,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="repository">
- <xs:annotation>
- <xs:documentation>tooltip: Storage location of specimen summary: description: Information about the curator or contact person and/or agency responsible for the specimens.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided. example: Please see the examples within the sub fields for the responsible party.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -7953,25 +6618,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided. example: Please see the examples within the sub fields for the responsible party.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8084,25 +6730,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="generalTaxonomicCoverage" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: General taxonomic coverage summary: A description of the range of taxa addressed in the data set or collection. description: A description of the range of taxa addressed in the data set or collection. example: "All vascular plants were identified to family or species, mosses and lichens were identified as moss or lichen."</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8252,25 +6879,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonomicClassification" type="TaxonomicClassificationType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic classification summary: Information about the range of taxa addressed in the data set or collection. description: Information about the range of taxa addressed in the data set or collection. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8384,25 +6992,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonRankName" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxon rank name summary: The name of the taxonomic rank for which the Taxon rank value is provided. description: The name of the taxonomic rank for which the Taxon rank value is provided. This field allows for the name one of the accepted levels of Taxa. example: 'Kingdom', 'Division/Phylum', 'Class', 'Order', 'Family', 'Genus', and 'Species'</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8521,25 +7110,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonRankValue" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxon rank value summary: The taxonomic rank name being described. description: The name for the taxonomic rank being described. Typically the values are from authoritative sources such as the Integrated Taxonomic Information System (ITIS) in the U.S. (http://www/itis.usda.gov) and in Canada (http://sis.agr.gc.ca/pls/itisca/taxaget). Species2000 is another source of taxonomic information, found at (http://www.sp2000.org). Note that for the taxonomic rank "species", the accepted practice is to use binomial nomenclaure, i.e., a combination of the genus name plus species epithet is required to denote the species. Therefore the "species" is not the species epithet alone. example: For the rank genus, 'Acer' is an example of the rank value, 'Acer rubrum' for a species rank value, and a common name of 'Red Maple'. Additional examples of "species" are "Homo sapiens" and "Tyrannosaurus rex".</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8655,25 +7225,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="commonName" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Common name summary: Specification of applicable common names. description: Specification of applicable common names. These common names may be general descriptions of a group of organisms if appropriate. example: insects, vertebrate, grasses, waterfowl, vascular plants, red maple.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8819,36 +7370,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonId" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic Identifier summary: Element holds an ID and ID-provider for this taxon. description: The identifier for this taxon from an authority, such as ITIS or USDA Plant Database. Using an external system identifer allows referencing of additional information about a taxon, e.g., authoritative names, historical synonyms, published descriptions or rank hierarchies. example: 11274 example: 35122</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="provider" type="xs:anyURI" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Taxon ID Provider summary: The taxonomic authority or catalog from which the taxonId can be retrieved, defined as the namespace URI for the provider. description: This attribute holds the namespace URI for the taxonomic authority or catalog to which this taxonId applies. taxonId providers should be chosen for their stability and longevity, and with discernable website URIs or APIs. Examples are given for ITIS, NCBI, the USDA plants database, Encyclopedia of Life and the World Register of Marine Species (WoRMS). example: https://www.itis.gov example: https://www.ncbi.nlm.nih.gov/taxonomy example: https://plants.usda.gov example: https://eol.org example: http://www.marinespecies.org</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -9002,25 +7523,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="taxonomicClassification" type="TaxonomicClassificationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic classification summary: Information about the range of taxa addressed in the data set or collection. description: Information about the range of taxa addressed in the data set or collection. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="Coverage">
- <xs:annotation>
- <xs:documentation>tooltip: Coverage summary: Spatial, temporal, and taxonomic coverage information. description: This field is a container for the spatial, temporal and taxonomic coverages that apply to various resources, often dataset resources. Please see the individual descriptions of the sub fields for more detail. example: Please see the individual sub fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="geographicCoverage" type="GeographicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic coverage summary: Geographic coverage information. description: Geographic Coverage is a container for spatial information about a project, a resource, or an entity within a resource. It allows a bounding box for the overall coverage (in lat long), and also allows description of arbitrary polygons with exclusions. example: Please see the individual sub fields for specific examples.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="temporalCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Temporal coverage summary: Temporal coverage information. description: This field specifies temporal coverage, and allows coverages to be a single point in time, multiple points in time, or a range of dates. Dates can be expressed in terms of both calendar dates and geologic dating systems. example: Please see the individual sub fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="TemporalCoverage">
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="taxonomicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic coverage summary: Taxonomic coverage information. description: Taxonomic Coverage is a container for Taxonomic information about a project, a resource, or an entity within a resource. It includes a list of species names (or higher level ranks) from one or more classification systems. example: Please see the individual sub fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="TaxonomicCoverage">
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="GeographicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic coverage summary: Geographic coverage information. description: Geographic Coverage is a container for spatial information about a a project, a resource, or an entity within a resource. It is meant for general information and not for accurate mapping. More specific information, including mapping projections, is covered by EML in the spatialReference schema. example: Please see the individual sub-elements for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="geographicDescription" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Description of geographic extent summary: Short text description of the geographic areal domain of the data set. description: geographicDescription is a short text description of a dataset's geographic areal domain. A text description is especially important to provide a geographic setting when the extent of the data set cannot be well described by the "boundingCoordinates", or in the case of data which are not specifically geospatial. Assuming the "boundingCoordinates" do not adequately describe the extent of the data set, the discrepancy can be identified and described here. The coordinates may define a rectangle around a country, with this geographicDescription element containing a disclaimer and/or further details concerning the border. A study of the diseases of salmon may not have a specific geographic extent associated with it, but the salmon were collected in the states of Washington and Oregon. The "boundingCoordinates" might form a general rectangle around the states of Washington and Oregon, but the "geographicDescription" might describe the fact that the study took place only along certain rivers within those states. This data element differs from the standard data element "Place_Keyword" in that it allows a free text description of the geographic extent, rather than just a list of words or phrases useful as an index of location names associated with the data set. This element can also contain information about the collection of the boundingCoordinates, e.g., an altitude value that is referenced to Mean Lower Low Water, or the projection system that the latitude and longitude coordinates were taken from. example: "Manistee River watershed" example: "extent of 7 1/2 minute quads containing any property belonging to Yellowstone National Park" example: "ponds and reservoirs larger than 2 acres in Jefferson County, Colorado".</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="boundingCoordinates">
- <xs:annotation>
- <xs:documentation>tooltip: Bounding coordinates summary: The four margins (N, S, E, W) of a bounding box on the earth's surface, or when considered in lat-lon pairs, the corners of the box. To define a single point, use the same value in each lat or lon pair. These elements are meant to convey general information and are not for accurate mapping. More specific information may be included by using the elements in the spatialReference schema. description: Bounding Coordinates are the four margins (N, S, E, W) of a bounding box, or when considered in lat-lon pairs, the corners of the box. These elements are meant to convey general information and are not for accurate mapping. More specific information may be included by using the elements in the spatialReference schema. The limits of coverage of a data set should be expressed as decimal latitudes and longitudes, and in the order western-most, eastern-most, northern-most, and southern-most. By convention, latitudes and longitudes are referenced to the Equator and to the Prime Meridian (the datums), respectively. By definition, the 0 and 180 meridians themselves do not belong in either hemisphere, but local conventions may place them in either. All coordinates are typed as decimals. Since all four elements are required, a bounding area that is a single point should use the same values for northBoundingCoordinate and southBoundingCoordinate, and likewise for westBoundingCoordinate and eastBoundingCoordinate. In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended example: Please see the individual sub-fields.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="westBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: West bounding coordinate, in decimal degrees summary: Western-most limit of a bounding box, expressed in degrees of longitude. description: The westBoundingCoordinate field defines the longitude of the western-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended. example: -118.25 example: +25 example: 45.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-180.0"/>
- <xs:maxInclusive value="180.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="eastBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: East bounding coordinate summary: Eastern-most limit of a bounding box, expressed in degrees of longitude. description: The eastBoundingCoordinate field defines the longitude of the eastern-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended. example: -118.25 example: +25 example: 45.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-180.0"/>
- <xs:maxInclusive value="180.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="northBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: North bounding coordinate summary: Northern-most lilmit of a bounding box expressed in latitude. description: The northBoundingCoordinate field defines the latitude of the northern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively. example: -18.25 example: +25 example: 65.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-90.0"/>
- <xs:maxInclusive value="90.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="southBoundingCoordinate">
- <xs:annotation>
- <xs:documentation>tooltip: South bounding coordinate summary: Southern-most limit of the bounding box expressed in latitude. description: The southBoundingCoordinate field defines the latitude of the southern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively. example: -118.25 example: +25 example: 84.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-90.0"/>
- <xs:maxInclusive value="90.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="boundingAltitudes" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bounding altitudes summary: The vertical limits of a data set expressed by altitude. description: The bounding altitude field is intended to contain altitudinal (elevation) measurements for the bounding box being described. It allows for minimum and maximum altitude fields, as well as a field for the units of measure. The combination of these fields provide the vertical extent information for the bounding box. example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="altitudeMinimum" type="xs:decimal">
- <xs:annotation>
- <xs:documentation>tooltip: Minimum altitude summary: The minimum altitude extent of coverage. description: The minimum altitude extent of coverage for the bounding box that is being described. The minimum altitude should be in reference to a known datum (e.g., Mean Sea Level), which should be part of the geographicDescription. example: 100.6 example: -12</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeMaximum" type="xs:decimal">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum altitude summary: The maximum altitude extent of coverage. description: The maximum altitude extent of coverage for the bounding box that is being described. The maximum altitude should be in reference to a known datum, which should be part of the geographicDescription. example: 100.6 example: -10</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeUnits" type="unit:LengthUnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Units summary: The unit of altitude description: The unit that the altitude is expressed in. See the description under the Type definition</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="datasetGPolygon" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Polygon data set summary: This construct creates a spatial ring with a hollow center. description: This construct creates a spatial ring with a hollow center. This doughnut shape is specified by the outer ring (datasetGPolygonOuterRing) and the inner exclusion zone (datasetGPolygonExclusionGRing) which can be thought of as the hole in the center of a doughnut. This is useful for defining areas such as the shores of a pond where you only want to specify the shore excluding the pond itself. example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="datasetGPolygonOuterGRing">
- <xs:annotation>
- <xs:documentation>tooltip: Outer polygon summary: The outer containment loop of a datasetGPolygon. description: The outer containment loop of a datasetGPolygon. This is the outer part of the doughnut shape that encompasses the broadest area of coverage. It can be created either by a gRing (list of points) or 3 or more gRingPoints. See the sub-elements and their Type definitions for more specific information. This element is generally analogous to the FGDC outer ring although somewhat differently specified. Documentation for an FGDC G-Ring states that 4 points are required to define a polygon, and the first and last should be identical. However this is not enforceable in XML Schema, and so in EML a minimum of 3 <gRingPoint>s is required to define a polygon, and it can be assumed that a polygon is closed by joining the last point to the first. XSL stylesheets that transform EML instances to the FGDC specification should repeat the first gRingPoint node as the last when creating a list of points.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:sequence>
- <xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. As a child of <datasetGPolygonOuterGRing> a minimum of 3 are required to define a polygon. The polygon is presumed to be closed. Please see the sub elements and the Type description for more information about creating a point location.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:element name="gRing" type="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, The number of points in the string is not enforced by EML. However, authors should note that in order for this field is to be directly translated to FGDC, 4 points should be included in the string. See the Type for more information on constructing the string.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="datasetGPolygonExclusionGRing" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Exclusion polygon summary: Data Set G-Polygon Exclusion G-Ring, the closed nonintersecting boundary of a void area (or hole in an interior area). description: the closed nonintersecting boundary of a void area (or hole in an interior area). This is the center of the doughnut shape created by the datasetGPolygon. It can be created either by a gRing (list of points) or one or more gRingPoints. See the sub-elements and their Type definitions for more information. This element is generally analogous to an FGDC exclusion ring "Data Set G-Polygon Exclusion G-Ring", although it's children are somewhat differently described. Documentation for the FGDC component states that 4 points are required to define a polygon, and the first and last should be identical. However this EML element requires only one point so that a single point can be excluded, presumably, a single station. If multiple single stations are to be excluded, then authors should include multiple <datasetGPolygonExclusionGRing>s.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. This is useful if you register your datasets by a single geospatial point, such as the lat/long of your research station. Please see the sub elements and the Type description for more information on constructing a gRingPoint</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="gRing" type="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, See the Type for more information</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="GRingPointType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring point summary: A single geographic location. description: A single geographic location. This is useful if you register your datasets by a single geospatial point, such as the lat/long of your research station.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="gRingLatitude">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring Latitude summary: The latitude of a point of the g-ring. description: A latitude coordinate is typed as a decimal, i.e., decimal degrees from -90 to 90, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'S' or 'south') are not allowed. Latitudes north of the equator must be specified by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). example: 34.123 example: -18.25 example: +78.25</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-90.0"/>
- <xs:maxInclusive value="90.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="gRingLongitude">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring Longitude summary: description: The longitude of a point of the g-ring A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). example: -118.25 example: +25 example: 45.24755</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:decimal">
- <xs:minInclusive value="-180.0"/>
- <xs:maxInclusive value="180.0"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:simpleType name="GRingType">
- <xs:annotation>
- <xs:documentation>tooltip: G-Ring summary: description: A set of ordered pairs of floating-point numbers, separated by commas, in which the first number in each pair is the longitude of a point and the second is the latitude of the point. Longitude and latitude are specified in decimal degrees with north latitudes positive and south negative, east longitude positive and west negative Note on the relationship to FGDC: This element is generally analogous to the FGDC component for ring, although implemented somewhat differently. Documentation for FGDC states that 4 points are required to define a polygon, and the first and last should be identical, although this is not enforceable in XML Schema. In addition, EML does not enforce any pattern on the string used for a GRingType, so that it may be used differently as a child of EML's <datasetGPolygonOuterGRing> or <datasetGPolygonExclusionGRing> elements. If authors of EML instance documents wish the contents of this element to be directly translated to FGDC, they should comply with the example below when constructing their strings. Alternatively, in most cases, a sequence of gRingPoints can be used in EML instances, which can be processed into content for an FGDC Data Set G-Polygon G-Ring. example: This is an acceptable gRing: example: 12, 2.0987 12, -7.5555 34.345,10.40 example: However, for translation to FGDC, construct your string like this: example: -119.453,35.0 -125,37.5555 -122,40 -119.453,35.0</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string"/>
-</xs:simpleType>
<xs:complexType name="TemporalCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Temporal coverage summary: Temporal coverage information. description: The temporal coverage fields are intended to be used in describing the date and time of an event. It allows for three general descriptions: a single date or time, multiple dates or times, and a range of date or times. example: Please see the individual sub fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:choice>
- <xs:element name="singleDateTime" type="SingleDateTimeType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Single Date/Time summary: Means of encoding a single date and time description: The singleDateTime field is intended to describe a single date and time for an event. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="rangeOfDates">
- <xs:annotation>
- <xs:documentation>tooltip: Range of dates/times summary: Means of encoding a range of dates and times. description: The 'RangeOfDatesType' field is intended to be used for describing a range of dates and/or times. It may be used multiple times to document multiple date ranges. It allows for two 'singleDateTime' fields, the first to be used as the beginning dateTime, and the second to be used as the ending dateTime of the range. example: Please see the examples from the 'singleDateTime' field for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="beginDate" type="SingleDateTimeType">
- <xs:annotation>
- <xs:documentation>tooltip: Begin Date summary: A single time stamp signifying the beginning of some time period description: A single time stamp signifying the beginning of some time period. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="endDate" type="SingleDateTimeType">
- <xs:annotation>
- <xs:documentation>tooltip: End Date summary: A single time stamp signifying the end of some time period description: A single time stamp signifying the end of some time period. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
-</xs:complexType>
<xs:complexType name="SingleDateTimeType">
- <xs:annotation>
- <xs:documentation>tooltip: Single Date/Time summary: Means of encoding a single date and time description: The SingleDateTimeType field is intended to describe a single date and time for an event. There is a choice between two options: a calendar date with a time, or a geologic age. example: Please see the individual sub-elements for example.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="calendarDate" type="res:yearDate">
- <xs:annotation>
- <xs:documentation>tooltip: Calendar date summary: The calendar date for an event. description: The calendar date field is used to express a date, giving the year, month, and day. The format should be one that complies with the International Standards Organization's standard 8601. The recommended format for EML is YYYY-MM-DD, where Y is the four digit year, M is the two digit month code (01 - 12, where January = 01), and D is the two digit day of the month (01 - 31). This field can also be used to enter just the year portion of a date. example: 2001-01-01 example: 2001-10-12 example: 2001 example: 1895</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="time" type="xs:time" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Time of day summary: The time of day for an event. description: The time field is used to express the hour (and optionally minute, or minute and second) of the day for an event, and should comply with the International Standards Organization's standard 8601. The recommended format for EML is hh:mm:ssTZD, where hh is the two digit hour of the day, mm is the two digit minute of the hour, and ss is the two digit second of the minute. TZD stands for Time Zone Designator which is used to handle time zone offsets. Times may be expressed in two ways: 1) UTC (Coordinated Universal Time, also known as Greenwich Mean Time, or GMT), with a special UTC designator ("Z"), 2) local time, together with a time zone offset in hours and minutes. A time zone offset of "+hh:mm" indicates that the date or time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC. A time zone offset of "-hh:mm" indicates a local time zone which is "hh" hours and "mm" minutes behind UTC. example: 1) 08:31:22Z , which means eight thirty one and 22 seconds in the morning at Coordinated Universal Time (Greenwich Mean Time). 2) 14:06:09-08:00 , which means six minutes, nine seconds past two o'clock p.m., Pacific Standard Time (which is offset eight hours behind UTC)</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:element name="alternativeTimeScale">
- <xs:annotation>
- <xs:documentation>tooltip: Alternative Time Scale summary: A name, code, or date describing an event or period in an alternative time scale, such as one of the geologic time scales. description: A name, code, or date describing an event or period in an alternative time scale, for instance as an absolute date calculated using a named dating method, or as a relative date that is drawn from stratigraphy or biostratigraphy. Calendar dates as provided in the ISO 8601 dating system used in the standard CSDGM are not adequate to describe geologic time periods. Absolute geologic time is usually measured in millions of years before present, but may use different units and relative base times. Relative geologic time is measured by subdivisions of the earth's geology. in an order based upon relative age, most commonly, vertical or stratigraphic position. The actual dating systems used in geologic studies often tie relative times measured through stratigraphy or biostratigraphy to a particular absolute time using radioisotope dating techniques, among others. As these methods for absolute dating have improved, the estimates of the dates for strata have changed, consequently, it would be inaccurate to record absolute dates in situations where relative dates were measured. This structure is provided as an optional alternative to the standard calendar dates provided by ISO 8601. example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="timeScaleName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: alternative time scale summary: Name of a recognized alternative time scale. description: Name of a recognized alternative time scale. This includes 'Absolute' as the name of the time scale for measuring geologic dates before the present and names of geologic dating systems that are arrangements of symbols or names in order of relative geologic time. example: 'Absolute', 'Geomagnetic Polarity Time Scale', 'International Geological Time Scale', 'Oxygen-Isotope'</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="timeScaleAgeEstimate" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age estimate summary: description: Either an absolute date or a relative age name describing an event or period in an alternative time scale such as the Geologic Time Scale. example: For example, '300 Ma' (300 million years before present) is a Geologic_Age_Estimate based on the Absolute Geologic_Time_Scale, 'C28r' is a chron name from the Geomagnetic Polarity Time Scale, and 'Maastrichtian' and 'Jurassic' are names from the International Geological Time Scale. Since different relative geologic time scales are often not aligned, multiple geologic dates may need to be specified. For example, the Geomagnetic Polarity Time Scale chron 'C29r', at the K/T boundary lies in both the 'Maastrichtian' and the 'Danian' stages from the International Geological Time Scale, thus if you were documenting this event using the International Geological Time Scale, both 'Maastrichtian' and 'Danian' should be included here.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="timeScaleAgeUncertainty" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age uncertainty summary: The error estimate for the alternative time scale. description: The error estimate for the alternative time. This should include the units of measure, a description of what the error estimate represents and how it was calculated. example: +/- 5 Ma (Million Years)</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="timeScaleAgeExplanation" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Time scale age explanation summary: The name and/or description of the method used to calculate the time scale age estimate. description: The name and/or description of the method used to calculate the age estimate. Detailed information about the method may be provided through references contained in the Time Scale Citation field.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="timeScaleCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Time Scale citation summary: Citation for works providing detailed information about any element of the time scale age. description: Citation for works providing detailed information about any element of the time scale age. example: For example, a publication describing the methodology used for carbon dating or describing the basic geologic time scale in more detail could be cited here.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
-</xs:complexType>
<xs:complexType name="TaxonomicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic coverage summary: Taxonomic coverage information. description: Taxonomic Coverage is a container for taxonomic information about a project, a resource, or an entity within a resource. example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="taxonomicSystem" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic system summary: Documentation of taxonomic sources, procedures, and treatments. description: Documentation of taxonomic sources, procedures, and treatments.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="classificationSystem" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Classification system/authority summary: Information about the classification system or authority used. description: Information about the classification system or authority used. example: Flora of North America</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="classificationSystemCitation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic citation summary: description: Relevant literature for documenting the used classification system.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="classificationSystemModifications" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Classification system modification summary: description: A description of any modifications or exceptions made to the classification system or authority used.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="identificationReference" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Non-authoritative citation summary: description: Information on any non-authoritative materials (e.g. field guides) useful for reconstructing the actual identification process.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="identifierName" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Identifier's Name summary: description: Information about the individual(s) responsible for the identification(s) of the specimens or sightings, etc.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="taxonomicProcedures" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic procedures summary: description: Description of the methods used for the taxonomic identification. example: specimen processing, comparison with museum materials, keys and key characters, chemical or genetic analyses</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="taxonomicCompleteness" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic completeness summary: description: Information concerning the proportions and treatment of unidentified materials, estimates of the importance and possible identities of uncertain determinations, synonyms or other incorrect usages, taxa not well treated or requiring further work, and expertise of field workers. example: materials sent to experts, and not yet determined</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="vouchers" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Specimen information summary: description: Information on the types of specimen, the repository, and the individuals who identified the vouchers.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="specimen" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Specimen type summary: description: A word or phrase describing the type of specimen collected. example: herbarium specimens, blood samples, photographs, individuals, or batches</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="repository">
- <xs:annotation>
- <xs:documentation>tooltip: Storage location of specimen summary: description: Information about the curator or contact person and/or agency responsible for the specimens.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided. example: Please see the examples within the sub fields for the responsible party.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="generalTaxonomicCoverage" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: General taxonomic coverage summary: A description of the range of taxa addressed in the data set or collection. description: A description of the range of taxa addressed in the data set or collection. example: "All vascular plants were identified to family or species, mosses and lichens were identified as moss or lichen."</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="taxonomicClassification" type="TaxonomicClassificationType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic classification summary: Information about the range of taxa addressed in the data set or collection. description: Information about the range of taxa addressed in the data set or collection. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
-</xs:complexType>
<xs:complexType name="TaxonomicClassificationType">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic classification summary: Information about the range of taxa addressed in the data set or collection. description: Information about the range of taxa addressed in the data set or collection. It is recommended that one provide information starting from the taxonomic rank of kingdom, to a level which reflects the data set or collection being documented. The levels of Kingdom, Division/Phylum, Class, Order, Family, Genus, and Species should be included as ranks as appropriate. Because the taxonomic ranks are hierarchical, the Taxonomic Classification field is self-referencing to allow for an arbitrary depth of rank, down to species. example: The Taxonomic Classification field consists of a sequence of 4 fields: taxonomic rank, taxonomic rank value, common name, and finally Taxonomic Classification (self-referencing). Please see the sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="taxonRankName" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxon rank name summary: The name of the taxonomic rank for which the Taxon rank value is provided. description: The name of the taxonomic rank for which the Taxon rank value is provided. This field allows for the name one of the accepted levels of Taxa. example: 'Kingdom', 'Division/Phylum', 'Class', 'Order', 'Family', 'Genus', and 'Species'</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="taxonRankValue" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Taxon rank value summary: The taxonomic rank name being described. description: The name for the taxonomic rank being described. Typically the values are from authoritative sources such as the Integrated Taxonomic Information System (ITIS) in the U.S. (http://www/itis.usda.gov) and in Canada (http://sis.agr.gc.ca/pls/itisca/taxaget). Species2000 is another source of taxonomic information, found at (http://www.sp2000.org). Note that for the taxonomic rank "species", the accepted practice is to use binomial nomenclaure, i.e., a combination of the genus name plus species epithet is required to denote the species. Therefore the "species" is not the species epithet alone. example: For the rank genus, 'Acer' is an example of the rank value, 'Acer rubrum' for a species rank value, and a common name of 'Red Maple'. Additional examples of "species" are "Homo sapiens" and "Tyrannosaurus rex".</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="commonName" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Common name summary: Specification of applicable common names. description: Specification of applicable common names. These common names may be general descriptions of a group of organisms if appropriate. example: insects, vertebrate, grasses, waterfowl, vascular plants, red maple.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="taxonId" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic Identifier summary: Element holds an ID and ID-provider for this taxon. description: The identifier for this taxon from an authority, such as ITIS or USDA Plant Database. Using an external system identifer allows referencing of additional information about a taxon, e.g., authoritative names, historical synonyms, published descriptions or rank hierarchies. example: 11274 example: 35122</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="provider" type="xs:anyURI" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Taxon ID Provider summary: The taxonomic authority or catalog from which the taxonId can be retrieved, defined as the namespace URI for the provider. description: This attribute holds the namespace URI for the taxonomic authority or catalog to which this taxonId applies. taxonId providers should be chosen for their stability and longevity, and with discernable website URIs or APIs. Examples are given for ITIS, NCBI, the USDA plants database, Encyclopedia of Life and the World Register of Marine Species (WoRMS). example: https://www.itis.gov example: https://www.ncbi.nlm.nih.gov/taxonomy example: https://plants.usda.gov example: https://eol.org example: http://www.marinespecies.org</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="taxonomicClassification" type="TaxonomicClassificationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic classification summary: Information about the range of taxa addressed in the data set or collection. description: Information about the range of taxa addressed in the data set or collection. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
-</xs:complexType>
<xs:attribute name="provider" type="xs:anyURI" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Taxon ID Provider summary: The taxonomic authority or catalog from which the taxonId can be retrieved, defined as the namespace URI for the provider. description: This attribute holds the namespace URI for the taxonomic authority or catalog to which this taxonId applies. taxonId providers should be chosen for their stability and longevity, and with discernable website URIs or APIs. Examples are given for ITIS, NCBI, the USDA plants database, Encyclopedia of Life and the World Register of Marine Species (WoRMS). example: https://www.itis.gov example: https://www.ncbi.nlm.nih.gov/taxonomy example: https://plants.usda.gov example: https://eol.org example: http://www.marinespecies.org</xs:documentation>
- </xs:annotation>
-</xs:attribute>
diff --git a/dist/schema/eml-dataTable_xsd.html b/dist/schema/eml-dataTable_xsd.html
index 7dc7cf07..58822bd4 100644
--- a/dist/schema/eml-dataTable_xsd.html
+++ b/dist/schema/eml-dataTable_xsd.html
@@ -18,19 +18,6 @@
var facetsBoxes= new Array('facets_DataTableType_caseSensitive',
'facets_DataTableType_numberOfRecords',
'facets_DataTableType_scope');
-var usedByBoxes= new Array('usedBy_DataTableType',
- 'usedBy_DataTableType_id',
- 'usedBy_DataTableType_system',
- 'usedBy_DataTableType_scope');
-var sourceBoxes= new Array('source_DataTableType_attributeList',
- 'source_DataTableType_constraint',
- 'source_DataTableType_caseSensitive',
- 'source_DataTableType_numberOfRecords',
- 'source_dataTable',
- 'source_DataTableType',
- 'source_DataTableType_id',
- 'source_DataTableType_system',
- 'source_DataTableType_scope');
var instanceBoxes= new Array('instance_DataTableType_attributeList',
'instance_DataTableType_constraint',
'instance_dataTable');
@@ -320,12 +307,6 @@
Showing:
Properties
-
-
Source
-
-
-
Used by
-
@@ -580,25 +561,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -776,25 +738,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -912,31 +855,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="caseSensitive" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Case sensitivity summary: Specification of text case sensitivity in the dataTable. description: The caseSensitive element specifies text case sensitivity of the data in the dataTable. The valid values are yes or no. If it is set to yes, then values of attributes that differ only in case (e.g., LOW, low) represent distinct values. If set to no, then values of attributes that differ only in case represent the same value. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -1052,25 +970,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="numberOfRecords" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of records summary: The integer count of the number of records in the dataTable. description: The numberOfRecords element contains a count of the number of records in the dataTable. This is typically an integer value, and only includes records that represent observations. It would not include any details of physical formatting such as the number of header lines (see eml-physical for that information). example: 975</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1263,25 +1162,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dataTable" type="DataTableType">
- <xs:annotation>
- <xs:documentation>tooltip: Table Entity descriptor summary: Descriptor of one table entity in the dataset. description: The dataTable element is a descriptor of one entity in the dataset identified by its name. This element can contain information about the dataTable's orientation, number of records, case sensitivity, and temporal, geographic and taxonomic coverage. Because the dataTable element refers to the complex type 'DataTableType', it must contain all the elements defined for the type. description for DataTableType to review component element rules.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="DataTableType">
- <xs:choice>
- <xs:sequence>
- <xs:group ref="ent:EntityGroup"/>
- <xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="caseSensitive" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Case sensitivity summary: Specification of text case sensitivity in the dataTable. description: The caseSensitive element specifies text case sensitivity of the data in the dataTable. The valid values are yes or no. If it is set to yes, then values of attributes that differ only in case (e.g., LOW, low) represent distinct values. If set to no, then values of attributes that differ only in case represent the same value. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="numberOfRecords" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of records summary: The integer count of the number of records in the dataTable. description: The numberOfRecords element contains a count of the number of records in the dataTable. This is typically an integer value, and only includes records that represent observations. It would not include any details of physical formatting such as the number of header lines (see eml-physical for that information). example: 975</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:element name="purpose" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Purpose summary: A synopsis of the purpose of this dataset. description: A synopsis of the purpose of this dataset. It may include one or more paragraphs as well as inline links to table(s) and figure(s) that summarize the data included in the data paper, including a summary of key findings if appropriate. Note that this element requires DocBook style formatting. See eml-text for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -922,25 +858,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="introduction" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Introduction summary: An overview of the background and context for the dataset. description: One to many paragraphs that provide background and context for the dataset with appropriate figures and references. This is similar to the introduction for a journal article, and would include, for example, project objectives, hypotheses being addressed, what is known about the pattern or process under study, how the data have been used to date (including references), and how they could be used in the future. The introduction may include figure(s) and table(s) by first attaching those entities to the dataset (e.g., dataTable, otherEntity), providing an id attribute for that entity, and then referencing that entity id in the text of the introduction using Markdown's syntax for inline images. See eml-text for more information on formatting within this section.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1104,25 +1021,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="gettingStarted" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Getting Started summary: A high level overview of interpretation, structure, and content of the dataset. description: One or more paragraphs that describe the overall interpretation, content and structure of the dataset. For example, the number and names of data files, they types of measurements that they contain, how those data files fit together in an overall design, and how they relate to the data collections methods, experimental design, and sampling design that are described in other EML sections. One might describe any specialized software that is available and/or may be necessary for analyzing or interpreting the data, and possibly include a high level description of data formats if they are unusual, keeping in mind that detailed desriptions of data structure and format are contained in the entity sections of EML. Citations, inline figures, and inline images can be included via inline references in Markdown sections. See eml-text for more information on formatting within this section.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1281,25 +1179,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="acknowledgements" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Acknowledgements summary: Text that acknowledges funders and other key contributors. description: One or more sentences that acknowledge funders and other key contributors to the study (excluding the dataset authors listed in the creator field). Note that funding awards are also listed by award number in the eml-project award element, which provides a structured list of funders, award numbers, and award URIs for the dataset. When displaying acknowledgements, client software should provide both the information in this acknowledgements element as well as links from the award element. See eml-text for more information on formatting within this section.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1418,25 +1297,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="maintenance" type="MaintenanceType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maintenance summary: A description of the maintenance of this data resource. description: A description of the maintenance of this data resource. This includes information about the frequency of update, and whether there is ongoing data collection.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1583,25 +1443,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Maintenance Description summary: A text description of the maintenance of this data resource. description: A text description of the maintenance of this data resource. Note that this field must be marked up using DocBook like tagging. See eml-text for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1784,25 +1625,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="maintenanceUpdateFrequency" type="MaintUpFreqType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maintenance Update Frequency summary: Frequency with which changes and additions are made to the dataset after the initial dataset is completed. description: Frequency with which changes and additions are made to the dataset after the initial dataset is completed. The values for this field must come from the enumeration MaintUpFreqType.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1920,49 +1742,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="changeHistory" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Change History summary: A description of changes made to the data since its release. description: A description of changes made to the data since its release.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="changeScope" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Change Scope summary: An expression describing the scope to which the documented change was applied. description: The expression should unambiguously identify the entity(s) and attribute(s) that were changed.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="oldValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Old Value summary: The previous value of the data prior to the change. description: The previous value or an expression that describes the previous value of the data.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="changeDate" type="xs:date">
- <xs:annotation>
- <xs:documentation>tooltip: Change Date summary: The date the changes were applied. description: The date the changes were applied.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="comment" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Comment summary: Explanation or justification for the change made to the data. description: Explanation or justification for the change made to the data.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2070,25 +1849,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="changeScope" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Change Scope summary: An expression describing the scope to which the documented change was applied. description: The expression should unambiguously identify the entity(s) and attribute(s) that were changed.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2195,25 +1955,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="oldValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Old Value summary: The previous value of the data prior to the change. description: The previous value or an expression that describes the previous value of the data.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2291,25 +2032,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="changeDate" type="xs:date">
- <xs:annotation>
- <xs:documentation>tooltip: Change Date summary: The date the changes were applied. description: The date the changes were applied.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2419,25 +2141,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="comment" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Comment summary: Explanation or justification for the change made to the data. description: Explanation or justification for the change made to the data.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2620,25 +2323,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="contact" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Contact summary: The contact for this dataset description: The contact field contains contact information for this dataset. This is the person or institution to contact with questions about the use, interpretation of a data set.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2821,25 +2505,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Data Set Publisher summary: The publisher of this data set description: The publisher of this data set. At times this is a traditional publishing house, but it may also simply be an institution that is making the data available in a published (ie, citable) format.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2954,25 +2619,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="pubPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication place summary: The location that the resource was published. description: The pubPlace field is the location where the resource was published, which may be different from where the resource was created. example: San Francisco, CA, USA example: New York, NY, USA</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3091,25 +2737,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="methods" type="md:MethodsType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: methods summary: The methods field documents scientific methods used in the collection of this dataset. description: The methods field documents scientific methods used in the collection of this dataset. It includes information on items such as tools, instrument calibration and software.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3294,25 +2921,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="project" type="proj:ResearchProjectType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: project summary: The project field contains information on the project in which this dataset was collected. description: The project field contains information on the project in which this dataset was collected. It includes information such as project personnel, funding, study area, project design and related projects. The project description can also contain documentation on subprojects.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3501,25 +3109,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dataTable" type="dat:DataTableType">
- <xs:annotation>
- <xs:documentation>tooltip: data table summary: The dataTable field documents the dataTable(s) that make up this dataset. description: The dataTable field documents the dataTable(s) that make up this dataset. A dataTable could be anything from a Comma Separated Value (CSV) file to a spreadsheet to a table in an RDBMS.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3734,25 +3323,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="spatialRaster" type="sr:SpatialRasterType">
- <xs:annotation>
- <xs:documentation>tooltip: spatial raster summary: The spatialRaster field describes any spatial raster images included in this dataset. description: The spatialRaster field describes any spatial raster images included in this dataset.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3947,25 +3517,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="spatialVector" type="sv:SpatialVectorType">
- <xs:annotation>
- <xs:documentation>tooltip: spatial vector summary: The spatialVector field describes any spatial vectors included in this dataset. description: The spatialVector field describes any spatial vectors included in this dataset.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4154,25 +3705,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="storedProcedure" type="sp:StoredProcedureType">
- <xs:annotation>
- <xs:documentation>tooltip: stored procedure summary: The storedProcedure field contains information about any stored procedures included with this dataset. description: The storedProcedure field contains information about any stored procedures included with this dataset. This usually implies that the dataset is stored in a DBMS or some other data management system capable of processing your dataset.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4361,25 +3893,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="view" type="v:ViewType">
- <xs:annotation>
- <xs:documentation>tooltip: view summary: The view field contains information about any views included with this dataset. description: The view field contains information about any view included with this dataset. This usually implies that the dataset is stored in a DBMS or some other data management system capable of processing your dataset.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4570,25 +4083,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="otherEntity" type="ent:OtherEntityType">
- <xs:annotation>
- <xs:documentation>tooltip: other entity summary: The otherEntity field contains information about any entity in the dataset that is not any of the preceding entities. description: The otherEntity field contains information about any entity in the dataset that is not any of the preceding entities. (i.e. it is not a table, spatialRaster, spatialVector, storedProcedure or view.) OtherEntity allows the documentation of basic entity fields as well as a plain text field to allow you to type your entity.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4821,25 +4315,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="referencePublication" type="cit:CitationType" minOccurs="0" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Reference Publication summary: A citation to an additional publication that serves as an important reference for a dataset. description: A citation to an additional publication that serves as an important reference for a dataset. People using this dataset should generally cite the dataset itself (using the creator, pubDate, title, publisher, and packageId fields), and consider providing an additional citation to the Reference Publication. Common cases where a Reference Publication may be useful include when a data paper is published that describes the dataset, or when a paper is intended to be the canonical or examplar reference to the dataset.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5079,25 +4554,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="usageCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Usage Citation summary: A citation to articles or products in which the dataset is used or referenced. description: A citation to articles or products in which the dataset is used or referenced. The citation element contains general information about a literature resource that has used or references this dataset resource. It is not expected that the list of usageCitations will necessarily be complete, but rather they serve as examples and pointers to scholarly works in which this dataset has been used.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5218,25 +4674,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="literatureCited" type="cit:CitationListType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literature Cited summary: A citation to articles or products which were referenced in the dataset or its associated metadata. description: A citation to articles or products which were referenced in the dataset or its associated metadata. The list represents the bibliography of works related to the dataset, whether for reference, comparison, or others purposes.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5476,25 +4913,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dataset" type="DatasetType">
- <xs:annotation>
- <xs:documentation>tooltip: Dataset Descriptors summary: The dataset field encompasses all information about a single dataset. description: The dataset field encompasses all information about a single dataset. A dataset is defined as all of the information describing a data collection event. This event may take place over some period of time and include many actual collections (a time series or remote sensing application) or it could be just one actual collection (a day in the field).</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="DatasetType">
- <xs:annotation>
- <xs:documentation>tooltip: Dataset summary: DatasetType is the base type for the dataset element. description: DatasetType is the base type for the dataset element. The dataset field encompasses all information about a single dataset. A dataset is defined as all of the information describing a data collection event. This event may take place over some period of time and include many actual collections (a time series or remote sensing application) or it could be just one actual collection (a day in the field).</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:group ref="res:ResourceGroup"/>
- <xs:element name="purpose" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Purpose summary: A synopsis of the purpose of this dataset. description: A synopsis of the purpose of this dataset. It may include one or more paragraphs as well as inline links to table(s) and figure(s) that summarize the data included in the data paper, including a summary of key findings if appropriate. Note that this element requires DocBook style formatting. See eml-text for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="introduction" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Introduction summary: An overview of the background and context for the dataset. description: One to many paragraphs that provide background and context for the dataset with appropriate figures and references. This is similar to the introduction for a journal article, and would include, for example, project objectives, hypotheses being addressed, what is known about the pattern or process under study, how the data have been used to date (including references), and how they could be used in the future. The introduction may include figure(s) and table(s) by first attaching those entities to the dataset (e.g., dataTable, otherEntity), providing an id attribute for that entity, and then referencing that entity id in the text of the introduction using Markdown's syntax for inline images. See eml-text for more information on formatting within this section.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="gettingStarted" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Getting Started summary: A high level overview of interpretation, structure, and content of the dataset. description: One or more paragraphs that describe the overall interpretation, content and structure of the dataset. For example, the number and names of data files, they types of measurements that they contain, how those data files fit together in an overall design, and how they relate to the data collections methods, experimental design, and sampling design that are described in other EML sections. One might describe any specialized software that is available and/or may be necessary for analyzing or interpreting the data, and possibly include a high level description of data formats if they are unusual, keeping in mind that detailed desriptions of data structure and format are contained in the entity sections of EML. Citations, inline figures, and inline images can be included via inline references in Markdown sections. See eml-text for more information on formatting within this section.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="acknowledgements" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Acknowledgements summary: Text that acknowledges funders and other key contributors. description: One or more sentences that acknowledge funders and other key contributors to the study (excluding the dataset authors listed in the creator field). Note that funding awards are also listed by award number in the eml-project award element, which provides a structured list of funders, award numbers, and award URIs for the dataset. When displaying acknowledgements, client software should provide both the information in this acknowledgements element as well as links from the award element. See eml-text for more information on formatting within this section.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="maintenance" type="MaintenanceType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maintenance summary: A description of the maintenance of this data resource. description: A description of the maintenance of this data resource. This includes information about the frequency of update, and whether there is ongoing data collection.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="contact" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Contact summary: The contact for this dataset description: The contact field contains contact information for this dataset. This is the person or institution to contact with questions about the use, interpretation of a data set.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Data Set Publisher summary: The publisher of this data set description: The publisher of this data set. At times this is a traditional publishing house, but it may also simply be an institution that is making the data available in a published (ie, citable) format.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pubPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication place summary: The location that the resource was published. description: The pubPlace field is the location where the resource was published, which may be different from where the resource was created. example: San Francisco, CA, USA example: New York, NY, USA</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="methods" type="md:MethodsType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: methods summary: The methods field documents scientific methods used in the collection of this dataset. description: The methods field documents scientific methods used in the collection of this dataset. It includes information on items such as tools, instrument calibration and software.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="project" type="proj:ResearchProjectType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: project summary: The project field contains information on the project in which this dataset was collected. description: The project field contains information on the project in which this dataset was collected. It includes information such as project personnel, funding, study area, project design and related projects. The project description can also contain documentation on subprojects.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice minOccurs="0" maxOccurs="unbounded">
- <xs:element name="dataTable" type="dat:DataTableType">
- <xs:annotation>
- <xs:documentation>tooltip: data table summary: The dataTable field documents the dataTable(s) that make up this dataset. description: The dataTable field documents the dataTable(s) that make up this dataset. A dataTable could be anything from a Comma Separated Value (CSV) file to a spreadsheet to a table in an RDBMS.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="spatialRaster" type="sr:SpatialRasterType">
- <xs:annotation>
- <xs:documentation>tooltip: spatial raster summary: The spatialRaster field describes any spatial raster images included in this dataset. description: The spatialRaster field describes any spatial raster images included in this dataset.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="spatialVector" type="sv:SpatialVectorType">
- <xs:annotation>
- <xs:documentation>tooltip: spatial vector summary: The spatialVector field describes any spatial vectors included in this dataset. description: The spatialVector field describes any spatial vectors included in this dataset.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="storedProcedure" type="sp:StoredProcedureType">
- <xs:annotation>
- <xs:documentation>tooltip: stored procedure summary: The storedProcedure field contains information about any stored procedures included with this dataset. description: The storedProcedure field contains information about any stored procedures included with this dataset. This usually implies that the dataset is stored in a DBMS or some other data management system capable of processing your dataset.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="view" type="v:ViewType">
- <xs:annotation>
- <xs:documentation>tooltip: view summary: The view field contains information about any views included with this dataset. description: The view field contains information about any view included with this dataset. This usually implies that the dataset is stored in a DBMS or some other data management system capable of processing your dataset.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="otherEntity" type="ent:OtherEntityType">
- <xs:annotation>
- <xs:documentation>tooltip: other entity summary: The otherEntity field contains information about any entity in the dataset that is not any of the preceding entities. description: The otherEntity field contains information about any entity in the dataset that is not any of the preceding entities. (i.e. it is not a table, spatialRaster, spatialVector, storedProcedure or view.) OtherEntity allows the documentation of basic entity fields as well as a plain text field to allow you to type your entity.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:element name="referencePublication" type="cit:CitationType" minOccurs="0" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Reference Publication summary: A citation to an additional publication that serves as an important reference for a dataset. description: A citation to an additional publication that serves as an important reference for a dataset. People using this dataset should generally cite the dataset itself (using the creator, pubDate, title, publisher, and packageId fields), and consider providing an additional citation to the Reference Publication. Common cases where a Reference Publication may be useful include when a data paper is published that describes the dataset, or when a paper is intended to be the canonical or examplar reference to the dataset.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="usageCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Usage Citation summary: A citation to articles or products in which the dataset is used or referenced. description: A citation to articles or products in which the dataset is used or referenced. The citation element contains general information about a literature resource that has used or references this dataset resource. It is not expected that the list of usageCitations will necessarily be complete, but rather they serve as examples and pointers to scholarly works in which this dataset has been used.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literatureCited" type="cit:CitationListType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literature Cited summary: A citation to articles or products which were referenced in the dataset or its associated metadata. description: A citation to articles or products which were referenced in the dataset or its associated metadata. The list represents the bibliography of works related to the dataset, whether for reference, comparison, or others purposes.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="MaintenanceType">
- <xs:annotation>
- <xs:documentation>tooltip: Maintenance Type summary: The maintenance type defines the fields for the maintenance element. It encompasses all information related to the maintenance and upkeep of this dataset. description: The maintenance type defines the fields for the maintenance element.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Maintenance Description summary: A text description of the maintenance of this data resource. description: A text description of the maintenance of this data resource. Note that this field must be marked up using DocBook like tagging. See eml-text for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="maintenanceUpdateFrequency" type="MaintUpFreqType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maintenance Update Frequency summary: Frequency with which changes and additions are made to the dataset after the initial dataset is completed. description: Frequency with which changes and additions are made to the dataset after the initial dataset is completed. The values for this field must come from the enumeration MaintUpFreqType.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="changeHistory" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Change History summary: A description of changes made to the data since its release. description: A description of changes made to the data since its release.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="changeScope" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Change Scope summary: An expression describing the scope to which the documented change was applied. description: The expression should unambiguously identify the entity(s) and attribute(s) that were changed.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="oldValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Old Value summary: The previous value of the data prior to the change. description: The previous value or an expression that describes the previous value of the data.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="changeDate" type="xs:date">
- <xs:annotation>
- <xs:documentation>tooltip: Change Date summary: The date the changes were applied. description: The date the changes were applied.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="comment" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Comment summary: Explanation or justification for the change made to the data. description: Explanation or justification for the change made to the data.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:element name="alternateIdentifier" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Alternate Identifier summary: A secondary identifier for this entity description: An additional, secondary identifier for this entity. The primary identifier belongs in the "id" attribute, but additional identifiers that are used to label this entity, possibly from different data management systems, can be listed here. example: VCR3465</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="system" type="res:SystemType" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Identifier System summary: The system in which this id is relevant description: The information management system within which this identifier has relevance. Generally, the identifier would be unique within the "system" and would be sufficient to retrieve the entity from the system. The system is often a URL or URI that identifies the main entry point for the information management system. example: http://knb.ecoinformatics.org/knb/</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -768,25 +708,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="entityName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Entity name summary: The name of the entity name description: The name identifies the entity in the dataset: file name, name of database table, etc. example: SpeciesAbundance1996</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -900,25 +821,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="entityDescription" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Entity description summary: General description of the entity and its contents description: Text generally describing the entity, its type, and relevant information about the data in the entity. example: Species abundance data for 1996 at the VCR LTER site</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1111,25 +1013,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="physical" type="phys:PhysicalType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: physical descriptors summary: Description of the physical format of the entity description: Information on the physical format of this entity. Each logical entity can be serialized in one or more physical formats, which can be described here. For each physical format, provide a "physical" element that describes the format and how to obtain that version. Two physical elements MUST describe the same entity precisely (i.e., after obtaining and parsing the physical data stream described under each physical element, one MUST end with an identical logical entity). For more information see the eml-physical module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1302,25 +1185,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="coverage" type="cov:Coverage" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: coverage descriptors summary: Information on the geographic, spatial and temporal coverages used in this entity. description: Information on the geographic, spatial and temporal coverages used in this entity. Please see the eml-coverage module for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1439,25 +1303,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="methods" type="md:MethodsType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: method descriptions summary: description: Information on the specific methods used to collect information in this entity. Please see the eml-methods module for more information. example:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1614,25 +1459,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="additionalInfo" type="txt:TextType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Additional Information summary: Any extra information pertitent to the entity. description: This field provides any information that is not characterized by the other entity metadata fields. example: Multiple sampling events represented</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1809,25 +1635,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="annotation" type="sem:SemanticAnnotation" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about this entity. description: An annotation represents a precisely-defined semantic statement that applies to this entity. This semantic statement is used to associate precise measurement semantics with the entity. Each annotation consists of a propertyURI and valueURI, which define a property and a value that apply to the entity. The associated labels can be used to display the property and value to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1974,25 +1781,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeList" type="att:AttributeListType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2170,25 +1958,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2300,25 +2069,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="entityType" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Entity type summary: Contains the name of the type for this entity. description: The entityType field contains the name of the entity's type. The entity's type is typically the name of the type of data represented in the entity, such as "photograph". This field is used only if this is an 'other' entity and you want to specify the kind of "other" entity this is. example: Photograph</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2509,25 +2259,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="otherEntity" type="OtherEntityType">
- <xs:annotation>
- <xs:documentation>tooltip: Other Entity summary: Descriptor of single data entity in a dataset of a type not specifically described in eml. description: The other entity element is a descriptor of a not-otherwise-defined entity in the dataset, identified by its name. The element can contain information about the entity's basic identity, its temporal, geographic and taxonomic coverage, and its type. example: Photograph of rocky intertidal plot 12 from Santa Cruz Island</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="OtherEntityType">
- <xs:choice>
- <xs:sequence>
- <xs:group ref="EntityGroup"/>
- <xs:sequence>
- <xs:element name="attributeList" type="att:AttributeListType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="entityType" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Entity type summary: Contains the name of the type for this entity. description: The entityType field contains the name of the entity's type. The entity's type is typically the name of the type of data represented in the entity, such as "photograph". This field is used only if this is an 'other' entity and you want to specify the kind of "other" entity this is. example: Photograph</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:attribute name="system" type="res:SystemType" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Identifier System summary: The system in which this id is relevant description: The information management system within which this identifier has relevance. Generally, the identifier would be unique within the "system" and would be sufficient to retrieve the entity from the system. The system is often a URL or URI that identifies the main entry point for the information management system. example: http://knb.ecoinformatics.org/knb/</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:group name="EntityGroup">
- <xs:annotation>
- <xs:documentation>tooltip: Base Entity descriptors summary: Basic information about an entity common to all entity types. description: The EntityGroup defines the common structure for descriptions of any type of entity, including the name and attributes of the entity. The term entity is used in the sense of an entity in a relational model. The most common entity is a table, something with columns and rows, but can also represent an image or other type of data. See 'eml-attribute' for descriptions of the required attribute fields.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="alternateIdentifier" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Alternate Identifier summary: A secondary identifier for this entity description: An additional, secondary identifier for this entity. The primary identifier belongs in the "id" attribute, but additional identifiers that are used to label this entity, possibly from different data management systems, can be listed here. example: VCR3465</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="system" type="res:SystemType" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Identifier System summary: The system in which this id is relevant description: The information management system within which this identifier has relevance. Generally, the identifier would be unique within the "system" and would be sufficient to retrieve the entity from the system. The system is often a URL or URI that identifies the main entry point for the information management system. example: http://knb.ecoinformatics.org/knb/</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="entityName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Entity name summary: The name of the entity name description: The name identifies the entity in the dataset: file name, name of database table, etc. example: SpeciesAbundance1996</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="entityDescription" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Entity description summary: General description of the entity and its contents description: Text generally describing the entity, its type, and relevant information about the data in the entity. example: Species abundance data for 1996 at the VCR LTER site</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="physical" type="phys:PhysicalType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: physical descriptors summary: Description of the physical format of the entity description: Information on the physical format of this entity. Each logical entity can be serialized in one or more physical formats, which can be described here. For each physical format, provide a "physical" element that describes the format and how to obtain that version. Two physical elements MUST describe the same entity precisely (i.e., after obtaining and parsing the physical data stream described under each physical element, one MUST end with an identical logical entity). For more information see the eml-physical module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="coverage" type="cov:Coverage" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: coverage descriptors summary: Information on the geographic, spatial and temporal coverages used in this entity. description: Information on the geographic, spatial and temporal coverages used in this entity. Please see the eml-coverage module for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="methods" type="md:MethodsType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: method descriptions summary: description: Information on the specific methods used to collect information in this entity. Please see the eml-methods module for more information. example:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="additionalInfo" type="txt:TextType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Additional Information summary: Any extra information pertitent to the entity. description: This field provides any information that is not characterized by the other entity metadata fields. example: Multiple sampling events represented</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="annotation" type="sem:SemanticAnnotation" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about this entity. description: An annotation represents a precisely-defined semantic statement that applies to this entity. This semantic statement is used to associate precise measurement semantics with the entity. Each annotation consists of a propertyURI and valueURI, which define a property and a value that apply to the entity. The associated labels can be used to display the property and value to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:group>
<xs:element name="contact" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Contact summary: An optional contact individual for this citation description: The contact field contains information about an alternate person to be contacted about this citation. Usually, the first author serves as the contact for a citation resource, e.g., a reprint request. In some cases, an alternate individual(s) may serve that function, and can be indicated here. Since contact is of the type rp:ResponsibleParty, a reference may be used.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1238,25 +1100,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="article" type="Article">
- <xs:annotation>
- <xs:documentation>tooltip: article summary: Information for full citation of a journal article or other periodical article. description: The article field provides sub-fields for a full citation of an article in a journal or other periodical.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1368,25 +1211,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="journal" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Journal Name summary: The name of the journal, magazine, newspaper, zine, etc... in which the article was published. description: The name of the journal, magazine, newspaper, zine, etc... in which the article was published. example: "Ecology" example: "New York Times" example: "Harper's"</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1498,25 +1322,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Journal Volume summary: The volume of the journal in which the article appears description: The volume field is used to describe the volume of the journal in which the article appears. example: "Volume I"</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1628,25 +1433,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="issue" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Journal issue summary: The issue of the journal in which the article appears description: The issue field is used to describe the issue of the journal in which the article appears. example: November 2001</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1759,25 +1545,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="pageRange" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Journal Pages summary: The beginning and end page numbers of the journal article description: The page range field is used for the beginning and ending pages of the journal article that is being documented. example: 115-122</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1963,25 +1730,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the article description: The organization that physically puts together the article and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2096,25 +1844,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2227,25 +1956,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="ISSN" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Serial Number summary: The unique Internation Standard Serial Number description: The ISSN, or International Standard Serial Number that has been assigned to this literature resource. example: ISSN 1234-5679</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2370,25 +2080,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="book" type="Book">
- <xs:annotation>
- <xs:documentation>tooltip: Book summary: Information for full citation of a book description: The book field provides sub-fields for a full citation of a book.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2570,25 +2261,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publisher" type="rp:ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the book description: The organization that physically puts together the book and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2703,25 +2375,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2832,25 +2485,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Book edition summary: The edition of the book being described. description: The edition field is to document the edition of the book that is being described. example: Second Edition</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2963,25 +2597,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Book volume summary: The volume of the book that is part of a series. description: The volume field is used to describe the volume number of a book that is part of a multi-volume series of books. example: Volume 2</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3092,25 +2707,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="numberOfVolumes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Volumes summary: Number of volumes in a collection description: Number of volumes in a collection example: 12</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3222,25 +2818,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total book pages summary: The total number of pages in the book. description: The total pages field is used to describe the total number of pages in the book that is being described. example: 628</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3352,25 +2929,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalFigures" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of figures in book summary: The total number of figures in the book. description: the total figures field is used to describe the total number of figures, diagrams, and plates in the book that is being documented. example: 45</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3482,25 +3040,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalTables" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of tables in book summary: The total number of tables in a book. description: The total tables field is used to describe the total number of tables that are present in the book that is being documented. example: 10</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3613,25 +3152,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="ISBN" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource. example: ISBN 1-861003-11-0</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3779,25 +3299,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="chapter" type="Chapter">
- <xs:annotation>
- <xs:documentation>tooltip: Book Chapter summary: Information for citation of a chapter in a book description: The book chapter allows citation of a single chapter or section of a book. The "creator" for a book chapter are the chapter's authors, while the "editor" is the book editors. Likewise, "title" is the chapter title, while "bookTitle" is the title of the whole book.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3909,25 +3410,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="chapterNumber" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Chapter number summary: The chapter number of interest within a book description: The chapter number of the chapter of a book that is being described. example: 7</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4116,25 +3598,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="editor" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Book editor summary: The name of the editor of the book. description: The book editor field is used to document the name of the editor of the book that is being described. The editor may be a person, organization, or a role within an organization. example: Tom Christiansen example: Institute of Marine Science example: Publication Manager</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4241,25 +3704,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="bookTitle" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Book title summary: The title of the book. description: The book title field is used to document the title of the book that is being described. example: War and Peace</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4372,25 +3816,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="pageRange" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Chapter page range summary: The beginning and ending page numbers of a chapter. description: The page range field is used to document the beginning and ending pages of a chapter in a book. example: 25-122</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4517,25 +3942,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="editedBook" type="Book">
- <xs:annotation>
- <xs:documentation>tooltip: Book summary: Information for full citation of an edited book description: The edited book represents a book which was edited by one or more editors, but whose chapters were possibly authored by others. The editors of an edited book should be listed in the "creator" field.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4646,25 +4052,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="manuscript" type="Manuscript">
- <xs:annotation>
- <xs:documentation>tooltip: unpublished manuscipt summary: Information about an unpublished manuscript description: The manuscript field provides sub-fields for a full citation of an unpublished manuscript.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4850,25 +4237,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="institution" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Manuscript publication information summary: The address and contact information needed to request a manuscript. description: The institution information field is used to provide contact and address information that would be needed to request an unpublished manuscript example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4981,25 +4349,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total manuscript pages summary: The total number of pages in the manuscript. description: The total pages field is used to describe the total number of pages in the manuscript that is being described. example: 628</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5116,25 +4465,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="report" type="Report">
- <xs:annotation>
- <xs:documentation>tooltip: Report summary: Information about a report published by an institution. description: The report may be self published by the institution or through a publisher. They usually are available by request to the institution or can be purchased from the publisher.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5247,25 +4577,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="reportNumber" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Report Number summary: The unique identification number assigned to the report. description: The report number field is used to describe the unique identification number that has been issued by the report institution for the report being described. example: 22</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5451,25 +4762,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the report description: The organization that physically put together the report and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5584,25 +4876,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5714,25 +4987,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total report pages summary: The total number of pages in the report. description: The total pages field is used to describe the total number of pages in the report that is being described. example: 628</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5848,25 +5102,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="thesis" type="Thesis">
- <xs:annotation>
- <xs:documentation>tooltip: Thesis as part of a degree summary: Information about a thesis that has been written as part of a degree requirement and is frequently published in small numbers by the degree awarding institution. description: Information about a thesis that has been written as part of a degree requirement and is frequently published in small numbers by the degree awarding institution.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5978,25 +5213,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="degree" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Degee name summary: The name or degree level for which the thesis was completed. description: The degree field is used to describe the name or degree level for which the thesis was completed. example: Ph.D. example: M.S. example: Master of Science</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6177,25 +5393,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="institution" type="rp:ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Degree awarding institution summary: The name of the degree-awarding institution description: The degree institution field is used to name the institution from which the degree was awarded for the thesis being described. example: Western Washington University</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6307,25 +5504,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Thesis Pages summary: The total number of pages in the thesis. description: The total pages field is used to document the number of pages that are present in the thesis that is being described. example: 356</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6480,25 +5658,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="conferenceProceedings" type="ConferenceProceedings">
- <xs:annotation>
- <xs:documentation>tooltip: conference proceedings summary: The published notes, papers, presentations etc... of a conference. description: The published notes, papers, presentations, etc..., of a conference.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6610,25 +5769,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="conferenceName" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Name summary: The name of the conference whose proceedings have been published. description: The name of the conference whose proceedings have been published. example: North American Science Symposium</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6739,25 +5879,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="conferenceDate" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Date summary: The date the conference was held. description: The date the conference was held. example: November 1-6, 1998</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6933,25 +6054,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="conferenceLocation" type="rp:Address" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Location summary: The location where the conference was held. description: The location where the conference was held.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7067,25 +6169,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="personalCommunication" type="PersonalCommunication">
- <xs:annotation>
- <xs:documentation>tooltip: Personal communication summary: A personal communication that has been saved online or as hard-copy. description: This could be a widely distributed memo, an e-mail, a transcript from a conversation or interview, etc...</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7271,25 +6354,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the communication description: The organization that physically puts together the communication and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7404,25 +6468,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7538,25 +6583,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="communicationType" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Type of communication summary: The type of personal communication. description: The type of personal communication. Could be an email, letter, memo, transcript of conversation either hardcopy or online. example: memo example: letter example: email</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7745,25 +6771,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="recipient" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Recipient summary: Recipient of the communication description: The person, place or thing the personal communication was sent to. example: Schmedley, Joe example: jschmedley@lternet.edu</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7879,25 +6886,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="map" type="Map">
- <xs:annotation>
- <xs:documentation>tooltip: map summary: This element describes the map that is being cited or cataloged. description: This element describes the map that is being cited or cataloged, including its geographic coverage and scale.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8081,25 +7069,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the map description: The organization that physically puts together the map and publishes it. example: Harper Collins</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8210,25 +7179,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Map edition summary: The edition of the map being described. description: The edition field is to document the edition of the map that is being described. example: Second Edition</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8405,25 +7355,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="geographicCoverage" type="cov:GeographicCoverage" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic coverage summary: Description of the geographic area which the map covers description: This element describes the geographic area which the map covers. Could be descriptive text or Cartesian coordinates of the area.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:element name="generic" type="Generic">
- <xs:annotation>
- <xs:documentation>tooltip: Generic Citation summary: This reference type was created for references that do not fit in to the other existing reference types description: This reference type was created for references that do not fit in to the other existing reference types.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8889,25 +7782,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publisher" type="rp:ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization which actually publishes the reference description: The organization which physically puts together the reference and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9022,25 +7896,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9120,25 +7975,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="referenceType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Reference Type summary: The type of reference. description: The reference type describes the type of reference this generic type is being used to represent. example: zine example: film example: radio program</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9251,25 +8087,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Reference volume summary: The volume of the reference that is part of a series. description: The volume field is used to describe the volume number of a reference that is part of a multi-volume series of references. example: Volume 2</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9380,25 +8197,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="numberOfVolumes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Volumes summary: Number of volumes in a collection description: Number of volumes in a collection example: "12"</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9511,25 +8309,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total reference pages summary: The total number of pages in the references. description: The total pages field is used to describe the total number of pages in the references that is being described. example: 628</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9642,25 +8421,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalFigures" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of figures in reference summary: The total number of figures in the reference. description: The total figures field is used to describe the total number of figures, diagrams, and plates in the reference that is being documented. example: 45</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9773,25 +8533,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalTables" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of tables in reference summary: The total number of tables in a reference. description: The total tables field is used to describe the total number of tables that are present in the reference that is being documented. example: 10</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9904,25 +8645,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: edition summary: The edition of the generic reference being described. description: The edition field is to document the edition of the generic reference type that is being described. example: Second Edition</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10036,25 +8758,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="originalPublication" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Original Publication summary: References current publication to its original. description: Supplemental information about the original publication of the current reference. example: Date example: Publisher</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10167,25 +8870,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="reprintEdition" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Reprint Edition summary: Reference for current edition that was originally published under a different title. description: Reference for current edition that was originally published under a different title. example: Stream Research in the LTER Network, 1993</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10300,25 +8984,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="reviewedItem" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Reviewed Item summary: Reference types that are reviews of other references. description: Use for articles, chapters, audio visual, etc. that are critical review of books, cinema, art, or other works. example: Structure and Function of an Alpine Ecosystem Niwot Ridge, Colorado Edited by WILLIAM D. BOWMAN and TIMOTHY R. SEASTEDT, University of Colorado, Boulder</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10427,25 +9092,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="ISBN" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource. example: ISBN 1-861003-11-0</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10554,25 +9200,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="ISSN" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Serial Number summary: The unique Internation Standard Serial Number description: The ISSN, or International Standard Serial Number that has been assigned to this literature resource. example: ISSN 1234-5679</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10688,25 +9315,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="audioVisual" type="AudioVisual">
- <xs:annotation>
- <xs:documentation>tooltip: audio visual summary: This reference type is meant to cover all forms of audio and visual media. description: This reference type is meant to cover all forms of audio and visual media, including film, video, broadcast, other electronic media.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -10890,25 +9498,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publisher" type="rp:ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization which actually distributes the video, film, the broadcaster etc... description: Organization which actually distributes the video, film, the broadcaster etc... example: LTER Network Office example: Public Broadcasting example: Pacifica Radio</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -11027,25 +9616,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -11235,25 +9805,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="performer" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Performer summary: The performers in the audio visual production description: The performers involved in acting, narrating, or shown in the audio visual production. example: Jim Nabors example: Sir Lawrence Olivier</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -11366,25 +9917,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="ISBN" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource. example: ISBN 1-861003-11-0</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -11500,25 +10032,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="presentation" type="Presentation">
- <xs:annotation>
- <xs:documentation>tooltip: Unpublished Presentation summary: An unpublished presentation from a conference, workshop, workgroup, symposium etc. description: An unpublished presentation from a conference, workshop, workgroup, symposium, etc. It will be provided upon request in either in paper and/or electronic form. If the presentation was actually published in a proceedings, use the conferenceProceedings type instead.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -11630,25 +10143,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="conferenceName" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Name summary: The name of the conference at which this presentation was given. description: The name of the conference at which this presentation was given. example: North American Science Symposium</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -11759,25 +10253,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="conferenceDate" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Date summary: The date the conference was held. description: The date the conference was held. example: November 1-6, 1998</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -11953,25 +10428,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="conferenceLocation" type="rp:Address" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Location summary: The location where the conference was held. description: The location where the conference was held.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -12049,25 +10505,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="bibtex" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Bibtex Citation summary: Citation in Bibtex format. description: The bibtex field provides a parseable citation formatted according to the Bibtex formatting conventions. The citation entry is assigned a unique key that must be unique across all bibtex fields in the EML document. The citation key can be used in markdown sections of the text to refer to this citation using the pandoc-style of inline citation keys. See the markdown element for more details. The record is delimited using curly braces. Most reference software can both import and export citations in Bibtex format, so this is a simpler representation to produce and consume than native EML citation representations.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -12294,25 +10731,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: A citation within a list of citations. description: A citation within a list of citations, usually used for a literatureCited cited list or similar. Each citation is formatted following the EML CitationType structure.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -12389,25 +10807,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="bibtex" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Bibtex Citation List summary: List of citations in Bibtex format. description: The bibtex field provides a parseable list of citations formatted according to the Bibtex formatting conventions. Each citation entry is assigned a unique key that must be unique across all bibtex fields in the EML document. The citation key can be used in markdown sections of the text to refer to this citation using the pandoc-style of inline citation keys. See the markdown element for more details. The record is delimited using curly braces. Most reference software can both import and export citations in Bibtex format, so this is a simpler representation to produce and consume than native EML citation representations.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -12639,25 +11038,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Literature Citation summary: Information describing a literature resource. description: The citation element contains general information about a literature resource that is being documented, or a piece of literature that is being cited in support of a given resource, such as a dataset. It contains sub-elements that are specific to a literature resource such as a book, a journal article, a thesis, etc. It extends the generic resource elements with literature specific fields.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="CitationType">
- <xs:choice>
- <xs:sequence>
- <xs:group ref="res:ResourceGroup"/>
- <xs:element name="contact" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Contact summary: An optional contact individual for this citation description: The contact field contains information about an alternate person to be contacted about this citation. Usually, the first author serves as the contact for a citation resource, e.g., a reprint request. In some cases, an alternate individual(s) may serve that function, and can be indicated here. Since contact is of the type rp:ResponsibleParty, a reference may be used.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice>
- <xs:element name="article" type="Article">
- <xs:annotation>
- <xs:documentation>tooltip: article summary: Information for full citation of a journal article or other periodical article. description: The article field provides sub-fields for a full citation of an article in a journal or other periodical.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="book" type="Book">
- <xs:annotation>
- <xs:documentation>tooltip: Book summary: Information for full citation of a book description: The book field provides sub-fields for a full citation of a book.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="chapter" type="Chapter">
- <xs:annotation>
- <xs:documentation>tooltip: Book Chapter summary: Information for citation of a chapter in a book description: The book chapter allows citation of a single chapter or section of a book. The "creator" for a book chapter are the chapter's authors, while the "editor" is the book editors. Likewise, "title" is the chapter title, while "bookTitle" is the title of the whole book.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="editedBook" type="Book">
- <xs:annotation>
- <xs:documentation>tooltip: Book summary: Information for full citation of an edited book description: The edited book represents a book which was edited by one or more editors, but whose chapters were possibly authored by others. The editors of an edited book should be listed in the "creator" field.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="manuscript" type="Manuscript">
- <xs:annotation>
- <xs:documentation>tooltip: unpublished manuscipt summary: Information about an unpublished manuscript description: The manuscript field provides sub-fields for a full citation of an unpublished manuscript.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="report" type="Report">
- <xs:annotation>
- <xs:documentation>tooltip: Report summary: Information about a report published by an institution. description: The report may be self published by the institution or through a publisher. They usually are available by request to the institution or can be purchased from the publisher.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="thesis" type="Thesis">
- <xs:annotation>
- <xs:documentation>tooltip: Thesis as part of a degree summary: Information about a thesis that has been written as part of a degree requirement and is frequently published in small numbers by the degree awarding institution. description: Information about a thesis that has been written as part of a degree requirement and is frequently published in small numbers by the degree awarding institution.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="conferenceProceedings" type="ConferenceProceedings">
- <xs:annotation>
- <xs:documentation>tooltip: conference proceedings summary: The published notes, papers, presentations etc... of a conference. description: The published notes, papers, presentations, etc..., of a conference.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="personalCommunication" type="PersonalCommunication">
- <xs:annotation>
- <xs:documentation>tooltip: Personal communication summary: A personal communication that has been saved online or as hard-copy. description: This could be a widely distributed memo, an e-mail, a transcript from a conversation or interview, etc...</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="map" type="Map">
- <xs:annotation>
- <xs:documentation>tooltip: map summary: This element describes the map that is being cited or cataloged. description: This element describes the map that is being cited or cataloged, including its geographic coverage and scale.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="generic" type="Generic">
- <xs:annotation>
- <xs:documentation>tooltip: Generic Citation summary: This reference type was created for references that do not fit in to the other existing reference types description: This reference type was created for references that do not fit in to the other existing reference types.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="audioVisual" type="AudioVisual">
- <xs:annotation>
- <xs:documentation>tooltip: audio visual summary: This reference type is meant to cover all forms of audio and visual media. description: This reference type is meant to cover all forms of audio and visual media, including film, video, broadcast, other electronic media.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="presentation" type="Presentation">
- <xs:annotation>
- <xs:documentation>tooltip: Unpublished Presentation summary: An unpublished presentation from a conference, workshop, workgroup, symposium etc. description: An unpublished presentation from a conference, workshop, workgroup, symposium, etc. It will be provided upon request in either in paper and/or electronic form. If the presentation was actually published in a proceedings, use the conferenceProceedings type instead.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- <xs:element name="bibtex" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Bibtex Citation summary: Citation in Bibtex format. description: The bibtex field provides a parseable citation formatted according to the Bibtex formatting conventions. The citation entry is assigned a unique key that must be unique across all bibtex fields in the EML document. The citation key can be used in markdown sections of the text to refer to this citation using the pandoc-style of inline citation keys. See the markdown element for more details. The record is delimited using curly braces. Most reference software can both import and export citations in Bibtex format, so this is a simpler representation to produce and consume than native EML citation representations.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="Article">
- <xs:annotation>
- <xs:documentation>tooltip: article summary: Information for full citation of a journal article or other periodical article. description: The article field provides sub-fields for a full citation of an article in a journal or other periodical.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="journal" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Journal Name summary: The name of the journal, magazine, newspaper, zine, etc... in which the article was published. description: The name of the journal, magazine, newspaper, zine, etc... in which the article was published. example: "Ecology" example: "New York Times" example: "Harper's"</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Journal Volume summary: The volume of the journal in which the article appears description: The volume field is used to describe the volume of the journal in which the article appears. example: "Volume I"</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="issue" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Journal issue summary: The issue of the journal in which the article appears description: The issue field is used to describe the issue of the journal in which the article appears. example: November 2001</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pageRange" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Journal Pages summary: The beginning and end page numbers of the journal article description: The page range field is used for the beginning and ending pages of the journal article that is being documented. example: 115-122</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the article description: The organization that physically puts together the article and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="ISSN" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Serial Number summary: The unique Internation Standard Serial Number description: The ISSN, or International Standard Serial Number that has been assigned to this literature resource. example: ISSN 1234-5679</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="Book">
- <xs:annotation>
- <xs:documentation>tooltip: Book summary: Information for full citation of a book description: The book field provides sub-fields for a full citation of a book.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="publisher" type="rp:ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the book description: The organization that physically puts together the book and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Book edition summary: The edition of the book being described. description: The edition field is to document the edition of the book that is being described. example: Second Edition</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Book volume summary: The volume of the book that is part of a series. description: The volume field is used to describe the volume number of a book that is part of a multi-volume series of books. example: Volume 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numberOfVolumes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Volumes summary: Number of volumes in a collection description: Number of volumes in a collection example: 12</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total book pages summary: The total number of pages in the book. description: The total pages field is used to describe the total number of pages in the book that is being described. example: 628</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalFigures" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of figures in book summary: The total number of figures in the book. description: the total figures field is used to describe the total number of figures, diagrams, and plates in the book that is being documented. example: 45</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalTables" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of tables in book summary: The total number of tables in a book. description: The total tables field is used to describe the total number of tables that are present in the book that is being documented. example: 10</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="ISBN" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource. example: ISBN 1-861003-11-0</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="Chapter">
- <xs:annotation>
- <xs:documentation>tooltip: Book Chapter summary: Information for citation of a chapter in a book description: The book chapter allows citation of a single chapter or section of a book. The "creator" for a book chapter are the chapter's authors, while the "editor" is the book editors. Likewise, "title" is the chapter title, while "bookTitle" is the title of the whole book.</xs:documentation>
- </xs:annotation>
- <xs:complexContent>
- <xs:extension base="Book">
- <xs:sequence>
- <xs:element name="chapterNumber" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Chapter number summary: The chapter number of interest within a book description: The chapter number of the chapter of a book that is being described. example: 7</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="editor" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Book editor summary: The name of the editor of the book. description: The book editor field is used to document the name of the editor of the book that is being described. The editor may be a person, organization, or a role within an organization. example: Tom Christiansen example: Institute of Marine Science example: Publication Manager</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bookTitle" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Book title summary: The title of the book. description: The book title field is used to document the title of the book that is being described. example: War and Peace</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pageRange" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Chapter page range summary: The beginning and ending page numbers of a chapter. description: The page range field is used to document the beginning and ending pages of a chapter in a book. example: 25-122</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
<xs:complexType name="Manuscript">
- <xs:annotation>
- <xs:documentation>tooltip: unpublished manuscipt summary: Information about an unpublished manuscript description: The manuscript field provides sub-fields for a full citation of an unpublished manuscript.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="institution" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Manuscript publication information summary: The address and contact information needed to request a manuscript. description: The institution information field is used to provide contact and address information that would be needed to request an unpublished manuscript example: Please see the individual sub-fields for specific examples.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total manuscript pages summary: The total number of pages in the manuscript. description: The total pages field is used to describe the total number of pages in the manuscript that is being described. example: 628</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="Report">
- <xs:annotation>
- <xs:documentation>tooltip: Report summary: Information about a report published by an institution. description: The report may be self published by the institution or through a publisher. They usually are available by request to the institution or can be purchased from the publisher.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="reportNumber" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Report Number summary: The unique identification number assigned to the report. description: The report number field is used to describe the unique identification number that has been issued by the report institution for the report being described. example: 22</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the report description: The organization that physically put together the report and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total report pages summary: The total number of pages in the report. description: The total pages field is used to describe the total number of pages in the report that is being described. example: 628</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="Thesis">
- <xs:annotation>
- <xs:documentation>tooltip: Thesis as part of a degree summary: Information about a thesis that has been written as part of a degree requirement and is frequently published in small numbers by the degree awarding institution. description: Information about a thesis that has been written as part of a degree requirement and is frequently published in small numbers by the degree awarding institution.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="degree" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Degee name summary: The name or degree level for which the thesis was completed. description: The degree field is used to describe the name or degree level for which the thesis was completed. example: Ph.D. example: M.S. example: Master of Science</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="institution" type="rp:ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Degree awarding institution summary: The name of the degree-awarding institution description: The degree institution field is used to name the institution from which the degree was awarded for the thesis being described. example: Western Washington University</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Thesis Pages summary: The total number of pages in the thesis. description: The total pages field is used to document the number of pages that are present in the thesis that is being described. example: 356</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="ConferenceProceedings">
- <xs:annotation>
- <xs:documentation>tooltip: conference proceedings summary: The published notes, papers, presentations etc... of a conference. description: The published notes, papers, presentations, etc..., of a conference.</xs:documentation>
- </xs:annotation>
- <xs:complexContent>
- <xs:extension base="Chapter">
- <xs:sequence>
- <xs:element name="conferenceName" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Name summary: The name of the conference whose proceedings have been published. description: The name of the conference whose proceedings have been published. example: North American Science Symposium</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="conferenceDate" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Date summary: The date the conference was held. description: The date the conference was held. example: November 1-6, 1998</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="conferenceLocation" type="rp:Address" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Location summary: The location where the conference was held. description: The location where the conference was held.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
<xs:complexType name="PersonalCommunication">
- <xs:annotation>
- <xs:documentation>tooltip: Personal communication summary: A personal communication that has been saved online or as hard-copy. description: This could be a widely distributed memo, an e-mail, a transcript from a conversation or interview, etc...</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the communication description: The organization that physically puts together the communication and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="communicationType" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Type of communication summary: The type of personal communication. description: The type of personal communication. Could be an email, letter, memo, transcript of conversation either hardcopy or online. example: memo example: letter example: email</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="recipient" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Recipient summary: Recipient of the communication description: The person, place or thing the personal communication was sent to. example: Schmedley, Joe example: jschmedley@lternet.edu</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="Map">
- <xs:annotation>
- <xs:documentation>tooltip: map summary: This element describes the map that is being cited or cataloged. description: This element describes the map that is being cited or cataloged, including its geographic coverage and scale.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the map description: The organization that physically puts together the map and publishes it. example: Harper Collins</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Map edition summary: The edition of the map being described. description: The edition field is to document the edition of the map that is being described. example: Second Edition</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="geographicCoverage" type="cov:GeographicCoverage" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic coverage summary: Description of the geographic area which the map covers description: This element describes the geographic area which the map covers. Could be descriptive text or Cartesian coordinates of the area.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="scale" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Scale summary: The Map's scale description: The Map's scale example: 1:25,000</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="Generic">
- <xs:sequence>
- <xs:element name="publisher" type="rp:ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization which actually publishes the reference description: The organization which physically puts together the reference and publishes it. example: Harper Collins example: University Of California Press</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="referenceType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Reference Type summary: The type of reference. description: The reference type describes the type of reference this generic type is being used to represent. example: zine example: film example: radio program</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Reference volume summary: The volume of the reference that is part of a series. description: The volume field is used to describe the volume number of a reference that is part of a multi-volume series of references. example: Volume 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numberOfVolumes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Volumes summary: Number of volumes in a collection description: Number of volumes in a collection example: "12"</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total reference pages summary: The total number of pages in the references. description: The total pages field is used to describe the total number of pages in the references that is being described. example: 628</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalFigures" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of figures in reference summary: The total number of figures in the reference. description: The total figures field is used to describe the total number of figures, diagrams, and plates in the reference that is being documented. example: 45</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalTables" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of tables in reference summary: The total number of tables in a reference. description: The total tables field is used to describe the total number of tables that are present in the reference that is being documented. example: 10</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: edition summary: The edition of the generic reference being described. description: The edition field is to document the edition of the generic reference type that is being described. example: Second Edition</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="originalPublication" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Original Publication summary: References current publication to its original. description: Supplemental information about the original publication of the current reference. example: Date example: Publisher</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="reprintEdition" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Reprint Edition summary: Reference for current edition that was originally published under a different title. description: Reference for current edition that was originally published under a different title. example: Stream Research in the LTER Network, 1993</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="reviewedItem" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Reviewed Item summary: Reference types that are reviews of other references. description: Use for articles, chapters, audio visual, etc. that are critical review of books, cinema, art, or other works. example: Structure and Function of an Alpine Ecosystem Niwot Ridge, Colorado Edited by WILLIAM D. BOWMAN and TIMOTHY R. SEASTEDT, University of Colorado, Boulder</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice minOccurs="0">
- <xs:element name="ISBN" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource. example: ISBN 1-861003-11-0</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="ISSN" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Serial Number summary: The unique Internation Standard Serial Number description: The ISSN, or International Standard Serial Number that has been assigned to this literature resource. example: ISSN 1234-5679</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="AudioVisual">
- <xs:annotation>
- <xs:documentation>tooltip: audio visual summary: This reference type is meant to cover all forms of audio and visual media. description: This reference type is meant to cover all forms of audio and visual media, including film, video, broadcast, other electronic media.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="publisher" type="rp:ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Publisher summary: Organization which actually distributes the video, film, the broadcaster etc... description: Organization which actually distributes the video, film, the broadcaster etc... example: LTER Network Office example: Public Broadcasting example: Pacifica Radio</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. example: New York example: London</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="performer" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Performer summary: The performers in the audio visual production description: The performers involved in acting, narrating, or shown in the audio visual production. example: Jim Nabors example: Sir Lawrence Olivier</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="ISBN" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource. example: ISBN 1-861003-11-0</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="Presentation">
- <xs:annotation>
- <xs:documentation>tooltip: Unpublished Presentation summary: An unpublished presentation from a conference, workshop, workgroup, symposium, etc. description: An unpublished presentation from a conference, workshop, workgroup, symposium, etc. It will be provided upon request in either in paper and/or electronic form by contacting the authors. If the presentation was actually published in a proceedings, use the conferenceProceedings type instead.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="conferenceName" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Name summary: The name of the conference at which this presentation was given. description: The name of the conference at which this presentation was given. example: North American Science Symposium</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="conferenceDate" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Date summary: The date the conference was held. description: The date the conference was held. example: November 1-6, 1998</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="conferenceLocation" type="rp:Address" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Conference Location summary: The location where the conference was held. description: The location where the conference was held.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="CitationListType">
- <xs:choice minOccurs="1" maxOccurs="unbounded">
- <xs:element name="citation" type="CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: A citation within a list of citations. description: A citation within a list of citations, usually used for a literatureCited cited list or similar. Each citation is formatted following the EML CitationType structure.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bibtex" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Bibtex Citation List summary: List of citations in Bibtex format. description: The bibtex field provides a parseable list of citations formatted according to the Bibtex formatting conventions. Each citation entry is assigned a unique key that must be unique across all bibtex fields in the EML document. The citation key can be used in markdown sections of the text to refer to this citation using the pandoc-style of inline citation keys. See the markdown element for more details. The record is delimited using curly braces. Most reference software can both import and export citations in Bibtex format, so this is a simpler representation to produce and consume than native EML citation representations.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
-</xs:complexType>
<xs:element name="methodStep" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: method information summary: Information about the methods employed in collecting or generating a data set or other resource. description: The methodStep field allows for repeated sets of elements that document a series of procedures followed to produce a data object. These include text descriptions of the procedures, relevant literature, software, instrumentation, source data and any quality control measures taken. example: Please see the examples for the sub-fields.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="ProcedureStepType">
- <xs:sequence>
- <xs:element name="dataSource" type="ds:DatasetType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: data source summary: A source of data used by this methodStep. description: A source of data used by this methodStep.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -855,25 +794,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Methods description summary: Description of the methods employed in collecting or generating a data set or other resource or in quality control and assurance. description: The description field allows for repeated text that describes the methodology for a project, experiment, or particular data table or to describe the steps taken to control or assure the quality of the data. Likewise, a literature citation may be provided that describes the methodology that was employed. Or the information my be provided by either referencing a protocol resource or entering the structured protocol information example: 1.Collect tissues from algae of interest. a. We are currently collecting Egregia menziezii, Mazzaella splendens, M. flaccida, Hedophyllum sessile, Postelsia palmaeformis and Fucus gardneri.We stopped collecting Neorhodomela larix and Odonthalia floccosa because they can be heavily fouled and we feared that would skew the results. b. We collect a 7-10 cm blade or branch from each plant. For Egregia, try to sample small, young plants or take the base of the blade. For Postelsia, take a few of the blades. The other plants are small enough so a whole blade can be taken.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1101,25 +1021,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: Literature citation relating to the methods used. description: The citation field allows to either reference a literature resource or enter structured literature information</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1321,25 +1222,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="protocol" type="pro:ProtocolType">
- <xs:annotation>
- <xs:documentation>tooltip: Protocol summary: Protocol description relating to the methods used. description: The protocol field is used to either reference a protocol resource or describe methods and identify the processes that have been used to define / improve the quality of a data file, also used to identify potential problems with the data file.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1457,25 +1339,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="instrumentation" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Instrumentation summary: Instruments used for measurement and recording data. description: The Instrumentation field allows the description of any instruments used in the data collection or quality control and quality assurance. The description should include vendor, model number, optional equipment, etc. example: LACHAT analyzer, model XYX.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1691,25 +1554,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="software" type="sw:SoftwareType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Software summary: Software used in the processing of data. description: The software element allows reference to any software used to process data.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1836,25 +1680,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="subStep" type="ProcedureStepType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: substep summary: description: This fields allows the nesting of additional method steps within this step. This is useful for hierarchical method descriptions.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2096,25 +1921,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dataSource" type="ds:DatasetType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: data source summary: A source of data used by this methodStep. description: A source of data used by this methodStep.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2231,77 +2037,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="sampling" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: sampling methods summary: Description of sampling procedures including the geographic, temporal and taxonomic coverage of the study. description: Description of sampling procedures including the geographic, temporal and taxonomic coverage of the study. See individual elements for more detailed descriptions.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="studyExtent">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic, temporal, taxonomic coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="coverage" type="cov:Coverage">
- <xs:annotation>
- <xs:documentation>tooltip: coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element. See eml-coverage for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Text description of the coverage summary: A textual description of the specific areas sampled (geographic coverage), the sampling frequency (temporal coverage), and groups of living organisms sampled (taxonomic coverage). description: The coverage field allows for a textual description of the specific sampling area, the sampling frequency (temporal boundaries, frequency of occurrence), and groups of living organisms sampled (taxonomic coverage). example: The study was conducted on the North Platte River, starting 6 miles downstream and ending 9 miles downstream of the route 132 bridge in Evanston, ND.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="samplingDescription" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Sampling methods and procedures summary: A description of sampling methods and procedures description: The samplingDescription field allows for a text-based/human readable description of the sampling procedures used in the research project. The content of this element would be similar to a description of sampling procedures found in the methods section of a journal article.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="spatialSamplingUnits" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial sampling units summary: Spatial sampling units represent the plots sampled. description: A spatial sampling unit describes the specific geographic areas sampled. In the case of a study in which the measurements from several disbursed point collection devices are aggregated, then the sampling unit would be the area of that aggregation. Spatial sampling units can either be described by filling out the structured coverage element or by reference to the values in a data table (usually a GIS layer) example: If a researcher places a single light source at a specific point in a research location in order to attract insects to derive an estimate of the insect population, then the sampling unit is the area illuminated by the light source (in actual practice there might be multiple sampling units in this case since different species have different attraction rates). example: The bounding box of a specific 3-meter square plot. example: The location of a weather station.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="referencedEntityId">
- <xs:annotation>
- <xs:documentation>tooltip: The identifier of a spatial sampling entity. summary: The identifier of an entity described in the entity module. This is usually a GIS layer. description: A value of a referencedEntityId element is a reference to the identifier of the entity module that provides the metadata for a data table (RDBMS, GIS or ascii text) that has the actual spatial sampling unit values. The referencedEntityId field is an indirect pointer to the actual values. The referencedEntityId can be thought of as a foreign key in a relational database. example: x</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="coverage" type="cov:GeographicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: sampling unit location summary: Structured description of each sampling unit location description: Structured description of each sampling unit location</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: Literature citation relating to the sampling procedures used. description: The citation field allows to either reference a literature resource or enter structured literature information</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2416,39 +2151,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="studyExtent">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic, temporal, taxonomic coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="coverage" type="cov:Coverage">
- <xs:annotation>
- <xs:documentation>tooltip: coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element. See eml-coverage for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Text description of the coverage summary: A textual description of the specific areas sampled (geographic coverage), the sampling frequency (temporal coverage), and groups of living organisms sampled (taxonomic coverage). description: The coverage field allows for a textual description of the specific sampling area, the sampling frequency (temporal boundaries, frequency of occurrence), and groups of living organisms sampled (taxonomic coverage). example: The study was conducted on the North Platte River, starting 6 miles downstream and ending 9 miles downstream of the route 132 bridge in Evanston, ND.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2625,25 +2327,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="coverage" type="cov:Coverage">
- <xs:annotation>
- <xs:documentation>tooltip: coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element. See eml-coverage for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2800,25 +2483,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Text description of the coverage summary: A textual description of the specific areas sampled (geographic coverage), the sampling frequency (temporal coverage), and groups of living organisms sampled (taxonomic coverage). description: The coverage field allows for a textual description of the specific sampling area, the sampling frequency (temporal boundaries, frequency of occurrence), and groups of living organisms sampled (taxonomic coverage). example: The study was conducted on the North Platte River, starting 6 miles downstream and ending 9 miles downstream of the route 132 bridge in Evanston, ND.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2968,25 +2632,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="samplingDescription" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Sampling methods and procedures summary: A description of sampling methods and procedures description: The samplingDescription field allows for a text-based/human readable description of the sampling procedures used in the research project. The content of this element would be similar to a description of sampling procedures found in the methods section of a journal article.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3115,39 +2760,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="spatialSamplingUnits" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial sampling units summary: Spatial sampling units represent the plots sampled. description: A spatial sampling unit describes the specific geographic areas sampled. In the case of a study in which the measurements from several disbursed point collection devices are aggregated, then the sampling unit would be the area of that aggregation. Spatial sampling units can either be described by filling out the structured coverage element or by reference to the values in a data table (usually a GIS layer) example: If a researcher places a single light source at a specific point in a research location in order to attract insects to derive an estimate of the insect population, then the sampling unit is the area illuminated by the light source (in actual practice there might be multiple sampling units in this case since different species have different attraction rates). example: The bounding box of a specific 3-meter square plot. example: The location of a weather station.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="referencedEntityId">
- <xs:annotation>
- <xs:documentation>tooltip: The identifier of a spatial sampling entity. summary: The identifier of an entity described in the entity module. This is usually a GIS layer. description: A value of a referencedEntityId element is a reference to the identifier of the entity module that provides the metadata for a data table (RDBMS, GIS or ascii text) that has the actual spatial sampling unit values. The referencedEntityId field is an indirect pointer to the actual values. The referencedEntityId can be thought of as a foreign key in a relational database. example: x</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="coverage" type="cov:GeographicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: sampling unit location summary: Structured description of each sampling unit location description: Structured description of each sampling unit location</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3216,25 +2828,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="referencedEntityId">
- <xs:annotation>
- <xs:documentation>tooltip: The identifier of a spatial sampling entity. summary: The identifier of an entity described in the entity module. This is usually a GIS layer. description: A value of a referencedEntityId element is a reference to the identifier of the entity module that provides the metadata for a data table (RDBMS, GIS or ascii text) that has the actual spatial sampling unit values. The referencedEntityId field is an indirect pointer to the actual values. The referencedEntityId can be thought of as a foreign key in a relational database. example: x</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3402,25 +2995,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="coverage" type="cov:GeographicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: sampling unit location summary: Structured description of each sampling unit location description: Structured description of each sampling unit location</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3656,25 +3230,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: Literature citation relating to the sampling procedures used. description: The citation field allows to either reference a literature resource or enter structured literature information</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3808,25 +3363,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="qualityControl" type="ProcedureStepType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quality Control summary: Information on possible errors or on the quality of a data set. description: The qualityControl field provides a location for the description of actions taken to either control or assess the quality of data resulting from the associated method step. A quality control description should identify a quality goal and describe prescriptive steps taken to ensure that the data meet those standards and/or postscriptive steps taken to assess the extent to which they are met. A quality control statement is associated with the methodStep that could have affected the targeted quality goal.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="MethodsType">
- <xs:sequence maxOccurs="unbounded">
- <xs:element name="methodStep" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: method information summary: Information about the methods employed in collecting or generating a data set or other resource. description: The methodStep field allows for repeated sets of elements that document a series of procedures followed to produce a data object. These include text descriptions of the procedures, relevant literature, software, instrumentation, source data and any quality control measures taken. example: Please see the examples for the sub-fields.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="ProcedureStepType">
- <xs:sequence>
- <xs:element name="dataSource" type="ds:DatasetType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: data source summary: A source of data used by this methodStep. description: A source of data used by this methodStep.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="sampling" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: sampling methods summary: Description of sampling procedures including the geographic, temporal and taxonomic coverage of the study. description: Description of sampling procedures including the geographic, temporal and taxonomic coverage of the study. See individual elements for more detailed descriptions.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="studyExtent">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic, temporal, taxonomic coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="coverage" type="cov:Coverage">
- <xs:annotation>
- <xs:documentation>tooltip: coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element. See eml-coverage for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Text description of the coverage summary: A textual description of the specific areas sampled (geographic coverage), the sampling frequency (temporal coverage), and groups of living organisms sampled (taxonomic coverage). description: The coverage field allows for a textual description of the specific sampling area, the sampling frequency (temporal boundaries, frequency of occurrence), and groups of living organisms sampled (taxonomic coverage). example: The study was conducted on the North Platte River, starting 6 miles downstream and ending 9 miles downstream of the route 132 bridge in Evanston, ND.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="samplingDescription" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Sampling methods and procedures summary: A description of sampling methods and procedures description: The samplingDescription field allows for a text-based/human readable description of the sampling procedures used in the research project. The content of this element would be similar to a description of sampling procedures found in the methods section of a journal article.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="spatialSamplingUnits" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial sampling units summary: Spatial sampling units represent the plots sampled. description: A spatial sampling unit describes the specific geographic areas sampled. In the case of a study in which the measurements from several disbursed point collection devices are aggregated, then the sampling unit would be the area of that aggregation. Spatial sampling units can either be described by filling out the structured coverage element or by reference to the values in a data table (usually a GIS layer) example: If a researcher places a single light source at a specific point in a research location in order to attract insects to derive an estimate of the insect population, then the sampling unit is the area illuminated by the light source (in actual practice there might be multiple sampling units in this case since different species have different attraction rates). example: The bounding box of a specific 3-meter square plot. example: The location of a weather station.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="referencedEntityId">
- <xs:annotation>
- <xs:documentation>tooltip: The identifier of a spatial sampling entity. summary: The identifier of an entity described in the entity module. This is usually a GIS layer. description: A value of a referencedEntityId element is a reference to the identifier of the entity module that provides the metadata for a data table (RDBMS, GIS or ascii text) that has the actual spatial sampling unit values. The referencedEntityId field is an indirect pointer to the actual values. The referencedEntityId can be thought of as a foreign key in a relational database. example: x</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="coverage" type="cov:GeographicCoverage">
- <xs:annotation>
- <xs:documentation>tooltip: sampling unit location summary: Structured description of each sampling unit location description: Structured description of each sampling unit location</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: Literature citation relating to the sampling procedures used. description: The citation field allows to either reference a literature resource or enter structured literature information</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="qualityControl" type="ProcedureStepType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quality Control summary: Information on possible errors or on the quality of a data set. description: The qualityControl field provides a location for the description of actions taken to either control or assess the quality of data resulting from the associated method step. A quality control description should identify a quality goal and describe prescriptive steps taken to ensure that the data meet those standards and/or postscriptive steps taken to assess the extent to which they are met. A quality control statement is associated with the methodStep that could have affected the targeted quality goal.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="ProcedureStepType">
- <xs:sequence>
- <xs:sequence>
- <xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Methods description summary: Description of the methods employed in collecting or generating a data set or other resource or in quality control and assurance. description: The description field allows for repeated text that describes the methodology for a project, experiment, or particular data table or to describe the steps taken to control or assure the quality of the data. Likewise, a literature citation may be provided that describes the methodology that was employed. Or the information my be provided by either referencing a protocol resource or entering the structured protocol information example: 1.Collect tissues from algae of interest. a. We are currently collecting Egregia menziezii, Mazzaella splendens, M. flaccida, Hedophyllum sessile, Postelsia palmaeformis and Fucus gardneri.We stopped collecting Neorhodomela larix and Odonthalia floccosa because they can be heavily fouled and we feared that would skew the results. b. We collect a 7-10 cm blade or branch from each plant. For Egregia, try to sample small, young plants or take the base of the blade. For Postelsia, take a few of the blades. The other plants are small enough so a whole blade can be taken.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice minOccurs="0" maxOccurs="unbounded">
- <xs:element name="citation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: Literature citation relating to the methods used. description: The citation field allows to either reference a literature resource or enter structured literature information</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="protocol" type="pro:ProtocolType">
- <xs:annotation>
- <xs:documentation>tooltip: Protocol summary: Protocol description relating to the methods used. description: The protocol field is used to either reference a protocol resource or describe methods and identify the processes that have been used to define / improve the quality of a data file, also used to identify potential problems with the data file.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- <xs:element name="instrumentation" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Instrumentation summary: Instruments used for measurement and recording data. description: The Instrumentation field allows the description of any instruments used in the data collection or quality control and quality assurance. The description should include vendor, model number, optional equipment, etc. example: LACHAT analyzer, model XYX.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="software" type="sw:SoftwareType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Software summary: Software used in the processing of data. description: The software element allows reference to any software used to process data.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="subStep" type="ProcedureStepType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: substep summary: description: This fields allows the nesting of additional method steps within this step. This is useful for hierarchical method descriptions.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:element name="individualName" type="Person">
- <xs:annotation>
- <xs:documentation>tooltip: Individual Name summary: The full name of the person being described description: The individualName field contains subfields so that a person's name can be broken down into parts. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation. example: Because this is an 'elementOnly' field, please look at the examples for the subfields 'givenName' and 'surName'.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -860,25 +794,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="salutation" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Salutation summary: The salutation used to address an individual description: The salutation field is used in addressing an individual with a particular title, such as Dr., Ms., Mrs., Mr., etc. example: Dr.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1037,25 +952,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="givenName" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Given name summary: The given name of the individual. description: The given name field can be used for first name of the individual associated with the resource, or for any other names that are not intended to be alphabetized, (as appropriate). Note that while it is possible to include all given names in one field (as in the example below), it may be not be good practice to do so. For example, if an XSL transformation stylesheet were to abbreviate the content of a givenName to just the first initial, a givenName element that contained more than one name would not be transformed correctly. example: Juan Luis example: Jane</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1204,25 +1100,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="surName" type="res:i18nNonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Last name summary: The last name of the individual. description: The surname field is used for the last name of the individual associated with the resource. This is typically the family name of an individual, for example, the name by which s/he is referred to in citations. example: San Gil example: Curtis-Ainsworth example: Tao</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1389,25 +1266,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="organizationName" type="res:i18nNonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Organization name summary: The full name of the organization being described description: The responsible party field contains the full name of the organization that is associated with the resource. This field is intended to describe which institution or overall organization is associated with the resource being described. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation. example: National Center for Ecological Analysis and Synthesis</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1572,25 +1430,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="positionName" type="res:i18nNonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Position Name summary: The name of the title or position associated with the resource. description: This field is intended to be used instead of a particular person or full organization name. If the associated person who holds the role changes frequently, then Position Name would be used for consistency. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation. example: Niwot Ridge Data Manager</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1773,25 +1612,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="address" type="Address" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Contact address summary: The full address information for a given responsible party entry. description: The address field is a container for multiple subfields that describe the physical or electronic address of the responsible party for a resource. example: Please see the subfield examples.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1944,25 +1764,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="deliveryPoint" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Delivery point summary: The location for postal deliveries. description: The delivery point field is used for the physical address for postal communication. This field is used to accommodate the many different international conventions that are the equivalent to a U.S. 'street address'. example: 7209 Coast Drive, Building 44</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2109,25 +1910,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="city" type="res:i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: City summary: The name of the city for the contact. description: The city field is used for the city name of the contact associated with a particular resource. example: San Francisco</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2276,25 +2058,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="administrativeArea" type="res:i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Administrative area summary: The political area of a country. description: The administrative area field is the equivalent of a 'state' in the U.S., or Province in Canada. This field is intended to accommodate the many types of international administrative areas. example: Colorado</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2444,25 +2207,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="postalCode" type="res:i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Postal code summary: The postal code used for routing to an address. description: The postal code is equivalent to a U.S. zip code, or the number used for routing to an international address. The U.S. postal code should include the 5 digit code plus the 4 digit extension. example: 93106-2231</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2610,25 +2354,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="country" type="res:i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Country summary: The name of the country for the contact's address. description: The country field is used for the name of the contact's country. example: U.S.A.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2764,36 +2489,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="phone" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Phone summary: Information about the contact's telephone description: The phone field describes information about the responsible party's telephone, be it a voice phone, fax, or TTD/TTY type telephone. This field contains an attribute used to identify the type. example: 805-555-2500</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="phonetype" type="xs:string" use="optional" default="voice">
- <xs:annotation>
- <xs:documentation>tooltip: Phone type summary: The type of the phone to which this number applies description: This attribute gives the type of phone to which this number applies. By default, this is assumed to be of type "voice", but other possibilities include "facsimile" and "tdd".</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2947,25 +2642,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="electronicMailAddress" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Email address summary: The email address of the contact. description: The electronic mail address is the email address for the party. It is intended to be an Internet SMTP email address, which should consist of a username followed by the @ symbol, followed by the email server domain name address. Other address types are allowable. example: my-email@mydomain.edu</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3058,25 +2734,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="onlineUrl" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Online Link summary: A link to associated online information, usually a web site. description: A link to associated online information, usually a web site. When the party represents an organization, this is the URL to a website or other online information about the organization. If the party is an individual, it might be their personal web site or other related online information about the party. example: http://www.yourdomain.edu/~doe</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3223,36 +2880,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="userId" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: User Identifier summary: An identifier that links this party to a directory of individuals description: An identifier that links this party to a directory of individuals. Although specific contact information for a party might change, the underlying correspondence to a real individual does not. This identifier provides a pointer within a directory of individuals that may contain further, and possibly more current, information about the party. example: https://orcid.org/0000-0002-1825-0097 example: uid=jtown,o=NCEAS,dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="directory" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Directory summary: The directory system within which the directoryId can be retrieved. description: This attribute names the directory system to which this userId applies. This will generally be a URL that shows how to look up information, for example an LDAP URL. However, it could also be a non-parsable description of the directory system if that is all that is available. example: https://orcid.org example: ldap:///ldap.ecoinformatics.org/dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3434,25 +3061,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="party" type="ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Responsible party summary: An individual, organization, or role. description: The responsible party contains multiple subfields that are used to describe a person, organization, or position within an organization. It is intended to be used to fully document contact information for many types of associations, such as owner, manager, steward, curator, etc.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="ResponsibleParty">
- <xs:annotation>
- <xs:documentation>tooltip: Responsible party summary: The individual, organization, or role associated with a resource. description: The ResponsibleParty Type contains elements that are used to describe the person, organization or position within an organization that is associated in some way with the resource. It is intended to be used to fully document contact information for many types of associations, such as owner, manager, steward, curator, etc. Note that the content model for a responsible party type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation. example: Please see the examples for the particular subfields.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="individualName" type="Person">
- <xs:annotation>
- <xs:documentation>tooltip: Individual Name summary: The full name of the person being described description: The individualName field contains subfields so that a person's name can be broken down into parts. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation. example: Because this is an 'elementOnly' field, please look at the examples for the subfields 'givenName' and 'surName'.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="organizationName" type="res:i18nNonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Organization name summary: The full name of the organization being described description: The responsible party field contains the full name of the organization that is associated with the resource. This field is intended to describe which institution or overall organization is associated with the resource being described. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation. example: National Center for Ecological Analysis and Synthesis</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="positionName" type="res:i18nNonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Position Name summary: The name of the title or position associated with the resource. description: This field is intended to be used instead of a particular person or full organization name. If the associated person who holds the role changes frequently, then Position Name would be used for consistency. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation. example: Niwot Ridge Data Manager</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:element name="address" type="Address" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Contact address summary: The full address information for a given responsible party entry. description: The address field is a container for multiple subfields that describe the physical or electronic address of the responsible party for a resource. example: Please see the subfield examples.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="phone" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Phone summary: Information about the contact's telephone description: The phone field describes information about the responsible party's telephone, be it a voice phone, fax, or TTD/TTY type telephone. This field contains an attribute used to identify the type. example: 805-555-2500</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="phonetype" type="xs:string" use="optional" default="voice">
- <xs:annotation>
- <xs:documentation>tooltip: Phone type summary: The type of the phone to which this number applies description: This attribute gives the type of phone to which this number applies. By default, this is assumed to be of type "voice", but other possibilities include "facsimile" and "tdd".</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="electronicMailAddress" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Email address summary: The email address of the contact. description: The electronic mail address is the email address for the party. It is intended to be an Internet SMTP email address, which should consist of a username followed by the @ symbol, followed by the email server domain name address. Other address types are allowable. example: my-email@mydomain.edu</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="onlineUrl" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Online Link summary: A link to associated online information, usually a web site. description: A link to associated online information, usually a web site. When the party represents an organization, this is the URL to a website or other online information about the organization. If the party is an individual, it might be their personal web site or other related online information about the party. example: http://www.yourdomain.edu/~doe</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="userId" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: User Identifier summary: An identifier that links this party to a directory of individuals description: An identifier that links this party to a directory of individuals. Although specific contact information for a party might change, the underlying correspondence to a real individual does not. This identifier provides a pointer within a directory of individuals that may contain further, and possibly more current, information about the party. example: https://orcid.org/0000-0002-1825-0097 example: uid=jtown,o=NCEAS,dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="directory" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Directory summary: The directory system within which the directoryId can be retrieved. description: This attribute names the directory system to which this userId applies. This will generally be a URL that shows how to look up information, for example an LDAP URL. However, it could also be a non-parsable description of the directory system if that is all that is available. example: https://orcid.org example: ldap:///ldap.ecoinformatics.org/dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="Person">
- <xs:annotation>
- <xs:documentation>tooltip: Person summary: The full name of the individual associated with the resource. description: The person Type is used to enter the salutation, and two types of name parts for an individual associated with the resource. It uses these three subfields to help parse the person's entire name. The two elements, <givenName> and <surName>, allow parsing of many types of names, even though distinct elements do not exist for concepts like "middle name" and "compound surname". <givenName> should be used for parts of the name that are often shortened to a first initial, or are not used for ordering, and typically includes first and middle names. The <surName> field is intended to be used for the part of the name that is generally displayed in its entirety and/or is alphabetized or otherwise ordered when appropriate. Note that only one <surName> is allowed, and is required, while <givenName>s are optional and unbounded. The arrangement and content of the sub-elements is entirely up to the EML document's author, who presumably has first-hand knowledge of how the names are to be constructed. For example, if element position is important (e.g., the list of a book's authors), then EML authors should put the creators in that order. If it is appropriate for a resource to have its creators sorted alphabetically, then the EML author should construct the name parts so that the<surName> field may be used for this purpose. At this time, EML is not able to express cultural conventions so that authors may indicate the correct order for <givenName>s and <surName> when the whole name is expressed. However support for international names is under consideration for a future version of EML, along with other internationalization features. example: Please see the examples within each subfield.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="salutation" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Salutation summary: The salutation used to address an individual description: The salutation field is used in addressing an individual with a particular title, such as Dr., Ms., Mrs., Mr., etc. example: Dr.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="givenName" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Given name summary: The given name of the individual. description: The given name field can be used for first name of the individual associated with the resource, or for any other names that are not intended to be alphabetized, (as appropriate). Note that while it is possible to include all given names in one field (as in the example below), it may be not be good practice to do so. For example, if an XSL transformation stylesheet were to abbreviate the content of a givenName to just the first initial, a givenName element that contained more than one name would not be transformed correctly. example: Juan Luis example: Jane</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="surName" type="res:i18nNonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Last name summary: The last name of the individual. description: The surname field is used for the last name of the individual associated with the resource. This is typically the family name of an individual, for example, the name by which s/he is referred to in citations. example: San Gil example: Curtis-Ainsworth example: Tao</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="Address">
- <xs:annotation>
- <xs:documentation>tooltip: Address summary: The full address of the resposible party. description: The address field is provides detailed information for communicating with a party contact via electronic mail or postal mail, including the physical delivery location. example: Please see the examples for each subfield</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="deliveryPoint" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Delivery point summary: The location for postal deliveries. description: The delivery point field is used for the physical address for postal communication. This field is used to accommodate the many different international conventions that are the equivalent to a U.S. 'street address'. example: 7209 Coast Drive, Building 44</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="city" type="res:i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: City summary: The name of the city for the contact. description: The city field is used for the city name of the contact associated with a particular resource. example: San Francisco</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="administrativeArea" type="res:i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Administrative area summary: The political area of a country. description: The administrative area field is the equivalent of a 'state' in the U.S., or Province in Canada. This field is intended to accommodate the many types of international administrative areas. example: Colorado</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="postalCode" type="res:i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Postal code summary: The postal code used for routing to an address. description: The postal code is equivalent to a U.S. zip code, or the number used for routing to an international address. The U.S. postal code should include the 5 digit code plus the 4 digit extension. example: 93106-2231</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="country" type="res:i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Country summary: The name of the country for the contact's address. description: The country field is used for the name of the contact's country. example: U.S.A.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:simpleType name="RoleType">
- <xs:annotation>
- <xs:documentation>tooltip: Role summary: The classification of the associated person or organization. description: The role code field provides information on how a person or organization is related to a resource. There may be many people associated, including an 'originator' of a dataset, an 'author', 'editor', or 'publisher' of a literature resource, or an organization that is a 'distributor'. the full list of choices is included in the example. example: author, contentProvider, custodianSteward, distributor, editor, metadataProvider, originator, pointOfContact, principalInvestigator, processor, publisher, or user.</xs:documentation>
- </xs:annotation>
- <xs:union>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="contentProvider"/>
- <xs:enumeration value="custodianSteward"/>
- <xs:enumeration value="owner"/>
- <xs:enumeration value="user"/>
- <xs:enumeration value="distributor"/>
- <xs:enumeration value="metadataProvider"/>
- <xs:enumeration value="originator"/>
- <xs:enumeration value="pointOfContact"/>
- <xs:enumeration value="principalInvestigator"/>
- <xs:enumeration value="processor"/>
- <xs:enumeration value="publisher"/>
- <xs:enumeration value="author"/>
- <xs:enumeration value="editor"/>
- </xs:restriction>
- </xs:simpleType>
- <xs:simpleType>
- <xs:restriction base="xs:string"/>
- </xs:simpleType>
- </xs:union>
-</xs:simpleType>
<xs:attribute name="phonetype" type="xs:string" use="optional" default="voice">
- <xs:annotation>
- <xs:documentation>tooltip: Phone type summary: The type of the phone to which this number applies description: This attribute gives the type of phone to which this number applies. By default, this is assumed to be of type "voice", but other possibilities include "facsimile" and "tdd".</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="directory" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Directory summary: The directory system within which the directoryId can be retrieved. description: This attribute names the directory system to which this userId applies. This will generally be a URL that shows how to look up information, for example an LDAP URL. However, it could also be a non-parsable description of the directory system if that is all that is available. example: https://orcid.org example: ldap:///ldap.ecoinformatics.org/dc=ecoinformatics,dc=org</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:element name="online" type="PhysicalOnlineType">
- <xs:annotation>
- <xs:documentation>tooltip: online summary: online description: Information for a resource that is distributed online. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -958,25 +856,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="onlineDescription" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: onlineDescription summary: onlineDescription description: The onlineDescription element can hold a brief description of the content of the online element's online|offline|inline child. This description element could supply content for an html anchor tag.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1086,25 +965,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="url" type="res:UrlType">
- <xs:annotation>
- <xs:documentation>tooltip: url summary: url description: The URL of the resource that is available online. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1269,25 +1129,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="connection" type="res:ConnectionType">
- <xs:annotation>
- <xs:documentation>tooltip: connection summary: connection description: A connection to a resource that is available online. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1405,25 +1246,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="offline" type="res:OfflineType">
- <xs:annotation>
- <xs:documentation>tooltip: offline summary: offline description: Information for a resource that is distributed offline. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1514,25 +1336,6 @@
Showing:
ANY element from ANY namespace
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="inline" type="res:InlineType">
- <xs:annotation>
- <xs:documentation>tooltip: inline summary: inline description: Information for a resource that is distributed inline, i.e., along with the metadata. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1763,25 +1566,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="access" type="acc:AccessType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: access summary: access description: When this element occurs in a distribution module, it controls access only to the resource being described by the same distribution parent. Please see the Type definition for complete information on constructing an access tree.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1893,25 +1677,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="objectName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Data object name summary: The name of the data object. description: The name of the data object. This is possibly distinct from the entity name in that one physical object can contain multiple entities, even though that is not a recommended practice. The objectName often is the filename of a file in a file system or that is accessible on the network. example: rainfall-sev-2002-10.txt</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2044,36 +1809,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="size" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Data object size summary: Describes the physical size of the data object. description: This element contains information of the physical size of the entity, by default represented in bytes unless the unit attribute is provided to change the units. example: 134</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="unit" use="optional" default="byte">
- <xs:annotation>
- <xs:documentation>tooltip: Unit of measurement summary: Unit of measurement for the entity size, by default byte description: This element gives the unit of measurement for the size of the entity, and is by default a byte. example: byte</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2211,36 +1946,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="authentication" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Authentication value summary: A value, typically a checksum, used to authenticate that the bitstream delivered to the user is identical to the original. description: This element describes authentication procedures or techniques, typically by giving a checksum value for the object. The method used to compute the authentication value (e.g., MD5) is listed in the method attribute. example: f5b2177ea03aea73de12da81f896fe40</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="method" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Authentication method summary: The method used to calculate an authentication checksum. description: This element names the method used to calculate and authentication checksum that can be used to validate a bytestream. Typical checksum methods include MD5 and CRC. example: MD5</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2358,25 +2063,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="compressionMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Compression Method summary: Name of a compression method applied description: This element lists a compression method used to compress the object, such as zip, compress, etc. Compression and encoding methods must be listed in the order in which they were applied, so that decompression and decoding should occur in the reverse order of the listing. For example, if a file is compressed using zip and then encoded using MIME base64, the compression method would be listed first and the encoding method second. example: zip example: gzip example: compress</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2494,25 +2180,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="encodingMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Encoding Method summary: Name of a encoding method applied description: This element lists a encoding method used to encode the object, such as base64, BinHex, etc. Compression and encoding methods must be listed in the order in which they were applied, so that decompression and decoding should occur in the reverse order of the listing. For example, if a file is compressed using zip and then encoded using MIME base64, the compression method would be listed first and the encoding method second. example: base64 example: uuencode example: binhex</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2625,25 +2292,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="characterEncoding" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Character Encoding summary: Contains the name of the character encoding used for the data. description: This element contains the name of the character encoding. This is typically ASCII or UTF-8, or one of the other common encodings. example: UTF-8</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2756,282 +2404,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dataFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Data format summary: Describes the internal physical format of a data object. description: This element is the parent which is a CHOICE between four possible internal physical formats which describe the internal physical characteristics of the data object. Using this information the user should be able parse physical object to extract the entity and its attributes. Note that this is the format of the physical object itself.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="textFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Text Format summary: Description of a text formatted object description: Description of a text formatted object. The description includes detailed parsing instructions for extracting attributes from the bytestream for simple delimited file formats (e.g., CSV), fixed format files that use fixed columns for attribute locations, and mixtures of the two. It also supports records that span multiple lines.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="numHeaderLines" type="xs:int" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of header lines summary: Number of header lines preceding data. description: Number of header lines preceding data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of header lines that should be skipped before starting to parse the data. example: 4</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numFooterLines" type="xs:int" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of footer lines summary: Number of footer lines following data. description: Number of footer lines following data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of footer lines that should be skipped after parsing the data. If this value is omitted, parsers should assume the data continues to the end of the data stream. example: 4</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="recordDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Record delimiter character summary: Character used to delimit records. description: This element specifies the record delimiter character when the format is text. The record delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As record delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). example: \n\r</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="physicalLineDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Physical line delimiter character summary: Character used to delimit physical lines. description: This element specifies the physical line delimiter character when the format is text. The line delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As line delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). If this value is not provided, processors should assume that the physical line delimiter is the same as the record delimiter. example: \n\r</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numPhysicalLinesPerRecord" type="xs:unsignedInt" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical lines per record summary: The number of physical lines in the file spanned by a single logical data record. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, it is necessary to know the number of lines per record in order to correctly read them. If this value is not provided, processors should assume that records are wholly contained on one physical line. If the value is greater than 1, then processors should examine the lineNumber field for each attribute to determine which line of the record contains the information. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="maxRecordLength" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum record length summary: The maximum number of characters in any record in the physical file. description: The maximum number of characters in any record in the physical file. For delimited files, the record length varies and this is not particularly useful. However, for fixed format files that do not contain record delimiters, this field is critical to tell processors when one record stops and another begins. example: 597</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="attributeOrientation">
- <xs:annotation>
- <xs:documentation>tooltip: Orientation of attributes summary: Orientation of attributes. description: Specifies whether the attributes described in the physical stream are found in columns or rows. The valid values are column or row. If set to 'column', then the attributes are in columns. If set to 'row', then the attributes are in rows. Row orientation is rare, but some systems such as SPlus and R utilize it. For example, some data with column orientation: DATE PLOT SPECIES 2002-01-15 hfr5 acer rubrum 2002-01-15 hfr5 acer xxxx The same data in a rowMajor table: DATE 2002-01-15 PLOT hfr5 SPECIES acer rubrum acer xxxx example: column example: row</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="column"/>
- <xs:enumeration value="row"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:choice>
- <xs:element name="simpleDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Simple delimited format summary: A simple delimited format. description: A simple delimited format that uses one of a series of delimiters to indicate the ends of fields in the data stream. More complex formats such as fixed format or mixed delimited and fixed formats can be described using the "complex" element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="complex">
- <xs:annotation>
- <xs:documentation>tooltip: Complex text format summary: A complex text format. description: A complex text format that can describe delimited fields, fixed width fields, and mixtures of the two. This supports multiline records (where one record is distributed across multiple physical lines). When using the complex format, the number of textFixed and textDelimited elements should exactly equal the number of attributes that have been described for the entity, and the order of the textFixed and textDelimited elements should correspond to the order of the attributes as described in the entity. Thus, for a delimited file with fourteen attributes, one should provide exactly fourteen textDelimited elements.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="textFixed">
- <xs:annotation>
- <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldWidth" type="xs:unsignedLong">
- <xs:annotation>
- <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. example: 7</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: 58</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="textDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="externallyDefinedFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Externally Defined Format summary: Information about a non-text or proprietary formatted object. description: Information about a non-text or proprietary formatted object. The description names the format explicitly, but assumes a processor implicitly knows how to parse that format to extract the data. A format version can be included. This is mainly used for proprietary formats, including binary files like Microsoft Excel and text formats like ESRI's ArcInfo export format. This is not a recommended way to permanently archive data because the software to parse the format is unlikely to be available over extended periods, but is included to allow for commonly used physical formats.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="formatName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Format Name summary: Name of the format of the data object description: Name of the format of the data object example: Microsoft Excel</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="formatVersion" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Format Version summary: Version of the format of the data object description: Version of the format of the data object example: 2000 (9.0.2720)</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Format citation summary: Citation providing more details about the physical format. description: Citation providing more detail about the physical format, including parsing information or information about the software required for reading the object.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="binaryRasterFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Raster image format summary: Contains binary raster data header parameters description: The binaryRasterInfo element is a container for various parameters used to described the contents of binary raster image files. In this case, it is based on a white paper on the ESRI site that describes the header information used for BIP and BIL files ("Extendable Image Formats for ArcView GIS 3.1 and 3.2").</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="rowColumnOrientation">
- <xs:annotation>
- <xs:documentation>tooltip: Orientation for reading rows and columns summary: Orientation for reading rows and columns. description: Specifies whether the data should be read across rows or down columns. The valid values are column or row. If set to 'column', then the data are read down columns. If set to 'row', then the data are read across rows. example: column example: row</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="column"/>
- <xs:enumeration value="row"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="multiBand" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Multiple band image summary: Multiple band image information. description: Information needed to properly interpret a multiband image.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nbands" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1. example: 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="layout" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential. example: bil example: bip example: bsq</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="nbits" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bits summary: The number of bits per pixel per band. description: The number of bits per pixel per band. Acceptable values are typically 1, 4, 8, 16, and 32. The default value is eight bits per pixel per band. For a true color image with three bands (R, G, B) stored using eight bits for each pixel in each band, nbits equals eight and nbands equals three, for a total of twenty-four bits per pixel. example: 8</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="byteorder" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Byte Order summary: The byte order in which values are stored. description: The byte order in which values are stored. The byte order is important for sixteen-bit and higher images, that have two or more bytes per pixel. Acceptable values are little-endian (common on Intel systems like PCs) and big-endian (common on Motorola platforms). example: little-endian example: big-endian</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="skipbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Skip Bytes summary: The number of bytes of data in the image file to skip in order to reach the start of the image data. description: The number of bytes of data in the image file to skip in order to reach the start of the image data. This keyword allows you to bypass any existing image header information in the file. The default value is zero bytes. example: 0</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bandrowbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bytes per band per row summary: The number of bytes per band per row. description: The number of bytes per band per row. This must be an integer. This keyword is used only with BIL files when there are extra bits at the end of each band within a row that must be skipped. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalrowbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total bytes of data per row summary: The total number of bytes of data per row. description: The total number of bytes of data per row. Use totalrowbytes when there are extra trailing bits at the end of each row. example: 8</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bandgapbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bytes between bands summary: The number of bytes between bands in a BSQ format image. description: The number of bytes between bands in a BSQ format image. The default is zero. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3157,180 +2529,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="textFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Text Format summary: Description of a text formatted object description: Description of a text formatted object. The description includes detailed parsing instructions for extracting attributes from the bytestream for simple delimited file formats (e.g., CSV), fixed format files that use fixed columns for attribute locations, and mixtures of the two. It also supports records that span multiple lines.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="numHeaderLines" type="xs:int" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of header lines summary: Number of header lines preceding data. description: Number of header lines preceding data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of header lines that should be skipped before starting to parse the data. example: 4</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numFooterLines" type="xs:int" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of footer lines summary: Number of footer lines following data. description: Number of footer lines following data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of footer lines that should be skipped after parsing the data. If this value is omitted, parsers should assume the data continues to the end of the data stream. example: 4</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="recordDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Record delimiter character summary: Character used to delimit records. description: This element specifies the record delimiter character when the format is text. The record delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As record delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). example: \n\r</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="physicalLineDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Physical line delimiter character summary: Character used to delimit physical lines. description: This element specifies the physical line delimiter character when the format is text. The line delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As line delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). If this value is not provided, processors should assume that the physical line delimiter is the same as the record delimiter. example: \n\r</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numPhysicalLinesPerRecord" type="xs:unsignedInt" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical lines per record summary: The number of physical lines in the file spanned by a single logical data record. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, it is necessary to know the number of lines per record in order to correctly read them. If this value is not provided, processors should assume that records are wholly contained on one physical line. If the value is greater than 1, then processors should examine the lineNumber field for each attribute to determine which line of the record contains the information. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="maxRecordLength" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum record length summary: The maximum number of characters in any record in the physical file. description: The maximum number of characters in any record in the physical file. For delimited files, the record length varies and this is not particularly useful. However, for fixed format files that do not contain record delimiters, this field is critical to tell processors when one record stops and another begins. example: 597</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="attributeOrientation">
- <xs:annotation>
- <xs:documentation>tooltip: Orientation of attributes summary: Orientation of attributes. description: Specifies whether the attributes described in the physical stream are found in columns or rows. The valid values are column or row. If set to 'column', then the attributes are in columns. If set to 'row', then the attributes are in rows. Row orientation is rare, but some systems such as SPlus and R utilize it. For example, some data with column orientation: DATE PLOT SPECIES 2002-01-15 hfr5 acer rubrum 2002-01-15 hfr5 acer xxxx The same data in a rowMajor table: DATE 2002-01-15 PLOT hfr5 SPECIES acer rubrum acer xxxx example: column example: row</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="column"/>
- <xs:enumeration value="row"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:choice>
- <xs:element name="simpleDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Simple delimited format summary: A simple delimited format. description: A simple delimited format that uses one of a series of delimiters to indicate the ends of fields in the data stream. More complex formats such as fixed format or mixed delimited and fixed formats can be described using the "complex" element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="complex">
- <xs:annotation>
- <xs:documentation>tooltip: Complex text format summary: A complex text format. description: A complex text format that can describe delimited fields, fixed width fields, and mixtures of the two. This supports multiline records (where one record is distributed across multiple physical lines). When using the complex format, the number of textFixed and textDelimited elements should exactly equal the number of attributes that have been described for the entity, and the order of the textFixed and textDelimited elements should correspond to the order of the attributes as described in the entity. Thus, for a delimited file with fourteen attributes, one should provide exactly fourteen textDelimited elements.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="textFixed">
- <xs:annotation>
- <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldWidth" type="xs:unsignedLong">
- <xs:annotation>
- <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. example: 7</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: 58</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="textDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3420,25 +2618,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="numHeaderLines" type="xs:int" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of header lines summary: Number of header lines preceding data. description: Number of header lines preceding data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of header lines that should be skipped before starting to parse the data. example: 4</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3529,25 +2708,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="numFooterLines" type="xs:int" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of footer lines summary: Number of footer lines following data. description: Number of footer lines following data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of footer lines that should be skipped after parsing the data. If this value is omitted, parsers should assume the data continues to the end of the data stream. example: 4</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3647,25 +2807,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="recordDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Record delimiter character summary: Character used to delimit records. description: This element specifies the record delimiter character when the format is text. The record delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As record delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). example: \n\r</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3769,25 +2910,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="physicalLineDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Physical line delimiter character summary: Character used to delimit physical lines. description: This element specifies the physical line delimiter character when the format is text. The line delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As line delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). If this value is not provided, processors should assume that the physical line delimiter is the same as the record delimiter. example: \n\r</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3881,25 +3003,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="numPhysicalLinesPerRecord" type="xs:unsignedInt" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical lines per record summary: The number of physical lines in the file spanned by a single logical data record. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, it is necessary to know the number of lines per record in order to correctly read them. If this value is not provided, processors should assume that records are wholly contained on one physical line. If the value is greater than 1, then processors should examine the lineNumber field for each attribute to determine which line of the record contains the information. example: 3</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3990,25 +3093,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="maxRecordLength" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum record length summary: The maximum number of characters in any record in the physical file. description: The maximum number of characters in any record in the physical file. For delimited files, the record length varies and this is not particularly useful. However, for fixed format files that do not contain record delimiters, this field is critical to tell processors when one record stops and another begins. example: 597</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4132,31 +3216,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeOrientation">
- <xs:annotation>
- <xs:documentation>tooltip: Orientation of attributes summary: Orientation of attributes. description: Specifies whether the attributes described in the physical stream are found in columns or rows. The valid values are column or row. If set to 'column', then the attributes are in columns. If set to 'row', then the attributes are in rows. Row orientation is rare, but some systems such as SPlus and R utilize it. For example, some data with column orientation: DATE PLOT SPECIES 2002-01-15 hfr5 acer rubrum 2002-01-15 hfr5 acer xxxx The same data in a rowMajor table: DATE 2002-01-15 PLOT hfr5 SPECIES acer rubrum acer xxxx example: column example: row</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="column"/>
- <xs:enumeration value="row"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -4271,55 +3330,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="simpleDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Simple delimited format summary: A simple delimited format. description: A simple delimited format that uses one of a series of delimiters to indicate the ends of fields in the data stream. More complex formats such as fixed format or mixed delimited and fixed formats can be described using the "complex" element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -4432,25 +3442,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4580,31 +3571,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -4735,25 +3701,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4877,25 +3824,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5014,93 +3942,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="complex">
- <xs:annotation>
- <xs:documentation>tooltip: Complex text format summary: A complex text format. description: A complex text format that can describe delimited fields, fixed width fields, and mixtures of the two. This supports multiline records (where one record is distributed across multiple physical lines). When using the complex format, the number of textFixed and textDelimited elements should exactly equal the number of attributes that have been described for the entity, and the order of the textFixed and textDelimited elements should correspond to the order of the attributes as described in the entity. Thus, for a delimited file with fourteen attributes, one should provide exactly fourteen textDelimited elements.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="textFixed">
- <xs:annotation>
- <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldWidth" type="xs:unsignedLong">
- <xs:annotation>
- <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. example: 7</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: 58</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="textDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -5220,44 +4061,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="textFixed">
- <xs:annotation>
- <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldWidth" type="xs:unsignedLong">
- <xs:annotation>
- <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. example: 7</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: 58</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -5342,25 +4145,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="fieldWidth" type="xs:unsignedLong">
- <xs:annotation>
- <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. example: 7</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5459,25 +4243,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record. example: 3</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5575,25 +4340,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: 58</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5714,60 +4460,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="textDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -5881,25 +4573,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="fieldDelimiter" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6031,31 +4704,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -6160,25 +4808,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter. example: 3</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6314,25 +4943,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6460,25 +5070,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6597,44 +5188,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="externallyDefinedFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Externally Defined Format summary: Information about a non-text or proprietary formatted object. description: Information about a non-text or proprietary formatted object. The description names the format explicitly, but assumes a processor implicitly knows how to parse that format to extract the data. A format version can be included. This is mainly used for proprietary formats, including binary files like Microsoft Excel and text formats like ESRI's ArcInfo export format. This is not a recommended way to permanently archive data because the software to parse the format is unlikely to be available over extended periods, but is included to allow for commonly used physical formats.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="formatName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Format Name summary: Name of the format of the data object description: Name of the format of the data object example: Microsoft Excel</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="formatVersion" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Format Version summary: Version of the format of the data object description: Version of the format of the data object example: 2000 (9.0.2720)</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Format citation summary: Citation providing more details about the physical format. description: Citation providing more detail about the physical format, including parsing information or information about the software required for reading the object.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -6742,25 +5295,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="formatName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Format Name summary: Name of the format of the data object description: Name of the format of the data object example: Microsoft Excel</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6872,25 +5406,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="formatVersion" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Format Version summary: Version of the format of the data object description: Version of the format of the data object example: 2000 (9.0.2720)</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7124,25 +5639,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Format citation summary: Citation providing more details about the physical format. description: Citation providing more detail about the physical format, including parsing information or information about the software required for reading the object.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7265,89 +5761,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="binaryRasterFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Raster image format summary: Contains binary raster data header parameters description: The binaryRasterInfo element is a container for various parameters used to described the contents of binary raster image files. In this case, it is based on a white paper on the ESRI site that describes the header information used for BIP and BIL files ("Extendable Image Formats for ArcView GIS 3.1 and 3.2").</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="rowColumnOrientation">
- <xs:annotation>
- <xs:documentation>tooltip: Orientation for reading rows and columns summary: Orientation for reading rows and columns. description: Specifies whether the data should be read across rows or down columns. The valid values are column or row. If set to 'column', then the data are read down columns. If set to 'row', then the data are read across rows. example: column example: row</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="column"/>
- <xs:enumeration value="row"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="multiBand" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Multiple band image summary: Multiple band image information. description: Information needed to properly interpret a multiband image.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nbands" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1. example: 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="layout" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential. example: bil example: bip example: bsq</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="nbits" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bits summary: The number of bits per pixel per band. description: The number of bits per pixel per band. Acceptable values are typically 1, 4, 8, 16, and 32. The default value is eight bits per pixel per band. For a true color image with three bands (R, G, B) stored using eight bits for each pixel in each band, nbits equals eight and nbands equals three, for a total of twenty-four bits per pixel. example: 8</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="byteorder" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Byte Order summary: The byte order in which values are stored. description: The byte order in which values are stored. The byte order is important for sixteen-bit and higher images, that have two or more bytes per pixel. Acceptable values are little-endian (common on Intel systems like PCs) and big-endian (common on Motorola platforms). example: little-endian example: big-endian</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="skipbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Skip Bytes summary: The number of bytes of data in the image file to skip in order to reach the start of the image data. description: The number of bytes of data in the image file to skip in order to reach the start of the image data. This keyword allows you to bypass any existing image header information in the file. The default value is zero bytes. example: 0</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bandrowbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bytes per band per row summary: The number of bytes per band per row. description: The number of bytes per band per row. This must be an integer. This keyword is used only with BIL files when there are extra bits at the end of each band within a row that must be skipped. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalrowbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total bytes of data per row summary: The total number of bytes of data per row. description: The total number of bytes of data per row. Use totalrowbytes when there are extra trailing bits at the end of each row. example: 8</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bandgapbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bytes between bands summary: The number of bytes between bands in a BSQ format image. description: The number of bytes between bands in a BSQ format image. The default is zero. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -7460,31 +5873,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="rowColumnOrientation">
- <xs:annotation>
- <xs:documentation>tooltip: Orientation for reading rows and columns summary: Orientation for reading rows and columns. description: Specifies whether the data should be read across rows or down columns. The valid values are column or row. If set to 'column', then the data are read down columns. If set to 'row', then the data are read across rows. example: column example: row</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="column"/>
- <xs:enumeration value="row"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -7594,39 +5982,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="multiBand" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Multiple band image summary: Multiple band image information. description: Information needed to properly interpret a multiband image.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nbands" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1. example: 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="layout" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential. example: bil example: bip example: bsq</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -7708,25 +6063,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="nbands" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1. example: 2</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7842,25 +6178,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="layout" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential. example: bil example: bip example: bsq</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7947,25 +6264,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="nbits" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bits summary: The number of bits per pixel per band. description: The number of bits per pixel per band. Acceptable values are typically 1, 4, 8, 16, and 32. The default value is eight bits per pixel per band. For a true color image with three bands (R, G, B) stored using eight bits for each pixel in each band, nbits equals eight and nbands equals three, for a total of twenty-four bits per pixel. example: 8</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8080,25 +6378,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="byteorder" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Byte Order summary: The byte order in which values are stored. description: The byte order in which values are stored. The byte order is important for sixteen-bit and higher images, that have two or more bytes per pixel. Acceptable values are little-endian (common on Intel systems like PCs) and big-endian (common on Motorola platforms). example: little-endian example: big-endian</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8214,25 +6493,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="skipbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Skip Bytes summary: The number of bytes of data in the image file to skip in order to reach the start of the image data. description: The number of bytes of data in the image file to skip in order to reach the start of the image data. This keyword allows you to bypass any existing image header information in the file. The default value is zero bytes. example: 0</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8347,25 +6607,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="bandrowbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bytes per band per row summary: The number of bytes per band per row. description: The number of bytes per band per row. This must be an integer. This keyword is used only with BIL files when there are extra bits at the end of each band within a row that must be skipped. example: 3</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8479,25 +6720,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="totalrowbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total bytes of data per row summary: The total number of bytes of data per row. description: The total number of bytes of data per row. Use totalrowbytes when there are extra trailing bits at the end of each row. example: 8</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8610,25 +6832,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="bandgapbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bytes between bands summary: The number of bytes between bands in a BSQ format image. description: The number of bytes between bands in a BSQ format image. The default is zero. example: 1</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8808,25 +7011,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="distribution" type="PhysicalDistributionType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Distribution Information summary: Information on how the resource is distributed online and offline description: This element provides information on how the resource is distributed. Connections to online systems can be described as URLs or as a list of connection parameters. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -9008,25 +7192,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="physical" type="PhysicalType">
- <xs:annotation>
- <xs:documentation>tooltip: Physical structure summary: Physical structure of an entity or entities. description: The content model for physical is a CHOICE between "references" and all of the elements that let you describe the internal/external characteristics and distribution of a data object (e.g., dataObject, dataFormat, distribution.) A physical element can contain a reference to an physical element defined elsewhere. Using a reference means that the referenced physical is identical, not just in name but identical in its complete description.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="PhysicalDistributionType">
- <xs:annotation>
- <xs:documentation>tooltip: PhysicalDistributionType summary: PhysicalDistributionType description: The PhysicalDistributionType contains the information required for retrieving the resource. It differs from the res:DistributionType : Generally, the PhysicalDisribtutionType is intended for download whereas the Type at the resource level is intended primarily for information. The phys:PhysicalDistributionType includes an optional access tree which can be used to override access rules applied at the resource level. Access for the documents included entities can then be managed individually. Also see individual sub elements for more information.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:choice>
- <xs:element name="online" type="PhysicalOnlineType">
- <xs:annotation>
- <xs:documentation>tooltip: online summary: online description: Information for a resource that is distributed online. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="offline" type="res:OfflineType">
- <xs:annotation>
- <xs:documentation>tooltip: offline summary: offline description: Information for a resource that is distributed offline. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="inline" type="res:InlineType">
- <xs:annotation>
- <xs:documentation>tooltip: inline summary: inline description: Information for a resource that is distributed inline, i.e., along with the metadata. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:element name="access" type="acc:AccessType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: access summary: access description: When this element occurs in a distribution module, it controls access only to the resource being described by the same distribution parent. Please see the Type definition for complete information on constructing an access tree.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="PhysicalOnlineType">
- <xs:annotation>
- <xs:documentation>tooltip: PhysicalOnlineType summary: PhysicalOnlineType description: Distribution information for accessing the resource online, represented either as a URL or as the series of named parameters needed to connect. The URL field can contain a simple web address or an entire query string. The connection element allows the components of a complex protocol to be described individually. The PhysicalOnlineType differs from the res:OnlineType in that this type only allows a connectionDefinition to appear as the child of a connection. In other words, in a PhysicalOnlineType, the connectionDefinition cannot be abstracted, and must be included as part of an actual connection.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="onlineDescription" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: onlineDescription summary: onlineDescription description: The onlineDescription element can hold a brief description of the content of the online element's online|offline|inline child. This description element could supply content for an html anchor tag.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice>
- <xs:element name="url" type="res:UrlType">
- <xs:annotation>
- <xs:documentation>tooltip: url summary: url description: The URL of the resource that is available online. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="connection" type="res:ConnectionType">
- <xs:annotation>
- <xs:documentation>tooltip: connection summary: connection description: A connection to a resource that is available online. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="PhysicalType">
- <xs:annotation>
- <xs:documentation>tooltip: Physical structure summary: Physical structure of an entity or entities. description: The eml-physical module describes the physical characteristics of a data object and the information required for its distribution. External physical characteristics include the filename, size, compression, encoding methods, and authentication of a file or byte stream. Internal physical characteristics describe the format of the data object. Proprietary formats can be cited (e.g., Microsoft Access 2000), or text formats can be precisely described (e.g., ASCII text delimited with commas). The module includes the information needed to parse the text data object to extract the entity and its attributes. Distribution information describes how to retrieve the data object, either as online (a URL or connection definition), offline (e.g., a data object residing on an archival tape), or inline (i.e., the data are included with the metadata). Like many other EML elements, a physical Type can contain a reference to another physical element defined elsewhere in the document instead of a description of the resource. Using a reference means that the referenced physical is identical, not just in name but identical in its complete description.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="objectName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Data object name summary: The name of the data object. description: The name of the data object. This is possibly distinct from the entity name in that one physical object can contain multiple entities, even though that is not a recommended practice. The objectName often is the filename of a file in a file system or that is accessible on the network. example: rainfall-sev-2002-10.txt</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="size" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Data object size summary: Describes the physical size of the data object. description: This element contains information of the physical size of the entity, by default represented in bytes unless the unit attribute is provided to change the units. example: 134</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="unit" use="optional" default="byte">
- <xs:annotation>
- <xs:documentation>tooltip: Unit of measurement summary: Unit of measurement for the entity size, by default byte description: This element gives the unit of measurement for the size of the entity, and is by default a byte. example: byte</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="authentication" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Authentication value summary: A value, typically a checksum, used to authenticate that the bitstream delivered to the user is identical to the original. description: This element describes authentication procedures or techniques, typically by giving a checksum value for the object. The method used to compute the authentication value (e.g., MD5) is listed in the method attribute. example: f5b2177ea03aea73de12da81f896fe40</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="method" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Authentication method summary: The method used to calculate an authentication checksum. description: This element names the method used to calculate and authentication checksum that can be used to validate a bytestream. Typical checksum methods include MD5 and CRC. example: MD5</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:choice minOccurs="0" maxOccurs="unbounded">
- <xs:element name="compressionMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Compression Method summary: Name of a compression method applied description: This element lists a compression method used to compress the object, such as zip, compress, etc. Compression and encoding methods must be listed in the order in which they were applied, so that decompression and decoding should occur in the reverse order of the listing. For example, if a file is compressed using zip and then encoded using MIME base64, the compression method would be listed first and the encoding method second. example: zip example: gzip example: compress</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="encodingMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Encoding Method summary: Name of a encoding method applied description: This element lists a encoding method used to encode the object, such as base64, BinHex, etc. Compression and encoding methods must be listed in the order in which they were applied, so that decompression and decoding should occur in the reverse order of the listing. For example, if a file is compressed using zip and then encoded using MIME base64, the compression method would be listed first and the encoding method second. example: base64 example: uuencode example: binhex</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:element name="characterEncoding" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Character Encoding summary: Contains the name of the character encoding used for the data. description: This element contains the name of the character encoding. This is typically ASCII or UTF-8, or one of the other common encodings. example: UTF-8</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dataFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Data format summary: Describes the internal physical format of a data object. description: This element is the parent which is a CHOICE between four possible internal physical formats which describe the internal physical characteristics of the data object. Using this information the user should be able parse physical object to extract the entity and its attributes. Note that this is the format of the physical object itself.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="textFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Text Format summary: Description of a text formatted object description: Description of a text formatted object. The description includes detailed parsing instructions for extracting attributes from the bytestream for simple delimited file formats (e.g., CSV), fixed format files that use fixed columns for attribute locations, and mixtures of the two. It also supports records that span multiple lines.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="numHeaderLines" type="xs:int" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of header lines summary: Number of header lines preceding data. description: Number of header lines preceding data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of header lines that should be skipped before starting to parse the data. example: 4</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numFooterLines" type="xs:int" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Number of footer lines summary: Number of footer lines following data. description: Number of footer lines following data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of footer lines that should be skipped after parsing the data. If this value is omitted, parsers should assume the data continues to the end of the data stream. example: 4</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="recordDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Record delimiter character summary: Character used to delimit records. description: This element specifies the record delimiter character when the format is text. The record delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As record delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). example: \n\r</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="physicalLineDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Physical line delimiter character summary: Character used to delimit physical lines. description: This element specifies the physical line delimiter character when the format is text. The line delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As line delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). If this value is not provided, processors should assume that the physical line delimiter is the same as the record delimiter. example: \n\r</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numPhysicalLinesPerRecord" type="xs:unsignedInt" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical lines per record summary: The number of physical lines in the file spanned by a single logical data record. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, it is necessary to know the number of lines per record in order to correctly read them. If this value is not provided, processors should assume that records are wholly contained on one physical line. If the value is greater than 1, then processors should examine the lineNumber field for each attribute to determine which line of the record contains the information. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="maxRecordLength" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Maximum record length summary: The maximum number of characters in any record in the physical file. description: The maximum number of characters in any record in the physical file. For delimited files, the record length varies and this is not particularly useful. However, for fixed format files that do not contain record delimiters, this field is critical to tell processors when one record stops and another begins. example: 597</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="attributeOrientation">
- <xs:annotation>
- <xs:documentation>tooltip: Orientation of attributes summary: Orientation of attributes. description: Specifies whether the attributes described in the physical stream are found in columns or rows. The valid values are column or row. If set to 'column', then the attributes are in columns. If set to 'row', then the attributes are in rows. Row orientation is rare, but some systems such as SPlus and R utilize it. For example, some data with column orientation: DATE PLOT SPECIES 2002-01-15 hfr5 acer rubrum 2002-01-15 hfr5 acer xxxx The same data in a rowMajor table: DATE 2002-01-15 PLOT hfr5 SPECIES acer rubrum acer xxxx example: column example: row</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="column"/>
- <xs:enumeration value="row"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:choice>
- <xs:element name="simpleDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Simple delimited format summary: A simple delimited format. description: A simple delimited format that uses one of a series of delimiters to indicate the ends of fields in the data stream. More complex formats such as fixed format or mixed delimited and fixed formats can be described using the "complex" element.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="complex">
- <xs:annotation>
- <xs:documentation>tooltip: Complex text format summary: A complex text format. description: A complex text format that can describe delimited fields, fixed width fields, and mixtures of the two. This supports multiline records (where one record is distributed across multiple physical lines). When using the complex format, the number of textFixed and textDelimited elements should exactly equal the number of attributes that have been described for the entity, and the order of the textFixed and textDelimited elements should correspond to the order of the attributes as described in the entity. Thus, for a delimited file with fourteen attributes, one should provide exactly fourteen textDelimited elements.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="textFixed">
- <xs:annotation>
- <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldWidth" type="xs:unsignedLong">
- <xs:annotation>
- <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. example: 7</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: 58</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="textDelimited">
- <xs:annotation>
- <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="fieldDelimiter" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited. example: , example: \t example: 0x09 example: 0x20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="collapseDelimiters" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default. example: yes example: no</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="yes"/>
- <xs:enumeration value="no"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values. example: " example: '</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \. example: \</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="externallyDefinedFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Externally Defined Format summary: Information about a non-text or proprietary formatted object. description: Information about a non-text or proprietary formatted object. The description names the format explicitly, but assumes a processor implicitly knows how to parse that format to extract the data. A format version can be included. This is mainly used for proprietary formats, including binary files like Microsoft Excel and text formats like ESRI's ArcInfo export format. This is not a recommended way to permanently archive data because the software to parse the format is unlikely to be available over extended periods, but is included to allow for commonly used physical formats.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="formatName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Format Name summary: Name of the format of the data object description: Name of the format of the data object example: Microsoft Excel</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="formatVersion" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Format Version summary: Version of the format of the data object description: Version of the format of the data object example: 2000 (9.0.2720)</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Format citation summary: Citation providing more details about the physical format. description: Citation providing more detail about the physical format, including parsing information or information about the software required for reading the object.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="binaryRasterFormat">
- <xs:annotation>
- <xs:documentation>tooltip: Raster image format summary: Contains binary raster data header parameters description: The binaryRasterInfo element is a container for various parameters used to described the contents of binary raster image files. In this case, it is based on a white paper on the ESRI site that describes the header information used for BIP and BIL files ("Extendable Image Formats for ArcView GIS 3.1 and 3.2").</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="rowColumnOrientation">
- <xs:annotation>
- <xs:documentation>tooltip: Orientation for reading rows and columns summary: Orientation for reading rows and columns. description: Specifies whether the data should be read across rows or down columns. The valid values are column or row. If set to 'column', then the data are read down columns. If set to 'row', then the data are read across rows. example: column example: row</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="column"/>
- <xs:enumeration value="row"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="multiBand" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Multiple band image summary: Multiple band image information. description: Information needed to properly interpret a multiband image.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="nbands" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1. example: 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="layout" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential. example: bil example: bip example: bsq</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="nbits" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Number of Bits summary: The number of bits per pixel per band. description: The number of bits per pixel per band. Acceptable values are typically 1, 4, 8, 16, and 32. The default value is eight bits per pixel per band. For a true color image with three bands (R, G, B) stored using eight bits for each pixel in each band, nbits equals eight and nbands equals three, for a total of twenty-four bits per pixel. example: 8</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="byteorder" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Byte Order summary: The byte order in which values are stored. description: The byte order in which values are stored. The byte order is important for sixteen-bit and higher images, that have two or more bytes per pixel. Acceptable values are little-endian (common on Intel systems like PCs) and big-endian (common on Motorola platforms). example: little-endian example: big-endian</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="skipbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Skip Bytes summary: The number of bytes of data in the image file to skip in order to reach the start of the image data. description: The number of bytes of data in the image file to skip in order to reach the start of the image data. This keyword allows you to bypass any existing image header information in the file. The default value is zero bytes. example: 0</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bandrowbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bytes per band per row summary: The number of bytes per band per row. description: The number of bytes per band per row. This must be an integer. This keyword is used only with BIL files when there are extra bits at the end of each band within a row that must be skipped. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="totalrowbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Total bytes of data per row summary: The total number of bytes of data per row. description: The total number of bytes of data per row. Use totalrowbytes when there are extra trailing bits at the end of each row. example: 8</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bandgapbytes" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Bytes between bands summary: The number of bytes between bands in a BSQ format image. description: The number of bytes between bands in a BSQ format image. The default is zero. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="distribution" type="PhysicalDistributionType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Distribution Information summary: Information on how the resource is distributed online and offline description: This element provides information on how the resource is distributed. Connections to online systems can be described as URLs or as a list of connection parameters. Please see the Type definition for complete information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:attribute name="unit" use="optional" default="byte">
- <xs:annotation>
- <xs:documentation>tooltip: Unit of measurement summary: Unit of measurement for the entity size, by default byte description: This element gives the unit of measurement for the size of the entity, and is by default a byte. example: byte</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="method" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Authentication method summary: The method used to calculate an authentication checksum. description: This element names the method used to calculate and authentication checksum that can be used to validate a bytestream. Typical checksum methods include MD5 and CRC. example: MD5</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:element name="title" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Project Title summary: Title of the project. description: A descriptive title for the research project. example: Species diversity in Tennessee riparian habitats.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -882,38 +817,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="personnel" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Personnel summary: Contact and role information for people involved in the research project. description: The Personnel field extends ResponsibleParty with role information and is used to document people involved in a research project by providing contact information and their role in the project.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="rp:ResponsibleParty">
- <xs:sequence maxOccurs="unbounded">
- <xs:element name="role" type="rp:RoleType">
- <xs:annotation>
- <xs:documentation>tooltip: Role summary: Role information for people involved in the research project. description: The role field contains information about role a person plays in a research project. There are a number of suggested roles, however, it is possible to add a role if the suggested roles are not adequate. example: author example: contentProvider example: custodianSteward example: distributor example: editor example: metadataProvider example: originator example: owner example: pointOfContact example: principalInvestigator example: processor example: publisher example: user example: fieldStationManager example: informationManager</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1026,25 +929,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="role" type="rp:RoleType">
- <xs:annotation>
- <xs:documentation>tooltip: Role summary: Role information for people involved in the research project. description: The role field contains information about role a person plays in a research project. There are a number of suggested roles, however, it is possible to add a role if the suggested roles are not adequate. example: author example: contentProvider example: custodianSteward example: distributor example: editor example: metadataProvider example: originator example: owner example: pointOfContact example: principalInvestigator example: processor example: publisher example: user example: fieldStationManager example: informationManager</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1193,25 +1077,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="abstract" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Abstract summary: Project Abstract. description: Descriptive abstract that summarizes information about the research project.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1363,25 +1228,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="funding" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Funding summary: Funding information. description: The funding field is used to provide general information about the funding for a project, generally in prose form. This field is included for historical compatibility, and has been augmented by the award field that provides structured information about funding included.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1513,25 +1359,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="award" type="AwardType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Award information summary: Award information. description: The award field is used to provide specific information about the funding awards for a project in a structured format. Sub-fields are provided for the name of the funding agency, the Open Funder Registry identifiers for the agency and program that made the award, the award number assigned, the title of the award, and the URL to the award page describing the award. The award field replaces the earlier funding field from prior EML version releases. In general, the funding agency should be listed with a cross-reference to the appropriate identifier from the Open Funder Registry (included in the EML distribution, but which is also update periodically from the Open Funder Registry).</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1686,25 +1513,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="funderName" type="res:i18nNonEmptyStringType" minOccurs="1" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Funder Name summary: The name of the funding institution that made this award description: The name of the funding institution, with fully expanded acronyms to show the full, official name of the funding agency. In general, this should match the official name of the funder as listed in an Authority such as the Open Funder Registry. The Open Funder Registry and other organizational authorities may provide a list of other alternative names for the funding agency. example: National Science Foundation</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1864,25 +1672,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="funderIdentifier" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Funder identifier summary: The identifier of the funding agency. description: The funder identifier is used to provide one or more canonical identifiers that reference the funder. These identifiers should be globally unique. The most common form of a funder identifier is a DOI identifier of an institution or program drawn from the CrossRef Open Funder Registry (https://github.com/Crossref/open-funder-registry), which assigns DOIs to each funding agency and to their programs, and links these together in a navigable hierarchy. A copy of the current Funder Registry is included as an RDF file with EML for reference, but as the list is constantly growing, users can retrieve new copies of the RDF file to get updates and current metadata about funders. example: http://dx.doi.org/10.13039/100000001</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2038,25 +1827,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="awardNumber" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Award Number summary: The assigned award number. description: The awardNumber field provides the unique identifier used by the funder to uniquely identify an award. These are typically alphanumeric values that are unique within the system used by a given funder. The number should be listed using the canonical form that each funder uses to express its award numbers, and not be prefixed or postfixed with extra text such as the acronym of the funder or the name of the funder, which is available instead in the funderName field. example: 1546024</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2208,25 +1978,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="title" type="res:i18nNonEmptyStringType" minOccurs="1" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Title summary: The title of the award. description: The title field is used for the title of the award or grant being described. example: Scientia Arctica: A Knowledge Archive for Discovery and Reproducible Science in the Arctic</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2379,25 +2130,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="awardUrl" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Award URL summary: The URL associated with award. description: Typically, the awardUrl is use to find and locate the award, and generally addresses the internet location to find out more information about the award. This should point to a funder site for the award, rather than a project site. example: https://www.nsf.gov/awardsearch/showAward?AWD_ID=1546024</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2516,79 +2248,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="studyAreaDescription" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Description of the study area. summary: Description of the physical area associated with the research project, potentially including coverage, climate, geology, disturbances, etc. description: The studyAreaDescription field documents the physical area associated with the research project. It can include descriptions of the geographic, temporal, and taxonomic coverage of the research location and descriptions of domains (themes) of interest such as climate, geology, soils or disturbances or reference to citable biological or geophysical classification systems such as the Bailey Ecoregions or the Holdridge Life Zones.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="descriptor">
- <xs:annotation>
- <xs:documentation>tooltip: Non-coverage characteristics of the study area summary: Description of non-coverage characteristics of the study area such as climate, geology, disturbances description: The descriptor field is used to document domains (themes) of interest such as climate, geology, soils or disturbances or references to citable biological or geophysical classification systems such as the Bailey Ecoregions or the Holdridge Life Zones.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence maxOccurs="unbounded">
- <xs:element name="descriptorValue" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Description of some aspect of the study area. summary: Description of some aspect of the study area. description: The descriptorValue field contains the value of a descriptor, describing some aspect of the study area. This may either be a general description in textual form or the value part of a "name/value" pair where the name is entered in the attribute "name_or_id". For example, if the value of the "name" attribute" of the element "descriptor" is "climate", and the value of the attribute "name_or_id" of the element "descriptorValue" is "Annual Precipitation" then the value of this element could be "12.5 inches". example: 12.5 inches example: tundra-forest</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="name_or_id" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography". example: M131 example: Average Annual Rainfall</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: A citation for this descriptor. description: A citation for this descriptor.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="name" type="DescriptorType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: name summary: The name of the descriptor system. description: The name of the descriptor system. The name can be either a theme such as climate or hydrology, or the name of a citable classification system.</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="citableClassificationSystem" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: citation classification system summary: This boolean attribute defines whether this descriptor comes from a citable classification system or not. description: This boolean attribute defines whether this descriptor comes from a citable classification system or not.</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: The citation for this descriptor. description: The citation for this descriptor.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="coverage" type="cov:Coverage" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: coverage summary: The coverage of this descriptor. description: The coverage of this descriptor.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2766,60 +2425,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="descriptor">
- <xs:annotation>
- <xs:documentation>tooltip: Non-coverage characteristics of the study area summary: Description of non-coverage characteristics of the study area such as climate, geology, disturbances description: The descriptor field is used to document domains (themes) of interest such as climate, geology, soils or disturbances or references to citable biological or geophysical classification systems such as the Bailey Ecoregions or the Holdridge Life Zones.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence maxOccurs="unbounded">
- <xs:element name="descriptorValue" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Description of some aspect of the study area. summary: Description of some aspect of the study area. description: The descriptorValue field contains the value of a descriptor, describing some aspect of the study area. This may either be a general description in textual form or the value part of a "name/value" pair where the name is entered in the attribute "name_or_id". For example, if the value of the "name" attribute" of the element "descriptor" is "climate", and the value of the attribute "name_or_id" of the element "descriptorValue" is "Annual Precipitation" then the value of this element could be "12.5 inches". example: 12.5 inches example: tundra-forest</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="name_or_id" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography". example: M131 example: Average Annual Rainfall</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: A citation for this descriptor. description: A citation for this descriptor.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="name" type="DescriptorType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: name summary: The name of the descriptor system. description: The name of the descriptor system. The name can be either a theme such as climate or hydrology, or the name of a citable classification system.</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="citableClassificationSystem" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: citation classification system summary: This boolean attribute defines whether this descriptor comes from a citable classification system or not. description: This boolean attribute defines whether this descriptor comes from a citable classification system or not.</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2977,36 +2582,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="descriptorValue" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Description of some aspect of the study area. summary: Description of some aspect of the study area. description: The descriptorValue field contains the value of a descriptor, describing some aspect of the study area. This may either be a general description in textual form or the value part of a "name/value" pair where the name is entered in the attribute "name_or_id". For example, if the value of the "name" attribute" of the element "descriptor" is "climate", and the value of the attribute "name_or_id" of the element "descriptorValue" is "Annual Precipitation" then the value of this element could be "12.5 inches". example: 12.5 inches example: tundra-forest</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="name_or_id" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography". example: M131 example: Average Annual Rainfall</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3241,25 +2816,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: A citation for this descriptor. description: A citation for this descriptor.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3490,25 +3046,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: The citation for this descriptor. description: The citation for this descriptor.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3679,25 +3216,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="coverage" type="cov:Coverage" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: coverage summary: The coverage of this descriptor. description: The coverage of this descriptor.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3810,39 +3328,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="designDescription" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Description of research design summary: Description of the design of the research project description: The field designDescription contains general textual descriptions of research design. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work. Literature citations may also be used to describe the research design.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Description of research design summary: Textual description of research design. description: The field designDescription contains general textual descriptions of research design. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Citation for research design summary: Citation that describes the research design. description: The citation field is a citation to literature that describes elements of the research design, such as goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3991,25 +3476,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Description of research design summary: Textual description of research design. description: The field designDescription contains general textual descriptions of research design. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4242,25 +3708,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Citation for research design summary: Citation that describes the research design. description: The citation field is a citation to literature that describes elements of the research design, such as goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4447,25 +3894,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="relatedProject" type="ResearchProjectType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: related project summary: This field is a recursive link to another project. description: This field is a recursive link to another project. This allows projects to be nested under one another for the case where one project spawns another.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4643,25 +4071,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="researchProject" type="ResearchProjectType">
- <xs:annotation>
- <xs:documentation>tooltip: research project summary: The root element of this module. description: The root element of this module. This is used for testing or if you want to instantiate a stand-alone project file.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="ResearchProjectType">
- <xs:annotation>
- <xs:documentation>tooltip: Research project descriptor summary: Descriptor of a research context for a dataset or another project. description: The researchProject complex type describes the structure for documenting the research context of a dataset or another project. It can include research goals, motivations, theory, hypotheses, etc., as well as a description of research efforts that form the basis for other work. (To document methods specific to a dataset use eml-methods.) This field can be associated with a dataset using the project field of eml-dataset, and can be associated with another project using the relatedProject field of eml-project (this module).</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="title" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Project Title summary: Title of the project. description: A descriptive title for the research project. example: Species diversity in Tennessee riparian habitats.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="personnel" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Personnel summary: Contact and role information for people involved in the research project. description: The Personnel field extends ResponsibleParty with role information and is used to document people involved in a research project by providing contact information and their role in the project.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="rp:ResponsibleParty">
- <xs:sequence maxOccurs="unbounded">
- <xs:element name="role" type="rp:RoleType">
- <xs:annotation>
- <xs:documentation>tooltip: Role summary: Role information for people involved in the research project. description: The role field contains information about role a person plays in a research project. There are a number of suggested roles, however, it is possible to add a role if the suggested roles are not adequate. example: author example: contentProvider example: custodianSteward example: distributor example: editor example: metadataProvider example: originator example: owner example: pointOfContact example: principalInvestigator example: processor example: publisher example: user example: fieldStationManager example: informationManager</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="abstract" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Abstract summary: Project Abstract. description: Descriptive abstract that summarizes information about the research project.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="funding" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Funding summary: Funding information. description: The funding field is used to provide general information about the funding for a project, generally in prose form. This field is included for historical compatibility, and has been augmented by the award field that provides structured information about funding included.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="award" type="AwardType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Award information summary: Award information. description: The award field is used to provide specific information about the funding awards for a project in a structured format. Sub-fields are provided for the name of the funding agency, the Open Funder Registry identifiers for the agency and program that made the award, the award number assigned, the title of the award, and the URL to the award page describing the award. The award field replaces the earlier funding field from prior EML version releases. In general, the funding agency should be listed with a cross-reference to the appropriate identifier from the Open Funder Registry (included in the EML distribution, but which is also update periodically from the Open Funder Registry).</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="studyAreaDescription" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Description of the study area. summary: Description of the physical area associated with the research project, potentially including coverage, climate, geology, disturbances, etc. description: The studyAreaDescription field documents the physical area associated with the research project. It can include descriptions of the geographic, temporal, and taxonomic coverage of the research location and descriptions of domains (themes) of interest such as climate, geology, soils or disturbances or reference to citable biological or geophysical classification systems such as the Bailey Ecoregions or the Holdridge Life Zones.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="descriptor">
- <xs:annotation>
- <xs:documentation>tooltip: Non-coverage characteristics of the study area summary: Description of non-coverage characteristics of the study area such as climate, geology, disturbances description: The descriptor field is used to document domains (themes) of interest such as climate, geology, soils or disturbances or references to citable biological or geophysical classification systems such as the Bailey Ecoregions or the Holdridge Life Zones.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence maxOccurs="unbounded">
- <xs:element name="descriptorValue" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Description of some aspect of the study area. summary: Description of some aspect of the study area. description: The descriptorValue field contains the value of a descriptor, describing some aspect of the study area. This may either be a general description in textual form or the value part of a "name/value" pair where the name is entered in the attribute "name_or_id". For example, if the value of the "name" attribute" of the element "descriptor" is "climate", and the value of the attribute "name_or_id" of the element "descriptorValue" is "Annual Precipitation" then the value of this element could be "12.5 inches". example: 12.5 inches example: tundra-forest</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="name_or_id" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography". example: M131 example: Average Annual Rainfall</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: A citation for this descriptor. description: A citation for this descriptor.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="name" type="DescriptorType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: name summary: The name of the descriptor system. description: The name of the descriptor system. The name can be either a theme such as climate or hydrology, or the name of a citable classification system.</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="citableClassificationSystem" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: citation classification system summary: This boolean attribute defines whether this descriptor comes from a citable classification system or not. description: This boolean attribute defines whether this descriptor comes from a citable classification system or not.</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: citation summary: The citation for this descriptor. description: The citation for this descriptor.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="coverage" type="cov:Coverage" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: coverage summary: The coverage of this descriptor. description: The coverage of this descriptor.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="designDescription" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Description of research design summary: Description of the design of the research project description: The field designDescription contains general textual descriptions of research design. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work. Literature citations may also be used to describe the research design.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Description of research design summary: Textual description of research design. description: The field designDescription contains general textual descriptions of research design. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Citation for research design summary: Citation that describes the research design. description: The citation field is a citation to literature that describes elements of the research design, such as goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="relatedProject" type="ResearchProjectType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: related project summary: This field is a recursive link to another project. description: This field is a recursive link to another project. This allows projects to be nested under one another for the case where one project spawns another.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="AwardType">
- <xs:annotation>
- <xs:documentation>tooltip: AwardType summary: Information about a funding award. resource. description: The AwardType is used to enter information about a funding award associated with a project. The containing project contains the list of investigators and for the award, while the `award` field contains specifics such as the agency name, award number, and funding program identifiers. example: Please see the examples within each subfield.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <!--
-<funder_name>National Science Foundation</funder_name >
-<funder_identifier>https://doi.org/10.13039/00000001<funder_identifier>
-<award_number>1546024</award_number>
-<title>Scientia Arctica: A Knowledge Archive for Discovery and Reproducible Science in the Arctic</title>
-<awardURL>https://www.nsf.gov/awardsearch/showAward?AWD_ID=1546024</awardURL>
--->
- <xs:element name="funderName" type="res:i18nNonEmptyStringType" minOccurs="1" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Funder Name summary: The name of the funding institution that made this award description: The name of the funding institution, with fully expanded acronyms to show the full, official name of the funding agency. In general, this should match the official name of the funder as listed in an Authority such as the Open Funder Registry. The Open Funder Registry and other organizational authorities may provide a list of other alternative names for the funding agency. example: National Science Foundation</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="funderIdentifier" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Funder identifier summary: The identifier of the funding agency. description: The funder identifier is used to provide one or more canonical identifiers that reference the funder. These identifiers should be globally unique. The most common form of a funder identifier is a DOI identifier of an institution or program drawn from the CrossRef Open Funder Registry (https://github.com/Crossref/open-funder-registry), which assigns DOIs to each funding agency and to their programs, and links these together in a navigable hierarchy. A copy of the current Funder Registry is included as an RDF file with EML for reference, but as the list is constantly growing, users can retrieve new copies of the RDF file to get updates and current metadata about funders. example: http://dx.doi.org/10.13039/100000001</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="awardNumber" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Award Number summary: The assigned award number. description: The awardNumber field provides the unique identifier used by the funder to uniquely identify an award. These are typically alphanumeric values that are unique within the system used by a given funder. The number should be listed using the canonical form that each funder uses to express its award numbers, and not be prefixed or postfixed with extra text such as the acronym of the funder or the name of the funder, which is available instead in the funderName field. example: 1546024</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="title" type="res:i18nNonEmptyStringType" minOccurs="1" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Title summary: The title of the award. description: The title field is used for the title of the award or grant being described. example: Scientia Arctica: A Knowledge Archive for Discovery and Reproducible Science in the Arctic</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="awardUrl" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Award URL summary: The URL associated with award. description: Typically, the awardUrl is use to find and locate the award, and generally addresses the internet location to find out more information about the award. This should point to a funder site for the award, rather than a project site. example: https://www.nsf.gov/awardsearch/showAward?AWD_ID=1546024</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:simpleType name="DescriptorType">
- <xs:annotation>
- <xs:documentation>tooltip: Descriptor Theme Type summary: The type of descriptor theme or the name of a classification system. description: The DescriptorType is used to represent either the name of a citable classification system/controlled vocabulary such as the Bailey classification of ecoregions or a domain of physical descriptors such as climate or disturbances. example: climate example: soils example: hydrology example: "bailey" example: biome example: disturbance example: geology</xs:documentation>
- </xs:annotation>
- <xs:union>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="climate"/>
- <xs:enumeration value="hydrology"/>
- <xs:enumeration value="soils"/>
- <xs:enumeration value="geology"/>
- <xs:enumeration value="disturbance"/>
- <xs:enumeration value="bailey"/>
- <xs:enumeration value="biome"/>
- </xs:restriction>
- </xs:simpleType>
- <xs:simpleType>
- <xs:restriction base="xs:string"/>
- </xs:simpleType>
- </xs:union>
-</xs:simpleType>
<xs:attribute name="name_or_id" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography". example: M131 example: Average Annual Rainfall</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="name" type="DescriptorType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: name summary: The name of the descriptor system. description: The name of the descriptor system. The name can be either a theme such as climate or hydrology, or the name of a citable classification system.</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="citableClassificationSystem" type="xs:boolean" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: citation classification system summary: This boolean attribute defines whether this descriptor comes from a citable classification system or not. description: This boolean attribute defines whether this descriptor comes from a citable classification system or not.</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:element name="protocol" type="ProtocolType">
- <xs:annotation>
- <xs:documentation>tooltip: A prescriptive procedure summary: A reusable container for information related to a prescriptive procedure. description: The protocol field provides a container for other related fields, such as proceduralStep and ResourceGroup.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="ProtocolType">
- <xs:annotation>
- <xs:documentation>tooltip: A prescriptive procedure; a standardized method summary: A reusable container for information related to a prescriptive procedure. description: The ProtocolType container defines a number of reusable fields that can be referenced from multiple EML modules. It represents well-defined, prescriptive procedures that can be used to document other prescriptive procedures or descriptive procedures such as methods.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:group ref="res:ResourceGroup"/>
- <xs:element name="proceduralStep" type="md:ProcedureStepType" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:element name="references">
- <xs:annotation>
- <xs:documentation>tooltip: References summary: The id of another element in this EML document to be used to here in this context. description: The id of another element in this EML document to be used to here in this context. This is used instead of duplicating information when an identical piece of information needs to be used multiple times in an EML document. For example, if the same person is the creator, metadataProvider, and contact for a dataset, their name and address can be provided once as part of the "creator" element, and then their "id" can be used in the "references" element of metadataProvider and contact. This reduces the likelihood of error by reducing redundancy, and allows one to specify that two pieces of information are identical. To be a valid EML document, the content of every "references" element MUST be defined in the document as the value of an "id" attribute on some element within the document. Other critical rules about the use of IDs and references in EML are provided in the text of the EML specification. example: knb.45.3</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="system" type="SystemType" use="optional"/>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1080,32 +936,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="alternateIdentifier" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Alternate Identifier summary: A secondary identifier for this entity description: An additional, secondary identifier for this entity. The primary identifier belongs in the "id" attribute, but additional identifiers that are used to label this entity, possibly from different data management systems, can be listed here. example: VCR3465</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="system" type="SystemType" use="optional"/>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1219,25 +1049,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="shortName" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Short Name summary: A short name that describes the resource, sometimes a filename. description: The 'shortName' field provides a concise name that describes the resource that is being documented. It is the appropriate place to store a filename associated with other storage systems. example: vernal-data-1999</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:element name="value" minOccurs="0" maxOccurs="unbounded">
- <xs:complexType>
- <xs:annotation>
- <xs:documentation>tooltip: i18n Value summary: i18n Value description: Allows multiple language translations to appear as children of a mixed-content parent element. The xml:lang attribute is optional and will override any xml:lang attribute that has been specified in the ancestor elements. The content is subject to the same rules defined by NonEmptyStringType.</xs:documentation>
- </xs:annotation>
- <xs:simpleContent>
- <xs:extension base="NonEmptyStringType">
- <xs:attribute ref="xml:lang" use="optional"/>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1742,25 +1508,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="creator" type="rp:ResponsibleParty" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Creator summary: The people or organizations who created this resource. description: The 'creator' element provides the full name of the person, organization, or position who created the resource. The list of creators for a resource represent the people and organizations who should be cited for the resource. example: For a book, the creators are its authors.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1950,25 +1697,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="metadataProvider" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Metadata Provider summary: The people or organizations who created provided documentation and other metadata for this resource. description: The 'metadataProvider' element provides the full name of the person, organization, or position who created documentation for the resource. example: The scientist who collected the data, sometimes a data technician, or other individual.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2168,38 +1896,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="associatedParty" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Associated Party summary: Other people or organizations who should be associated with this resource. description: The 'associatedParty' element provides the full name of other people, organizations, or positions who should be associated with the resource. These parties might play various roles in the creation or maintenance of the resource, and these roles should be indicated in the "role" element. example: The technician who collected the data.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="rp:ResponsibleParty">
- <xs:sequence>
- <xs:element name="role" type="rp:RoleType">
- <xs:annotation>
- <xs:documentation>tooltip: Role summary: The role the party played with respect to the resource. description: Use this field to describe the role the party played with respect to the resource. Some potential roles include technician, reviewer, principal investigator, and many others. example: principalInvestigator</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2283,25 +1979,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="role" type="rp:RoleType">
- <xs:annotation>
- <xs:documentation>tooltip: Role summary: The role the party played with respect to the resource. description: Use this field to describe the role the party played with respect to the resource. Some potential roles include technician, reviewer, principal investigator, and many others. example: principalInvestigator</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2389,25 +2066,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="pubDate" type="yearDate" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Publication date summary: The publication date of the resource. description: The 'pubDate' field represents the date that the resource was published. The format should be represented as: CCYY, which represents a 4 digit year, or as CCYY-MM-DD, which denotes the full year, month, and day. Note that month and day are optional components. Formats must conform to ISO 8601. example: 1999-10-26</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2556,25 +2214,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="language" type="i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Language summary: The language in which the resource is written. description: The language in which the resource is written. This can be a well-known language name, or one of the ISO language codes to be more precise. example: English</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2687,25 +2326,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="series" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Series summary: The series from which the resource came. description: This field describes the series of resources that include the resource being described. For example, a volume of a journal may be part of a series of the journal for a particular year. example: Volume 20</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2855,25 +2475,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="abstract" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Abstract summary: A brief overview of the resource. description: A brief overview of the resource that is being documented. The abstract should include basic information that summarizes the resource.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2994,50 +2595,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="keywordSet" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword information summary: Keyword information that describes the resource. description: The 'keywordSet' element is a container for the 'keyword' and 'keywordThesaurus' fields. Each keywordSet field can contain one or more keywords and a name of a thesaurus for the set of keywords. Each keyword field should contain one and only one keyword (i.e., keywords should not be separated by commas or other delimiters). example: Please see the examples for the subfields contained within this field.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="keyword" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword summary: A single keyword that describes the resource. description: This field names a keyword or key phrase that concisely describes the resource or is related to the resource. Each keyword field should contain one and only one keyword (i.e., keywords should not be separated by commas or other delimiters). example: biodiversity</xs:documentation>
- </xs:annotation>
- <xs:complexType mixed="true">
- <xs:complexContent>
- <xs:extension base="i18nNonEmptyStringType">
- <xs:attribute name="keywordType" type="KeyTypeCode" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword type summary: The type of each keyword. description: This field classifies the keyword that has been provided from a list of pre-determined categories. The possible types are listed in the example. example: "place","stratum","temporal","theme", or "taxonomic"</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="keywordThesaurus" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword thesaurus summary: The name of a thesaurus from which the keyword is derived. description: This field provides the name of the official keyword thesaurus from which keyword was derived. The keyword thesauri are usually discipline specific. example: IRIS keyword thesaurus</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3222,36 +2779,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="keyword" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword summary: A single keyword that describes the resource. description: This field names a keyword or key phrase that concisely describes the resource or is related to the resource. Each keyword field should contain one and only one keyword (i.e., keywords should not be separated by commas or other delimiters). example: biodiversity</xs:documentation>
- </xs:annotation>
- <xs:complexType mixed="true">
- <xs:complexContent>
- <xs:extension base="i18nNonEmptyStringType">
- <xs:attribute name="keywordType" type="KeyTypeCode" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword type summary: The type of each keyword. description: This field classifies the keyword that has been provided from a list of pre-determined categories. The possible types are listed in the example. example: "place","stratum","temporal","theme", or "taxonomic"</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3364,25 +2891,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="keywordThesaurus" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword thesaurus summary: The name of a thesaurus from which the keyword is derived. description: This field provides the name of the official keyword thesaurus from which keyword was derived. The keyword thesauri are usually discipline specific. example: IRIS keyword thesaurus</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3539,25 +3047,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="additionalInfo" type="txt:TextType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Additional Information summary: Any extra information pertitent to the resource. description: This field provides any information that is not characterized by the other resource metadata fields. example: Copyright 2001, Robert Warner</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3716,25 +3205,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="intellectualRights" type="txt:TextType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Intellectual Property Rights summary: Intellectual property rights regarding usage and licensing of this resource. description: Typically, an intellectual Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. In the case of a data set, rights might include requirements for use, requirements for attribution, or other requirements the owner would like to impose. example: Copyright 2001 Regents of the University of California Santa Barbara. Free for use by all individuals provided that the owners are acknowledged in any use or publication.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3878,25 +3348,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="licensed" type="LicenseType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: License summary: Information identifying a well-known license for the metadata and data description: This element provides information on how the resource is licensed and what rights may be available to users. While data are often not copyrightable in the US and other jurisdictions, it is still useful to clarify rights by declaring a CC0, CC-BY, or similar license for both the metadata and data. Whatever license is declared here is intended to apply to all metadata and data described in the metadata record, including attached data resources such as external files and databases. If multiple license elements are provided, this indicates that the resource can be used under the terms of any of the listed licenses. The field is meant to be highly structured to allow machine-interpretable licenses to be asserted for the resource. This is done by identifying a well-defined license or contract and providing the SPDX license key or the license URL, and the name of the license. Where posisble, the name, URL, and SPDX key should match the values found in the official SPDX license vocabulary (https://spdx.org/licenses/). If the license is not found in SPDX, then other well-established URIs for licenses can be used, but avoid using arbitrary URIs that are not maintained for persistence. example: <license> <licenseName>Apache License 2.0</licenseName> <url>https://spdx.org/licenses/Apache-2.0.html</url> <identifier>Apache-2.0</identifier> </license></xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4010,25 +3461,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="licenseName" type="NonEmptyStringType" minOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: License Name summary: The official name of the license description: The official name of a license that applies to the data and metadata described in this metadata record. The name should match the name of a well-known license from the SPDX license vocabulary or a similar persistent vocabulary. example: Apache License 2.0</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4115,25 +3547,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="url" type="xs:anyURI" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: License URL summary: The persistent URL for the license description: The persistent URL for the license, typically a SPDX URL, or an official URL from another well-known license vocabulary. Users should avoid using arbitrary URLs that are not the official URL for a license. example: https://spdx.org/licenses/Apache-2.0.html</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4246,25 +3659,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="identifier" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: License Identifier summary: License Identifier description: The official identifier for the license, which should be drawn from the SPDX license vocabulary, or a similar well-known license vocabulary. example: Apache-2.0</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4442,25 +3836,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="distribution" type="DistributionType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Distribution Information summary: Information on how the resource is distributed online and offline description: This element provides information on how the resource is distributed. When used at the resource level, this element can provide only general information, but elements for describing connections to online systems are provided. See the Type for specific recommendations and examples.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4577,25 +3952,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="online" type="OnlineType">
- <xs:annotation>
- <xs:documentation>tooltip: distribution/online summary: Online distribution information description: This element contains information for accessing the resource online, represented either as a URL a connection, or a connectionDefinition which may be referenced in other parts of the EML document. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4741,25 +4097,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="onlineDescription" type="i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Description of online information summary: Brief description of the the content of online description: This element can hold a brief description of the content of the online element's online|offline|inline child. This description element could supply content for an html anchor tag.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4873,25 +4210,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="url" type="UrlType">
- <xs:annotation>
- <xs:documentation>tooltip: URL summary: A URL or this resource. description: A URL (Uniform Resource Locator) from which this additional information can be obtained, or from which the resource can be downloaded directly. In the resource module, the distribution URL is generally meant for informational purposes, and the "function" attribute should be set to "information". However, if the URL returns the data stream itself, then the "function" attribute should be set to "download". See the Type Definition for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5058,25 +4376,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="connection" type="ConnectionType">
- <xs:annotation>
- <xs:documentation>tooltip: Connection summary: A connection to a data service description: A description of the information needed to make an application connection to a data service. The connection contains a connectionDefinition and optional parameters for overriding defaults. See the Type Definition for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5242,25 +4541,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="connectionDefinition" type="ConnectionDefinitionType">
- <xs:annotation>
- <xs:documentation>tooltip: Connection Definition summary: Connection Definition description: In a ConnectionType, the connectionDefinition element provides the definition of the protocol and its parameters. The definition has a "scheme" which identifies the protocol by name, with a detailed description and its required parameters. A connectionDefinition lists all of the parameters needed for the connection and possible default values for each.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5399,36 +4679,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="schemeName">
- <xs:annotation>
- <xs:documentation>tooltip: Scheme Name summary: The name of the scheme used to identify this connection. description: The name of the scheme used to identify this connection. The scheme name is qualified by its system attribute. The scheme name implies a particular protocol for accessing information from the connection. Applications must have a knowledge of the scheme or be able to deduce the protocol from the scheme description in order to effectively access data over the connection. Many schemes will be unknown to client applications. At some later point in time a registry for connection schemes may be established in order to promote application interoperability, and we may expand this portion of EML to adopt a more comprehensive standard such as WSDL, but for now this simpler description is provided. example: metacat</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="system" type="SystemType" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Scheme System summary: The system in which this scheme name is relevant description: The computing system within which this scheme name has relevance. This attribute qualifies the scheme name in order to decrease the likelihood of scheme name collisions when more that one EML user defines a scheme name with the same name but different semantics. example: http://knb.ecoinformatics.org/knb/</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -5591,25 +4841,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Scheme Description summary: The description of the scheme used to identify this connection. description: The description of the scheme used to identify this connection. The scheme name implies a particular protocol for accessing information from the connection. Applications must have a knowledge of the scheme or be able to deduce the protocol from the scheme description in order to effectively access data over the connection. example: The metacat application protocol. Applications must first log into metacat by sending an HTTP POST request in http-url-encoded format with the parameters action, username, and password. Action must be set to "login". If authentication is successful, the metacat server will respond with a session cookie. All future requests should include the session cookie in the HTTP header. To retrieve an object, the client then would send an HTTP POST in http-url-encoded format, with an action parameter set to "get" and the docid parameter set to the identifier for the desired object. The response will either be an XML document or a multipart-form-encoded response containing data.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5725,44 +4956,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="parameterDefinition" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Definition summary: The definition of a parameter that is needed to properly use this connection scheme. description: The definition of a parameter that is needed to properly use this connection scheme. Each parameter has a name and a definition that are used by applications to assess the type of information needed for the request. Parameters may also set default values that are used if a connection does not provide a value for a parameter.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="name" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The Name of a parameter that is needed to properly use this connection scheme. description: The name of a parameter that is needed to properly use this connection scheme. example: hostname</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="definition" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Definition summary: The definition of a parameter that is needed to properly use this connection scheme. description: The definition of a parameter that is needed to properly use this connection scheme. The definition is used by applications to assess the type of information needed for the request. example: The fully qualified name of the internet host that is providing the metacat service, as would be returned by a Domain Name System (DNS) query.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="defaultValue" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Default Parameter Value summary: The default value for a parameter that is needed to properly use this connection scheme. description: The default value for a parameter that is needed to properly use this connection scheme. If a default value is set, then it should be used for connections that do not override the default with a connection-specific value. This allows a definition to be established that declares common information that might be shared by several connections as default values. Parameter values provided in the connection always override any default values provided in the connection definition. example: metacat.nceas.ucsb.edu</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -5870,25 +5063,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="name" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The Name of a parameter that is needed to properly use this connection scheme. description: The name of a parameter that is needed to properly use this connection scheme. example: hostname</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6000,25 +5174,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="definition" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Definition summary: The definition of a parameter that is needed to properly use this connection scheme. description: The definition of a parameter that is needed to properly use this connection scheme. The definition is used by applications to assess the type of information needed for the request. example: The fully qualified name of the internet host that is providing the metacat service, as would be returned by a Domain Name System (DNS) query.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6137,25 +5292,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="defaultValue" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Default Parameter Value summary: The default value for a parameter that is needed to properly use this connection scheme. description: The default value for a parameter that is needed to properly use this connection scheme. If a default value is set, then it should be used for connections that do not override the default with a connection-specific value. This allows a definition to be established that declares common information that might be shared by several connections as default values. Parameter values provided in the connection always override any default values provided in the connection definition. example: metacat.nceas.ucsb.edu</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6271,39 +5407,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter summary: A parameter to be used to make this connection. description: A parameter to be used to make this connection. This value overrides any default value that may have been provided in the connection definition.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="name" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: Name of the parameter to be used to make this connection. description: The name of the parameter to be used to make this connection. example: hostname</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="value" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Value summary: The value of the parameter to be used to make this connection. description: The value of the parameter to be used to make this connection. This value overrides any default value that may have been provided in the connection definition. example: nceas.ucsb.edu</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -6412,25 +5515,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="name" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: Name of the parameter to be used to make this connection. description: The name of the parameter to be used to make this connection. example: hostname</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6542,25 +5626,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="value" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Value summary: The value of the parameter to be used to make this connection. description: The value of the parameter to be used to make this connection. This value overrides any default value that may have been provided in the connection definition. example: nceas.ucsb.edu</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6744,25 +5809,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="connectionDefinition" type="ConnectionDefinitionType">
- <xs:annotation>
- <xs:documentation>tooltip: Connection Definition summary: The definition of a connection that will be used in another location in the EML document description: The definition of a type of connection that will be used in another location in the EML document. The connectionDefinition element only provides the definition of the protocol and its parameters, but not the actual values to be used to make the connection (instead, see the connection element). This connectionDefinition may be used by multiple connections (e.g., to download different files from the same database), but each connection must provide or reference a valid connection definition. The definition has a "scheme" which identifies the protocol by name, with a detailed description and its required parameters. A connectionDefinition lists all of the parameters needed for the connection and possible default values for each.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6881,25 +5927,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="offline" type="OfflineType">
- <xs:annotation>
- <xs:documentation>tooltip: Offline distribution summary: data are available offline description: This element is for data which are distributed offline, generally by request. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7010,25 +6037,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="mediumName" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Medium name summary: Name of the medium that for this resource distribution description: Name of the medium on which this resource is distributed. Can be various digital media such as tapes and disks, or printed media which can collectively be termed 'hardcopy'. example: Tape, 3.5 inch Floppy Disk, hardcopy</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7142,25 +6150,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="mediumDensity" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: density of the digital medium summary: the density of the digital medium if this is relevant. description: the density of the digital medium if this is relevant. Used mainly for floppy disks or tape. example: High Density (HD), Double Density (DD)</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7271,25 +6260,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="mediumDensityUnits" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: units of a numerical density summary: a numerical density's units description: if a density is given numerically, the units should be given here. example: B/cm</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7401,25 +6371,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="mediumVolume" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: storage volume summary: total volume of the storage medium description: the total volume of the storage medium on which this resource is shipped. example: 650 MB</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7535,25 +6486,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="mediumFormat" type="NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: medium format summary: format of the medium on which the resource is shipped. description: the file system format of the medium on which the resource is shipped example: NTFS, FAT32, EXT2, QIK80</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7662,25 +6594,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="mediumNote" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: note about the media summary: note about the media description: any additional pertinent information about the media</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7770,25 +6683,6 @@
Showing:
ANY element from ANY namespace
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="inline" type="InlineType">
- <xs:annotation>
- <xs:documentation>tooltip: Inline distribution summary: data distributed inline in the metadata. description: The data are distributed inline, with the metadata. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7964,25 +6858,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="coverage" type="cov:Coverage" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Resource coverage summary: Extent of the coverage of the resource. description: This element describes the extent of the coverage of the resource in terms of its spatial extent, temporal extent, and taxonomic extent. For data sets, this is useful to specify the entire extent to which all of the data might apply. example: See the coverage module for examples.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8161,25 +7036,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="annotation" type="sem:SemanticAnnotation" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about this resource. description: An annotation represents a precisely-defined semantic statement that applies to this resource. This semantic statement is used to associate precise semantics with the resource. Each annotation consists of a propertyURI and valueURI that define a property and value that apply to the resource. The subject of the statement is implicitly the eml:resource that contains the annotation. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:simpleType name="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Non Empty String Type summary: Non Empty String Type description: This type specifies a content pattern for all elements that are required by EML to ensure that there is actual content (i.e., not just whitespace). The pattern described can be interpreted as "at least one non-whitespace character, followed by any number of whitespace plus not-whitespace characters. " Leading and/or trailing whitespace is allowed, and whitespace may include carriage returns and newlines.</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:minLength value="1"/>
- <xs:pattern value="[\s]*[\S][\s\S]*"/>
- </xs:restriction>
-</xs:simpleType>
<xs:simpleType name="SystemType">
- <xs:annotation>
- <xs:documentation>tooltip: Identifer System summary: The data management system within which an identifier is in scope and therefore unique. description: The data management system within which an identifier is in scope and therefore unique. This is typically a URL (Uniform Resource Locator) that indicates a data management system. All identifiers that share a system must be unique. In other words, if the same identifier is used in two locations with identical systems, then by definition the objects at which they point are in fact the same object. example: http://metacat.somewhere.org/svc/mc/</xs:documentation>
- </xs:annotation>
- <xs:list itemType="xs:string"/>
-</xs:simpleType>
<xs:simpleType name="IDType">
- <xs:annotation>
- <xs:documentation>tooltip: Identifer summary: A unique identifier for this additional metadata that can be used to reference it elsewhere. description: A unique identifier for this additional metadata that can be used to reference it elsewhere. This is a formal field in that it is an error to provide a value for the id attribute that is not unique within the document's set of id attributes. This is designed to allow other portions of the metadata to reference this section formally. example: knb.343.22</xs:documentation>
- </xs:annotation>
- <xs:list itemType="xs:string"/>
-</xs:simpleType>
<xs:simpleType name="ScopeType">
- <xs:annotation>
- <xs:documentation>tooltip: Identifer Scope summary: The scope of the identifier. description: The scope of the identifier. Scope is generally set to either "system", meaning that it is scoped according to the "system" attribute, or "document" if it is only to be in scope within this single document instance. In this particular use of scope, it is FIXED to be "system" because the packageId is required and always has the scope of the required "system". example: system</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:enumeration value="system"/>
- <xs:enumeration value="document"/>
- </xs:restriction>
-</xs:simpleType>
<xs:complexType name="i18nNonEmptyStringType" mixed="true">
- <xs:annotation>
- <xs:documentation>tooltip: i18n Non Empty String Type summary: i18n Non Empty String Type description: This type specifies a content pattern for all elements that require language translations. The xml:lang attribute can be used to define the default language for element content. Additional translations should be included as child 'value' elements that also have an optional xml:lang attribute.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="value" minOccurs="0" maxOccurs="unbounded">
- <xs:complexType>
- <xs:annotation>
- <xs:documentation>tooltip: i18n Value summary: i18n Value description: Allows multiple language translations to appear as children of a mixed-content parent element. The xml:lang attribute is optional and will override any xml:lang attribute that has been specified in the ancestor elements. The content is subject to the same rules defined by NonEmptyStringType.</xs:documentation>
- </xs:annotation>
- <xs:simpleContent>
- <xs:extension base="NonEmptyStringType">
- <xs:attribute ref="xml:lang" use="optional"/>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute ref="xml:lang" use="optional"/>
-</xs:complexType>
<xs:simpleType name="yearDate">
- <xs:annotation>
- <xs:documentation>tooltip: Year or Date summary: A type allowing a year or date value description: This type is the union of the built-in types for year and date. example: 1999, or 2001-03-15</xs:documentation>
- </xs:annotation>
- <xs:union memberTypes="xs:gYear xs:date"/>
-</xs:simpleType>
<xs:simpleType name="KeyTypeCode">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword type codes summary: The list of keyword categories description: This field provides a restricted list of categories that a keyword may fall under. example: place</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:enumeration value="place">
- <xs:annotation>
- <xs:documentation>tooltip: Place Keywords summary: Keywords pertaining to a spatial location description: Keywords naming geographic locations associated with the data set.</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- <xs:enumeration value="stratum">
- <xs:annotation>
- <xs:documentation>tooltip: Stratum Keywords summary: Keywords pertaining to a vertical stratum description: Keywords naming vertical strata associated with the data set (e.g., soil horizons).</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- <xs:enumeration value="temporal">
- <xs:annotation>
- <xs:documentation>tooltip: Temporal Keywords summary: Keywords pertaining to temporal data description: Keywords listing time periods associated with the data set.</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- <xs:enumeration value="theme">
- <xs:annotation>
- <xs:documentation>tooltip: Thematic Keywords summary: Keywords pertaining to thematic subject description: Keywords naming thematics subjects associated with the data set.</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- <xs:enumeration value="taxonomic">
- <xs:annotation>
- <xs:documentation>tooltip: Taxonomic Keywords summary: Keywords pertaining to taxon information description: Keywords listing taxonomic terms associated with the data set. Note that lists of species names or other taxon lists should be presented in the taxonomicCoverage element.</xs:documentation>
- </xs:annotation>
- </xs:enumeration>
- </xs:restriction>
-</xs:simpleType>
<xs:complexType name="LicenseType">
- <xs:annotation>
- <xs:documentation>tooltip: License summary: Information identifying a well-known license for the metadata and data description: This element provides information on how the resource is licensed and what rights may be available to users. While data are often not copyrightable in the US and other jurisdictions, it is still useful to clarify rights by declaring a CC0, CC-BY, or similar license for both the metadata and data. Whatever license is declared here is intended to apply to all metadata and data described in the metadata record, including attached data resources such as external files and databases. If multiple license elements are provided, this indicates that the resource can be used under the terms of any of the listed licenses. The field is meant to be highly structured to allow machine-interpretable licenses to be asserted for the resource. This is done by identifying a well-defined license or contract and providing the SPDX license key or the license URL, and the name of the license. Where posisble, the name, URL, and SPDX key should match the values found in the official SPDX license vocabulary (see SPDX License List). If the license is not found in SPDX, then other well-established URIs for licenses can be used, but avoid using arbitrary URIs that are not maintained for persistence. example: <license> <licenseName>Apache License 2.0</licenseName> <url>https://spdx.org/licenses/Apache-2.0.html</url> <identifier>Apache-2.0</identifier> </license></xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="licenseName" type="NonEmptyStringType" minOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: License Name summary: The official name of the license description: The official name of a license that applies to the data and metadata described in this metadata record. The name should match the name of a well-known license from the SPDX license vocabulary or a similar persistent vocabulary. example: Apache License 2.0</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="url" type="xs:anyURI" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: License URL summary: The persistent URL for the license description: The persistent URL for the license, typically a SPDX URL, or an official URL from another well-known license vocabulary. Users should avoid using arbitrary URLs that are not the official URL for a license. example: https://spdx.org/licenses/Apache-2.0.html</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="identifier" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: License Identifier summary: License Identifier description: The official identifier for the license, which should be drawn from the SPDX license vocabulary, or a similar well-known license vocabulary. example: Apache-2.0</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="DistributionType">
- <xs:annotation>
- <xs:documentation>tooltip: Distribution Information summary: Distribution information for accessing the resource. description: Distribution information for accessing the resource by one of three methods: online, offline or inline. Generally, the Type at the resource level is intended to be informational, although elements are included to describe a complex connection protocol. For more information, see the sub-elements. Also compare to phys:PhysicalDistributionType .</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:choice>
- <xs:element name="online" type="OnlineType">
- <xs:annotation>
- <xs:documentation>tooltip: distribution/online summary: Online distribution information description: This element contains information for accessing the resource online, represented either as a URL a connection, or a connectionDefinition which may be referenced in other parts of the EML document. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="offline" type="OfflineType">
- <xs:annotation>
- <xs:documentation>tooltip: Offline distribution summary: data are available offline description: This element is for data which are distributed offline, generally by request. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="inline" type="InlineType">
- <xs:annotation>
- <xs:documentation>tooltip: Inline distribution summary: data distributed inline in the metadata. description: The data are distributed inline, with the metadata. See the Type definition for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:group ref="ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="IDType" use="optional"/>
- <xs:attribute name="system" type="SystemType" use="optional"/>
- <xs:attribute name="scope" type="ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="OnlineType">
- <xs:annotation>
- <xs:documentation>tooltip: Online Distribution Type summary: Distribution information for accessing the resource online. description: Distribution information for accessing the resource online, represented either as a URL or as the series of named parameters needed to connect. The URL field can contain a simple web address or an entire query string. The connection element allows the components of a complex protocol to be described individually. The connectionDefinition element can also be appear outside of the connection elements, so that it can be defined once and referenced by several connections. Also see the phys:PhysicalOnlineType, which may be more appropriate for describing the online connections to a specific entity described by this metadata document.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="onlineDescription" type="i18nNonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Description of online information summary: Brief description of the the content of online description: This element can hold a brief description of the content of the online element's online|offline|inline child. This description element could supply content for an html anchor tag.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice>
- <xs:element name="url" type="UrlType">
- <xs:annotation>
- <xs:documentation>tooltip: URL summary: A URL or this resource. description: A URL (Uniform Resource Locator) from which this additional information can be obtained, or from which the resource can be downloaded directly. In the resource module, the distribution URL is generally meant for informational purposes, and the "function" attribute should be set to "information". However, if the URL returns the data stream itself, then the "function" attribute should be set to "download". See the Type Definition for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="connection" type="ConnectionType">
- <xs:annotation>
- <xs:documentation>tooltip: Connection summary: A connection to a data service description: A description of the information needed to make an application connection to a data service. The connection contains a connectionDefinition and optional parameters for overriding defaults. See the Type Definition for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="connectionDefinition" type="ConnectionDefinitionType">
- <xs:annotation>
- <xs:documentation>tooltip: Connection Definition summary: The definition of a connection that will be used in another location in the EML document description: The definition of a type of connection that will be used in another location in the EML document. The connectionDefinition element only provides the definition of the protocol and its parameters, but not the actual values to be used to make the connection (instead, see the connection element). This connectionDefinition may be used by multiple connections (e.g., to download different files from the same database), but each connection must provide or reference a valid connection definition. The definition has a "scheme" which identifies the protocol by name, with a detailed description and its required parameters. A connectionDefinition lists all of the parameters needed for the connection and possible default values for each.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="UrlType">
- <xs:annotation>
- <xs:documentation>tooltip: Download site URL summary: A URL (Uniform Resource Locator) from which this resource can be downloaded or information can be obtained about downloading it. description: A URL (Uniform Resource Locator) from which this resource can be downloaded or additional information can be obtained. If the URL provides further information about downloading the object but does not directly return the data stream, then the "function" attribute should be set to "information". If accessing the URL would directly return the data stream, then the "function" attribute should be set to "download". If the "function" attribute is omitted, then "download" is implied for the URL function. In more complex cases where a non-standard connection must be established that complies with application specific procedures beyond what can be described in the simple URL, then the "connection" element should be used instead of the URL element. example: http://data.org/getdata?id=98332</xs:documentation>
- </xs:annotation>
- <xs:simpleContent>
- <xs:extension base="xs:anyURI">
- <xs:attribute name="function" type="FunctionType" use="optional" default="download"/>
- </xs:extension>
- </xs:simpleContent>
-</xs:complexType>
<xs:complexType name="ConnectionType">
- <xs:annotation>
- <xs:documentation>tooltip: Connection summary: A description of the information needed to make an application connection to a data service. description: A description of the information needed to make an application connection to a data service. The connection starts with a connectionDefinition which lists all of the parameters needed for the connection and possible default values for each. It may also include a list of parameter values (one for each), that override the defaults for this particular connection. One parameter element should exist for every parameterDefinition that is present in the connectionDefinition, although parameters that were defined with a defaultValue in their parameterDefinition can be omitted. All information about how to use the parameters to establish a session and extract data is present in the connectionDefinition, possibly implicitly by naming a connection schemeName that is well-known. See descriptions of the child element types for further information.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="connectionDefinition" type="ConnectionDefinitionType">
- <xs:annotation>
- <xs:documentation>tooltip: Connection Definition summary: Connection Definition description: In a ConnectionType, the connectionDefinition element provides the definition of the protocol and its parameters. The definition has a "scheme" which identifies the protocol by name, with a detailed description and its required parameters. A connectionDefinition lists all of the parameters needed for the connection and possible default values for each.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter summary: A parameter to be used to make this connection. description: A parameter to be used to make this connection. This value overrides any default value that may have been provided in the connection definition.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="name" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: Name of the parameter to be used to make this connection. description: The name of the parameter to be used to make this connection. example: hostname</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="value" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Value summary: The value of the parameter to be used to make this connection. description: The value of the parameter to be used to make this connection. This value overrides any default value that may have been provided in the connection definition. example: nceas.ucsb.edu</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:group ref="ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="IDType" use="optional"/>
- <xs:attribute name="system" type="SystemType" use="optional"/>
- <xs:attribute name="scope" type="ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="ConnectionDefinitionType">
- <xs:annotation>
- <xs:documentation>tooltip: Connection Definition summary: Definition of the connection protocol. description: Definition of the connection protocol. The definition has a "scheme" which identifies the protocol by name, with a detailed description and its required parameters. A connectionDefinition lists all of the parameters needed for the connection and possible default values for each. A definition provided in this element may be used in other parts of the EML document.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:element name="schemeName">
- <xs:annotation>
- <xs:documentation>tooltip: Scheme Name summary: The name of the scheme used to identify this connection. description: The name of the scheme used to identify this connection. The scheme name is qualified by its system attribute. The scheme name implies a particular protocol for accessing information from the connection. Applications must have a knowledge of the scheme or be able to deduce the protocol from the scheme description in order to effectively access data over the connection. Many schemes will be unknown to client applications. At some later point in time a registry for connection schemes may be established in order to promote application interoperability, and we may expand this portion of EML to adopt a more comprehensive standard such as WSDL, but for now this simpler description is provided. example: metacat</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="system" type="SystemType" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Scheme System summary: The system in which this scheme name is relevant description: The computing system within which this scheme name has relevance. This attribute qualifies the scheme name in order to decrease the likelihood of scheme name collisions when more that one EML user defines a scheme name with the same name but different semantics. example: http://knb.ecoinformatics.org/knb/</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="description" type="txt:TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Scheme Description summary: The description of the scheme used to identify this connection. description: The description of the scheme used to identify this connection. The scheme name implies a particular protocol for accessing information from the connection. Applications must have a knowledge of the scheme or be able to deduce the protocol from the scheme description in order to effectively access data over the connection. example: The metacat application protocol. Applications must first log into metacat by sending an HTTP POST request in http-url-encoded format with the parameters action, username, and password. Action must be set to "login". If authentication is successful, the metacat server will respond with a session cookie. All future requests should include the session cookie in the HTTP header. To retrieve an object, the client then would send an HTTP POST in http-url-encoded format, with an action parameter set to "get" and the docid parameter set to the identifier for the desired object. The response will either be an XML document or a multipart-form-encoded response containing data.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="parameterDefinition" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Definition summary: The definition of a parameter that is needed to properly use this connection scheme. description: The definition of a parameter that is needed to properly use this connection scheme. Each parameter has a name and a definition that are used by applications to assess the type of information needed for the request. Parameters may also set default values that are used if a connection does not provide a value for a parameter.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="name" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The Name of a parameter that is needed to properly use this connection scheme. description: The name of a parameter that is needed to properly use this connection scheme. example: hostname</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="definition" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Definition summary: The definition of a parameter that is needed to properly use this connection scheme. description: The definition of a parameter that is needed to properly use this connection scheme. The definition is used by applications to assess the type of information needed for the request. example: The fully qualified name of the internet host that is providing the metacat service, as would be returned by a Domain Name System (DNS) query.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="defaultValue" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Default Parameter Value summary: The default value for a parameter that is needed to properly use this connection scheme. description: The default value for a parameter that is needed to properly use this connection scheme. If a default value is set, then it should be used for connections that do not override the default with a connection-specific value. This allows a definition to be established that declares common information that might be shared by several connections as default values. Parameter values provided in the connection always override any default values provided in the connection definition. example: metacat.nceas.ucsb.edu</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:group ref="ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="IDType" use="optional"/>
- <xs:attribute name="system" type="SystemType" use="optional"/>
- <xs:attribute name="scope" type="ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="OfflineType">
- <xs:annotation>
- <xs:documentation>tooltip: medium of the resource summary: the medium on which this resource is distributed, either digitally or as hardcopy description: the medium on which this resource is distributed digitally, such as 3.5" floppy disk, or various tape media types, or 'hardcopy' example: CD-ROM, 3.5 in. floppy disk, Zip disk</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="mediumName" type="NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Medium name summary: Name of the medium that for this resource distribution description: Name of the medium on which this resource is distributed. Can be various digital media such as tapes and disks, or printed media which can collectively be termed 'hardcopy'. example: Tape, 3.5 inch Floppy Disk, hardcopy</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="mediumDensity" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: density of the digital medium summary: the density of the digital medium if this is relevant. description: the density of the digital medium if this is relevant. Used mainly for floppy disks or tape. example: High Density (HD), Double Density (DD)</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="mediumDensityUnits" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: units of a numerical density summary: a numerical density's units description: if a density is given numerically, the units should be given here. example: B/cm</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="mediumVolume" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: storage volume summary: total volume of the storage medium description: the total volume of the storage medium on which this resource is shipped. example: 650 MB</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="mediumFormat" type="NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: medium format summary: format of the medium on which the resource is shipped. description: the file system format of the medium on which the resource is shipped example: NTFS, FAT32, EXT2, QIK80</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="mediumNote" type="NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: note about the media summary: note about the media description: any additional pertinent information about the media</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="InlineType" mixed="true">
- <xs:annotation>
- <xs:documentation>tooltip: Inline distribution summary: Object data distributed inline in the metadata. description: Object data distributed inline in the metadata. Users have the option of including the data right inline in the metadata by providing it inside of the "inline" element. For many text formats, the data can be simply included directly in the element. However, certain character sequences are invalid in an XML document (e.g., <), so care will need to be taken to either 1) wrap the data in a CDATA section if needed, or 2) encode the data using a text encoding algorithm such as base64, and then include that in a CDATA section. The latter will be necessary for binary formats.</xs:documentation>
- </xs:annotation>
- <xs:complexContent mixed="true">
- <xs:restriction base="xs:anyType">
- <xs:sequence>
- <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:restriction>
- </xs:complexContent>
-</xs:complexType>
<xs:attribute name="keywordType" type="KeyTypeCode" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Keyword type summary: The type of each keyword. description: This field classifies the keyword that has been provided from a list of pre-determined categories. The possible types are listed in the example. example: "place","stratum","temporal","theme", or "taxonomic"</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="system" type="SystemType" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Scheme System summary: The system in which this scheme name is relevant description: The computing system within which this scheme name has relevance. This attribute qualifies the scheme name in order to decrease the likelihood of scheme name collisions when more that one EML user defines a scheme name with the same name but different semantics. example: http://knb.ecoinformatics.org/knb/</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:group name="ReferencesGroup">
- <xs:annotation>
- <xs:documentation>tooltip: References Group summary: A group of elements repeatedly used throughout EML to reference IDs. description: A group containing the "references" element that is used throughout EML.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="references">
- <xs:annotation>
- <xs:documentation>tooltip: References summary: The id of another element in this EML document to be used to here in this context. description: The id of another element in this EML document to be used to here in this context. This is used instead of duplicating information when an identical piece of information needs to be used multiple times in an EML document. For example, if the same person is the creator, metadataProvider, and contact for a dataset, their name and address can be provided once as part of the "creator" element, and then their "id" can be used in the "references" element of metadataProvider and contact. This reduces the likelihood of error by reducing redundancy, and allows one to specify that two pieces of information are identical. To be a valid EML document, the content of every "references" element MUST be defined in the document as the value of an "id" attribute on some element within the document. Other critical rules about the use of IDs and references in EML are provided in the text of the EML specification. example: knb.45.3</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="system" type="SystemType" use="optional"/>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:group>
diff --git a/dist/schema/eml-semantics_xsd.html b/dist/schema/eml-semantics_xsd.html
index 2edd1c04..013d734d 100644
--- a/dist/schema/eml-semantics_xsd.html
+++ b/dist/schema/eml-semantics_xsd.html
@@ -16,21 +16,6 @@
'properties_SemanticAnnotation_system',
'properties_SemanticAnnotation_scope');
var facetsBoxes= new Array('facets_SemanticAnnotation_scope');
-var usedByBoxes= new Array('usedBy_SemanticAnnotation',
- 'usedBy_SemanticAnnotation_SemanticAnnotation_propertyURI_label',
- 'usedBy_SemanticAnnotation_SemanticAnnotation_valueURI_label',
- 'usedBy_SemanticAnnotation_id',
- 'usedBy_SemanticAnnotation_system',
- 'usedBy_SemanticAnnotation_scope');
-var sourceBoxes= new Array('source_SemanticAnnotation_propertyURI',
- 'source_SemanticAnnotation_valueURI',
- 'source_annotation',
- 'source_SemanticAnnotation',
- 'source_SemanticAnnotation_SemanticAnnotation_propertyURI_label',
- 'source_SemanticAnnotation_SemanticAnnotation_valueURI_label',
- 'source_SemanticAnnotation_id',
- 'source_SemanticAnnotation_system',
- 'source_SemanticAnnotation_scope');
var instanceBoxes= new Array('instance_annotation');
var diagramBoxes= new Array('diagram_SemanticAnnotation_propertyURI',
'diagram_SemanticAnnotation_valueURI',
@@ -315,12 +300,6 @@
Showing:
Properties
-
-
Source
-
-
-
Used by
-
@@ -592,36 +571,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="propertyURI" minOccurs="1" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Property URI summary: The persistent URI used to identify a property from a vocabulary. description: The URI for a property that is drawn from a controlled vocabulary, and that links the subject of this annotation (which is implied by its parent element) to the annotation value. The propertyURI represents a semantically well-defined concept that one wants to apply to an element within EML. These properties should be precisely defined, including defining various relationships to related concepts. Property URIs are typically drawn from formal ontologies that provide well-defined logical semantics and provide for various types of reasoning about equivalence and overlap. Property URIs should be persistent and unique over decades, and the meaning of the URI should be stable over time as well. These URIs are usually constructed using an additional abstraction layer via link resolvers, rather than directly resolving to the term definition itself. Thus, when resolving the propertyURI, software user agents should be prepared to follow multiple redirects before finally resolving the current location of the definition. However, there is no requirement that propertyURIs need to be resolvable, and metadata parsers should expect to find propertyURIs that do not resolve and are only used as unique URIs for the property (i.e., a name). example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-characteristics.owl#ofCharacteristic example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-standards.owl#usesStandard</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:anyURI">
- <xs:attribute name="label" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Property Label summary: A human readable representation of the controlled property. description: A label that provides a human readable representation of the controlled property. The label is often used to represent the controlled property when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the propertyURI. Property definitions and relationships to other properties are also typically provided within the vocabularly accessible at the propertyURI. Software and people may be able to resolve the URI to find out the definition and retrieve additional labels and other metadata for presentation to users. example: has characteristic example: uses protocol</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -800,36 +749,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="valueURI" minOccurs="1" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Value URI summary: The persistent URI used to identify a value from a vocabulary. description: The URI for a value that is drawn from a controlled vocabulary such as a published ontology or controlled term list. The value represents the object of a semantic statement in which the subject is the containing element, the property is defined by the sibling propertyURI, and this valueURI element represents the object. These values should be precisely defined, including defining various relationships to related concepts. Value URIs are typically drawn from formal ontologies that provide well-defined logical semantics and provide for various types of reasoning about value equivalence and overlap. Value URIs should be persistent and unique over decades, and the meaning of the values associated with the URI should be stable over time as well. These URIs are usually constructed using an additional abstraction layer via link resolvers, rather than directly resolving to the term definition itself. Thus, when resolving the valueURI, software user agents should be prepared to follow multiple redirects before finally resolving the current location of the value definition. However, there is no requirement that valueURIs need to be resolvable, and metadata parsers should expect to find valueURIs that do not resolve and are only used as unique URIs for the value (i.e., a name) example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-characteristics.owl#Mass example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-standards.owl#Kilogram</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:anyURI">
- <xs:attribute name="label" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Value Label summary: A human readable representation of the controlled value. description: A label that provides a human readable representation of the controlled value. The label is often used to represent the controlled value when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the valueURI. Value definitions and relationships to other terms are also typically provided within the vocabularly accessible at the valueURI. Software and people can resolve the value URI to find out the definition of the value and retrieve additional labels and other metadata about the value for presentation to users. example: Mass example: Kilogram example: Net Primary Production example: Carbon example: Density</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1011,25 +930,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="annotation" type="SemanticAnnotation">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement. description: An annotation represents a precisely-defined semantic statement that is used to semantically label another structure within EML, such as an attribute, entity, or dataset. The annotation is composed of a subject (implied by the element containing the annotation or pointed at from within eml:additionalMetadata), a property that defines the relationship between the subject and the object of the statement, and the value of that property. This is equivalent to RDF Statements that consist of a Subject, Predicate, and Object. More concretely, the annotation provides a way to state that an element within EML has a specific property with a specific value. example: For example, a common annotation would state that a containing 'attribute' uses a measurement unit of 'grams'. This would be equivalent to defining a statement using the OBOE design pattern that says: 'attribute7' 'oboe:usesStandard' 'oboe:Gram', where 'attribute7' is shorthand for the attribute in EML containing the annotation, and 'oboe:' is shorthand for the full OBOE URI. In this example, 'attribute7' is the subject represented as the id of the attribute containing the annotation, 'oboe:standard' is the propertyURI for the statement, and 'oboe:Gram' is the object of the statement.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="SemanticAnnotation">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic annotation summary: A semantically-precise statement about an EML element. description: The SemanticAnnotation Type contains elements that are used to associate a semantic statement using a property and value from specific formal vocabularies with other elements within EML. For example, one might want to provide the precise set of semantic statements that clarify the measurement semantics of an attribute (variable) within a data set, or associate a specific statement with a data table or dataset. The eml-semantics module defines an 'annotation' element and associated type that can be used within EML resources (dataset, software, etc.), EML Entities (dataTable, spatialRaster, spatialVector, otherEntity), and EML Attributes. They can also be applied within the EML additionalMetadata field to label arbitrary structures within EML, in which case the subject of the annotation is the element listed in the describes element within the additionalMetadata field. example: Please see the examples for the particular subfields.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="propertyURI" minOccurs="1" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Property URI summary: The persistent URI used to identify a property from a vocabulary. description: The URI for a property that is drawn from a controlled vocabulary, and that links the subject of this annotation (which is implied by its parent element) to the annotation value. The propertyURI represents a semantically well-defined concept that one wants to apply to an element within EML. These properties should be precisely defined, including defining various relationships to related concepts. Property URIs are typically drawn from formal ontologies that provide well-defined logical semantics and provide for various types of reasoning about equivalence and overlap. Property URIs should be persistent and unique over decades, and the meaning of the URI should be stable over time as well. These URIs are usually constructed using an additional abstraction layer via link resolvers, rather than directly resolving to the term definition itself. Thus, when resolving the propertyURI, software user agents should be prepared to follow multiple redirects before finally resolving the current location of the definition. However, there is no requirement that propertyURIs need to be resolvable, and metadata parsers should expect to find propertyURIs that do not resolve and are only used as unique URIs for the property (i.e., a name). example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-characteristics.owl#ofCharacteristic example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-standards.owl#usesStandard</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:anyURI">
- <xs:attribute name="label" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Property Label summary: A human readable representation of the controlled property. description: A label that provides a human readable representation of the controlled property. The label is often used to represent the controlled property when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the propertyURI. Property definitions and relationships to other properties are also typically provided within the vocabularly accessible at the propertyURI. Software and people may be able to resolve the URI to find out the definition and retrieve additional labels and other metadata for presentation to users. example: has characteristic example: uses protocol</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- <xs:element name="valueURI" minOccurs="1" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Value URI summary: The persistent URI used to identify a value from a vocabulary. description: The URI for a value that is drawn from a controlled vocabulary such as a published ontology or controlled term list. The value represents the object of a semantic statement in which the subject is the containing element, the property is defined by the sibling propertyURI, and this valueURI element represents the object. These values should be precisely defined, including defining various relationships to related concepts. Value URIs are typically drawn from formal ontologies that provide well-defined logical semantics and provide for various types of reasoning about value equivalence and overlap. Value URIs should be persistent and unique over decades, and the meaning of the values associated with the URI should be stable over time as well. These URIs are usually constructed using an additional abstraction layer via link resolvers, rather than directly resolving to the term definition itself. Thus, when resolving the valueURI, software user agents should be prepared to follow multiple redirects before finally resolving the current location of the value definition. However, there is no requirement that valueURIs need to be resolvable, and metadata parsers should expect to find valueURIs that do not resolve and are only used as unique URIs for the value (i.e., a name) example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-characteristics.owl#Mass example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-standards.owl#Kilogram</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:anyURI">
- <xs:attribute name="label" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Value Label summary: A human readable representation of the controlled value. description: A label that provides a human readable representation of the controlled value. The label is often used to represent the controlled value when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the valueURI. Value definitions and relationships to other terms are also typically provided within the vocabularly accessible at the valueURI. Software and people can resolve the value URI to find out the definition of the value and retrieve additional labels and other metadata about the value for presentation to users. example: Mass example: Kilogram example: Net Primary Production example: Carbon example: Density</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:attribute name="label" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Property Label summary: A human readable representation of the controlled property. description: A label that provides a human readable representation of the controlled property. The label is often used to represent the controlled property when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the propertyURI. Property definitions and relationships to other properties are also typically provided within the vocabularly accessible at the propertyURI. Software and people may be able to resolve the URI to find out the definition and retrieve additional labels and other metadata for presentation to users. example: has characteristic example: uses protocol</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="label" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Value Label summary: A human readable representation of the controlled value. description: A label that provides a human readable representation of the controlled value. The label is often used to represent the controlled value when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the valueURI. Value definitions and relationships to other terms are also typically provided within the vocabularly accessible at the valueURI. Software and people can resolve the value URI to find out the definition of the value and retrieve additional labels and other metadata about the value for presentation to users. example: Mass example: Kilogram example: Net Primary Production example: Carbon example: Density</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:element name="implementation" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Implementation summary: Describes the hardware and/or operating system requirements for one implementation of a package. description: Implementation describes the hardware, operating system resources a package runs on. Note, a package can have multiple implementations. So for example, a package may be written in java and the package may run on numerous hardware and/or operating systems like Pentium/Linux, Pentium/NT and so on. Hardware and Software descriptions that have different requirements can be placed here. example: Please see the examples for each sub-element of the implementation type.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="distribution" type="phys:PhysicalDistributionType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Distribution summary: Information on how the resource is distributed online and offline description: This field provides information on how the resource is distributed online and offline. Connections to online systems can be described as URLs and as a list of relevant connection parameters.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="size" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Size summary: Physical size of an implementation. description: The physical size of an implementation on disk. example: 100 Megabytes</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="language" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: International Language summary: The International Language of the software implementation. description: The International Language of the software implementation.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="LanguageValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Language Value summary: The actual value for the language or a code for the language. description: The actual value for the language or a code for the language. example: english example: eng</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="LanguageCodeStandard" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Language Code Standard summary: The International Language Code being used in the field languageValue. description: The International Language Code being used in the field languageValue. See http://www.loc.gov/standards/iso639-2/ example: ISO639-2</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="operatingSystem" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Operating System summary: The operating system(s) an implementation runs on. description: The operating system(s) an implementation runs on. example: Linux example: Windows 95 example: Windows NT4 example: Windows XP example: Sun Solaris 2.8 example: Mac OS X</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="machineProcessor" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Machine Processor summary: The machine processor(s) required for executing the implementation. description: The Machine Processor required for executing the implementation. example: Pentium II example: Intel 486 example: SUN Sparc example: Motorola</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="virtualMachine" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Virtual Machine summary: The virtual machine that the implementation requires. description: The virtual machine that the implementation requires. example: Java Virtual Machine 1.2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="diskUsage" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Disk Usage summary: The minimum amount of Disk Space required to install this implementation. description: The minimum amount of Disk Space required to install this implementation. example: 220 Megabytes example: 15 MB example: 100 kB</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="runtimeMemoryUsage" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Runtime Memory Usage summary: The minimum amount of memory required to run an implementation. description: The minimum amount of memory required to run an implementation. example: 32 Megabytes example: 128 MB</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="programmingLanguage" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Programming Language summary: The computer programming language the software package was programmed in. description: The computer programming language the software package was programmed in. example: C++ example: Java example: C example: C# example: Perl example: Cobol example: Fortran example: Lisp example: Visual Basic example: VBA example: Bourne Shell Script</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="checksum" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Checksum summary: The generated checksum value of a software package that is a self-contained module. description: The generated checksum value of a software package that is a self-contained module. example: $sum software.jar 27021 22660</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dependency" type="DependencyType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: dependency summary: This fields documents any dependencies that this implementation might have. description: This fields documents any dependencies that this implementation might have.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -948,25 +815,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="distribution" type="phys:PhysicalDistributionType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Distribution summary: Information on how the resource is distributed online and offline description: This field provides information on how the resource is distributed online and offline. Connections to online systems can be described as URLs and as a list of relevant connection parameters.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1078,25 +926,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="size" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Size summary: Physical size of an implementation. description: The physical size of an implementation on disk. example: 100 Megabytes</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1210,39 +1039,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="language" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: International Language summary: The International Language of the software implementation. description: The International Language of the software implementation.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="LanguageValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Language Value summary: The actual value for the language or a code for the language. description: The actual value for the language or a code for the language. example: english example: eng</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="LanguageCodeStandard" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Language Code Standard summary: The International Language Code being used in the field languageValue. description: The International Language Code being used in the field languageValue. See http://www.loc.gov/standards/iso639-2/ example: ISO639-2</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1352,25 +1148,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="LanguageValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Language Value summary: The actual value for the language or a code for the language. description: The actual value for the language or a code for the language. example: english example: eng</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1483,25 +1260,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="LanguageCodeStandard" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Language Code Standard summary: The International Language Code being used in the field languageValue. description: The International Language Code being used in the field languageValue. See http://www.loc.gov/standards/iso639-2/ example: ISO639-2</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1627,25 +1385,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="operatingSystem" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Operating System summary: The operating system(s) an implementation runs on. description: The operating system(s) an implementation runs on. example: Linux example: Windows 95 example: Windows NT4 example: Windows XP example: Sun Solaris 2.8 example: Mac OS X</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1767,25 +1506,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="machineProcessor" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Machine Processor summary: The machine processor(s) required for executing the implementation. description: The Machine Processor required for executing the implementation. example: Pentium II example: Intel 486 example: SUN Sparc example: Motorola</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1897,25 +1617,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="virtualMachine" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Virtual Machine summary: The virtual machine that the implementation requires. description: The virtual machine that the implementation requires. example: Java Virtual Machine 1.2</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2031,25 +1732,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="diskUsage" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Disk Usage summary: The minimum amount of Disk Space required to install this implementation. description: The minimum amount of Disk Space required to install this implementation. example: 220 Megabytes example: 15 MB example: 100 kB</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2163,25 +1845,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="runtimeMemoryUsage" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Runtime Memory Usage summary: The minimum amount of memory required to run an implementation. description: The minimum amount of memory required to run an implementation. example: 32 Megabytes example: 128 MB</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2317,25 +1980,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="programmingLanguage" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Programming Language summary: The computer programming language the software package was programmed in. description: The computer programming language the software package was programmed in. example: C++ example: Java example: C example: C# example: Perl example: Cobol example: Fortran example: Lisp example: Visual Basic example: VBA example: Bourne Shell Script</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2447,25 +2091,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="checksum" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Checksum summary: The generated checksum value of a software package that is a self-contained module. description: The generated checksum value of a software package that is a self-contained module. example: $sum software.jar 27021 22660</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2584,25 +2209,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dependency" type="DependencyType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: dependency summary: This fields documents any dependencies that this implementation might have. description: This fields documents any dependencies that this implementation might have.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2714,25 +2320,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="action" type="Action">
- <xs:annotation>
- <xs:documentation>tooltip: Action summary: Describes what action needs to be undertaken (if any) for a software dependency at either the software package or implementation level. description: This element and its enumerations of assert and install can be used as commands by a software application to carry out these actions on software package dependencies. This is a change from how we have used all previous elements within eml. Up until now all other elements have been simply metadata designed to describe data, literature citations, etc... with the Action element we can use this module as a command to carry out the action.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2918,21 +2505,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="software" type="SoftwareType"/>
-
-
-
-
-
@@ -3051,25 +2623,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dependency" type="DependencyType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: dependency summary: This fields documents any dependencies that this software package in general might have. description: This fields documents any dependencies that this software package in general might have.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3173,25 +2726,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="licenseURL" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: URL for License summary: URL where the license can be found description: URL where the license can be found</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3295,25 +2829,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="license" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: License summary: Text of the license description: Text of the license</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3419,25 +2934,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="version" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Version summary: Version of the software being packaged. description: String value corresponding to the major, minor, custom, and build version.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3619,25 +3115,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="project" type="proj:ResearchProjectType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: project descriptor summary: description: This field is a description of the project with which this software product is related. Please see the eml-project module for more information.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3854,25 +3331,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="software" type="SoftwareType">
- <xs:annotation>
- <xs:documentation>tooltip: Software Package summary: Defines a software distribution and all of its dependent software. description: The software element contains general information about a software resource that is being documented. This field is intended to give information for software tools that are needed to interpret a dataset, software that was written to process a resource, or software as a resource in itself. It is based on eml-resource and Open Software Description (OSD) a W3C submission. There can be multiple implementations within a software package because a physical software package can run on multiple hardware and/or operating systems. See implementation element documentation for a more thorough explanation.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="SoftwareType">
- <xs:choice>
- <xs:sequence>
- <xs:group ref="res:ResourceGroup"/>
- <xs:element name="implementation" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Implementation summary: Describes the hardware and/or operating system requirements for one implementation of a package. description: Implementation describes the hardware, operating system resources a package runs on. Note, a package can have multiple implementations. So for example, a package may be written in java and the package may run on numerous hardware and/or operating systems like Pentium/Linux, Pentium/NT and so on. Hardware and Software descriptions that have different requirements can be placed here. example: Please see the examples for each sub-element of the implementation type.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="distribution" type="phys:PhysicalDistributionType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Distribution summary: Information on how the resource is distributed online and offline description: This field provides information on how the resource is distributed online and offline. Connections to online systems can be described as URLs and as a list of relevant connection parameters.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="size" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Physical Size summary: Physical size of an implementation. description: The physical size of an implementation on disk. example: 100 Megabytes</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="language" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: International Language summary: The International Language of the software implementation. description: The International Language of the software implementation.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="LanguageValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Language Value summary: The actual value for the language or a code for the language. description: The actual value for the language or a code for the language. example: english example: eng</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="LanguageCodeStandard" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Language Code Standard summary: The International Language Code being used in the field languageValue. description: The International Language Code being used in the field languageValue. See http://www.loc.gov/standards/iso639-2/ example: ISO639-2</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="operatingSystem" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Operating System summary: The operating system(s) an implementation runs on. description: The operating system(s) an implementation runs on. example: Linux example: Windows 95 example: Windows NT4 example: Windows XP example: Sun Solaris 2.8 example: Mac OS X</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="machineProcessor" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Machine Processor summary: The machine processor(s) required for executing the implementation. description: The Machine Processor required for executing the implementation. example: Pentium II example: Intel 486 example: SUN Sparc example: Motorola</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="virtualMachine" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Virtual Machine summary: The virtual machine that the implementation requires. description: The virtual machine that the implementation requires. example: Java Virtual Machine 1.2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="diskUsage" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Disk Usage summary: The minimum amount of Disk Space required to install this implementation. description: The minimum amount of Disk Space required to install this implementation. example: 220 Megabytes example: 15 MB example: 100 kB</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="runtimeMemoryUsage" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Runtime Memory Usage summary: The minimum amount of memory required to run an implementation. description: The minimum amount of memory required to run an implementation. example: 32 Megabytes example: 128 MB</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="programmingLanguage" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Programming Language summary: The computer programming language the software package was programmed in. description: The computer programming language the software package was programmed in. example: C++ example: Java example: C example: C# example: Perl example: Cobol example: Fortran example: Lisp example: Visual Basic example: VBA example: Bourne Shell Script</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="checksum" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Checksum summary: The generated checksum value of a software package that is a self-contained module. description: The generated checksum value of a software package that is a self-contained module. example: $sum software.jar 27021 22660</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dependency" type="DependencyType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: dependency summary: This fields documents any dependencies that this implementation might have. description: This fields documents any dependencies that this implementation might have.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="dependency" type="DependencyType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: dependency summary: This fields documents any dependencies that this software package in general might have. description: This fields documents any dependencies that this software package in general might have.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice minOccurs="0" maxOccurs="unbounded">
- <xs:element name="licenseURL" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: URL for License summary: URL where the license can be found description: URL where the license can be found</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="license" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: License summary: Text of the license description: Text of the license</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:element name="version" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Version summary: Version of the software being packaged. description: String value corresponding to the major, minor, custom, and build version.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="project" type="proj:ResearchProjectType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: project descriptor summary: description: This field is a description of the project with which this software product is related. Please see the eml-project module for more information.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="DependencyType">
- <xs:annotation>
- <xs:documentation>tooltip: Dependency summary: Dependency describes the software package(s) that the software package is dependent upon. description: The dependency element is recursive. It is a sub-element of the software Element but it also has as a sub-element its parent element Software Package. Dependency has been made optional because to make it mandatory does not allow the recursion to end. Dependency has also been made a sub-element of implementation because there can be both implementation and package level dependencies within a package.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="action" type="Action">
- <xs:annotation>
- <xs:documentation>tooltip: Action summary: Describes what action needs to be undertaken (if any) for a software dependency at either the software package or implementation level. description: This element and its enumerations of assert and install can be used as commands by a software application to carry out these actions on software package dependencies. This is a change from how we have used all previous elements within eml. Up until now all other elements have been simply metadata designed to describe data, literature citations, etc... with the Action element we can use this module as a command to carry out the action.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="software" type="SoftwareType"/>
- </xs:sequence>
-</xs:complexType>
<xs:simpleType name="Action">
- <xs:annotation>
- <xs:documentation>tooltip: Action summary: Describes what action needs to be undertaken (if any) for a software dependency at either the software package or implementation level. description: This element and its enumerations of assert and install can be used as commands by a software application to carry out these actions on software package dependencies. This is a change from how we have used all previous elements within eml. Up until now all other elements have been simply metadata designed to describe data, literature citations, etc... with the Action element we can use this module as a command to carry out the action.</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:enumeration value="install"/>
- <xs:enumeration value="assert"/>
- </xs:restriction>
-</xs:simpleType>
<xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1053,25 +951,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: Description of any relational constraints on this entity. description: Description of any relational constraints on this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1240,25 +1119,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="spatialReference" type="spref:SpatialReferenceType">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial Reference summary: The means by which positional information in this entity is related to points on the earth's surface. description: Spatial Referencing systems define the coordinates used to describe horizontal and vertical locations. These are typically either geographic, projected planar, or arbitrary planar.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1370,139 +1230,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="georeferenceInfo" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Georeferenc information summary: Information on how to position the grid within the coordinate system defined in the spatial reference module. description: Information on how to position the grid within the coordinate system defined in the spatial reference module.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="cornerPoint" maxOccurs="4">
- <xs:annotation>
- <xs:documentation>tooltip: Corner point summary: Location of a corner on a rectified grid within the coordinate system. description: Location of a corner on the coordinate system defined in the spatial reference module. Use this element when the rows and columns of the grid are aligned with the coordinate system. One or more corner points are needed to locate a rectified grid.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="xCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pointInPixel">
- <xs:annotation>
- <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point. example: upperLeft</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="upperLeft"/>
- <xs:enumeration value="upperRight"/>
- <xs:enumeration value="lowerRight"/>
- <xs:enumeration value="lowerLeft"/>
- <xs:enumeration value="center"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="corner" type="rasterOriginType">
- <xs:annotation>
- <xs:documentation>tooltip: Corner summary: Identification of the corner in the grid corresponding to the coordinates provided. description: Identification of the corner in the grid corresponding to the coordinates provided. example: Upper Left</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="controlPoint" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Georeference Point summary: A point defined in both grid cell and georeferenced coordinates that is used to position the raster grid within the coordinate system defined in the spatialReference modoule. description: If the grid is rectified to the coordinate system, then a single point may be used to position the grid. Otherwise, a series of points is necessary to fit the grid to the coordinate system.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="column" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Column summary: Column location of the georeferencing point in the grid. description: Column location of the georeferencing point indicated as the nth column counting the cell indicated in rasterOrigin as column 1. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="row" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Row summary: Row location of the georeferencing point in the grid. description: Row location of the georeferencing point indicated as the nth row counting the cell indicated in rasterOrigin as row 1. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="xCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pointInPixel">
- <xs:annotation>
- <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point. example: upperLeft</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="upperLeft"/>
- <xs:enumeration value="upperRight"/>
- <xs:enumeration value="lowerRight"/>
- <xs:enumeration value="lowerLeft"/>
- <xs:enumeration value="center"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="bilinearFit">
- <xs:annotation>
- <xs:documentation>tooltip: Bilinear Fit summary: Terms of a bilinear model to fit the grid to the coordinate system. description: Intercept and slope terms to describe the orientation and position of the grid to the coordinate system based on corner point identified in the rasterOrigin element. defined in the spatial Reference module.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="xIntercept" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X Intercept summary: Location of the rasterOrigin point on the x axis of the the coordinate system. description: X Intercept of the rasterOrigin point within the coordinate system. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="xSlope" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into x coordinates. description: Slope describing transformation of grid cell distances into x coordinates. example: 5.0123</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yIntercept" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y Intercept summary: Location of the rasterOrigin point on the y axis of the the coordinate system. description: Location of the rasterOrigin point on the y axis of the the coordinate system. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="ySlope" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into y axis coordinates. description: Slope describing transformation of grid cell distances into y axis coordinates. example: 5.0123</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1618,58 +1345,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="cornerPoint" maxOccurs="4">
- <xs:annotation>
- <xs:documentation>tooltip: Corner point summary: Location of a corner on a rectified grid within the coordinate system. description: Location of a corner on the coordinate system defined in the spatial reference module. Use this element when the rows and columns of the grid are aligned with the coordinate system. One or more corner points are needed to locate a rectified grid.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="xCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pointInPixel">
- <xs:annotation>
- <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point. example: upperLeft</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="upperLeft"/>
- <xs:enumeration value="upperRight"/>
- <xs:enumeration value="lowerRight"/>
- <xs:enumeration value="lowerLeft"/>
- <xs:enumeration value="center"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="corner" type="rasterOriginType">
- <xs:annotation>
- <xs:documentation>tooltip: Corner summary: Identification of the corner in the grid corresponding to the coordinates provided. description: Identification of the corner in the grid corresponding to the coordinates provided. example: Upper Left</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1751,25 +1426,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="xCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 455000</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1850,25 +1506,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="yCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 3455000</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1994,34 +1631,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="pointInPixel">
- <xs:annotation>
- <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point. example: upperLeft</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="upperLeft"/>
- <xs:enumeration value="upperRight"/>
- <xs:enumeration value="lowerRight"/>
- <xs:enumeration value="lowerLeft"/>
- <xs:enumeration value="center"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -2144,25 +1753,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="corner" type="rasterOriginType">
- <xs:annotation>
- <xs:documentation>tooltip: Corner summary: Identification of the corner in the grid corresponding to the coordinates provided. description: Identification of the corner in the grid corresponding to the coordinates provided. example: Upper Left</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2280,63 +1870,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="controlPoint" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Georeference Point summary: A point defined in both grid cell and georeferenced coordinates that is used to position the raster grid within the coordinate system defined in the spatialReference modoule. description: If the grid is rectified to the coordinate system, then a single point may be used to position the grid. Otherwise, a series of points is necessary to fit the grid to the coordinate system.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="column" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Column summary: Column location of the georeferencing point in the grid. description: Column location of the georeferencing point indicated as the nth column counting the cell indicated in rasterOrigin as column 1. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="row" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Row summary: Row location of the georeferencing point in the grid. description: Row location of the georeferencing point indicated as the nth row counting the cell indicated in rasterOrigin as row 1. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="xCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pointInPixel">
- <xs:annotation>
- <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point. example: upperLeft</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="upperLeft"/>
- <xs:enumeration value="upperRight"/>
- <xs:enumeration value="lowerRight"/>
- <xs:enumeration value="lowerLeft"/>
- <xs:enumeration value="center"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2416,25 +1949,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="column" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Column summary: Column location of the georeferencing point in the grid. description: Column location of the georeferencing point indicated as the nth column counting the cell indicated in rasterOrigin as column 1. example: 1</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2514,25 +2028,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="row" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Row summary: Row location of the georeferencing point in the grid. description: Row location of the georeferencing point indicated as the nth row counting the cell indicated in rasterOrigin as row 1. example: 1</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2613,25 +2108,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="xCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 455000</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2713,25 +2189,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="yCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 3455000</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2857,34 +2314,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="pointInPixel">
- <xs:annotation>
- <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point. example: upperLeft</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="upperLeft"/>
- <xs:enumeration value="upperRight"/>
- <xs:enumeration value="lowerRight"/>
- <xs:enumeration value="lowerLeft"/>
- <xs:enumeration value="center"/>
- </xs:restriction>
- </xs:simpleType>
-</xs:element>
-
-
-
-
-
@@ -2995,49 +2424,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="bilinearFit">
- <xs:annotation>
- <xs:documentation>tooltip: Bilinear Fit summary: Terms of a bilinear model to fit the grid to the coordinate system. description: Intercept and slope terms to describe the orientation and position of the grid to the coordinate system based on corner point identified in the rasterOrigin element. defined in the spatial Reference module.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="xIntercept" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X Intercept summary: Location of the rasterOrigin point on the x axis of the the coordinate system. description: X Intercept of the rasterOrigin point within the coordinate system. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="xSlope" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into x coordinates. description: Slope describing transformation of grid cell distances into x coordinates. example: 5.0123</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yIntercept" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y Intercept summary: Location of the rasterOrigin point on the y axis of the the coordinate system. description: Location of the rasterOrigin point on the y axis of the the coordinate system. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="ySlope" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into y axis coordinates. description: Slope describing transformation of grid cell distances into y axis coordinates. example: 5.0123</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3118,25 +2504,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="xIntercept" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X Intercept summary: Location of the rasterOrigin point on the x axis of the the coordinate system. description: X Intercept of the rasterOrigin point within the coordinate system. example: 3455000</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3217,25 +2584,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="xSlope" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into x coordinates. description: Slope describing transformation of grid cell distances into x coordinates. example: 5.0123</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3316,25 +2664,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="yIntercept" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y Intercept summary: Location of the rasterOrigin point on the y axis of the the coordinate system. description: Location of the rasterOrigin point on the y axis of the the coordinate system. example: 455000</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3415,25 +2744,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="ySlope" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into y axis coordinates. description: Slope describing transformation of grid cell distances into y axis coordinates. example: 5.0123</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3545,25 +2855,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="horizontalAccuracy" type="DataQuality">
- <xs:annotation>
- <xs:documentation>tooltip: Horizontal Accuracy summary: The accuracy of horizontal locational measurements within the data. description: Horizontal accuracy may be reported either as a quantitative estimate expressed in the units of the coordinate system or as a text assessment.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3667,25 +2958,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="accuracyReport" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Accuracy Report summary: A qualitative statement about the accuracy of the data. description: A text statement of the data quality, included the means by which it was determined.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3798,39 +3070,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quantitativeAccuracyReport" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Report summary: A quantitative assessment of the data quality. description: A quantitative assessment of the data quality expressed as a value and the method of its determination.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed. example: 4.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment. example: Error expressed as root mean square of 5 control points.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3937,25 +3176,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed. example: 4.5</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4062,25 +3282,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment. example: Error expressed as root mean square of 5 control points.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4192,25 +3393,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="verticalAccuracy" type="DataQuality">
- <xs:annotation>
- <xs:documentation>tooltip: Vertical Accuracy summary: The accuracy of vertical locational measurements within the data. description: Vertical accuracy may be reported either as a quantitative estimate expressed in the units of the height or depth measurement system or as a text assessment.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4270,25 +3452,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="cellSizeXDirection">
- <xs:annotation>
- <xs:documentation>tooltip: Cell Size X Direction summary: The width of the cell in the x direction. description: Cell sizes should be expressed in the units declared in the spatialReference module. example: 28.5</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4348,25 +3511,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="cellSizeYDirection">
- <xs:annotation>
- <xs:documentation>tooltip: Cell Size Y Direction summary: The width of the cell in the x direction. description: Cell sizes should be expressed in the units declared in the spatialReference module. example: 28.5</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4426,25 +3570,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="numberOfBands">
- <xs:annotation>
- <xs:documentation>tooltip: Number Of Bands summary: The number of bands in the image. description: Image data may have more than one sensor band represented for each pixel. example: 7</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4567,25 +3692,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="rasterOrigin" type="rasterOriginType">
- <xs:annotation>
- <xs:documentation>tooltip: Raster Origin summary: The corner location of the pixel having the minimum x and y values description: Identification the corner of the grid where the first values for both the x and y axes begin in the file. example: Upper Left</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4693,25 +3799,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="rows" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Rows summary: Maximum number of raster objects along the ordinate (y) axis description: Maximum number of raster objects along the ordinate (y) axis example: 455</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4819,25 +3906,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="columns" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Columns summary: Maximum number of raster objects along the abscissa (x) axis description: Maximum number of raster objects along the abscissa (x) axis example: 455</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4896,25 +3964,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="verticals">
- <xs:annotation>
- <xs:documentation>tooltip: Verticals summary: Maximum number of raster objects along the vertical (z) axis description: Maximum number of raster objects along the vertical (z) axis.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5021,25 +4070,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="cellGeometry" type="CellGeometryType">
- <xs:annotation>
- <xs:documentation>tooltip: Cell Geometry summary: Geometric representation of the cell's content. description: Indication of whether the cell value is representative of a single point(matrix) within the cell or the entire cell (pixel) example: pixel</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5124,25 +4154,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="toneGradation" type="xs:integer" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Tone Gradation summary: Number of colors present in the image. description: Number of colors present in the image. example: 255</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5256,25 +4267,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="scaleFactor" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Scale Factor summary: The value used for scaling the source raster. description: The scale factor is used for raster-rescaling operations, where the following operation is applied to each pixel in the data in the source: rescaled=(source*scaleFactor)+offset. example: 2</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5388,25 +4380,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="offset" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Offset summary: The offset value used for scaling the source raster. description: The offset is used for raster-rescaling operations, where the following operation is applied to each pixel in the data in the source: rescaled=(source*scaleFactor)+offset. example: 20</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5541,99 +4514,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="imageDescription" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Image Description summary: Detailed information for data derived from image sensors. description: Provides information about the image's suitability for use, sensor properties, and individual band descriptions.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="illuminationElevationAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Illumination Elevation Angle summary: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface. description: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface. example: 45.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="illuminationAzimuthAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Illumination Azimuth Angle summary: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken. description: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken. example: 45.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="imageOrientationAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Image Orientation Angle summary: Angle from the first row of the image to true north in degrees, clockwise. description: Angle from the first row of the image to true north in degrees, clockwise. example: 45.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="imagingCondition" type="ImagingConditionCode" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Imaging Condition summary: Code which indicates conditions which affect the quality of the image. description: Code which indicates conditions which affect the quality of the image. example: cloud</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="imageQualityCode" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Image Quality Code summary: Specifies the image quality. description: Specifies the image quality. example: Excellent</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="cloudCoverPercentage" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Cloud Cover Percentage summary: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent. description: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent. example: 12</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="preProcessingTypeCode" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Preprocessing Type Code summary: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image. description: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image. example: LEVELl1A, SPOTVIEWORTHO</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="compressionGenerationQuality" type="xs:integer" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Compression Generation Quality summary: Counts the number of lossy compression cycles performed on the image. description: Counts the number of lossy compression cycles performed on the image. example: 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="triangulationIndicator" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Triangulation Indicator summary: Code which indicates whether or not triangulation has been performed upon the image. description: Code which indicates whether or not triangulation has been performed upon the image. example: false</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="radiometricDataAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Radiometric Data Availability summary: Code which indicates whether or not Standard Radiometric Product data is available. description: Code which indicates whether or not Standard Radiometric Product data is available. example: false</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="cameraCalibrationInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Camera Calibration Information Availability summary: Code which indicates whether or not constants are available which allow for camera calibration corrections. description: Code which indicates whether or not constants are available which allow for camera calibration corrections. example: false</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="filmDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Film Distortion Information Availability summary: Code which indicates whether or not Calibration Reseau information is available description: Code which indicates whether or not Calibration Reseau information is available example: true</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="lensDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Lens Distortion Information Availability summary: Code which indicates whether or not lens aberration correction information is available description: Code which indicates whether or not lens aberration correction information is available example: true</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bandDescription" type="BandType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Band Description summary: Description of the wavelength domain that the sensor operates in. description: Description of the wavelength domain that the sensor operates in</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -5722,25 +4602,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="illuminationElevationAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Illumination Elevation Angle summary: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface. description: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface. example: 45.5</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5827,25 +4688,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="illuminationAzimuthAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Illumination Azimuth Angle summary: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken. description: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken. example: 45.5</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -5930,25 +4772,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="imageOrientationAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Image Orientation Angle summary: Angle from the first row of the image to true north in degrees, clockwise. description: Angle from the first row of the image to true north in degrees, clockwise. example: 45.5</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6123,25 +4946,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="imagingCondition" type="ImagingConditionCode" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Imaging Condition summary: Code which indicates conditions which affect the quality of the image. description: Code which indicates conditions which affect the quality of the image. example: cloud</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:element name="cloudCoverPercentage" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Cloud Cover Percentage summary: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent. description: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent. example: 12</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6489,25 +5255,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="preProcessingTypeCode" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Preprocessing Type Code summary: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image. description: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image. example: LEVELl1A, SPOTVIEWORTHO</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6592,25 +5339,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="compressionGenerationQuality" type="xs:integer" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Compression Generation Quality summary: Counts the number of lossy compression cycles performed on the image. description: Counts the number of lossy compression cycles performed on the image. example: 2</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6697,25 +5425,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="triangulationIndicator" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Triangulation Indicator summary: Code which indicates whether or not triangulation has been performed upon the image. description: Code which indicates whether or not triangulation has been performed upon the image. example: false</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6801,25 +5510,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="radiometricDataAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Radiometric Data Availability summary: Code which indicates whether or not Standard Radiometric Product data is available. description: Code which indicates whether or not Standard Radiometric Product data is available. example: false</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -6907,25 +5597,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="cameraCalibrationInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Camera Calibration Information Availability summary: Code which indicates whether or not constants are available which allow for camera calibration corrections. description: Code which indicates whether or not constants are available which allow for camera calibration corrections. example: false</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7012,25 +5683,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="filmDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Film Distortion Information Availability summary: Code which indicates whether or not Calibration Reseau information is available description: Code which indicates whether or not Calibration Reseau information is available example: true</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7118,25 +5770,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="lensDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Lens Distortion Information Availability summary: Code which indicates whether or not lens aberration correction information is available description: Code which indicates whether or not lens aberration correction information is available example: true</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7261,25 +5894,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="bandDescription" type="BandType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Band Description summary: Description of the wavelength domain that the sensor operates in. description: Description of the wavelength domain that the sensor operates in</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7391,25 +6005,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="sequenceIdentifier" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Sequence Identifier summary: Number that uniquely identifies instances of bands of wavelengths on which a sensor operates. description: Number that uniquely identifies instances of bands of wavelengths on which a sensor operates. example: 3</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7494,25 +6089,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="highWavelength" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: High Wavelength summary: Highest wavelength that the sensor is capable of collecting within a designated band in metres. description: Highest wavelength that the sensor is capable of collecting within a designated band. example: 2.456</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7597,25 +6173,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="lowWaveLength" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Low Wavelength summary: Lowest wavelength that the sensor is capable of collecting within a designated band in metres. description: Lowest wavelength that the sensor is capable of collecting within a designated band. example: 0.1234</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7874,25 +6431,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="waveLengthUnits" type="spref:lengthUnits" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Wave Length Units summary: Units in which the sensor wavelegths are expressed. description: Units of measure for the wavelength at which the sensor collected the data. example: microns</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -7965,25 +6503,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="peakResponse" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Peak Response summary: Wavelength at which the response is the highest. description:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -8205,25 +6724,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="spatialRaster" type="SpatialRasterType">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial Raster summary: Description of a GIS layer composed of raster pixels. description: Description of a GIS layer composed of raster pixels comprising a regular-pattern grid. Generally, a raster object may be thought of as a pattern of closely spaced rows of dots that collectively form an image. Raster spatial objects are used to locate zero-, two-, or three-dimensional locations in the dataset example: An interpolated grid of irregularly spaced data is an example of this element.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="SpatialRasterType">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial Raster Type summary: description:</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:group ref="ent:EntityGroup"/>
- <xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: Description of any relational constraints on this entity. description: Description of any relational constraints on this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="spatialReference" type="spref:SpatialReferenceType">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial Reference summary: The means by which positional information in this entity is related to points on the earth's surface. description: Spatial Referencing systems define the coordinates used to describe horizontal and vertical locations. These are typically either geographic, projected planar, or arbitrary planar.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="georeferenceInfo" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Georeferenc information summary: Information on how to position the grid within the coordinate system defined in the spatial reference module. description: Information on how to position the grid within the coordinate system defined in the spatial reference module.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice>
- <xs:element name="cornerPoint" maxOccurs="4">
- <xs:annotation>
- <xs:documentation>tooltip: Corner point summary: Location of a corner on a rectified grid within the coordinate system. description: Location of a corner on the coordinate system defined in the spatial reference module. Use this element when the rows and columns of the grid are aligned with the coordinate system. One or more corner points are needed to locate a rectified grid.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="xCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pointInPixel">
- <xs:annotation>
- <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point. example: upperLeft</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="upperLeft"/>
- <xs:enumeration value="upperRight"/>
- <xs:enumeration value="lowerRight"/>
- <xs:enumeration value="lowerLeft"/>
- <xs:enumeration value="center"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- <xs:element name="corner" type="rasterOriginType">
- <xs:annotation>
- <xs:documentation>tooltip: Corner summary: Identification of the corner in the grid corresponding to the coordinates provided. description: Identification of the corner in the grid corresponding to the coordinates provided. example: Upper Left</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="controlPoint" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Georeference Point summary: A point defined in both grid cell and georeferenced coordinates that is used to position the raster grid within the coordinate system defined in the spatialReference modoule. description: If the grid is rectified to the coordinate system, then a single point may be used to position the grid. Otherwise, a series of points is necessary to fit the grid to the coordinate system.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="column" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Column summary: Column location of the georeferencing point in the grid. description: Column location of the georeferencing point indicated as the nth column counting the cell indicated in rasterOrigin as column 1. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="row" type="xs:int">
- <xs:annotation>
- <xs:documentation>tooltip: Row summary: Row location of the georeferencing point in the grid. description: Row location of the georeferencing point indicated as the nth row counting the cell indicated in rasterOrigin as row 1. example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="xCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yCoordinate" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="pointInPixel">
- <xs:annotation>
- <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point. example: upperLeft</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="upperLeft"/>
- <xs:enumeration value="upperRight"/>
- <xs:enumeration value="lowerRight"/>
- <xs:enumeration value="lowerLeft"/>
- <xs:enumeration value="center"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="bilinearFit">
- <xs:annotation>
- <xs:documentation>tooltip: Bilinear Fit summary: Terms of a bilinear model to fit the grid to the coordinate system. description: Intercept and slope terms to describe the orientation and position of the grid to the coordinate system based on corner point identified in the rasterOrigin element. defined in the spatial Reference module.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="xIntercept" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X Intercept summary: Location of the rasterOrigin point on the x axis of the the coordinate system. description: X Intercept of the rasterOrigin point within the coordinate system. example: 3455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="xSlope" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into x coordinates. description: Slope describing transformation of grid cell distances into x coordinates. example: 5.0123</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="yIntercept" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Y Intercept summary: Location of the rasterOrigin point on the y axis of the the coordinate system. description: Location of the rasterOrigin point on the y axis of the the coordinate system. example: 455000</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="ySlope" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into y axis coordinates. description: Slope describing transformation of grid cell distances into y axis coordinates. example: 5.0123</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- <xs:element name="horizontalAccuracy" type="DataQuality">
- <xs:annotation>
- <xs:documentation>tooltip: Horizontal Accuracy summary: The accuracy of horizontal locational measurements within the data. description: Horizontal accuracy may be reported either as a quantitative estimate expressed in the units of the coordinate system or as a text assessment.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="verticalAccuracy" type="DataQuality">
- <xs:annotation>
- <xs:documentation>tooltip: Vertical Accuracy summary: The accuracy of vertical locational measurements within the data. description: Vertical accuracy may be reported either as a quantitative estimate expressed in the units of the height or depth measurement system or as a text assessment.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="cellSizeXDirection">
- <xs:annotation>
- <xs:documentation>tooltip: Cell Size X Direction summary: The width of the cell in the x direction. description: Cell sizes should be expressed in the units declared in the spatialReference module. example: 28.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="cellSizeYDirection">
- <xs:annotation>
- <xs:documentation>tooltip: Cell Size Y Direction summary: The width of the cell in the x direction. description: Cell sizes should be expressed in the units declared in the spatialReference module. example: 28.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="numberOfBands">
- <xs:annotation>
- <xs:documentation>tooltip: Number Of Bands summary: The number of bands in the image. description: Image data may have more than one sensor band represented for each pixel. example: 7</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="rasterOrigin" type="rasterOriginType">
- <xs:annotation>
- <xs:documentation>tooltip: Raster Origin summary: The corner location of the pixel having the minimum x and y values description: Identification the corner of the grid where the first values for both the x and y axes begin in the file. example: Upper Left</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="rows" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Rows summary: Maximum number of raster objects along the ordinate (y) axis description: Maximum number of raster objects along the ordinate (y) axis example: 455</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="columns" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Columns summary: Maximum number of raster objects along the abscissa (x) axis description: Maximum number of raster objects along the abscissa (x) axis example: 455</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="verticals">
- <xs:annotation>
- <xs:documentation>tooltip: Verticals summary: Maximum number of raster objects along the vertical (z) axis description: Maximum number of raster objects along the vertical (z) axis.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="cellGeometry" type="CellGeometryType">
- <xs:annotation>
- <xs:documentation>tooltip: Cell Geometry summary: Geometric representation of the cell's content. description: Indication of whether the cell value is representative of a single point(matrix) within the cell or the entire cell (pixel) example: pixel</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="toneGradation" type="xs:integer" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Tone Gradation summary: Number of colors present in the image. description: Number of colors present in the image. example: 255</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="scaleFactor" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Scale Factor summary: The value used for scaling the source raster. description: The scale factor is used for raster-rescaling operations, where the following operation is applied to each pixel in the data in the source: rescaled=(source*scaleFactor)+offset. example: 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="offset" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Offset summary: The offset value used for scaling the source raster. description: The offset is used for raster-rescaling operations, where the following operation is applied to each pixel in the data in the source: rescaled=(source*scaleFactor)+offset. example: 20</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="imageDescription" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Image Description summary: Detailed information for data derived from image sensors. description: Provides information about the image's suitability for use, sensor properties, and individual band descriptions.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="illuminationElevationAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Illumination Elevation Angle summary: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface. description: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface. example: 45.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="illuminationAzimuthAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Illumination Azimuth Angle summary: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken. description: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken. example: 45.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="imageOrientationAngle" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Image Orientation Angle summary: Angle from the first row of the image to true north in degrees, clockwise. description: Angle from the first row of the image to true north in degrees, clockwise. example: 45.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="imagingCondition" type="ImagingConditionCode" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Imaging Condition summary: Code which indicates conditions which affect the quality of the image. description: Code which indicates conditions which affect the quality of the image. example: cloud</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="imageQualityCode" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Image Quality Code summary: Specifies the image quality. description: Specifies the image quality. example: Excellent</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="cloudCoverPercentage" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Cloud Cover Percentage summary: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent. description: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent. example: 12</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="preProcessingTypeCode" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Preprocessing Type Code summary: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image. description: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image. example: LEVELl1A, SPOTVIEWORTHO</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="compressionGenerationQuality" type="xs:integer" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Compression Generation Quality summary: Counts the number of lossy compression cycles performed on the image. description: Counts the number of lossy compression cycles performed on the image. example: 2</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="triangulationIndicator" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Triangulation Indicator summary: Code which indicates whether or not triangulation has been performed upon the image. description: Code which indicates whether or not triangulation has been performed upon the image. example: false</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="radiometricDataAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Radiometric Data Availability summary: Code which indicates whether or not Standard Radiometric Product data is available. description: Code which indicates whether or not Standard Radiometric Product data is available. example: false</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="cameraCalibrationInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Camera Calibration Information Availability summary: Code which indicates whether or not constants are available which allow for camera calibration corrections. description: Code which indicates whether or not constants are available which allow for camera calibration corrections. example: false</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="filmDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Film Distortion Information Availability summary: Code which indicates whether or not Calibration Reseau information is available description: Code which indicates whether or not Calibration Reseau information is available example: true</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="lensDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Lens Distortion Information Availability summary: Code which indicates whether or not lens aberration correction information is available description: Code which indicates whether or not lens aberration correction information is available example: true</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="bandDescription" type="BandType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Band Description summary: Description of the wavelength domain that the sensor operates in. description: Description of the wavelength domain that the sensor operates in</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="DataQuality">
- <xs:annotation>
- <xs:documentation>tooltip: Data Quality Type summary: description:</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="accuracyReport" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Accuracy Report summary: A qualitative statement about the accuracy of the data. description: A text statement of the data quality, included the means by which it was determined.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quantitativeAccuracyReport" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Report summary: A quantitative assessment of the data quality. description: A quantitative assessment of the data quality expressed as a value and the method of its determination.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed. example: 4.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment. example: Error expressed as root mean square of 5 control points.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="BandType">
- <xs:annotation>
- <xs:documentation>tooltip: Band Type summary: Complex type definition for band description. description:</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="sequenceIdentifier" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Sequence Identifier summary: Number that uniquely identifies instances of bands of wavelengths on which a sensor operates. description: Number that uniquely identifies instances of bands of wavelengths on which a sensor operates. example: 3</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="highWavelength" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: High Wavelength summary: Highest wavelength that the sensor is capable of collecting within a designated band in metres. description: Highest wavelength that the sensor is capable of collecting within a designated band. example: 2.456</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="lowWaveLength" type="xs:float" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Low Wavelength summary: Lowest wavelength that the sensor is capable of collecting within a designated band in metres. description: Lowest wavelength that the sensor is capable of collecting within a designated band. example: 0.1234</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="waveLengthUnits" type="spref:lengthUnits" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Wave Length Units summary: Units in which the sensor wavelegths are expressed. description: Units of measure for the wavelength at which the sensor collected the data. example: microns</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="peakResponse" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Peak Response summary: Wavelength at which the response is the highest. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:element name="horizCoordSysDef" type="horizCoordSysType">
- <xs:annotation>
- <xs:documentation>tooltip: Horizonal Coordinate System Definition summary: The definition of a coordinate system description: Terms and parameters necessary to define a geographic or projected coordinate system for horizonal distances.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -17463,25 +15292,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="geogCoordSys" type="geogCoordSysType">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic Coordinate System summary: The coodinate system used to express the geographic coordinates. description:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -17586,28 +15396,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="datum">
- <xs:annotation>
- <xs:documentation>tooltip: Datum summary: The point on the earth representing the origin for the geographic coordinates to which the coorinate system is related to. description: example: WGS_1984</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="xs:string"/>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -17751,38 +15539,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="spheroid">
- <xs:annotation>
- <xs:documentation>tooltip: Spheroid summary: An ellipse that is used to model the earth's surface. description: An ellipse is used to define a idealized surface that ignores variation in elevation.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Spheroid name summary: The name of the spheroid. description: example: Bessel 1866</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="semiAxisMajor" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Semi-axis Major summary: The larger of two orthogonal axes that define the ellipse description: example: Meter</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="denomFlatRatio" type="xs:float"/>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -17896,40 +15652,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="primeMeridian">
- <xs:complexType>
- <xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Prime Meridian Name summary: The name of the Prime Meridian description: example: Greenwich</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="longitude" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Longitude summary: The longitude of the Prime Meridian description: example: 0.0</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:float">
- <xs:minInclusive value="-180"/>
- <xs:maxInclusive value="180"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -18045,32 +15767,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="unit">
- <xs:annotation>
- <xs:documentation>tooltip: Unit summary: The unit of angle by which coordinates are expressed. description: example: degrees</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="angleUnits" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Unit Name summary: The name of the unit of measure . description: example: Degrees</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -18174,82 +15870,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="projCoordSys">
- <xs:annotation>
- <xs:documentation>tooltip: Projected Coordinate System summary: The coodinate system used to express planar coordinates. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="geogCoordSys" type="geogCoordSysType">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic Coordinate System summary: The coodinate system used to express the geographic coordinates. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="projection">
- <xs:annotation>
- <xs:documentation>tooltip: Projection summary: The method used to tranform between geographic and planar coordinates. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="parameter" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter summary: A parameter required by the projection method. description: Most projections require one or more parameters to control the orientation and positon of the projected coordinate plane.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability. example: False_Easting</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="description" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description: example: An offset by which x origin has been adjusted, expressed in projection units</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="value" type="xs:anySimpleType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description: example: 500000</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="unit">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit summary: The unit of measure coordinates are expressed in. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="lengthUnits" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description: example: Meter</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Name summary: The name of the projection method. description: EML does not attempt to document the details of the particular projection algorithm. It is incumbent on metadata provider to ensure that the meaning of the names used to identify the method and its parameters will be as clear as possible. example: Transverse_Mercator</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -18392,25 +16012,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="geogCoordSys" type="geogCoordSysType">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic Coordinate System summary: The coodinate system used to express the geographic coordinates. description:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -18559,68 +16160,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="projection">
- <xs:annotation>
- <xs:documentation>tooltip: Projection summary: The method used to tranform between geographic and planar coordinates. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="parameter" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter summary: A parameter required by the projection method. description: Most projections require one or more parameters to control the orientation and positon of the projected coordinate plane.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability. example: False_Easting</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="description" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description: example: An offset by which x origin has been adjusted, expressed in projection units</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="value" type="xs:anySimpleType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description: example: 500000</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="unit">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit summary: The unit of measure coordinates are expressed in. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="lengthUnits" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description: example: Meter</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Name summary: The name of the projection method. description: EML does not attempt to document the details of the particular projection algorithm. It is incumbent on metadata provider to ensure that the meaning of the names used to identify the method and its parameters will be as clear as possible. example: Transverse_Mercator</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -18784,42 +16323,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="parameter" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter summary: A parameter required by the projection method. description: Most projections require one or more parameters to control the orientation and positon of the projected coordinate plane.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability. example: False_Easting</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="description" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description: example: An offset by which x origin has been adjusted, expressed in projection units</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="value" type="xs:anySimpleType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description: example: 500000</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -18933,32 +16436,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="unit">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit summary: The unit of measure coordinates are expressed in. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="lengthUnits" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description: example: Meter</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -19067,87 +16544,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="vertCoordSys" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Vertical Coordinate System Definition summary: The reference frame or system from which vertical distances (altitudes or depths) are measured. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="altitudeSysDef" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude System Definition summary: the reference frame or system from which altitudes (elevations) are measured. description: The term "altitude"' is used instead of the common term "elevation" to conform to the terminology in Federal Information Processing Standards 70-1 and 173.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="altitudeDatumName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Datum Name summary: The identification given to the surface taken as the surface of reference from which altitudes are measured. description: example: WGS_datum</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Resolution summary: The minimum distance possible between two adjacent altitude values, expressed in Altitude Distance Units of measure. description: example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeDistanceUnits" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Distance Units summary: Units in which altitude is measured. description: example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeEncodingMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Encoding Method summary: The means used to encode the altitudes. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="depthSysDef" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Depth System Definition summary: The reference frame or system from which depths are measured. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="depthDatumName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Datum Name summary: The identification given to surface of reference from which depths are measured. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="depthResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Resolution summary: The minimum distance possible between two adjacent depth values, expressed in Depth Distance Units of measure. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="depthDistanceUnits" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Distance Units summary: The units in which depths are recorded. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="depthEncodingMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Encoding Method summary: The means used to encode depths. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -19263,49 +16659,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="altitudeSysDef" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude System Definition summary: the reference frame or system from which altitudes (elevations) are measured. description: The term "altitude"' is used instead of the common term "elevation" to conform to the terminology in Federal Information Processing Standards 70-1 and 173.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="altitudeDatumName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Datum Name summary: The identification given to the surface taken as the surface of reference from which altitudes are measured. description: example: WGS_datum</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Resolution summary: The minimum distance possible between two adjacent altitude values, expressed in Altitude Distance Units of measure. description: example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeDistanceUnits" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Distance Units summary: Units in which altitude is measured. description: example: 1</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="altitudeEncodingMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Encoding Method summary: The means used to encode the altitudes. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -19413,25 +16766,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="altitudeDatumName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Datum Name summary: The identification given to the surface taken as the surface of reference from which altitudes are measured. description: example: WGS_datum</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -19543,25 +16877,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="altitudeResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Resolution summary: The minimum distance possible between two adjacent altitude values, expressed in Altitude Distance Units of measure. description: example: 1</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -19668,25 +16983,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="altitudeDistanceUnits" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Distance Units summary: Units in which altitude is measured. description: example: 1</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -19791,25 +17087,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="altitudeEncodingMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Altitude Encoding Method summary: The means used to encode the altitudes. description:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -19922,49 +17199,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="depthSysDef" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Depth System Definition summary: The reference frame or system from which depths are measured. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="depthDatumName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Datum Name summary: The identification given to surface of reference from which depths are measured. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="depthResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Resolution summary: The minimum distance possible between two adjacent depth values, expressed in Depth Distance Units of measure. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="depthDistanceUnits" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Distance Units summary: The units in which depths are recorded. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="depthEncodingMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Encoding Method summary: The means used to encode depths. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -20070,25 +17304,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="depthDatumName" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Datum Name summary: The identification given to surface of reference from which depths are measured. description:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -20198,25 +17413,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="depthResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Resolution summary: The minimum distance possible between two adjacent depth values, expressed in Depth Distance Units of measure. description:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -20321,25 +17517,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="depthDistanceUnits" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Distance Units summary: The units in which depths are recorded. description:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -20444,25 +17621,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="depthEncodingMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Depth Encoding Method summary: The means used to encode depths. description:</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -20543,31 +17701,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="projectionList">
- <xs:complexType>
- <xs:sequence>
- <xs:element name="horizCoordSysDef" type="horizCoordSysType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Horizonal Coordinate System Definition summary: The definition of a coordinate system description: Terms and parameters necessary to define a geographic or projected coordinate system for horizonal distances.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -20710,25 +17843,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="horizCoordSysDef" type="horizCoordSysType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Horizonal Coordinate System Definition summary: The definition of a coordinate system description: Terms and parameters necessary to define a geographic or projected coordinate system for horizonal distances.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="horizCoordSysType">
- <xs:choice>
- <xs:element name="geogCoordSys" type="geogCoordSysType">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic Coordinate System summary: The coodinate system used to express the geographic coordinates. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="projCoordSys">
- <xs:annotation>
- <xs:documentation>tooltip: Projected Coordinate System summary: The coodinate system used to express planar coordinates. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="geogCoordSys" type="geogCoordSysType">
- <xs:annotation>
- <xs:documentation>tooltip: Geographic Coordinate System summary: The coodinate system used to express the geographic coordinates. description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="projection">
- <xs:annotation>
- <xs:documentation>tooltip: Projection summary: The method used to tranform between geographic and planar coordinates. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="parameter" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter summary: A parameter required by the projection method. description: Most projections require one or more parameters to control the orientation and positon of the projected coordinate plane.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability. example: False_Easting</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="description" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description: example: An offset by which x origin has been adjusted, expressed in projection units</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="value" type="xs:anySimpleType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description: example: 500000</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="unit">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit summary: The unit of measure coordinates are expressed in. description:</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="lengthUnits" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description: example: Meter</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Name summary: The name of the projection method. description: EML does not attempt to document the details of the particular projection algorithm. It is incumbent on metadata provider to ensure that the meaning of the names used to identify the method and its parameters will be as clear as possible. example: Transverse_Mercator</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:attribute name="name" type="xs:string" use="required"/>
-</xs:complexType>
<xs:complexType name="geogCoordSysType">
- <xs:sequence>
- <xs:element name="datum">
- <xs:annotation>
- <xs:documentation>tooltip: Datum summary: The point on the earth representing the origin for the geographic coordinates to which the coorinate system is related to. description: example: WGS_1984</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="xs:string"/>
- </xs:complexType>
- </xs:element>
- <xs:element name="spheroid">
- <xs:annotation>
- <xs:documentation>tooltip: Spheroid summary: An ellipse that is used to model the earth's surface. description: An ellipse is used to define a idealized surface that ignores variation in elevation.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Spheroid name summary: The name of the spheroid. description: example: Bessel 1866</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="semiAxisMajor" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Semi-axis Major summary: The larger of two orthogonal axes that define the ellipse description: example: Meter</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="denomFlatRatio" type="xs:float"/>
- </xs:complexType>
- </xs:element>
- <xs:element name="primeMeridian">
- <xs:complexType>
- <xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Prime Meridian Name summary: The name of the Prime Meridian description: example: Greenwich</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="longitude" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Longitude summary: The longitude of the Prime Meridian description: example: 0.0</xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:float">
- <xs:minInclusive value="-180"/>
- <xs:maxInclusive value="180"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- <xs:element name="unit">
- <xs:annotation>
- <xs:documentation>tooltip: Unit summary: The unit of angle by which coordinates are expressed. description: example: degrees</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:attribute name="name" type="angleUnits" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Unit Name summary: The name of the unit of measure . description: example: Degrees</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="name" type="xs:string"/>
-</xs:complexType>
<xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Spheroid name summary: The name of the spheroid. description: example: Bessel 1866</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="semiAxisMajor" type="xs:float">
- <xs:annotation>
- <xs:documentation>tooltip: Semi-axis Major summary: The larger of two orthogonal axes that define the ellipse description: example: Meter</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Prime Meridian Name summary: The name of the Prime Meridian description: example: Greenwich</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="name" type="angleUnits" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Unit Name summary: The name of the unit of measure . description: example: Degrees</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="name" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability. example: False_Easting</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="description" type="xs:string" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description: example: An offset by which x origin has been adjusted, expressed in projection units</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="value" type="xs:anySimpleType" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description: example: 500000</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="name" type="lengthUnits" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description: example: Meter</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="name" type="xs:string">
- <xs:annotation>
- <xs:documentation>tooltip: Projection Name summary: The name of the projection method. description: EML does not attempt to document the details of the particular projection algorithm. It is incumbent on metadata provider to ensure that the meaning of the names used to identify the method and its parameters will be as clear as possible. example: Transverse_Mercator</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -841,25 +789,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: Description of any relational constraints on this entity. description: Description of any relational constraints on this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1015,25 +944,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="geometry" type="GeometryType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Geometry summary: Type of geometric feature(s) represented in the entity. description: Geometric feature classification is based on an enumeration of simple feature classes defined by the OpenGIS consortium and implemented in Geographic Markup Language as simple feature types. example: polygon</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1145,25 +1055,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="geometricObjectCount" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Geometric Object Count summary: Total number of the geometric objects occurring in the dataset. description: Total number of the geometric objects occurring in the dataset. example: 24</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1303,25 +1194,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="topologyLevel" type="TopologyLevel" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Topology Level summary: Code which identifies the degree of complexity. description: This element describes the relative complexity of the geometric information in the data file. example: geometryOnly</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:element name="horizontalAccuracy" type="DataQuality" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Horizontal Accuracy summary: Horizontal positional accuracy of the data description: Horizontal positional accuracy of the data expressed as either text or quantitative assessment.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1745,25 +1579,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="accuracyReport" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Accuracy Report summary: A qualitative statement about the accuracy of the data. description: A text statement of the data quality, included the means by which it was determined.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1876,39 +1691,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quantitativeAccuracyReport" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Report summary: A quantitative assessment of the data quality. description: A quantitative assessment of the data quality expressed as a value and the method of its determination.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed. example: 4.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment. example: Error expressed as root mean square of 5 control points.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2015,25 +1797,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed. example: 4.5</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2140,25 +1903,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment. example: Error expressed as root mean square of 5 control points.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2272,25 +2016,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="verticalAccuracy" type="DataQuality" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Vertical Accuracy summary: Vertical positional accuracy of the data description: Vertical positional accuracy of the data expressed as either text or quantitative assessment.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2485,25 +2210,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="spatialVector" type="SpatialVectorType">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial Vector summary: Description of a spatial data entity based on features represented by vectors description: Description of a spatial data entity based on features represented by vectors</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="SpatialVectorType">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial Vector Type summary: description:</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:group ref="ent:EntityGroup"/>
- <xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: Description of any relational constraints on this entity. description: Description of any relational constraints on this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="geometry" type="GeometryType" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Geometry summary: Type of geometric feature(s) represented in the entity. description: Geometric feature classification is based on an enumeration of simple feature classes defined by the OpenGIS consortium and implemented in Geographic Markup Language as simple feature types. example: polygon</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="geometricObjectCount" type="res:NonEmptyStringType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Geometric Object Count summary: Total number of the geometric objects occurring in the dataset. description: Total number of the geometric objects occurring in the dataset. example: 24</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="topologyLevel" type="TopologyLevel" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Topology Level summary: Code which identifies the degree of complexity. description: This element describes the relative complexity of the geometric information in the data file. example: geometryOnly</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="spatialReference" type="spref:SpatialReferenceType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Spatial Reference summary: description:</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="horizontalAccuracy" type="DataQuality" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Horizontal Accuracy summary: Horizontal positional accuracy of the data description: Horizontal positional accuracy of the data expressed as either text or quantitative assessment.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="verticalAccuracy" type="DataQuality" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Vertical Accuracy summary: Vertical positional accuracy of the data description: Vertical positional accuracy of the data expressed as either text or quantitative assessment.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="DataQuality">
- <xs:annotation>
- <xs:documentation>tooltip: Data Quality Type summary: description:</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="accuracyReport" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Accuracy Report summary: A qualitative statement about the accuracy of the data. description: A text statement of the data quality, included the means by which it was determined.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quantitativeAccuracyReport" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Report summary: A quantitative assessment of the data quality. description: A quantitative assessment of the data quality expressed as a value and the method of its determination.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed. example: 4.5</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment. example: Error expressed as root mean square of 5 control points.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -800,25 +757,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -941,25 +879,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="parameter" type="ParameterType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter summary: A parameter that is required as input to the stored procedure. description: The parameter elements defines the fields that may be required to invoke a stored procedure.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1066,25 +985,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="name" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: The value of the name field is the name of the parameter. example: SiteID</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1196,25 +1096,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="domainDescription" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Domain Description summary: A description of domain of valid values for the parameter. description: The domainDescription field is used to describe the valid entries for the parameter being described. A stored procedure will work only when the parameter's value corresponds to an actual value in a database. example: The database has SiteId values that range from cap1 to cap10, however the allowable SiteId values for this stored procedure are cap1,cap2,cap4 or cap7.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1296,25 +1177,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="required" type="xs:boolean">
- <xs:annotation>
- <xs:documentation>tooltip: Required summary: Whether or not the parameter is required. description: The required field is used to document whether the parameter being described is or is not required when invoking the stored procedure. example: true</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1395,25 +1257,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="repeats" type="xs:boolean">
- <xs:annotation>
- <xs:documentation>tooltip: Repeats summary: Whether or not the parameter repeats. description: The repeats field is used to document whether or not the parameter being described can be repeated when invoking the stored procedure. example: true</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1605,25 +1448,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="storedProcedure" type="StoredProcedureType">
- <xs:annotation>
- <xs:documentation>tooltip: Stored Procedure> summary: The storedProcedure element documents stored procedures. description: The storedProcedure element is meant to capture information on procedures that produce data output in the form of a data table. In an RDBMS one can code complex queries and transactions into stored procedures and then invoke them directly from front-end applications. This element allows the optional description of any parameters that are expected to be passed to the procedure when it is called. A common use of a stored procedure is to rotate a data table from attributes in columns to attributes in rows for statistical analysis.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="StoredProcedureType">
- <xs:annotation>
- <xs:documentation>tooltip: Stored Procedure complex type> summary: Structure for documenting a stored procedure description: The StoredProcedureType complex type defines the structure for documenting a stored procedure.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:group ref="ent:EntityGroup"/>
- <xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="parameter" type="ParameterType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter summary: A parameter that is required as input to the stored procedure. description: The parameter elements defines the fields that may be required to invoke a stored procedure.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:complexType name="ParameterType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter complex type summary: The structure for defining a parameter that is required as input to the stored procedure. description: The parameter complex type defines the structure for documenting the parameters that may be required to invoke a stored procedure.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="name" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: The value of the name field is the name of the parameter. example: SiteID</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="domainDescription" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Domain Description summary: A description of domain of valid values for the parameter. description: The domainDescription field is used to describe the valid entries for the parameter being described. A stored procedure will work only when the parameter's value corresponds to an actual value in a database. example: The database has SiteId values that range from cap1 to cap10, however the allowable SiteId values for this stored procedure are cap1,cap2,cap4 or cap7.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="required" type="xs:boolean">
- <xs:annotation>
- <xs:documentation>tooltip: Required summary: Whether or not the parameter is required. description: The required field is used to document whether the parameter being described is or is not required when invoking the stored procedure. example: true</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="repeats" type="xs:boolean">
- <xs:annotation>
- <xs:documentation>tooltip: Repeats summary: Whether or not the parameter repeats. description: The repeats field is used to document whether or not the parameter being described can be repeated when invoking the stored procedure. example: true</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:element name="section" type="SectionType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Section summary: A section of related text. description: The "section" element allows for grouping related paragraphs of text together, with an optional title. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -854,25 +790,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="title" type="i18nString" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Title summary: The optional title of the section. description: The optional title for a section. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1027,25 +944,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="para" type="ParagraphType">
- <xs:annotation>
- <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1160,25 +1058,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Localized string for the paragraph summary: Language translation for the paragraph description: Language translation as specified by the xml:lang attribute</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1286,25 +1165,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="itemizedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Itemized List summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1419,44 +1279,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="listitem" minOccurs="1" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: List Item summary: An item in a list of items. description: An item in a list of items. Each list item is formatted as a bulleted or numbered item depending on the list type in which it resides. List items contain paragraphs which in turn can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice minOccurs="1" maxOccurs="unbounded">
- <xs:element name="para" type="ParagraphType">
- <xs:annotation>
- <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="itemizedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Itemized List summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="orderedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Ordered List summary: An ordered list of items in a text paragraph. description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1611,25 +1433,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="para" type="ParagraphType">
- <xs:annotation>
- <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1737,25 +1540,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="orderedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Ordered List summary: An ordered list of items in a text paragraph. description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1890,31 +1674,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="emphasis">
- <xs:annotation>
- <xs:documentation>tooltip: Emphasis summary: A span of emphasized text in a paragraph. description: A span of emphasized text in a paragraph. Emphasized text is generally rendered as boldfaced or otherwise distinct from the surrounding text. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:complexType mixed="true">
- <xs:sequence>
- <xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="xml:lang"/>
- </xs:complexType>
-</xs:element>
<xs:element name="subscript" type="SubSuperScriptType">
- <xs:annotation>
- <xs:documentation>tooltip: Subscript summary: A subscript in a text paragraph. description: A subscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2299,25 +2024,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Localized string for the sub/superscript summary: Language translation for the sub/superscript description: Language translation as specified by the xml:lang attribute</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2461,25 +2167,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="subscript" type="SubSuperScriptType">
- <xs:annotation>
- <xs:documentation>tooltip: Subscript summary: A subscript in a text paragraph. description: A subscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2623,25 +2310,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="superscript" type="SubSuperScriptType">
- <xs:annotation>
- <xs:documentation>tooltip: Superscript summary: A superscript in a text paragraph. description: A superscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2785,25 +2453,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="superscript" type="SubSuperScriptType">
- <xs:annotation>
- <xs:documentation>tooltip: Superscript summary: A superscript in a text paragraph. description: A superscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2909,30 +2558,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="literalLayout">
- <xs:annotation>
- <xs:documentation>tooltip: literalLayout summary: The equivalent to <pre> in html. description: This element specifies that the structure of the text within the tag, specifically the whitespace, should not be altered.</xs:documentation>
- </xs:annotation>
- <xs:complexType mixed="true">
- <xs:sequence>
- <xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
<xs:element name="ulink" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: ulink summary: a link that addresses its target by means of a URL description: this element and its children allow paragraphs to contain urls and titles for anchor tags. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:complexType mixed="true">
- <xs:sequence minOccurs="0" maxOccurs="unbounded">
- <xs:element name="citetitle" type="i18nString">
- <xs:annotation>
- <xs:documentation>tooltip: citetitle summary: the title of the cited work description: the citetitle element contains a text title for the url. It can be displayed in an anchor tag. This markup is a subset of DocBook. example: The Dublin Core Metadata Initiative</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="url" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: url summary: the Uniform Resource Locator for the cited work description: the url attribute contains the location of the work for a link. This markup is a subset of DocBook. example: url="http://dublincore.org/documents/usageguide/"</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -3332,25 +2909,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citetitle" type="i18nString">
- <xs:annotation>
- <xs:documentation>tooltip: citetitle summary: the title of the cited work description: the citetitle element contains a text title for the url. It can be displayed in an anchor tag. This markup is a subset of DocBook. example: The Dublin Core Metadata Initiative</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3458,25 +3016,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="itemizedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Itemized List summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3584,25 +3123,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="orderedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Ordered List summary: An ordered list of items in a text paragraph. description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3743,25 +3263,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="section" type="SectionType">
- <xs:annotation>
- <xs:documentation>tooltip: Section summary: A section of related text. description: The "section" element allows for grouping related paragraphs of text together, with an optional title. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -3923,25 +3424,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="para" type="ParagraphType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -4103,43 +3585,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="markdown" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Markdown summary: A block of text formatted with Markdown directives. description: Markdown is a family of text-based formatting directives that can be used to structure and format a block of text. A single markdown element in EML can contain multiple formatting directives that support creation of sections and subsections with headings, a wide variety of text formatting directives, the ability to include inline links to external content, and the ability to embed inline citations, figures, and tables. EML's markdown element follows the GitHub Flavored Markdown (GFM) extensions to the CommonMark specification. Clients that display EML should use a markdown preprocessor to convert the Markdown formatting into an appropriate display format such as HTML or PDF as appropriate. When a Markdown block is interleaved with other blocks of text such as section and paragraph elements from Docbook, the Markdown section should be interleaved as a block-level element in the flow of the document. This allows authors to specify, for example, an initial section in DocBook, followed by a Markdown section, and then possibly other sections in DocBook. This will likely be uncommon because Markdown and Docbook have similar formatting capabilities, but it may be helpful when converting legacy documents that use DocBook. Because markdown uses special characters that might be reserved by XML processors, one must be careful to escape such characters, which is typically done by embedding the text in a CDATA block, or other XML escaping measures. These escape sequences must be unescaped before parsing the text with a Markdown processor. Within a Markdown block, one can use embedded images to specify the location where an inline image should be displayed within the document. For example, the syntax for an embedded image uses the markdown reference syntax, for example ![Figure 1][fig.1.ab567w], where "fig.1.ab567w" is the unique id attribute for the entity containing the reference to the image. When client tools process such image links, they should inline the image data from that entity at the location specified, which may involve, for example, resolving the image url from an otherEntity section. This means that there is an implied link in all Markdown documents of the form [id]: url/to/image "Optional title attribute", which is derived from the metadata for each entity within a document. Users do not need to insert these links in order to use them, but client software that might be generating HTML from the markdown will likely need to generate them from the entity metadata if they are using an external Markdown pre-processor to handle conversion to HTML and other languages. Inline citations can also be used to cite scholarly works in the text of an EML document. This follows the Pandoc syntax for citation keys, in which the citation keys are in inside square brackets and separated by semicolons. Each citation is identified by a key, which consists of an ‘@’ symbol and the citation identifier from the entry for that citation. Citation keys may optionally have a prefix, a locator, and a suffix to further qualify what is being cited. For example, a simple citation would be constructed as '[@fegraus_2005]', and a list would be '[@jones_2001; @fegraus_2005]'. The keys must be present in either the 'id' field of a citation element in the EML document, or as the BibTex key in a 'bibtex' entry in the EML document. It is a validation error to cite an entry for which the corresponding citation key is not present in the EML document, and it is a validation error for the same citation key to be reused across citation and bibtex elements in the document (each citation identifier must be unique within the document). Clients that parse and display EML documents should first gather up all citation and bibtex elements in the document to create a citation database in bibtext format, and then pass that database along with the text in markdown sections to pandoc or an equivalent tool to convert the citations into properly formatted, human readable citations. Pandoc supports the use of Citation Style Language (CSL) files to specify the formatting of citations upon conversion. See http://citationstyles.org/ for more details. Because bulleted lists and other structures within Markdown are dependent on indenting the raw markdown text, authors and processors should pay close attention to formatting within the markdown block. In particular, if the XML document within which the markdown block is embedded is in an indented hierarchy, then the first non-whitespace character of the markdown block defines the column for the leftmost column of the markdown, and all subsequent markdown should be indented relative to that column. For example, if the first character of the markdown is in column 16 of the document, then all subsequent markdown lines in that block should also start on column 16. A bulleted list would start on column 16, and its sublist would be indented four space to column 20.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="res:NonEmptyStringType">
- <!--
- <xs:attribute name="syntax" type="i18nNonEmptyStringType" use="optional">
- <xs:annotation>
- <xs:appinfo>
- <doc:tooltip>url</doc:tooltip>
- <doc:summary>the Uniform Resource Locator for the cited work</doc:summary>
- <doc:description>the url attribute contains the location of the work for a link. This markup is a subset of DocBook.</doc:description>
- <doc:example>url="http://dublincore.org/documents/usageguide/"</doc:example>
- </xs:appinfo>
- </xs:annotation>
- </xs:attribute>
- -->
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -4283,25 +3728,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="text" type="TextType">
- <xs:annotation>
- <xs:documentation>tooltip: Text summary: A simple text desription. description: The "text" element allows for both formatted and unformatted text blocks to be included in EML. It can contain a number of relevant subsections that allow the use of titles, sections, and paragraphs in the text block. The structured elements can be specified using a subset of DocBook so the predefined DocBook stylesheets can be used to style EML fields that implement this module, or alternatively can be specified using Markdown text blocks.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="TextType" mixed="true">
- <xs:annotation>
- <xs:documentation>tooltip: Text summary: A simple text desription. description: The "text" element allows for both formatted and unformatted text blocks to be included in EML. It can contain a number of relevant subsections that allow the use of titles, sections, and paragraphs in the text block. This markup is a subset of DocBook, or alternatively can be specified using Markdown text blocks.</xs:documentation>
- </xs:annotation>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="section" type="SectionType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Section summary: A section of related text. description: The "section" element allows for grouping related paragraphs of text together, with an optional title. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="para" type="ParagraphType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="markdown" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Markdown summary: A block of text formatted with Markdown directives. description: Markdown is a family of text-based formatting directives that can be used to structure and format a block of text. A single markdown element in EML can contain multiple formatting directives that support creation of sections and subsections with headings, a wide variety of text formatting directives, the ability to include inline links to external content, and the ability to embed inline citations, figures, and tables. EML's markdown element follows the GitHub Flavored Markdown (GFM) extensions to the CommonMark specification. Clients that display EML should use a markdown preprocessor to convert the Markdown formatting into an appropriate display format such as HTML or PDF as appropriate. When a Markdown block is interleaved with other blocks of text such as section and paragraph elements from Docbook, the Markdown section should be interleaved as a block-level element in the flow of the document. This allows authors to specify, for example, an initial section in DocBook, followed by a Markdown section, and then possibly other sections in DocBook. This will likely be uncommon because Markdown and Docbook have similar formatting capabilities, but it may be helpful when converting legacy documents that use DocBook. Because markdown uses special characters that might be reserved by XML processors, one must be careful to escape such characters, which is typically done by embedding the text in a CDATA block, or other XML escaping measures. These escape sequences must be unescaped before parsing the text with a Markdown processor. Within a Markdown block, one can use embedded images to specify the location where an inline image should be displayed within the document. For example, the syntax for an embedded image uses the markdown reference syntax, for example ![Figure 1][fig.1.ab567w], where "fig.1.ab567w" is the unique id attribute for the entity containing the reference to the image. When client tools process such image links, they should inline the image data from that entity at the location specified, which may involve, for example, resolving the image url from an otherEntity section. This means that there is an implied link in all Markdown documents of the form [id]: url/to/image "Optional title attribute", which is derived from the metadata for each entity within a document. Users do not need to insert these links in order to use them, but client software that might be generating HTML from the markdown will likely need to generate them from the entity metadata if they are using an external Markdown pre-processor to handle conversion to HTML and other languages. Inline citations can also be used to cite scholarly works in the text of an EML document. This follows the Pandoc syntax for citation keys, in which the citation keys are in inside square brackets and separated by semicolons. Each citation is identified by a key, which consists of an ‘@’ symbol and the citation identifier from the entry for that citation. Citation keys may optionally have a prefix, a locator, and a suffix to further qualify what is being cited. For example, a simple citation would be constructed as '[@fegraus_2005]', and a list would be '[@jones_2001; @fegraus_2005]'. The keys must be present in either the 'id' field of a citation element in the EML document, or as the BibTex key in a 'bibtex' entry in the EML document. It is a validation error to cite an entry for which the corresponding citation key is not present in the EML document, and it is a validation error for the same citation key to be reused across citation and bibtex elements in the document (each citation identifier must be unique within the document). Clients that parse and display EML documents should first gather up all citation and bibtex elements in the document to create a citation database in bibtext format, and then pass that database along with the text in markdown sections to pandoc or an equivalent tool to convert the citations into properly formatted, human readable citations. Pandoc supports the use of Citation Style Language (CSL) files to specify the formatting of citations upon conversion. See http://citationstyles.org/ for more details. Because bulleted lists and other structures within Markdown are dependent on indenting the raw markdown text, authors and processors should pay close attention to formatting within the markdown block. In particular, if the XML document within which the markdown block is embedded is in an indented hierarchy, then the first non-whitespace character of the markdown block defines the column for the leftmost column of the markdown, and all subsequent markdown should be indented relative to that column. For example, if the first character of the markdown is in column 16 of the document, then all subsequent markdown lines in that block should also start on column 16. A bulleted list would start on column 16, and its sublist would be indented four space to column 20.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="res:NonEmptyStringType">
- <!--
- <xs:attribute name="syntax" type="i18nNonEmptyStringType" use="optional">
- <xs:annotation>
- <xs:appinfo>
- <doc:tooltip>url</doc:tooltip>
- <doc:summary>the Uniform Resource Locator for the cited work</doc:summary>
- <doc:description>the url attribute contains the location of the work for a link. This markup is a subset of DocBook.</doc:description>
- <doc:example>url="http://dublincore.org/documents/usageguide/"</doc:example>
- </xs:appinfo>
- </xs:annotation>
- </xs:attribute>
- -->
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:attribute ref="xml:lang"/>
-</xs:complexType>
<xs:complexType name="SectionType">
- <xs:annotation>
- <xs:documentation>tooltip: Section summary: A section of related text. description: The "section" element allows for grouping related paragraphs (or other sections) of text together, with an optional title. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="title" type="i18nString" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Title summary: The optional title of the section. description: The optional title for a section. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice maxOccurs="unbounded">
- <xs:element name="para" type="ParagraphType">
- <xs:annotation>
- <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="section" type="SectionType">
- <xs:annotation>
- <xs:documentation>tooltip: Section summary: A section of related text. description: The "section" element allows for grouping related paragraphs of text together, with an optional title. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:sequence>
- <xs:attribute ref="xml:lang"/>
-</xs:complexType>
<xs:complexType name="i18nString">
- <xs:annotation>
- <xs:documentation>tooltip: Localized string summary: Language translation for the text description: Language translation as specified by the xml:lang attribute</xs:documentation>
- </xs:annotation>
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute ref="xml:lang">
- <xs:annotation>
- <xs:documentation>tooltip: xml:lang summary: language code for element content description: Specifies the language example: xml:lang="en-US"</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
-</xs:complexType>
<xs:complexType name="ParagraphType" mixed="true">
- <xs:annotation>
- <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, lists and links. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:choice minOccurs="0" maxOccurs="unbounded">
- <xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Localized string for the paragraph summary: Language translation for the paragraph description: Language translation as specified by the xml:lang attribute</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="itemizedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Itemized List summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="orderedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Ordered List summary: An ordered list of items in a text paragraph. description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="emphasis">
- <xs:annotation>
- <xs:documentation>tooltip: Emphasis summary: A span of emphasized text in a paragraph. description: A span of emphasized text in a paragraph. Emphasized text is generally rendered as boldfaced or otherwise distinct from the surrounding text. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:complexType mixed="true">
- <xs:sequence>
- <xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="xml:lang"/>
- </xs:complexType>
- </xs:element>
- <xs:element name="subscript" type="SubSuperScriptType">
- <xs:annotation>
- <xs:documentation>tooltip: Subscript summary: A subscript in a text paragraph. description: A subscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="superscript" type="SubSuperScriptType">
- <xs:annotation>
- <xs:documentation>tooltip: Superscript summary: A superscript in a text paragraph. description: A superscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="literalLayout">
- <xs:annotation>
- <xs:documentation>tooltip: literalLayout summary: The equivalent to <pre> in html. description: This element specifies that the structure of the text within the tag, specifically the whitespace, should not be altered.</xs:documentation>
- </xs:annotation>
- <xs:complexType mixed="true">
- <xs:sequence>
- <xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="ulink" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: ulink summary: a link that addresses its target by means of a URL description: this element and its children allow paragraphs to contain urls and titles for anchor tags. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:complexType mixed="true">
- <xs:sequence minOccurs="0" maxOccurs="unbounded">
- <xs:element name="citetitle" type="i18nString">
- <xs:annotation>
- <xs:documentation>tooltip: citetitle summary: the title of the cited work description: the citetitle element contains a text title for the url. It can be displayed in an anchor tag. This markup is a subset of DocBook. example: The Dublin Core Metadata Initiative</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="url" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: url summary: the Uniform Resource Locator for the cited work description: the url attribute contains the location of the work for a link. This markup is a subset of DocBook. example: url="http://dublincore.org/documents/usageguide/"</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- </xs:element>
- </xs:choice>
- <xs:attribute ref="xml:lang"/>
-</xs:complexType>
<xs:complexType name="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: ListType summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The ListType is used by both orderedlist elements and itemizedlist elements. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:sequence>
- <xs:element name="listitem" minOccurs="1" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: List Item summary: An item in a list of items. description: An item in a list of items. Each list item is formatted as a bulleted or numbered item depending on the list type in which it resides. List items contain paragraphs which in turn can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:choice minOccurs="1" maxOccurs="unbounded">
- <xs:element name="para" type="ParagraphType">
- <xs:annotation>
- <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="itemizedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Itemized List summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="orderedlist" type="ListType">
- <xs:annotation>
- <xs:documentation>tooltip: Ordered List summary: An ordered list of items in a text paragraph. description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
-</xs:complexType>
<xs:complexType name="SubSuperScriptType" mixed="true">
- <xs:annotation>
- <xs:documentation>tooltip: Subscript/Superscript Type summary: A subscript or a superscript in a text paragraph. description: A subscript or a superscript in a text paragraph. This type is used by both subscript and superscript elements to define their recursive content. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- <xs:choice minOccurs="0" maxOccurs="unbounded">
- <xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Localized string for the sub/superscript summary: Language translation for the sub/superscript description: Language translation as specified by the xml:lang attribute</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="subscript" type="SubSuperScriptType">
- <xs:annotation>
- <xs:documentation>tooltip: Subscript summary: A subscript in a text paragraph. description: A subscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="superscript" type="SubSuperScriptType">
- <xs:annotation>
- <xs:documentation>tooltip: Superscript summary: A superscript in a text paragraph. description: A superscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:attribute ref="xml:lang"/>
-</xs:complexType>
<xs:attribute name="url" use="optional">
- <xs:annotation>
- <xs:documentation>tooltip: url summary: the Uniform Resource Locator for the cited work description: the url attribute contains the location of the work for a link. This markup is a subset of DocBook. example: url="http://dublincore.org/documents/usageguide/"</xs:documentation>
- </xs:annotation>
-</xs:attribute>
-
-
-
-
-
diff --git a/dist/schema/eml-unitTypeDefinitions_xsd.html b/dist/schema/eml-unitTypeDefinitions_xsd.html
index 81e7d749..8fce3aff 100644
--- a/dist/schema/eml-unitTypeDefinitions_xsd.html
+++ b/dist/schema/eml-unitTypeDefinitions_xsd.html
@@ -11,13 +11,6 @@
'facets_MassUnitType',
'facets_otherUnitType',
'facets_angleUnitType');
-var usedByBoxes= new Array('usedBy_LengthUnitType',
- 'usedBy_StandardUnitDictionary');
-var sourceBoxes= new Array('source_LengthUnitType',
- 'source_StandardUnitDictionary',
- 'source_MassUnitType',
- 'source_otherUnitType',
- 'source_angleUnitType');
var diagramBoxes= new Array('diagram_LengthUnitType',
'diagram_StandardUnitDictionary',
'diagram_MassUnitType',
@@ -286,12 +279,6 @@
<xs:simpleType name="LengthUnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Length Units summary: The list of units which are of length type, or have a parentSI of meter SI description: The LengthUnitType is the enumerated list of units which are of length type, or have a parentSI of meter. These unit names can be used where ever content should be restricted to a length, such as a distance or altitude. The units are defined in the STMML language in a document that is shipped with each release of EML called eml-unitDictionary.xml. See this file for precise, quantitative definitions of each of these units and their relationships to base SI units.</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:enumeration value="meter"/>
- <xs:enumeration value="nanometer"/>
- <xs:enumeration value="micrometer"/>
- <xs:enumeration value="micron"/>
- <xs:enumeration value="millimeter"/>
- <xs:enumeration value="centimeter"/>
- <xs:enumeration value="decimeter"/>
- <xs:enumeration value="dekameter"/>
- <xs:enumeration value="hectometer"/>
- <xs:enumeration value="kilometer"/>
- <xs:enumeration value="megameter"/>
- <xs:enumeration value="angstrom"/>
- <xs:enumeration value="inch"/>
- <xs:enumeration value="Foot_US"/>
- <xs:enumeration value="foot"/>
- <xs:enumeration value="Foot_Gold_Coast"/>
- <xs:enumeration value="fathom"/>
- <xs:enumeration value="nauticalMile"/>
- <xs:enumeration value="yard"/>
- <xs:enumeration value="Yard_Indian"/>
- <xs:enumeration value="Link_Clarke"/>
- <xs:enumeration value="Yard_Sears"/>
- <xs:enumeration value="mile"/>
- </xs:restriction>
-</xs:simpleType>
<xs:simpleType name="StandardUnitDictionary">
- <xs:annotation>
- <xs:documentation>tooltip: Standard Units summary: The enumerated list of standard units, mainly S unitsI description: The unitDictionary is the standard set of units included with the EML distribution, mainly from the SI standard. These unit names should be used in the standardUnit field to describe an attribute. See the accompanying STMML file, eml-unitDictionary.xml, for precise, quantitative definitions of each of these units and their relationships to base SI units. The standard Unit Dictionary is built from a union of simpleTypes. This construct allows unit types to be used individually as appropriate in EML content (e.g., LengthUnitType for distances )</xs:documentation>
- </xs:annotation>
- <xs:union memberTypes="unit:LengthUnitType unit:MassUnitType unit:angleUnitType unit:otherUnitType"/>
-</xs:simpleType>
-
-
-
-
-
@@ -958,40 +849,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:simpleType name="MassUnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Mass Units summary: The list of units which are of mass type, or have a parentSI of kilogram description: The MassUnitType is the enumerated list of units which are of mass type, or have a parentSI of kilogram. These unit names can be used where ever content should be restricted to a mass, such as an amount. The units are defined in the STMML language in a document that is shipped with each release of EML called eml-unitDictionary.xml. See this file for precise, quantitative definitions of each of these units and their relationships to base SI units.</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:enumeration value="kilogram"/>
- <xs:enumeration value="nanogram"/>
- <xs:enumeration value="microgram"/>
- <xs:enumeration value="milligram"/>
- <xs:enumeration value="centigram"/>
- <xs:enumeration value="decigram"/>
- <xs:enumeration value="gram"/>
- <xs:enumeration value="dekagram"/>
- <xs:enumeration value="hectogram"/>
- <xs:enumeration value="megagram"/>
- <xs:enumeration value="tonne"/>
- <xs:enumeration value="pound"/>
- <xs:enumeration value="ton"/>
- </xs:restriction>
-</xs:simpleType>
-
-
-
-
-
@@ -3139,325 +2996,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:simpleType name="otherUnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Other Standard Units summary: The enumerated list of standard units that are not included in the any other named simpleType description: The unitDictionary is the standard set of units included with the EML distribution, mainly from the SI standard. These unit names can be used in the standardUnit field to describe an attribute. The units are defined in the STMML language in a document that is shipped with each release of EML. See the accompanying STMML file eml-unitDictionary.xml for precise, quantitative definitions of each of these units and their relationships to base SI units. The standard Unit Dictionary is built from a union of simpleTypes. This Type enumerates the units which are not in other Type definitions, but are to be included as standard.</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:enumeration value="acre"/>
- <xs:enumeration value="ampere"/>
- <xs:enumeration value="amperePerMeter"/>
- <xs:enumeration value="amperePerMeterSquared"/>
- <xs:enumeration value="amperePerSquareMeter"/>
- <xs:enumeration value="are"/>
- <xs:enumeration value="atmosphere"/>
- <xs:enumeration value="bar"/>
- <xs:enumeration value="becquerel"/>
- <xs:enumeration value="britishThermalUnit"/>
- <xs:enumeration value="bushel"/>
- <xs:enumeration value="bushelPerAcre"/>
- <xs:enumeration value="bushelsPerAcre"/>
- <xs:enumeration value="calorie"/>
- <xs:enumeration value="candela"/>
- <xs:enumeration value="candelaPerMeterSquared"/>
- <xs:enumeration value="candelaPerSquareMeter"/>
- <xs:enumeration value="celsius"/>
- <xs:enumeration value="centimeterCubed"/>
- <xs:enumeration value="centimeterPerSecond"/>
- <xs:enumeration value="centimeterPerYear"/>
- <xs:enumeration value="centimeterSquared"/>
- <xs:enumeration value="centimetersPerSecond"/>
- <xs:enumeration value="centisecond"/>
- <xs:enumeration value="coulomb"/>
- <xs:enumeration value="cubicCentimetersPerCubicCentimeters"/>
- <xs:enumeration value="cubicFeetPerSecond"/>
- <xs:enumeration value="cubicInch"/>
- <xs:enumeration value="cubicMeter"/>
- <xs:enumeration value="cubicMeterPerKilogram"/>
- <xs:enumeration value="cubicMetersPerSecond"/>
- <xs:enumeration value="cubicMicrometersPerGram"/>
- <xs:enumeration value="decibar"/>
- <xs:enumeration value="decisecond"/>
- <xs:enumeration value="dekasecond"/>
- <xs:enumeration value="dimensionless"/>
- <xs:enumeration value="equivalentPerLiter"/>
- <xs:enumeration value="fahrenheit"/>
- <xs:enumeration value="farad"/>
- <xs:enumeration value="feetPerDay"/>
- <xs:enumeration value="feetPerHour"/>
- <xs:enumeration value="feetPerSecond"/>
- <xs:enumeration value="feetSquaredPerDay"/>
- <xs:enumeration value="footCubedPerSecond"/>
- <xs:enumeration value="footPerDay"/>
- <xs:enumeration value="footPerHour"/>
- <xs:enumeration value="footPerSecond"/>
- <xs:enumeration value="footPound"/>
- <xs:enumeration value="footSquared"/>
- <xs:enumeration value="footSquaredPerDay"/>
- <xs:enumeration value="gallon"/>
- <xs:enumeration value="gramPerCentimeterCubed"/>
- <xs:enumeration value="gramPerCentimeterSquaredPerSecond"/>
- <xs:enumeration value="gramPerDayPerHectare"/>
- <xs:enumeration value="gramPerDayPerLiter"/>
- <xs:enumeration value="gramPerGram"/>
- <xs:enumeration value="gramPerLiter"/>
- <xs:enumeration value="gramPerMeterSquared"/>
- <xs:enumeration value="gramPerMeterSquaredPerDay"/>
- <xs:enumeration value="gramPerMeterSquaredPerYear"/>
- <xs:enumeration value="gramPerMilliliter"/>
- <xs:enumeration value="gramPerYear"/>
- <xs:enumeration value="gramPercentimeterSquared"/>
- <xs:enumeration value="gramsPerCentimeterSquaredPerSecond"/>
- <xs:enumeration value="gramsPerCubicCentimeter"/>
- <xs:enumeration value="gramsPerGram"/>
- <xs:enumeration value="gramsPerHectarePerDay"/>
- <xs:enumeration value="gramsPerLiter"/>
- <xs:enumeration value="gramsPerLiterPerDay"/>
- <xs:enumeration value="gramsPerMeterSquaredPerYear"/>
- <xs:enumeration value="gramsPerMilliliter"/>
- <xs:enumeration value="gramsPerSquareMeter"/>
- <xs:enumeration value="gramsPerYear"/>
- <xs:enumeration value="gray"/>
- <xs:enumeration value="hectare"/>
- <xs:enumeration value="hectopascal"/>
- <xs:enumeration value="hectosecond"/>
- <xs:enumeration value="henry"/>
- <xs:enumeration value="hertz"/>
- <xs:enumeration value="hour"/>
- <xs:enumeration value="inchCubed"/>
- <xs:enumeration value="inchPerHour"/>
- <xs:enumeration value="inverseCentimeter"/>
- <xs:enumeration value="inverseMeter"/>
- <xs:enumeration value="joule"/>
- <xs:enumeration value="katal"/>
- <xs:enumeration value="kelvin"/>
- <xs:enumeration value="kilogramPerCubicMeter"/>
- <xs:enumeration value="kilogramPerHectare"/>
- <xs:enumeration value="kilogramPerHectarePerYear"/>
- <xs:enumeration value="kilogramPerMeterCubed"/>
- <xs:enumeration value="kilogramPerMeterSquared"/>
- <xs:enumeration value="kilogramPerMeterSquaredPerDay"/>
- <xs:enumeration value="kilogramPerMeterSquaredPerSecond"/>
- <xs:enumeration value="kilogramPerMeterSquaredPerYear"/>
- <xs:enumeration value="kilogramPerSecond"/>
- <xs:enumeration value="kilogramsPerHectare"/>
- <xs:enumeration value="kilogramsPerHectarePerYear"/>
- <xs:enumeration value="kilogramsPerMeterSquaredPerSecond"/>
- <xs:enumeration value="kilogramsPerMeterSquaredPerYear"/>
- <xs:enumeration value="kilogramsPerSecond"/>
- <xs:enumeration value="kilogramsPerSquareMeter"/>
- <xs:enumeration value="kilohertz"/>
- <xs:enumeration value="kiloliter"/>
- <xs:enumeration value="kilometerPerHour"/>
- <xs:enumeration value="kilometerSquared"/>
- <xs:enumeration value="kilometersPerHour"/>
- <xs:enumeration value="kilopascal"/>
- <xs:enumeration value="kilosecond"/>
- <xs:enumeration value="kilovolt"/>
- <xs:enumeration value="kilowatt"/>
- <xs:enumeration value="kilowattPerMeterSquared"/>
- <xs:enumeration value="knot"/>
- <xs:enumeration value="knots"/>
- <xs:enumeration value="langley"/>
- <xs:enumeration value="langleyPerDay"/>
- <xs:enumeration value="liter"/>
- <xs:enumeration value="literPerHectare"/>
- <xs:enumeration value="literPerLiter"/>
- <xs:enumeration value="literPerMeterSquared"/>
- <xs:enumeration value="literPerSecond"/>
- <xs:enumeration value="litersPerHectare"/>
- <xs:enumeration value="litersPerSecond"/>
- <xs:enumeration value="litersPerSquareMeter"/>
- <xs:enumeration value="lumen"/>
- <xs:enumeration value="lux"/>
- <xs:enumeration value="megagramPerMeterCubed"/>
- <xs:enumeration value="megahertz"/>
- <xs:enumeration value="megajoulePerMeterSquaredPerDay"/>
- <xs:enumeration value="megapascal"/>
- <xs:enumeration value="megasecond"/>
- <xs:enumeration value="megavolt"/>
- <xs:enumeration value="megawatt"/>
- <xs:enumeration value="meterCubed"/>
- <xs:enumeration value="meterCubedPerHectare"/>
- <xs:enumeration value="meterCubedPerKilogram"/>
- <xs:enumeration value="meterCubedPerMeterCubed"/>
- <xs:enumeration value="meterCubedPerMeterSquared"/>
- <xs:enumeration value="meterCubedPerSecond"/>
- <xs:enumeration value="meterPerDay"/>
- <xs:enumeration value="meterPerGram"/>
- <xs:enumeration value="meterPerSecond"/>
- <xs:enumeration value="meterPerSecondSquared"/>
- <xs:enumeration value="meterSquared"/>
- <xs:enumeration value="meterSquaredPerDay"/>
- <xs:enumeration value="meterSquaredPerHectare"/>
- <xs:enumeration value="meterSquaredPerKilogram"/>
- <xs:enumeration value="meterSquaredPerSecond"/>
- <xs:enumeration value="metersPerDay"/>
- <xs:enumeration value="metersPerGram"/>
- <xs:enumeration value="metersPerSecond"/>
- <xs:enumeration value="metersPerSecondSquared"/>
- <xs:enumeration value="metersSquaredPerDay"/>
- <xs:enumeration value="metersSquaredPerSecond"/>
- <xs:enumeration value="microequivalentPerLiter"/>
- <xs:enumeration value="microgramPerGram"/>
- <xs:enumeration value="microgramPerGramPerDay"/>
- <xs:enumeration value="microgramPerGramPerHour"/>
- <xs:enumeration value="microgramPerGramPerWeek"/>
- <xs:enumeration value="microgramPerLiter"/>
- <xs:enumeration value="microgramsPerGram"/>
- <xs:enumeration value="microgramsPerLiter"/>
- <xs:enumeration value="microliter"/>
- <xs:enumeration value="microliterPerLiter"/>
- <xs:enumeration value="micrometerCubedPerGram"/>
- <xs:enumeration value="micromolePerCentimeterSquaredPerSecond"/>
- <xs:enumeration value="micromolePerGram"/>
- <xs:enumeration value="micromolePerGramPerDay"/>
- <xs:enumeration value="micromolePerGramPerHour"/>
- <xs:enumeration value="micromolePerGramPerSecond"/>
- <xs:enumeration value="micromolePerKilogram"/>
- <xs:enumeration value="micromolePerLiter"/>
- <xs:enumeration value="micromolePerMeterSquaredPerSecond"/>
- <xs:enumeration value="micromolePerMole"/>
- <xs:enumeration value="microsecond"/>
- <xs:enumeration value="microwattPerCentimeterSquaredPerNanometer"/>
- <xs:enumeration value="microwattPerCentimeterSquaredPerNanometerPerSteradian"/>
- <xs:enumeration value="microwattPerCentimeterSquaredPerSteradian"/>
- <xs:enumeration value="milePerHour"/>
- <xs:enumeration value="milePerMinute"/>
- <xs:enumeration value="milePerSecond"/>
- <xs:enumeration value="mileSquared"/>
- <xs:enumeration value="milesPerHour"/>
- <xs:enumeration value="milesPerMinute"/>
- <xs:enumeration value="milesPerSecond"/>
- <xs:enumeration value="milliGramsPerMilliLiter"/>
- <xs:enumeration value="millibar"/>
- <xs:enumeration value="milliequivalentPerLiter"/>
- <xs:enumeration value="milligramPerKilogram"/>
- <xs:enumeration value="milligramPerLiter"/>
- <xs:enumeration value="milligramPerMeterCubed"/>
- <xs:enumeration value="milligramPerMeterCubedPerDay"/>
- <xs:enumeration value="milligramPerMeterSquared"/>
- <xs:enumeration value="milligramPerMeterSquaredPerDay"/>
- <xs:enumeration value="milligramPerMilliliter"/>
- <xs:enumeration value="milligramsPerCubicMeter"/>
- <xs:enumeration value="milligramsPerLiter"/>
- <xs:enumeration value="milligramsPerSquareMeter"/>
- <xs:enumeration value="millihertz"/>
- <xs:enumeration value="milliliter"/>
- <xs:enumeration value="milliliterPerLiter"/>
- <xs:enumeration value="millimeterPerDay"/>
- <xs:enumeration value="millimeterPerSecond"/>
- <xs:enumeration value="millimeterSquared"/>
- <xs:enumeration value="millimetersPerSecond"/>
- <xs:enumeration value="millimolePerGram"/>
- <xs:enumeration value="millimolePerKilogram"/>
- <xs:enumeration value="millimolePerLiter"/>
- <xs:enumeration value="millimolePerMeterCubed"/>
- <xs:enumeration value="millimolePerMole"/>
- <xs:enumeration value="millimolesPerGram"/>
- <xs:enumeration value="millisecond"/>
- <xs:enumeration value="millivolt"/>
- <xs:enumeration value="milliwatt"/>
- <xs:enumeration value="minute"/>
- <xs:enumeration value="molality"/>
- <xs:enumeration value="molarity"/>
- <xs:enumeration value="mole"/>
- <xs:enumeration value="molePerCubicMeter"/>
- <xs:enumeration value="molePerGram"/>
- <xs:enumeration value="molePerKilogram"/>
- <xs:enumeration value="molePerKilogram"/>
- <xs:enumeration value="molePerKilogramPerSecond"/>
- <xs:enumeration value="molePerLiter"/>
- <xs:enumeration value="molePerMeterCubed"/>
- <xs:enumeration value="molePerMeterSquaredPerSecond"/>
- <xs:enumeration value="molePerMole"/>
- <xs:enumeration value="molesPerGram"/>
- <xs:enumeration value="molesPerKilogram"/>
- <xs:enumeration value="molesPerKilogramPerSecond"/>
- <xs:enumeration value="nanogramPerGram"/>
- <xs:enumeration value="nanogramPerGramPerHour"/>
- <xs:enumeration value="nanoliterPerLiter"/>
- <xs:enumeration value="nanomolePerGramPerDay"/>
- <xs:enumeration value="nanomolePerGramPerHour"/>
- <xs:enumeration value="nanomolePerGramPerSecond"/>
- <xs:enumeration value="nanomolePerKilogram"/>
- <xs:enumeration value="nanomolePerLiter"/>
- <xs:enumeration value="nanomolePerMole"/>
- <xs:enumeration value="nanomolesPerGramPerSecond"/>
- <xs:enumeration value="nanosecond"/>
- <xs:enumeration value="newton"/>
- <xs:enumeration value="nominalDay"/>
- <xs:enumeration value="nominalHour"/>
- <xs:enumeration value="nominalLeapYear"/>
- <xs:enumeration value="nominalMinute"/>
- <xs:enumeration value="nominalWeek"/>
- <xs:enumeration value="nominalYear"/>
- <xs:enumeration value="number"/>
- <xs:enumeration value="numberPerGram"/>
- <xs:enumeration value="numberPerHectare"/>
- <xs:enumeration value="numberPerKilometerSquared"/>
- <xs:enumeration value="numberPerLiter"/>
- <xs:enumeration value="numberPerMeterCubed"/>
- <xs:enumeration value="numberPerMeterSquared"/>
- <xs:enumeration value="numberPerMilliliter"/>
- <xs:enumeration value="ohm"/>
- <xs:enumeration value="ohmMeter"/>
- <xs:enumeration value="pascal"/>
- <xs:enumeration value="percent"/>
- <xs:enumeration value="permil"/>
- <xs:enumeration value="pint"/>
- <xs:enumeration value="poundPerAcre"/>
- <xs:enumeration value="poundPerInchSquared"/>
- <xs:enumeration value="poundsPerSquareInch"/>
- <xs:enumeration value="quart"/>
- <xs:enumeration value="second"/>
- <xs:enumeration value="siemen"/>
- <xs:enumeration value="siemens"/>
- <xs:enumeration value="siemensPerCentimeter"/>
- <xs:enumeration value="siemensPerMeter"/>
- <xs:enumeration value="sievert"/>
- <xs:enumeration value="squareCentimeters"/>
- <xs:enumeration value="squareFoot"/>
- <xs:enumeration value="squareKilometers"/>
- <xs:enumeration value="squareMeter"/>
- <xs:enumeration value="squareMeterPerKilogram"/>
- <xs:enumeration value="squareMile"/>
- <xs:enumeration value="squareMillimeters"/>
- <xs:enumeration value="squareYard"/>
- <xs:enumeration value="tesla"/>
- <xs:enumeration value="tonnePerHectare"/>
- <xs:enumeration value="tonnePerYear"/>
- <xs:enumeration value="tonnesPerYear"/>
- <xs:enumeration value="volt"/>
- <xs:enumeration value="watt"/>
- <xs:enumeration value="wattPerMeterSquared"/>
- <xs:enumeration value="wattPerMeterSquaredPerNanometer"/>
- <xs:enumeration value="wattPerMeterSquaredPerNanometerPerSteradian"/>
- <xs:enumeration value="wattPerMeterSquaredPerSteradian"/>
- <xs:enumeration value="waveNumber"/>
- <xs:enumeration value="weber"/>
- <xs:enumeration value="yardPerSecond"/>
- <xs:enumeration value="yardSquared"/>
- <xs:enumeration value="yardsPerSecond"/>
- <!-- removed the mass units to their named type -->
- <!-- removed the length units to their named type -->
- <!-- removed the angle units to their named type -->
- </xs:restriction>
-</xs:simpleType>
-
-
-
-
-
@@ -3563,31 +3101,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:simpleType name="angleUnitType">
- <xs:annotation>
- <xs:documentation>tooltip: Angle Units summary: An example of a group of units which could be added. These units are a derived typein the group of derived SI units with a special name or symbol. description: The AngleUnitType is the enumerated list of angle units. For example, plane angle (radian, rad) and solid angle (steradian, sr) are actually dimensionless, and their symbols used as appropriate (e.g, sr in photometry). These unit names could be used where ever content should be restricted.</xs:documentation>
- </xs:annotation>
- <xs:restriction base="xs:string">
- <xs:enumeration value="radian"/>
- <xs:enumeration value="degree"/>
- <xs:enumeration value="grad"/>
- <xs:enumeration value="steradian"/>
- </xs:restriction>
-</xs:simpleType>
-
-
-
-
-
diff --git a/dist/schema/eml-view_xsd.html b/dist/schema/eml-view_xsd.html
index c1664419..60a1039d 100644
--- a/dist/schema/eml-view_xsd.html
+++ b/dist/schema/eml-view_xsd.html
@@ -16,18 +16,6 @@
'properties_ViewType_scope');
var facetsBoxes= new Array('facets_ViewType_queryStatement',
'facets_ViewType_scope');
-var usedByBoxes= new Array('usedBy_ViewType',
- 'usedBy_ViewType_id',
- 'usedBy_ViewType_system',
- 'usedBy_ViewType_scope');
-var sourceBoxes= new Array('source_ViewType_attributeList',
- 'source_ViewType_constraint',
- 'source_ViewType_queryStatement',
- 'source_view',
- 'source_ViewType',
- 'source_ViewType_id',
- 'source_ViewType_system',
- 'source_ViewType_scope');
var instanceBoxes= new Array('instance_ViewType_attributeList',
'instance_ViewType_constraint',
'instance_view');
@@ -316,12 +304,6 @@
Showing:
Properties
-
-
Source
-
-
-
Used by
-
@@ -579,25 +561,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -775,25 +738,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -904,25 +848,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="queryStatement" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Query Statement summary: Query syntax that produced the view description: The value of a queryStatement field is the actual query statement stored in the database is entered here. The query statement generates the entity being documented. example: Select site as SiteID,common_name as CommonName, count as CountOfIndividuals from samples inner join taxonlist on samples.speciesid=taxonlist.speciesid</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1108,25 +1033,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="view" type="ViewType">
- <xs:annotation>
- <xs:documentation>tooltip: View summary: The View element is a container for documenting a view. description: The View element is a container for documenting a view. The structure of the view element is defined by the ViewType.</xs:documentation>
- </xs:annotation>
-</xs:element>
<xs:complexType name="ViewType">
- <xs:annotation>
- <xs:documentation>tooltip: ViewType summary: The ViewType complex type defines the structure for documenting a view. description: The ViewType complex type defines the structure for documenting a view. This type extends the EntityGroup with a queryStatement.</xs:documentation>
- </xs:annotation>
- <xs:choice>
- <xs:sequence>
- <xs:group ref="ent:EntityGroup"/>
- <xs:element name="attributeList" type="att:AttributeListType">
- <xs:annotation>
- <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="queryStatement" type="res:NonEmptyStringType">
- <xs:annotation>
- <xs:documentation>tooltip: Query Statement summary: Query syntax that produced the view description: The value of a queryStatement field is the actual query statement stored in the database is entered here. The query statement generates the entity being documented. example: Select site as SiteID,common_name as CommonName, count as CountOfIndividuals from samples inner join taxonlist on samples.speciesid=taxonlist.speciesid</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:group ref="res:ReferencesGroup"/>
- </xs:choice>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- <xs:attribute name="system" type="res:SystemType" use="optional"/>
- <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
-</xs:complexType>
<xs:element name="eml">
- <xs:annotation>
- <xs:documentation>tooltip: Ecological Metadata summary: A collection of EML metadata and additional metadata linked using the inline references. description: The "eml" element allows for the inclusion of any metadata content in a single EML document. In general, dataset resources, literature resources, and software resources, or another type that extends eml-resource are described using an eml document. The eml document represents a "package" that can contain both metadata and data. It can optionally include non-EML metadata through the flexibility of the "additionalMetadata" element. Any additional metadata that is provided can provide a pointer into the EML metadata indicating what the context of the additional metadata is (i.e., what it describes). For example, a spatial raster image might be described in EML, and an FGDC CSDGM metadata document could be included in the additionalMetadata element with a pointer to the EML spatialRaster element to indicate that the FGDC metadata is providing supplemental documentation about that particular image entity. There is no validity constraint that restricts what metadata may be present in additionalMetadata.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="access" type="acc:AccessType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Access summary: Access control rules for the entire resource, which can be overridden by access rules in distribution trees description: An optional access tree at this location controls access to the entire metadata document. If this access element is omitted from the document, then the package submitter should be given full access to the package but all other users should be denied all access.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:choice>
- <xs:element name="dataset" type="ds:DatasetType">
- <xs:annotation>
- <xs:documentation>tooltip: Dataset Resource summary: A resource that describes a data set, which can include one or more data entities such as data tables. description: A resource that describes a data set, which can include one or more data entities such as data tables and spatial images (raster and vector). If included, this represents the primary resource that is described in this eml document.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="citation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Literature Resource summary: A resource that describes a literature citation that one might find in a bibliography. description: A resource that describes a literature citation that one might find in a bibliography. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="software" type="sw:SoftwareType">
- <xs:annotation>
- <xs:documentation>tooltip: Software Resource summary: A resource that describes a software package, which can include commercial and non-commercial software as well as data processing programs. description: A resource that describes a software package, which can include commercial and non-commercial software as well as data processing programs. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="protocol" type="pro:ProtocolType">
- <xs:annotation>
- <xs:documentation>tooltip: Protocol Resource summary: A resource that describes a scientific protocol, which can include one or more descriptions of methods and procedures. description: A resource that describes a scientific protocol, which can include one or more descriptions of methods and procedures. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:choice>
- <xs:element name="annotations" minOccurs="0" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation List summary: A list of precisely-defined semantic statements about this resource. description: A list of annotations defining precise semantics for parts of this resource. The list consists of a set of annotation elements, each referring to a subject within the EML document using its references attribute, which provides a pointer to the id of the element being annotated.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="annotation" minOccurs="1" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about an element in the EML document. description: An annotation represents a precisely-defined semantic statement that applies to this resource. This semantic statement is used to associate precise semantics with a particular element in the EML document. The id of the element being annotated is listed in the references attribute, and must point to a unique id within the EML document. Each annotation consists of a propertyURI and valueURI that define a property and value that apply to the resource. The subject of the statement is implicitly the element that is listed in the references attribute. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="sem:SemanticAnnotation">
- <xs:attribute name="references" type="xs:string" use="required"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- <xs:element name="additionalMetadata" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Additional Metadata summary: A flexible field for including any other relevant metadata that pertains to the resource being described. description: A flexible field for including any other relevant metadata that pertains to the resource being described. This field allows EML to be extensible in that any XML-based metadata can be included in this element, including metadata from other standards such as the FGDC CSDGM. The "describes" element of this field allows the specific part of the resource which is described by the additional metadata to be indicated formally.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="describes" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Describes Reference summary: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. description: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. This is a formal field in that it is an error to provide a value in the "describes" element that does not correspond to the value of one of the "id" attributes in another eml module. This is designed to allow automated processors to discover the contextual relationship between the additional metadata and the resource it describes. example: knb.343.22</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="metadata">
- <xs:annotation>
- <xs:documentation>tooltip: Additional metadata summary: This element contains the additional metadata that is to be included in the document. The content of this field can be any well-formed XML fragment. description: This element contains the additional metadata to be included in the document. This element should be used for extending EML to include metadata that is not already available in another part of the EML specification, or to include site- or system-specific extensions that are needed beyond the core metadata. The additional metadata contained in this field describes the element referenced in the 'describes' element preceding it. The content of this field is any well-formed XML fragment. If that content contains namespace declarations, and if the namespace declaration can be resolved to a schema definition, then the content will be validated against that schema definition. If no namespace is present, or if no schema can be resolved, validation for this fragment will be skipped (validation is "lax"). example: <embargoDate>2006-10-10</embargoDate></xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:any processContents="lax">
- <xs:annotation>
- <xs:documentation>tooltip: Any Metadata summary: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur. description: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur.</xs:documentation>
- </xs:annotation>
- </xs:any>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="packageId" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Package Identifer summary: A globally unique identifier for the data package described by this EML metadata document that can be used to cite it elsewhere. description: A globally unique identifier for the data package described by this EML metadata document that can be used to cite it elsewhere. This identifier can be interpreted as the formal accession number for the data package, and is therefore required. It must be globally unique within a particular data management system, which should be specified in the system attribute as a URI. Typically a DOI or other identifier that is both citable and resolvable is used for published data packages. example: doi:10.5063/F17P8WGK example: https://doi.org/10.5063/F17P8WGK example: urn:uuid:04cd34fd-25d4-447f-ab6e-73a572c5d383</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="system" type="res:SystemType" use="required"/>
- <xs:attribute name="scope" type="res:ScopeType" fixed="system">
- <xs:annotation>
- <xs:documentation>tooltip: Identifer Scope summary: The scope of the identifier. description: The scope of the identifier. Scope is generally set to either "system", meaning that it is scoped according to the "system" attribute, or "document" if it is only to be in scope within this single document instance. In this particular use of scope, it is FIXED to be "system" because the packageId is required and always has the scope of the required "system". example: system</xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute ref="xml:lang" use="optional"/>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -1048,25 +909,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="access" type="acc:AccessType" minOccurs="0">
- <xs:annotation>
- <xs:documentation>tooltip: Access summary: Access control rules for the entire resource, which can be overridden by access rules in distribution trees description: An optional access tree at this location controls access to the entire metadata document. If this access element is omitted from the document, then the package submitter should be given full access to the package but all other users should be denied all access.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1303,25 +1145,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="dataset" type="ds:DatasetType">
- <xs:annotation>
- <xs:documentation>tooltip: Dataset Resource summary: A resource that describes a data set, which can include one or more data entities such as data tables. description: A resource that describes a data set, which can include one or more data entities such as data tables and spatial images (raster and vector). If included, this represents the primary resource that is described in this eml document.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1549,25 +1372,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="citation" type="cit:CitationType">
- <xs:annotation>
- <xs:documentation>tooltip: Literature Resource summary: A resource that describes a literature citation that one might find in a bibliography. description: A resource that describes a literature citation that one might find in a bibliography. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1778,25 +1582,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="software" type="sw:SoftwareType">
- <xs:annotation>
- <xs:documentation>tooltip: Software Resource summary: A resource that describes a software package, which can include commercial and non-commercial software as well as data processing programs. description: A resource that describes a software package, which can include commercial and non-commercial software as well as data processing programs. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -1996,25 +1781,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="protocol" type="pro:ProtocolType">
- <xs:annotation>
- <xs:documentation>tooltip: Protocol Resource summary: A resource that describes a scientific protocol, which can include one or more descriptions of methods and procedures. description: A resource that describes a scientific protocol, which can include one or more descriptions of methods and procedures. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2129,41 +1895,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="annotations" minOccurs="0" maxOccurs="1">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation List summary: A list of precisely-defined semantic statements about this resource. description: A list of annotations defining precise semantics for parts of this resource. The list consists of a set of annotation elements, each referring to a subject within the EML document using its references attribute, which provides a pointer to the id of the element being annotated.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="annotation" minOccurs="1" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about an element in the EML document. description: An annotation represents a precisely-defined semantic statement that applies to this resource. This semantic statement is used to associate precise semantics with a particular element in the EML document. The id of the element being annotated is listed in the references attribute, and must point to a unique id within the EML document. Each annotation consists of a propertyURI and valueURI that define a property and value that apply to the resource. The subject of the statement is implicitly the element that is listed in the references attribute. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="sem:SemanticAnnotation">
- <xs:attribute name="references" type="xs:string" use="required"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2364,32 +2095,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="annotation" minOccurs="1" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about an element in the EML document. description: An annotation represents a precisely-defined semantic statement that applies to this resource. This semantic statement is used to associate precise semantics with a particular element in the EML document. The id of the element being annotated is listed in the references attribute, and must point to a unique id within the EML document. Each annotation consists of a propertyURI and valueURI that define a property and value that apply to the resource. The subject of the statement is implicitly the element that is listed in the references attribute. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="sem:SemanticAnnotation">
- <xs:attribute name="references" type="xs:string" use="required"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2536,49 +2241,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="additionalMetadata" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Additional Metadata summary: A flexible field for including any other relevant metadata that pertains to the resource being described. description: A flexible field for including any other relevant metadata that pertains to the resource being described. This field allows EML to be extensible in that any XML-based metadata can be included in this element, including metadata from other standards such as the FGDC CSDGM. The "describes" element of this field allows the specific part of the resource which is described by the additional metadata to be indicated formally.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="describes" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Describes Reference summary: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. description: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. This is a formal field in that it is an error to provide a value in the "describes" element that does not correspond to the value of one of the "id" attributes in another eml module. This is designed to allow automated processors to discover the contextual relationship between the additional metadata and the resource it describes. example: knb.343.22</xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="metadata">
- <xs:annotation>
- <xs:documentation>tooltip: Additional metadata summary: This element contains the additional metadata that is to be included in the document. The content of this field can be any well-formed XML fragment. description: This element contains the additional metadata to be included in the document. This element should be used for extending EML to include metadata that is not already available in another part of the EML specification, or to include site- or system-specific extensions that are needed beyond the core metadata. The additional metadata contained in this field describes the element referenced in the 'describes' element preceding it. The content of this field is any well-formed XML fragment. If that content contains namespace declarations, and if the namespace declaration can be resolved to a schema definition, then the content will be validated against that schema definition. If no namespace is present, or if no schema can be resolved, validation for this fragment will be skipped (validation is "lax"). example: <embargoDate>2006-10-10</embargoDate></xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:any processContents="lax">
- <xs:annotation>
- <xs:documentation>tooltip: Any Metadata summary: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur. description: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur.</xs:documentation>
- </xs:annotation>
- </xs:any>
- </xs:sequence>
- </xs:complexType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="id" type="res:IDType" use="optional"/>
- </xs:complexType>
-</xs:element>
-
-
-
-
-
@@ -2699,25 +2361,6 @@
Showing:
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="describes" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
- <xs:annotation>
- <xs:documentation>tooltip: Describes Reference summary: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. description: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. This is a formal field in that it is an error to provide a value in the "describes" element that does not correspond to the value of one of the "id" attributes in another eml module. This is designed to allow automated processors to discover the contextual relationship between the additional metadata and the resource it describes. example: knb.343.22</xs:documentation>
- </xs:annotation>
-</xs:element>
-
-
-
-
-
@@ -2812,34 +2455,6 @@
Showing:
ANY element from ANY namespace
-
-
-
Source
-
-
-
-
-
-
-
<xs:element name="metadata">
- <xs:annotation>
- <xs:documentation>tooltip: Additional metadata summary: This element contains the additional metadata that is to be included in the document. The content of this field can be any well-formed XML fragment. description: This element contains the additional metadata to be included in the document. This element should be used for extending EML to include metadata that is not already available in another part of the EML specification, or to include site- or system-specific extensions that are needed beyond the core metadata. The additional metadata contained in this field describes the element referenced in the 'describes' element preceding it. The content of this field is any well-formed XML fragment. If that content contains namespace declarations, and if the namespace declaration can be resolved to a schema definition, then the content will be validated against that schema definition. If no namespace is present, or if no schema can be resolved, validation for this fragment will be skipped (validation is "lax"). example: <embargoDate>2006-10-10</embargoDate></xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:any processContents="lax">
- <xs:annotation>
- <xs:documentation>tooltip: Any Metadata summary: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur. description: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur.</xs:documentation>
- </xs:annotation>
- </xs:any>
- </xs:sequence>
- </xs:complexType>
-</xs:element>
<xs:attribute name="packageId" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation>tooltip: Package Identifer summary: A globally unique identifier for the data package described by this EML metadata document that can be used to cite it elsewhere. description: A globally unique identifier for the data package described by this EML metadata document that can be used to cite it elsewhere. This identifier can be interpreted as the formal accession number for the data package, and is therefore required. It must be globally unique within a particular data management system, which should be specified in the system attribute as a URI. Typically a DOI or other identifier that is both citable and resolvable is used for published data packages. example: doi:10.5063/F17P8WGK example: https://doi.org/10.5063/F17P8WGK example: urn:uuid:04cd34fd-25d4-447f-ab6e-73a572c5d383</xs:documentation>
- </xs:annotation>
-</xs:attribute>
<xs:attribute name="scope" type="res:ScopeType" fixed="system">
- <xs:annotation>
- <xs:documentation>tooltip: Identifer Scope summary: The scope of the identifier. description: The scope of the identifier. Scope is generally set to either "system", meaning that it is scoped according to the "system" attribute, or "document" if it is only to be in scope within this single document instance. In this particular use of scope, it is FIXED to be "system" because the packageId is required and always has the scope of the required "system". example: system</xs:documentation>
- </xs:annotation>
-</xs:attribute>
-
-
-
-
-
diff --git a/dist/schema/img/eml-access_xsd_Complex_Type_AccessRule.png b/dist/schema/img/eml-access_xsd_Complex_Type_AccessRule.png
index 47ea7108..79b0e9d2 100644
Binary files a/dist/schema/img/eml-access_xsd_Complex_Type_AccessRule.png and b/dist/schema/img/eml-access_xsd_Complex_Type_AccessRule.png differ
diff --git a/dist/schema/img/eml-access_xsd_Complex_Type_AccessType.png b/dist/schema/img/eml-access_xsd_Complex_Type_AccessType.png
index a3f6f44f..a9866ae5 100644
Binary files a/dist/schema/img/eml-access_xsd_Complex_Type_AccessType.png and b/dist/schema/img/eml-access_xsd_Complex_Type_AccessType.png differ
diff --git a/dist/schema/img/eml-access_xsd_Element_access.png b/dist/schema/img/eml-access_xsd_Element_access.png
index b7f0f37f..4ba2d203 100644
Binary files a/dist/schema/img/eml-access_xsd_Element_access.png and b/dist/schema/img/eml-access_xsd_Element_access.png differ
diff --git a/dist/schema/img/eml-access_xsd_Element_allow.png b/dist/schema/img/eml-access_xsd_Element_allow.png
index cf09b8ad..7e0ee41c 100644
Binary files a/dist/schema/img/eml-access_xsd_Element_allow.png and b/dist/schema/img/eml-access_xsd_Element_allow.png differ
diff --git a/dist/schema/img/eml-access_xsd_Element_deny.png b/dist/schema/img/eml-access_xsd_Element_deny.png
index 30446e20..1e58ffa0 100644
Binary files a/dist/schema/img/eml-access_xsd_Element_deny.png and b/dist/schema/img/eml-access_xsd_Element_deny.png differ
diff --git a/dist/schema/img/eml-access_xsd_Element_permission.png b/dist/schema/img/eml-access_xsd_Element_permission.png
index 7b924b41..ff4f32eb 100644
Binary files a/dist/schema/img/eml-access_xsd_Element_permission.png and b/dist/schema/img/eml-access_xsd_Element_permission.png differ
diff --git a/dist/schema/img/eml-access_xsd_Element_principal.png b/dist/schema/img/eml-access_xsd_Element_principal.png
index 4638d4d7..d6f476eb 100644
Binary files a/dist/schema/img/eml-access_xsd_Element_principal.png and b/dist/schema/img/eml-access_xsd_Element_principal.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Complex_Type_Accuracy.png b/dist/schema/img/eml-attribute_xsd_Complex_Type_Accuracy.png
index 07722f02..0e97828c 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Complex_Type_Accuracy.png and b/dist/schema/img/eml-attribute_xsd_Complex_Type_Accuracy.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Complex_Type_AttributeListType.png b/dist/schema/img/eml-attribute_xsd_Complex_Type_AttributeListType.png
index 549d2256..a234f810 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Complex_Type_AttributeListType.png and b/dist/schema/img/eml-attribute_xsd_Complex_Type_AttributeListType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Complex_Type_AttributeType.png b/dist/schema/img/eml-attribute_xsd_Complex_Type_AttributeType.png
index 0840b9d5..17f63057 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Complex_Type_AttributeType.png and b/dist/schema/img/eml-attribute_xsd_Complex_Type_AttributeType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Complex_Type_DateTimeDomainType.png b/dist/schema/img/eml-attribute_xsd_Complex_Type_DateTimeDomainType.png
index f52f7f60..5798fa83 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Complex_Type_DateTimeDomainType.png and b/dist/schema/img/eml-attribute_xsd_Complex_Type_DateTimeDomainType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Complex_Type_NonNumericDomainType.png b/dist/schema/img/eml-attribute_xsd_Complex_Type_NonNumericDomainType.png
index de645b01..01bcec74 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Complex_Type_NonNumericDomainType.png and b/dist/schema/img/eml-attribute_xsd_Complex_Type_NonNumericDomainType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Complex_Type_NumericDomainType.png b/dist/schema/img/eml-attribute_xsd_Complex_Type_NumericDomainType.png
index 499da3eb..39d91901 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Complex_Type_NumericDomainType.png and b/dist/schema/img/eml-attribute_xsd_Complex_Type_NumericDomainType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Complex_Type_PrecisionType.png b/dist/schema/img/eml-attribute_xsd_Complex_Type_PrecisionType.png
index f5de58ba..ec95a66b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Complex_Type_PrecisionType.png and b/dist/schema/img/eml-attribute_xsd_Complex_Type_PrecisionType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Complex_Type_UnitType.png b/dist/schema/img/eml-attribute_xsd_Complex_Type_UnitType.png
index 67fe0d57..19f904d3 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Complex_Type_UnitType.png and b/dist/schema/img/eml-attribute_xsd_Complex_Type_UnitType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_Group_BoundsDateGroup.png b/dist/schema/img/eml-attribute_xsd_Element_Group_BoundsDateGroup.png
index 1d49b8e0..9ac83a8b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_Group_BoundsDateGroup.png and b/dist/schema/img/eml-attribute_xsd_Element_Group_BoundsDateGroup.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_Group_BoundsGroup.png b/dist/schema/img/eml-attribute_xsd_Element_Group_BoundsGroup.png
index d6141b60..ae59ce27 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_Group_BoundsGroup.png and b/dist/schema/img/eml-attribute_xsd_Element_Group_BoundsGroup.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_accuracy.png b/dist/schema/img/eml-attribute_xsd_Element_accuracy.png
index 93288c1b..f43520c5 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_accuracy.png and b/dist/schema/img/eml-attribute_xsd_Element_accuracy.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_annotation.png b/dist/schema/img/eml-attribute_xsd_Element_annotation.png
index 6d85193c..d9539e38 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_annotation.png and b/dist/schema/img/eml-attribute_xsd_Element_annotation.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attribute.png b/dist/schema/img/eml-attribute_xsd_Element_attribute.png
index 1733caa9..d13d819b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attribute.png and b/dist/schema/img/eml-attribute_xsd_Element_attribute.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyExplanation.png b/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyExplanation.png
index e31d2fd0..48b7a611 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyExplanation.png and b/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyExplanation.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyReport.png b/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyReport.png
index 5e3b807e..da21f628 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyReport.png and b/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyReport.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyValue.png b/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyValue.png
index 9911f6ae..34fab751 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyValue.png and b/dist/schema/img/eml-attribute_xsd_Element_attributeAccuracyValue.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attributeDefinition.png b/dist/schema/img/eml-attribute_xsd_Element_attributeDefinition.png
index 98262e01..58aae77b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attributeDefinition.png and b/dist/schema/img/eml-attribute_xsd_Element_attributeDefinition.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attributeLabel.png b/dist/schema/img/eml-attribute_xsd_Element_attributeLabel.png
index 99b47771..6e05742b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attributeLabel.png and b/dist/schema/img/eml-attribute_xsd_Element_attributeLabel.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attributeList.png b/dist/schema/img/eml-attribute_xsd_Element_attributeList.png
index ffdc79cb..efa3fba2 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attributeList.png and b/dist/schema/img/eml-attribute_xsd_Element_attributeList.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attributeName.png b/dist/schema/img/eml-attribute_xsd_Element_attributeName.png
index 2f3d89e8..41f3dd7b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attributeName.png and b/dist/schema/img/eml-attribute_xsd_Element_attributeName.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_attribute_1.png b/dist/schema/img/eml-attribute_xsd_Element_attribute_1.png
index b589e360..62ffddfd 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_attribute_1.png and b/dist/schema/img/eml-attribute_xsd_Element_attribute_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_bounds.png b/dist/schema/img/eml-attribute_xsd_Element_bounds.png
index a789d316..1025a11c 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_bounds.png and b/dist/schema/img/eml-attribute_xsd_Element_bounds.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_bounds_1.png b/dist/schema/img/eml-attribute_xsd_Element_bounds_1.png
index 62274efe..55c63dde 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_bounds_1.png and b/dist/schema/img/eml-attribute_xsd_Element_bounds_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_citation.png b/dist/schema/img/eml-attribute_xsd_Element_citation.png
index ec80fc8a..bc13c190 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_citation.png and b/dist/schema/img/eml-attribute_xsd_Element_citation.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_code.png b/dist/schema/img/eml-attribute_xsd_Element_code.png
index 69fd3e85..cd706c10 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_code.png and b/dist/schema/img/eml-attribute_xsd_Element_code.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_codeDefinition.png b/dist/schema/img/eml-attribute_xsd_Element_codeDefinition.png
index cbca1cd8..93ced280 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_codeDefinition.png and b/dist/schema/img/eml-attribute_xsd_Element_codeDefinition.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_codeExplanation.png b/dist/schema/img/eml-attribute_xsd_Element_codeExplanation.png
index 0fd5336b..f75ddfaf 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_codeExplanation.png and b/dist/schema/img/eml-attribute_xsd_Element_codeExplanation.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_code_1.png b/dist/schema/img/eml-attribute_xsd_Element_code_1.png
index a5bc9069..4ba8645b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_code_1.png and b/dist/schema/img/eml-attribute_xsd_Element_code_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_codesetName.png b/dist/schema/img/eml-attribute_xsd_Element_codesetName.png
index f8d04833..09a39330 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_codesetName.png and b/dist/schema/img/eml-attribute_xsd_Element_codesetName.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_codesetURL.png b/dist/schema/img/eml-attribute_xsd_Element_codesetURL.png
index 933dbbe2..31e6299c 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_codesetURL.png and b/dist/schema/img/eml-attribute_xsd_Element_codesetURL.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_coverage.png b/dist/schema/img/eml-attribute_xsd_Element_coverage.png
index b0a10beb..cc6699fb 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_coverage.png and b/dist/schema/img/eml-attribute_xsd_Element_coverage.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_customUnit.png b/dist/schema/img/eml-attribute_xsd_Element_customUnit.png
index 118097a7..193dc509 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_customUnit.png and b/dist/schema/img/eml-attribute_xsd_Element_customUnit.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_dateTime.png b/dist/schema/img/eml-attribute_xsd_Element_dateTime.png
index c2bd8fd9..9f221132 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_dateTime.png and b/dist/schema/img/eml-attribute_xsd_Element_dateTime.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_dateTimeDomain.png b/dist/schema/img/eml-attribute_xsd_Element_dateTimeDomain.png
index a472be6d..f33ad9c6 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_dateTimeDomain.png and b/dist/schema/img/eml-attribute_xsd_Element_dateTimeDomain.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_dateTimePrecision.png b/dist/schema/img/eml-attribute_xsd_Element_dateTimePrecision.png
index e923437c..87359381 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_dateTimePrecision.png and b/dist/schema/img/eml-attribute_xsd_Element_dateTimePrecision.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_definition.png b/dist/schema/img/eml-attribute_xsd_Element_definition.png
index 4971e895..e3badb93 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_definition.png and b/dist/schema/img/eml-attribute_xsd_Element_definition.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_definitionAttributeReference.png b/dist/schema/img/eml-attribute_xsd_Element_definitionAttributeReference.png
index c30ee2e3..c86f7fe4 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_definitionAttributeReference.png and b/dist/schema/img/eml-attribute_xsd_Element_definitionAttributeReference.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_definition_1.png b/dist/schema/img/eml-attribute_xsd_Element_definition_1.png
index 648e45ba..bc4e2555 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_definition_1.png and b/dist/schema/img/eml-attribute_xsd_Element_definition_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_entityCodeList.png b/dist/schema/img/eml-attribute_xsd_Element_entityCodeList.png
index ba82fe3a..ef5cf380 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_entityCodeList.png and b/dist/schema/img/eml-attribute_xsd_Element_entityCodeList.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_entityReference.png b/dist/schema/img/eml-attribute_xsd_Element_entityReference.png
index e12cdbff..ccadf3b7 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_entityReference.png and b/dist/schema/img/eml-attribute_xsd_Element_entityReference.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_enumeratedDomain.png b/dist/schema/img/eml-attribute_xsd_Element_enumeratedDomain.png
index fc3e780f..fce37982 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_enumeratedDomain.png and b/dist/schema/img/eml-attribute_xsd_Element_enumeratedDomain.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_externalCodeSet.png b/dist/schema/img/eml-attribute_xsd_Element_externalCodeSet.png
index 329a9c0a..ba5b7d5e 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_externalCodeSet.png and b/dist/schema/img/eml-attribute_xsd_Element_externalCodeSet.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_formatString.png b/dist/schema/img/eml-attribute_xsd_Element_formatString.png
index a3d27ad8..a49d6559 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_formatString.png and b/dist/schema/img/eml-attribute_xsd_Element_formatString.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_interval.png b/dist/schema/img/eml-attribute_xsd_Element_interval.png
index d15f6423..7f5aa73e 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_interval.png and b/dist/schema/img/eml-attribute_xsd_Element_interval.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_maximum.png b/dist/schema/img/eml-attribute_xsd_Element_maximum.png
index a2390e45..3fecc88c 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_maximum.png and b/dist/schema/img/eml-attribute_xsd_Element_maximum.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_maximum_1.png b/dist/schema/img/eml-attribute_xsd_Element_maximum_1.png
index 24010974..e718d4ec 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_maximum_1.png and b/dist/schema/img/eml-attribute_xsd_Element_maximum_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_measurementScale.png b/dist/schema/img/eml-attribute_xsd_Element_measurementScale.png
index 481d741e..652782b6 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_measurementScale.png and b/dist/schema/img/eml-attribute_xsd_Element_measurementScale.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_methods.png b/dist/schema/img/eml-attribute_xsd_Element_methods.png
index 6cd658bb..daef3b7a 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_methods.png and b/dist/schema/img/eml-attribute_xsd_Element_methods.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_minimum.png b/dist/schema/img/eml-attribute_xsd_Element_minimum.png
index d5c1a621..82e24c08 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_minimum.png and b/dist/schema/img/eml-attribute_xsd_Element_minimum.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_minimum_1.png b/dist/schema/img/eml-attribute_xsd_Element_minimum_1.png
index 27e753da..b0fc1fba 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_minimum_1.png and b/dist/schema/img/eml-attribute_xsd_Element_minimum_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_missingValueCode.png b/dist/schema/img/eml-attribute_xsd_Element_missingValueCode.png
index 8c28c0fc..8c2e07e1 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_missingValueCode.png and b/dist/schema/img/eml-attribute_xsd_Element_missingValueCode.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_nominal.png b/dist/schema/img/eml-attribute_xsd_Element_nominal.png
index 9b212f55..2d1deb66 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_nominal.png and b/dist/schema/img/eml-attribute_xsd_Element_nominal.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_nonNumericDomain.png b/dist/schema/img/eml-attribute_xsd_Element_nonNumericDomain.png
index 096feb97..31c48eac 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_nonNumericDomain.png and b/dist/schema/img/eml-attribute_xsd_Element_nonNumericDomain.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_nonNumericDomain_1.png b/dist/schema/img/eml-attribute_xsd_Element_nonNumericDomain_1.png
index 096feb97..31c48eac 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_nonNumericDomain_1.png and b/dist/schema/img/eml-attribute_xsd_Element_nonNumericDomain_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_numberType.png b/dist/schema/img/eml-attribute_xsd_Element_numberType.png
index 584d3483..2bc1cfeb 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_numberType.png and b/dist/schema/img/eml-attribute_xsd_Element_numberType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_numericDomain.png b/dist/schema/img/eml-attribute_xsd_Element_numericDomain.png
index ecaf79e3..6c4533ea 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_numericDomain.png and b/dist/schema/img/eml-attribute_xsd_Element_numericDomain.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_numericDomain_1.png b/dist/schema/img/eml-attribute_xsd_Element_numericDomain_1.png
index ecaf79e3..6c4533ea 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_numericDomain_1.png and b/dist/schema/img/eml-attribute_xsd_Element_numericDomain_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_orderAttributeReference.png b/dist/schema/img/eml-attribute_xsd_Element_orderAttributeReference.png
index 05536242..5532a444 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_orderAttributeReference.png and b/dist/schema/img/eml-attribute_xsd_Element_orderAttributeReference.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_ordinal.png b/dist/schema/img/eml-attribute_xsd_Element_ordinal.png
index 778f2153..5d3809f6 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_ordinal.png and b/dist/schema/img/eml-attribute_xsd_Element_ordinal.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_pattern.png b/dist/schema/img/eml-attribute_xsd_Element_pattern.png
index 8f122b2d..d41b8399 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_pattern.png and b/dist/schema/img/eml-attribute_xsd_Element_pattern.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_precision.png b/dist/schema/img/eml-attribute_xsd_Element_precision.png
index 2a314021..076f2f59 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_precision.png and b/dist/schema/img/eml-attribute_xsd_Element_precision.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_precision_1.png b/dist/schema/img/eml-attribute_xsd_Element_precision_1.png
index 2a314021..076f2f59 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_precision_1.png and b/dist/schema/img/eml-attribute_xsd_Element_precision_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_quantitativeAttributeAccuracyAssessment.png b/dist/schema/img/eml-attribute_xsd_Element_quantitativeAttributeAccuracyAssessment.png
index e4ab128e..61b11690 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_quantitativeAttributeAccuracyAssessment.png and b/dist/schema/img/eml-attribute_xsd_Element_quantitativeAttributeAccuracyAssessment.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_ratio.png b/dist/schema/img/eml-attribute_xsd_Element_ratio.png
index 936d3fcf..4f0f62f0 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_ratio.png and b/dist/schema/img/eml-attribute_xsd_Element_ratio.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_source.png b/dist/schema/img/eml-attribute_xsd_Element_source.png
index 90406b01..46e34990 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_source.png and b/dist/schema/img/eml-attribute_xsd_Element_source.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_source_1.png b/dist/schema/img/eml-attribute_xsd_Element_source_1.png
index 202953aa..f8be4236 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_source_1.png and b/dist/schema/img/eml-attribute_xsd_Element_source_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_standardUnit.png b/dist/schema/img/eml-attribute_xsd_Element_standardUnit.png
index 4163f6a5..74b8c444 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_standardUnit.png and b/dist/schema/img/eml-attribute_xsd_Element_standardUnit.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_storageType.png b/dist/schema/img/eml-attribute_xsd_Element_storageType.png
index f4161f56..4a802659 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_storageType.png and b/dist/schema/img/eml-attribute_xsd_Element_storageType.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_textDomain.png b/dist/schema/img/eml-attribute_xsd_Element_textDomain.png
index 2900b5b3..757d1983 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_textDomain.png and b/dist/schema/img/eml-attribute_xsd_Element_textDomain.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_unit.png b/dist/schema/img/eml-attribute_xsd_Element_unit.png
index 3d4c2e0d..46bd2b1b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_unit.png and b/dist/schema/img/eml-attribute_xsd_Element_unit.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_unit_1.png b/dist/schema/img/eml-attribute_xsd_Element_unit_1.png
index 3d4c2e0d..46bd2b1b 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_unit_1.png and b/dist/schema/img/eml-attribute_xsd_Element_unit_1.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Element_valueAttributeReference.png b/dist/schema/img/eml-attribute_xsd_Element_valueAttributeReference.png
index 0271ba40..5858b9c3 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Element_valueAttributeReference.png and b/dist/schema/img/eml-attribute_xsd_Element_valueAttributeReference.png differ
diff --git a/dist/schema/img/eml-attribute_xsd_Simple_Type_NumberType.png b/dist/schema/img/eml-attribute_xsd_Simple_Type_NumberType.png
index caeb3622..56464533 100644
Binary files a/dist/schema/img/eml-attribute_xsd_Simple_Type_NumberType.png and b/dist/schema/img/eml-attribute_xsd_Simple_Type_NumberType.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Complex_Type_ConstraintType.png b/dist/schema/img/eml-constraint_xsd_Complex_Type_ConstraintType.png
index a60faf8d..5af2186c 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Complex_Type_ConstraintType.png and b/dist/schema/img/eml-constraint_xsd_Complex_Type_ConstraintType.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_Group_ConstraintBaseGroup.png b/dist/schema/img/eml-constraint_xsd_Element_Group_ConstraintBaseGroup.png
index 4a5d066f..168e2a93 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_Group_ConstraintBaseGroup.png and b/dist/schema/img/eml-constraint_xsd_Element_Group_ConstraintBaseGroup.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_Group_ForeignKeyGroup.png b/dist/schema/img/eml-constraint_xsd_Element_Group_ForeignKeyGroup.png
index 903f59e2..14716ed6 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_Group_ForeignKeyGroup.png and b/dist/schema/img/eml-constraint_xsd_Element_Group_ForeignKeyGroup.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_attributeReference.png b/dist/schema/img/eml-constraint_xsd_Element_attributeReference.png
index c75ce856..5c72bf1b 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_attributeReference.png and b/dist/schema/img/eml-constraint_xsd_Element_attributeReference.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_attributeReference_1.png b/dist/schema/img/eml-constraint_xsd_Element_attributeReference_1.png
index c75ce856..5c72bf1b 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_attributeReference_1.png and b/dist/schema/img/eml-constraint_xsd_Element_attributeReference_1.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_attributeReference_2.png b/dist/schema/img/eml-constraint_xsd_Element_attributeReference_2.png
index c75ce856..5c72bf1b 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_attributeReference_2.png and b/dist/schema/img/eml-constraint_xsd_Element_attributeReference_2.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_attributeReference_3.png b/dist/schema/img/eml-constraint_xsd_Element_attributeReference_3.png
index c75ce856..5c72bf1b 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_attributeReference_3.png and b/dist/schema/img/eml-constraint_xsd_Element_attributeReference_3.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_attributeReference_4.png b/dist/schema/img/eml-constraint_xsd_Element_attributeReference_4.png
index c75ce856..5c72bf1b 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_attributeReference_4.png and b/dist/schema/img/eml-constraint_xsd_Element_attributeReference_4.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_cardinality.png b/dist/schema/img/eml-constraint_xsd_Element_cardinality.png
index 8cb599d0..3282e723 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_cardinality.png and b/dist/schema/img/eml-constraint_xsd_Element_cardinality.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_checkCondition.png b/dist/schema/img/eml-constraint_xsd_Element_checkCondition.png
index 146da04e..61e4fe05 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_checkCondition.png and b/dist/schema/img/eml-constraint_xsd_Element_checkCondition.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_checkConstraint.png b/dist/schema/img/eml-constraint_xsd_Element_checkConstraint.png
index b07e199b..edf16a95 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_checkConstraint.png and b/dist/schema/img/eml-constraint_xsd_Element_checkConstraint.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_childOccurences.png b/dist/schema/img/eml-constraint_xsd_Element_childOccurences.png
index aa98c46e..bf17f571 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_childOccurences.png and b/dist/schema/img/eml-constraint_xsd_Element_childOccurences.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_constraintDescription.png b/dist/schema/img/eml-constraint_xsd_Element_constraintDescription.png
index bdb87fb8..abb626eb 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_constraintDescription.png and b/dist/schema/img/eml-constraint_xsd_Element_constraintDescription.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_constraintName.png b/dist/schema/img/eml-constraint_xsd_Element_constraintName.png
index e770f445..7bfd8a7f 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_constraintName.png and b/dist/schema/img/eml-constraint_xsd_Element_constraintName.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_entityReference.png b/dist/schema/img/eml-constraint_xsd_Element_entityReference.png
index 9b4b4e93..ab4eee08 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_entityReference.png and b/dist/schema/img/eml-constraint_xsd_Element_entityReference.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_foreignKey.png b/dist/schema/img/eml-constraint_xsd_Element_foreignKey.png
index 27512a89..e876c28e 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_foreignKey.png and b/dist/schema/img/eml-constraint_xsd_Element_foreignKey.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_joinCondition.png b/dist/schema/img/eml-constraint_xsd_Element_joinCondition.png
index b9ebde50..3f33961d 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_joinCondition.png and b/dist/schema/img/eml-constraint_xsd_Element_joinCondition.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_key.png b/dist/schema/img/eml-constraint_xsd_Element_key.png
index e0fce5a1..09ce7eb0 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_key.png and b/dist/schema/img/eml-constraint_xsd_Element_key.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_key_1.png b/dist/schema/img/eml-constraint_xsd_Element_key_1.png
index e0fce5a1..09ce7eb0 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_key_1.png and b/dist/schema/img/eml-constraint_xsd_Element_key_1.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_key_2.png b/dist/schema/img/eml-constraint_xsd_Element_key_2.png
index e0fce5a1..09ce7eb0 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_key_2.png and b/dist/schema/img/eml-constraint_xsd_Element_key_2.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_key_3.png b/dist/schema/img/eml-constraint_xsd_Element_key_3.png
index e0fce5a1..09ce7eb0 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_key_3.png and b/dist/schema/img/eml-constraint_xsd_Element_key_3.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_notNullConstraint.png b/dist/schema/img/eml-constraint_xsd_Element_notNullConstraint.png
index b523e322..9b648bf6 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_notNullConstraint.png and b/dist/schema/img/eml-constraint_xsd_Element_notNullConstraint.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_parentOccurences.png b/dist/schema/img/eml-constraint_xsd_Element_parentOccurences.png
index f723a339..787ef4b4 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_parentOccurences.png and b/dist/schema/img/eml-constraint_xsd_Element_parentOccurences.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_primaryKey.png b/dist/schema/img/eml-constraint_xsd_Element_primaryKey.png
index 439644d0..9eea74c7 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_primaryKey.png and b/dist/schema/img/eml-constraint_xsd_Element_primaryKey.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_referencedKey.png b/dist/schema/img/eml-constraint_xsd_Element_referencedKey.png
index 8ac52c26..b27b7fd2 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_referencedKey.png and b/dist/schema/img/eml-constraint_xsd_Element_referencedKey.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_relationshipType.png b/dist/schema/img/eml-constraint_xsd_Element_relationshipType.png
index 1dae947b..640de581 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_relationshipType.png and b/dist/schema/img/eml-constraint_xsd_Element_relationshipType.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Element_uniqueKey.png b/dist/schema/img/eml-constraint_xsd_Element_uniqueKey.png
index 59cbf9af..1654beb0 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Element_uniqueKey.png and b/dist/schema/img/eml-constraint_xsd_Element_uniqueKey.png differ
diff --git a/dist/schema/img/eml-constraint_xsd_Simple_Type_CardinalityChildOccurancesType.png b/dist/schema/img/eml-constraint_xsd_Simple_Type_CardinalityChildOccurancesType.png
index fc8e8e99..ea02eaea 100644
Binary files a/dist/schema/img/eml-constraint_xsd_Simple_Type_CardinalityChildOccurancesType.png and b/dist/schema/img/eml-constraint_xsd_Simple_Type_CardinalityChildOccurancesType.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Complex_Type_Coverage.png b/dist/schema/img/eml-coverage_xsd_Complex_Type_Coverage.png
index b42681d1..6521c4ec 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Complex_Type_Coverage.png and b/dist/schema/img/eml-coverage_xsd_Complex_Type_Coverage.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Complex_Type_GRingPointType.png b/dist/schema/img/eml-coverage_xsd_Complex_Type_GRingPointType.png
index dfdeb626..090f3f54 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Complex_Type_GRingPointType.png and b/dist/schema/img/eml-coverage_xsd_Complex_Type_GRingPointType.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Complex_Type_GeographicCoverage.png b/dist/schema/img/eml-coverage_xsd_Complex_Type_GeographicCoverage.png
index 7367d3c9..f0e2fb9d 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Complex_Type_GeographicCoverage.png and b/dist/schema/img/eml-coverage_xsd_Complex_Type_GeographicCoverage.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Complex_Type_SingleDateTimeType.png b/dist/schema/img/eml-coverage_xsd_Complex_Type_SingleDateTimeType.png
index 339dff85..b9c02b2b 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Complex_Type_SingleDateTimeType.png and b/dist/schema/img/eml-coverage_xsd_Complex_Type_SingleDateTimeType.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Complex_Type_TaxonomicClassificationType.png b/dist/schema/img/eml-coverage_xsd_Complex_Type_TaxonomicClassificationType.png
index 5b70061e..813e3642 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Complex_Type_TaxonomicClassificationType.png and b/dist/schema/img/eml-coverage_xsd_Complex_Type_TaxonomicClassificationType.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Complex_Type_TaxonomicCoverage.png b/dist/schema/img/eml-coverage_xsd_Complex_Type_TaxonomicCoverage.png
index 30afada2..47534bf1 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Complex_Type_TaxonomicCoverage.png and b/dist/schema/img/eml-coverage_xsd_Complex_Type_TaxonomicCoverage.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Complex_Type_TemporalCoverage.png b/dist/schema/img/eml-coverage_xsd_Complex_Type_TemporalCoverage.png
index 464c0dbc..2e77074a 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Complex_Type_TemporalCoverage.png and b/dist/schema/img/eml-coverage_xsd_Complex_Type_TemporalCoverage.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_alternativeTimeScale.png b/dist/schema/img/eml-coverage_xsd_Element_alternativeTimeScale.png
index a16fdacb..47a0c898 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_alternativeTimeScale.png and b/dist/schema/img/eml-coverage_xsd_Element_alternativeTimeScale.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_altitudeMaximum.png b/dist/schema/img/eml-coverage_xsd_Element_altitudeMaximum.png
index 5a5c6550..5a9fb91a 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_altitudeMaximum.png and b/dist/schema/img/eml-coverage_xsd_Element_altitudeMaximum.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_altitudeMinimum.png b/dist/schema/img/eml-coverage_xsd_Element_altitudeMinimum.png
index 988456f6..43f29912 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_altitudeMinimum.png and b/dist/schema/img/eml-coverage_xsd_Element_altitudeMinimum.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_altitudeUnits.png b/dist/schema/img/eml-coverage_xsd_Element_altitudeUnits.png
index 36bde48c..7b15fa99 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_altitudeUnits.png and b/dist/schema/img/eml-coverage_xsd_Element_altitudeUnits.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_beginDate.png b/dist/schema/img/eml-coverage_xsd_Element_beginDate.png
index 3ad37cc9..604d844b 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_beginDate.png and b/dist/schema/img/eml-coverage_xsd_Element_beginDate.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_boundingAltitudes.png b/dist/schema/img/eml-coverage_xsd_Element_boundingAltitudes.png
index 820ca917..1ae716fb 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_boundingAltitudes.png and b/dist/schema/img/eml-coverage_xsd_Element_boundingAltitudes.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_boundingCoordinates.png b/dist/schema/img/eml-coverage_xsd_Element_boundingCoordinates.png
index 5d3d5f3e..b0b08760 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_boundingCoordinates.png and b/dist/schema/img/eml-coverage_xsd_Element_boundingCoordinates.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_calendarDate.png b/dist/schema/img/eml-coverage_xsd_Element_calendarDate.png
index b7274991..33cd81fc 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_calendarDate.png and b/dist/schema/img/eml-coverage_xsd_Element_calendarDate.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_classificationSystem.png b/dist/schema/img/eml-coverage_xsd_Element_classificationSystem.png
index bf231870..261570b1 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_classificationSystem.png and b/dist/schema/img/eml-coverage_xsd_Element_classificationSystem.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_classificationSystemCitation.png b/dist/schema/img/eml-coverage_xsd_Element_classificationSystemCitation.png
index 9fd7a18c..54b78b0e 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_classificationSystemCitation.png and b/dist/schema/img/eml-coverage_xsd_Element_classificationSystemCitation.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_classificationSystemModifications.png b/dist/schema/img/eml-coverage_xsd_Element_classificationSystemModifications.png
index d688759c..02f61565 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_classificationSystemModifications.png and b/dist/schema/img/eml-coverage_xsd_Element_classificationSystemModifications.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_commonName.png b/dist/schema/img/eml-coverage_xsd_Element_commonName.png
index 56f1db75..5a90c988 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_commonName.png and b/dist/schema/img/eml-coverage_xsd_Element_commonName.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygon.png b/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygon.png
index 701483d4..cae4008a 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygon.png and b/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygon.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygonExclusionGRing.png b/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygonExclusionGRing.png
index 649c879f..e65aad4a 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygonExclusionGRing.png and b/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygonExclusionGRing.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygonOuterGRing.png b/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygonOuterGRing.png
index f122e3ec..02ca3067 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygonOuterGRing.png and b/dist/schema/img/eml-coverage_xsd_Element_datasetGPolygonOuterGRing.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_eastBoundingCoordinate.png b/dist/schema/img/eml-coverage_xsd_Element_eastBoundingCoordinate.png
index 2edd136c..0070e5fb 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_eastBoundingCoordinate.png and b/dist/schema/img/eml-coverage_xsd_Element_eastBoundingCoordinate.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_endDate.png b/dist/schema/img/eml-coverage_xsd_Element_endDate.png
index c9e7bd9b..e03fa94d 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_endDate.png and b/dist/schema/img/eml-coverage_xsd_Element_endDate.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_gRing.png b/dist/schema/img/eml-coverage_xsd_Element_gRing.png
index 003c06e7..8962b423 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_gRing.png and b/dist/schema/img/eml-coverage_xsd_Element_gRing.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_gRingLatitude.png b/dist/schema/img/eml-coverage_xsd_Element_gRingLatitude.png
index cf2aff2b..54373199 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_gRingLatitude.png and b/dist/schema/img/eml-coverage_xsd_Element_gRingLatitude.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_gRingLongitude.png b/dist/schema/img/eml-coverage_xsd_Element_gRingLongitude.png
index b145bfe0..729ef5a6 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_gRingLongitude.png and b/dist/schema/img/eml-coverage_xsd_Element_gRingLongitude.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_gRingPoint.png b/dist/schema/img/eml-coverage_xsd_Element_gRingPoint.png
index 1ba0cdc3..c2055d09 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_gRingPoint.png and b/dist/schema/img/eml-coverage_xsd_Element_gRingPoint.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_gRingPoint_1.png b/dist/schema/img/eml-coverage_xsd_Element_gRingPoint_1.png
index 95ece1ba..554b573b 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_gRingPoint_1.png and b/dist/schema/img/eml-coverage_xsd_Element_gRingPoint_1.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_gRing_1.png b/dist/schema/img/eml-coverage_xsd_Element_gRing_1.png
index 565c4f2a..ced0c59e 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_gRing_1.png and b/dist/schema/img/eml-coverage_xsd_Element_gRing_1.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_generalTaxonomicCoverage.png b/dist/schema/img/eml-coverage_xsd_Element_generalTaxonomicCoverage.png
index 34cf7398..107c5969 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_generalTaxonomicCoverage.png and b/dist/schema/img/eml-coverage_xsd_Element_generalTaxonomicCoverage.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_geographicCoverage.png b/dist/schema/img/eml-coverage_xsd_Element_geographicCoverage.png
index ad03bafc..a4501044 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_geographicCoverage.png and b/dist/schema/img/eml-coverage_xsd_Element_geographicCoverage.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_geographicDescription.png b/dist/schema/img/eml-coverage_xsd_Element_geographicDescription.png
index b6b15d7e..ade1e007 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_geographicDescription.png and b/dist/schema/img/eml-coverage_xsd_Element_geographicDescription.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_identificationReference.png b/dist/schema/img/eml-coverage_xsd_Element_identificationReference.png
index f6240b97..b3d33801 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_identificationReference.png and b/dist/schema/img/eml-coverage_xsd_Element_identificationReference.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_identifierName.png b/dist/schema/img/eml-coverage_xsd_Element_identifierName.png
index c5fdf991..b24ed999 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_identifierName.png and b/dist/schema/img/eml-coverage_xsd_Element_identifierName.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_northBoundingCoordinate.png b/dist/schema/img/eml-coverage_xsd_Element_northBoundingCoordinate.png
index e9c86247..77b7eb7c 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_northBoundingCoordinate.png and b/dist/schema/img/eml-coverage_xsd_Element_northBoundingCoordinate.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_originator.png b/dist/schema/img/eml-coverage_xsd_Element_originator.png
index 8721d70d..1bfa7598 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_originator.png and b/dist/schema/img/eml-coverage_xsd_Element_originator.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_rangeOfDates.png b/dist/schema/img/eml-coverage_xsd_Element_rangeOfDates.png
index 3492a6c2..7c2024fe 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_rangeOfDates.png and b/dist/schema/img/eml-coverage_xsd_Element_rangeOfDates.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_repository.png b/dist/schema/img/eml-coverage_xsd_Element_repository.png
index 330c652a..9676e250 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_repository.png and b/dist/schema/img/eml-coverage_xsd_Element_repository.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_singleDateTime.png b/dist/schema/img/eml-coverage_xsd_Element_singleDateTime.png
index 2fd80181..ccc692a8 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_singleDateTime.png and b/dist/schema/img/eml-coverage_xsd_Element_singleDateTime.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_southBoundingCoordinate.png b/dist/schema/img/eml-coverage_xsd_Element_southBoundingCoordinate.png
index 647f69e2..9a79cf33 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_southBoundingCoordinate.png and b/dist/schema/img/eml-coverage_xsd_Element_southBoundingCoordinate.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_specimen.png b/dist/schema/img/eml-coverage_xsd_Element_specimen.png
index 159e1760..00bac4f1 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_specimen.png and b/dist/schema/img/eml-coverage_xsd_Element_specimen.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonId.png b/dist/schema/img/eml-coverage_xsd_Element_taxonId.png
index d376317a..5124ad3b 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonId.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonId.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonRankName.png b/dist/schema/img/eml-coverage_xsd_Element_taxonRankName.png
index 25e0c366..6760ca68 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonRankName.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonRankName.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonRankValue.png b/dist/schema/img/eml-coverage_xsd_Element_taxonRankValue.png
index d00b42b9..5e4a5bc1 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonRankValue.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonRankValue.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonomicClassification.png b/dist/schema/img/eml-coverage_xsd_Element_taxonomicClassification.png
index 42d04ce0..f17d81e4 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonomicClassification.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonomicClassification.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonomicClassification_1.png b/dist/schema/img/eml-coverage_xsd_Element_taxonomicClassification_1.png
index 6b81ff7e..59c9590e 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonomicClassification_1.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonomicClassification_1.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonomicCompleteness.png b/dist/schema/img/eml-coverage_xsd_Element_taxonomicCompleteness.png
index 3a85a890..355c218c 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonomicCompleteness.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonomicCompleteness.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonomicCoverage.png b/dist/schema/img/eml-coverage_xsd_Element_taxonomicCoverage.png
index 459f320b..24dccdc1 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonomicCoverage.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonomicCoverage.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonomicProcedures.png b/dist/schema/img/eml-coverage_xsd_Element_taxonomicProcedures.png
index 15af9c16..232eeff7 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonomicProcedures.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonomicProcedures.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_taxonomicSystem.png b/dist/schema/img/eml-coverage_xsd_Element_taxonomicSystem.png
index b5a88c71..ed870c3f 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_taxonomicSystem.png and b/dist/schema/img/eml-coverage_xsd_Element_taxonomicSystem.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_temporalCoverage.png b/dist/schema/img/eml-coverage_xsd_Element_temporalCoverage.png
index 5467dd3d..4403d1fc 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_temporalCoverage.png and b/dist/schema/img/eml-coverage_xsd_Element_temporalCoverage.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_time.png b/dist/schema/img/eml-coverage_xsd_Element_time.png
index 1b45bf41..ea717944 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_time.png and b/dist/schema/img/eml-coverage_xsd_Element_time.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeEstimate.png b/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeEstimate.png
index 89c87a98..d23b3ba4 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeEstimate.png and b/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeEstimate.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeExplanation.png b/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeExplanation.png
index cfdb6324..d7cea2a7 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeExplanation.png and b/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeExplanation.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeUncertainty.png b/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeUncertainty.png
index 98e4abdf..ce011ab6 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeUncertainty.png and b/dist/schema/img/eml-coverage_xsd_Element_timeScaleAgeUncertainty.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_timeScaleCitation.png b/dist/schema/img/eml-coverage_xsd_Element_timeScaleCitation.png
index 4f330a55..e2e6e9b3 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_timeScaleCitation.png and b/dist/schema/img/eml-coverage_xsd_Element_timeScaleCitation.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_timeScaleName.png b/dist/schema/img/eml-coverage_xsd_Element_timeScaleName.png
index e18ab97b..1181f18f 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_timeScaleName.png and b/dist/schema/img/eml-coverage_xsd_Element_timeScaleName.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_vouchers.png b/dist/schema/img/eml-coverage_xsd_Element_vouchers.png
index 6214fa1e..ff135b1a 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_vouchers.png and b/dist/schema/img/eml-coverage_xsd_Element_vouchers.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Element_westBoundingCoordinate.png b/dist/schema/img/eml-coverage_xsd_Element_westBoundingCoordinate.png
index 514fa1ff..16af0174 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Element_westBoundingCoordinate.png and b/dist/schema/img/eml-coverage_xsd_Element_westBoundingCoordinate.png differ
diff --git a/dist/schema/img/eml-coverage_xsd_Simple_Type_GRingType.png b/dist/schema/img/eml-coverage_xsd_Simple_Type_GRingType.png
index 9e079783..e98b58bd 100644
Binary files a/dist/schema/img/eml-coverage_xsd_Simple_Type_GRingType.png and b/dist/schema/img/eml-coverage_xsd_Simple_Type_GRingType.png differ
diff --git a/dist/schema/img/eml-dataTable_xsd_Complex_Type_DataTableType.png b/dist/schema/img/eml-dataTable_xsd_Complex_Type_DataTableType.png
index 0af313a4..ef21b7a0 100644
Binary files a/dist/schema/img/eml-dataTable_xsd_Complex_Type_DataTableType.png and b/dist/schema/img/eml-dataTable_xsd_Complex_Type_DataTableType.png differ
diff --git a/dist/schema/img/eml-dataTable_xsd_Element_attributeList.png b/dist/schema/img/eml-dataTable_xsd_Element_attributeList.png
index 9c6a98c6..66a27bd4 100644
Binary files a/dist/schema/img/eml-dataTable_xsd_Element_attributeList.png and b/dist/schema/img/eml-dataTable_xsd_Element_attributeList.png differ
diff --git a/dist/schema/img/eml-dataTable_xsd_Element_caseSensitive.png b/dist/schema/img/eml-dataTable_xsd_Element_caseSensitive.png
index e47e063b..a6efcbb8 100644
Binary files a/dist/schema/img/eml-dataTable_xsd_Element_caseSensitive.png and b/dist/schema/img/eml-dataTable_xsd_Element_caseSensitive.png differ
diff --git a/dist/schema/img/eml-dataTable_xsd_Element_constraint.png b/dist/schema/img/eml-dataTable_xsd_Element_constraint.png
index 53e6af35..4743f05b 100644
Binary files a/dist/schema/img/eml-dataTable_xsd_Element_constraint.png and b/dist/schema/img/eml-dataTable_xsd_Element_constraint.png differ
diff --git a/dist/schema/img/eml-dataTable_xsd_Element_dataTable.png b/dist/schema/img/eml-dataTable_xsd_Element_dataTable.png
index 50a2ea09..395cec30 100644
Binary files a/dist/schema/img/eml-dataTable_xsd_Element_dataTable.png and b/dist/schema/img/eml-dataTable_xsd_Element_dataTable.png differ
diff --git a/dist/schema/img/eml-dataTable_xsd_Element_numberOfRecords.png b/dist/schema/img/eml-dataTable_xsd_Element_numberOfRecords.png
index 65c802ca..a29780db 100644
Binary files a/dist/schema/img/eml-dataTable_xsd_Element_numberOfRecords.png and b/dist/schema/img/eml-dataTable_xsd_Element_numberOfRecords.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Complex_Type_DatasetType.png b/dist/schema/img/eml-dataset_xsd_Complex_Type_DatasetType.png
index 4cdacb64..a8d55a9c 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Complex_Type_DatasetType.png and b/dist/schema/img/eml-dataset_xsd_Complex_Type_DatasetType.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Complex_Type_MaintenanceType.png b/dist/schema/img/eml-dataset_xsd_Complex_Type_MaintenanceType.png
index c35e6a86..36270c73 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Complex_Type_MaintenanceType.png and b/dist/schema/img/eml-dataset_xsd_Complex_Type_MaintenanceType.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_acknowledgements.png b/dist/schema/img/eml-dataset_xsd_Element_acknowledgements.png
index f9ce3892..7e7cb9a9 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_acknowledgements.png and b/dist/schema/img/eml-dataset_xsd_Element_acknowledgements.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_changeDate.png b/dist/schema/img/eml-dataset_xsd_Element_changeDate.png
index 28ce6219..c348cfd7 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_changeDate.png and b/dist/schema/img/eml-dataset_xsd_Element_changeDate.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_changeHistory.png b/dist/schema/img/eml-dataset_xsd_Element_changeHistory.png
index dd783a6e..916e028c 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_changeHistory.png and b/dist/schema/img/eml-dataset_xsd_Element_changeHistory.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_changeScope.png b/dist/schema/img/eml-dataset_xsd_Element_changeScope.png
index 12b9052f..287390f3 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_changeScope.png and b/dist/schema/img/eml-dataset_xsd_Element_changeScope.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_comment.png b/dist/schema/img/eml-dataset_xsd_Element_comment.png
index 5ddfcb4e..cbd3d839 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_comment.png and b/dist/schema/img/eml-dataset_xsd_Element_comment.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_contact.png b/dist/schema/img/eml-dataset_xsd_Element_contact.png
index 218fce21..ab5b6c23 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_contact.png and b/dist/schema/img/eml-dataset_xsd_Element_contact.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_dataTable.png b/dist/schema/img/eml-dataset_xsd_Element_dataTable.png
index 21fbc227..414418e4 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_dataTable.png and b/dist/schema/img/eml-dataset_xsd_Element_dataTable.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_dataset.png b/dist/schema/img/eml-dataset_xsd_Element_dataset.png
index 9afc3eea..677b42f7 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_dataset.png and b/dist/schema/img/eml-dataset_xsd_Element_dataset.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_description.png b/dist/schema/img/eml-dataset_xsd_Element_description.png
index 3dd30569..12c00ac3 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_description.png and b/dist/schema/img/eml-dataset_xsd_Element_description.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_gettingStarted.png b/dist/schema/img/eml-dataset_xsd_Element_gettingStarted.png
index 09924450..e4c4ee2f 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_gettingStarted.png and b/dist/schema/img/eml-dataset_xsd_Element_gettingStarted.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_introduction.png b/dist/schema/img/eml-dataset_xsd_Element_introduction.png
index db53b35e..87c716f7 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_introduction.png and b/dist/schema/img/eml-dataset_xsd_Element_introduction.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_literatureCited.png b/dist/schema/img/eml-dataset_xsd_Element_literatureCited.png
index 5ce27fb9..f10f0694 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_literatureCited.png and b/dist/schema/img/eml-dataset_xsd_Element_literatureCited.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_maintenance.png b/dist/schema/img/eml-dataset_xsd_Element_maintenance.png
index 2aaf67fe..9835c138 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_maintenance.png and b/dist/schema/img/eml-dataset_xsd_Element_maintenance.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_maintenanceUpdateFrequency.png b/dist/schema/img/eml-dataset_xsd_Element_maintenanceUpdateFrequency.png
index bf33b73d..f030053b 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_maintenanceUpdateFrequency.png and b/dist/schema/img/eml-dataset_xsd_Element_maintenanceUpdateFrequency.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_methods.png b/dist/schema/img/eml-dataset_xsd_Element_methods.png
index 29566eb2..85fb83f1 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_methods.png and b/dist/schema/img/eml-dataset_xsd_Element_methods.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_oldValue.png b/dist/schema/img/eml-dataset_xsd_Element_oldValue.png
index a53b6555..e94c5e08 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_oldValue.png and b/dist/schema/img/eml-dataset_xsd_Element_oldValue.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_otherEntity.png b/dist/schema/img/eml-dataset_xsd_Element_otherEntity.png
index 35c2493c..7dd96209 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_otherEntity.png and b/dist/schema/img/eml-dataset_xsd_Element_otherEntity.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_project.png b/dist/schema/img/eml-dataset_xsd_Element_project.png
index e86957c6..b9bb16cb 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_project.png and b/dist/schema/img/eml-dataset_xsd_Element_project.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_pubPlace.png b/dist/schema/img/eml-dataset_xsd_Element_pubPlace.png
index ea6e5d82..1b95dce6 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_pubPlace.png and b/dist/schema/img/eml-dataset_xsd_Element_pubPlace.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_publisher.png b/dist/schema/img/eml-dataset_xsd_Element_publisher.png
index 3c899a33..40a89cdd 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_publisher.png and b/dist/schema/img/eml-dataset_xsd_Element_publisher.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_purpose.png b/dist/schema/img/eml-dataset_xsd_Element_purpose.png
index 649a7c16..df5420ce 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_purpose.png and b/dist/schema/img/eml-dataset_xsd_Element_purpose.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_referencePublication.png b/dist/schema/img/eml-dataset_xsd_Element_referencePublication.png
index 816e7fc8..635cca12 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_referencePublication.png and b/dist/schema/img/eml-dataset_xsd_Element_referencePublication.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_spatialRaster.png b/dist/schema/img/eml-dataset_xsd_Element_spatialRaster.png
index 2c3a69b2..8bba396d 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_spatialRaster.png and b/dist/schema/img/eml-dataset_xsd_Element_spatialRaster.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_spatialVector.png b/dist/schema/img/eml-dataset_xsd_Element_spatialVector.png
index 3dc4630d..b075aa7d 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_spatialVector.png and b/dist/schema/img/eml-dataset_xsd_Element_spatialVector.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_storedProcedure.png b/dist/schema/img/eml-dataset_xsd_Element_storedProcedure.png
index a0cf1cf7..ef23ffc8 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_storedProcedure.png and b/dist/schema/img/eml-dataset_xsd_Element_storedProcedure.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_usageCitation.png b/dist/schema/img/eml-dataset_xsd_Element_usageCitation.png
index 6fbe1043..aa3fb49a 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_usageCitation.png and b/dist/schema/img/eml-dataset_xsd_Element_usageCitation.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Element_view.png b/dist/schema/img/eml-dataset_xsd_Element_view.png
index 6520e8f1..1440e934 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Element_view.png and b/dist/schema/img/eml-dataset_xsd_Element_view.png differ
diff --git a/dist/schema/img/eml-dataset_xsd_Simple_Type_MaintUpFreqType.png b/dist/schema/img/eml-dataset_xsd_Simple_Type_MaintUpFreqType.png
index 930f26bb..a5aae1aa 100644
Binary files a/dist/schema/img/eml-dataset_xsd_Simple_Type_MaintUpFreqType.png and b/dist/schema/img/eml-dataset_xsd_Simple_Type_MaintUpFreqType.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_description.png b/dist/schema/img/eml-documentation_xsd_Element_description.png
index 49c46ba9..814a4691 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_description.png and b/dist/schema/img/eml-documentation_xsd_Element_description.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_example.png b/dist/schema/img/eml-documentation_xsd_Element_example.png
index b3d098e3..fd80f067 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_example.png and b/dist/schema/img/eml-documentation_xsd_Element_example.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_lineage.png b/dist/schema/img/eml-documentation_xsd_Element_lineage.png
index 3521169f..83952a4a 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_lineage.png and b/dist/schema/img/eml-documentation_xsd_Element_lineage.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_module.png b/dist/schema/img/eml-documentation_xsd_Element_module.png
index bdcd203e..2e34f1c9 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_module.png and b/dist/schema/img/eml-documentation_xsd_Element_module.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_moduleDescription.png b/dist/schema/img/eml-documentation_xsd_Element_moduleDescription.png
index 3937c8f8..ddecac39 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_moduleDescription.png and b/dist/schema/img/eml-documentation_xsd_Element_moduleDescription.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_moduleDocs.png b/dist/schema/img/eml-documentation_xsd_Element_moduleDocs.png
index 54340fd6..fc4510fe 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_moduleDocs.png and b/dist/schema/img/eml-documentation_xsd_Element_moduleDocs.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_moduleName.png b/dist/schema/img/eml-documentation_xsd_Element_moduleName.png
index 1058c306..65995ed2 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_moduleName.png and b/dist/schema/img/eml-documentation_xsd_Element_moduleName.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_recommendedUsage.png b/dist/schema/img/eml-documentation_xsd_Element_recommendedUsage.png
index 841c6eeb..65f9aa60 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_recommendedUsage.png and b/dist/schema/img/eml-documentation_xsd_Element_recommendedUsage.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_standAlone.png b/dist/schema/img/eml-documentation_xsd_Element_standAlone.png
index 2b895fba..f25814f5 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_standAlone.png and b/dist/schema/img/eml-documentation_xsd_Element_standAlone.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_summary.png b/dist/schema/img/eml-documentation_xsd_Element_summary.png
index 82f3909f..bd60016c 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_summary.png and b/dist/schema/img/eml-documentation_xsd_Element_summary.png differ
diff --git a/dist/schema/img/eml-documentation_xsd_Element_tooltip.png b/dist/schema/img/eml-documentation_xsd_Element_tooltip.png
index 8c68c6a8..4f7b2a7c 100644
Binary files a/dist/schema/img/eml-documentation_xsd_Element_tooltip.png and b/dist/schema/img/eml-documentation_xsd_Element_tooltip.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Complex_Type_OtherEntityType.png b/dist/schema/img/eml-entity_xsd_Complex_Type_OtherEntityType.png
index 57a51f2b..f52ae15a 100644
Binary files a/dist/schema/img/eml-entity_xsd_Complex_Type_OtherEntityType.png and b/dist/schema/img/eml-entity_xsd_Complex_Type_OtherEntityType.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_Group_EntityGroup.png b/dist/schema/img/eml-entity_xsd_Element_Group_EntityGroup.png
index b6207482..a5ca1882 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_Group_EntityGroup.png and b/dist/schema/img/eml-entity_xsd_Element_Group_EntityGroup.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_additionalInfo.png b/dist/schema/img/eml-entity_xsd_Element_additionalInfo.png
index cc08eefd..77ef3b93 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_additionalInfo.png and b/dist/schema/img/eml-entity_xsd_Element_additionalInfo.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_alternateIdentifier.png b/dist/schema/img/eml-entity_xsd_Element_alternateIdentifier.png
index 581ea88a..d0cbb679 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_alternateIdentifier.png and b/dist/schema/img/eml-entity_xsd_Element_alternateIdentifier.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_annotation.png b/dist/schema/img/eml-entity_xsd_Element_annotation.png
index ecd0fad5..513621a4 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_annotation.png and b/dist/schema/img/eml-entity_xsd_Element_annotation.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_attributeList.png b/dist/schema/img/eml-entity_xsd_Element_attributeList.png
index b5ecb89f..dd1d1c52 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_attributeList.png and b/dist/schema/img/eml-entity_xsd_Element_attributeList.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_constraint.png b/dist/schema/img/eml-entity_xsd_Element_constraint.png
index 53e6af35..4743f05b 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_constraint.png and b/dist/schema/img/eml-entity_xsd_Element_constraint.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_coverage.png b/dist/schema/img/eml-entity_xsd_Element_coverage.png
index 2cd0b800..a8702880 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_coverage.png and b/dist/schema/img/eml-entity_xsd_Element_coverage.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_entityDescription.png b/dist/schema/img/eml-entity_xsd_Element_entityDescription.png
index c1d47b6e..5348db30 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_entityDescription.png and b/dist/schema/img/eml-entity_xsd_Element_entityDescription.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_entityName.png b/dist/schema/img/eml-entity_xsd_Element_entityName.png
index fa9c250e..a126209e 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_entityName.png and b/dist/schema/img/eml-entity_xsd_Element_entityName.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_entityType.png b/dist/schema/img/eml-entity_xsd_Element_entityType.png
index 2b495b80..c13343ac 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_entityType.png and b/dist/schema/img/eml-entity_xsd_Element_entityType.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_methods.png b/dist/schema/img/eml-entity_xsd_Element_methods.png
index e3ded8fc..cd6c168f 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_methods.png and b/dist/schema/img/eml-entity_xsd_Element_methods.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_otherEntity.png b/dist/schema/img/eml-entity_xsd_Element_otherEntity.png
index 805976f4..3515bfb5 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_otherEntity.png and b/dist/schema/img/eml-entity_xsd_Element_otherEntity.png differ
diff --git a/dist/schema/img/eml-entity_xsd_Element_physical.png b/dist/schema/img/eml-entity_xsd_Element_physical.png
index 9251fe2a..f63279b7 100644
Binary files a/dist/schema/img/eml-entity_xsd_Element_physical.png and b/dist/schema/img/eml-entity_xsd_Element_physical.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Article.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Article.png
index 174d9294..2b4b3c12 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Article.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Article.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_AudioVisual.png b/dist/schema/img/eml-literature_xsd_Complex_Type_AudioVisual.png
index b0a04908..4bc341f4 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_AudioVisual.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_AudioVisual.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Book.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Book.png
index 31c4a796..fffce443 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Book.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Book.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Chapter.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Chapter.png
index e04d5a7f..3a719ada 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Chapter.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Chapter.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_CitationListType.png b/dist/schema/img/eml-literature_xsd_Complex_Type_CitationListType.png
index b3721c77..d5468370 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_CitationListType.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_CitationListType.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_CitationType.png b/dist/schema/img/eml-literature_xsd_Complex_Type_CitationType.png
index 3a0301ef..8692d1a5 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_CitationType.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_CitationType.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_ConferenceProceedings.png b/dist/schema/img/eml-literature_xsd_Complex_Type_ConferenceProceedings.png
index 4611ce7a..11ac5828 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_ConferenceProceedings.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_ConferenceProceedings.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Generic.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Generic.png
index 9f63eed6..575d174c 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Generic.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Generic.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Manuscript.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Manuscript.png
index 302376f2..029dafa8 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Manuscript.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Manuscript.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Map.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Map.png
index cda44acc..b2de05a5 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Map.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Map.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_PersonalCommunication.png b/dist/schema/img/eml-literature_xsd_Complex_Type_PersonalCommunication.png
index 1c099268..209c41ac 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_PersonalCommunication.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_PersonalCommunication.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Presentation.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Presentation.png
index 6c98ad5a..6d638586 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Presentation.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Presentation.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Report.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Report.png
index 2f72176c..c74fff61 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Report.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Report.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Complex_Type_Thesis.png b/dist/schema/img/eml-literature_xsd_Complex_Type_Thesis.png
index 64ccddac..deb64747 100644
Binary files a/dist/schema/img/eml-literature_xsd_Complex_Type_Thesis.png and b/dist/schema/img/eml-literature_xsd_Complex_Type_Thesis.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_ISBN.png b/dist/schema/img/eml-literature_xsd_Element_ISBN.png
index 7f2a5ad2..395eb874 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_ISBN.png and b/dist/schema/img/eml-literature_xsd_Element_ISBN.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_ISBN_1.png b/dist/schema/img/eml-literature_xsd_Element_ISBN_1.png
index 7ddb9ea2..838b72cf 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_ISBN_1.png and b/dist/schema/img/eml-literature_xsd_Element_ISBN_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_ISBN_2.png b/dist/schema/img/eml-literature_xsd_Element_ISBN_2.png
index 7f2a5ad2..395eb874 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_ISBN_2.png and b/dist/schema/img/eml-literature_xsd_Element_ISBN_2.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_ISSN.png b/dist/schema/img/eml-literature_xsd_Element_ISSN.png
index 67742eb7..8033da5c 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_ISSN.png and b/dist/schema/img/eml-literature_xsd_Element_ISSN.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_ISSN_1.png b/dist/schema/img/eml-literature_xsd_Element_ISSN_1.png
index be6ba70c..e8802ab9 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_ISSN_1.png and b/dist/schema/img/eml-literature_xsd_Element_ISSN_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_article.png b/dist/schema/img/eml-literature_xsd_Element_article.png
index e6d3d698..7b48cb7a 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_article.png and b/dist/schema/img/eml-literature_xsd_Element_article.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_audioVisual.png b/dist/schema/img/eml-literature_xsd_Element_audioVisual.png
index 15895d8c..376d3b33 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_audioVisual.png and b/dist/schema/img/eml-literature_xsd_Element_audioVisual.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_bibtex.png b/dist/schema/img/eml-literature_xsd_Element_bibtex.png
index fb71c178..1bb659bc 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_bibtex.png and b/dist/schema/img/eml-literature_xsd_Element_bibtex.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_bibtex_1.png b/dist/schema/img/eml-literature_xsd_Element_bibtex_1.png
index d3ba4867..b1f00c2d 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_bibtex_1.png and b/dist/schema/img/eml-literature_xsd_Element_bibtex_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_book.png b/dist/schema/img/eml-literature_xsd_Element_book.png
index 2d60d682..e927b3bc 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_book.png and b/dist/schema/img/eml-literature_xsd_Element_book.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_bookTitle.png b/dist/schema/img/eml-literature_xsd_Element_bookTitle.png
index 6f03e44e..ba491002 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_bookTitle.png and b/dist/schema/img/eml-literature_xsd_Element_bookTitle.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_chapter.png b/dist/schema/img/eml-literature_xsd_Element_chapter.png
index ec38fdf9..a6ae1287 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_chapter.png and b/dist/schema/img/eml-literature_xsd_Element_chapter.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_chapterNumber.png b/dist/schema/img/eml-literature_xsd_Element_chapterNumber.png
index 4abee906..9edcedba 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_chapterNumber.png and b/dist/schema/img/eml-literature_xsd_Element_chapterNumber.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_citation.png b/dist/schema/img/eml-literature_xsd_Element_citation.png
index b9d82c5c..03f78c48 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_citation.png and b/dist/schema/img/eml-literature_xsd_Element_citation.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_citation_1.png b/dist/schema/img/eml-literature_xsd_Element_citation_1.png
index f28be61f..195842a3 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_citation_1.png and b/dist/schema/img/eml-literature_xsd_Element_citation_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_communicationType.png b/dist/schema/img/eml-literature_xsd_Element_communicationType.png
index 17a350c1..3b186f23 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_communicationType.png and b/dist/schema/img/eml-literature_xsd_Element_communicationType.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_conferenceDate.png b/dist/schema/img/eml-literature_xsd_Element_conferenceDate.png
index 8e9c5acc..fdd1773d 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_conferenceDate.png and b/dist/schema/img/eml-literature_xsd_Element_conferenceDate.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_conferenceDate_1.png b/dist/schema/img/eml-literature_xsd_Element_conferenceDate_1.png
index 8e9c5acc..fdd1773d 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_conferenceDate_1.png and b/dist/schema/img/eml-literature_xsd_Element_conferenceDate_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_conferenceLocation.png b/dist/schema/img/eml-literature_xsd_Element_conferenceLocation.png
index 97193bf2..e3b03f41 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_conferenceLocation.png and b/dist/schema/img/eml-literature_xsd_Element_conferenceLocation.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_conferenceLocation_1.png b/dist/schema/img/eml-literature_xsd_Element_conferenceLocation_1.png
index 97193bf2..e3b03f41 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_conferenceLocation_1.png and b/dist/schema/img/eml-literature_xsd_Element_conferenceLocation_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_conferenceName.png b/dist/schema/img/eml-literature_xsd_Element_conferenceName.png
index 7b5b979b..869be0fd 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_conferenceName.png and b/dist/schema/img/eml-literature_xsd_Element_conferenceName.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_conferenceName_1.png b/dist/schema/img/eml-literature_xsd_Element_conferenceName_1.png
index da7ccdb3..dafc2562 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_conferenceName_1.png and b/dist/schema/img/eml-literature_xsd_Element_conferenceName_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_conferenceProceedings.png b/dist/schema/img/eml-literature_xsd_Element_conferenceProceedings.png
index 6a48b667..490a4941 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_conferenceProceedings.png and b/dist/schema/img/eml-literature_xsd_Element_conferenceProceedings.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_contact.png b/dist/schema/img/eml-literature_xsd_Element_contact.png
index 568e6c15..5654c348 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_contact.png and b/dist/schema/img/eml-literature_xsd_Element_contact.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_degree.png b/dist/schema/img/eml-literature_xsd_Element_degree.png
index b3ec6d85..a211040f 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_degree.png and b/dist/schema/img/eml-literature_xsd_Element_degree.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_editedBook.png b/dist/schema/img/eml-literature_xsd_Element_editedBook.png
index 85fc8a91..3b189d42 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_editedBook.png and b/dist/schema/img/eml-literature_xsd_Element_editedBook.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_edition.png b/dist/schema/img/eml-literature_xsd_Element_edition.png
index 3e44afb1..7d8c6c20 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_edition.png and b/dist/schema/img/eml-literature_xsd_Element_edition.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_edition_1.png b/dist/schema/img/eml-literature_xsd_Element_edition_1.png
index b44dd3da..0d10d5c4 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_edition_1.png and b/dist/schema/img/eml-literature_xsd_Element_edition_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_edition_2.png b/dist/schema/img/eml-literature_xsd_Element_edition_2.png
index 794e5045..fd6ff991 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_edition_2.png and b/dist/schema/img/eml-literature_xsd_Element_edition_2.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_editor.png b/dist/schema/img/eml-literature_xsd_Element_editor.png
index e7d556c2..77db7922 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_editor.png and b/dist/schema/img/eml-literature_xsd_Element_editor.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_generic.png b/dist/schema/img/eml-literature_xsd_Element_generic.png
index 5c127d52..e45c854e 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_generic.png and b/dist/schema/img/eml-literature_xsd_Element_generic.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_geographicCoverage.png b/dist/schema/img/eml-literature_xsd_Element_geographicCoverage.png
index cc73de1c..9010afe2 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_geographicCoverage.png and b/dist/schema/img/eml-literature_xsd_Element_geographicCoverage.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_institution.png b/dist/schema/img/eml-literature_xsd_Element_institution.png
index f1f6b885..47eb796e 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_institution.png and b/dist/schema/img/eml-literature_xsd_Element_institution.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_institution_1.png b/dist/schema/img/eml-literature_xsd_Element_institution_1.png
index b4c6866d..231ea2e4 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_institution_1.png and b/dist/schema/img/eml-literature_xsd_Element_institution_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_issue.png b/dist/schema/img/eml-literature_xsd_Element_issue.png
index b3bd1f31..b7194818 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_issue.png and b/dist/schema/img/eml-literature_xsd_Element_issue.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_journal.png b/dist/schema/img/eml-literature_xsd_Element_journal.png
index 16463811..e6d70f65 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_journal.png and b/dist/schema/img/eml-literature_xsd_Element_journal.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_manuscript.png b/dist/schema/img/eml-literature_xsd_Element_manuscript.png
index 1c2ae226..aed42a0e 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_manuscript.png and b/dist/schema/img/eml-literature_xsd_Element_manuscript.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_map.png b/dist/schema/img/eml-literature_xsd_Element_map.png
index df906121..5342013c 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_map.png and b/dist/schema/img/eml-literature_xsd_Element_map.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_numberOfVolumes.png b/dist/schema/img/eml-literature_xsd_Element_numberOfVolumes.png
index 6dd4f9ec..627daaa0 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_numberOfVolumes.png and b/dist/schema/img/eml-literature_xsd_Element_numberOfVolumes.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_numberOfVolumes_1.png b/dist/schema/img/eml-literature_xsd_Element_numberOfVolumes_1.png
index 6dd4f9ec..627daaa0 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_numberOfVolumes_1.png and b/dist/schema/img/eml-literature_xsd_Element_numberOfVolumes_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_originalPublication.png b/dist/schema/img/eml-literature_xsd_Element_originalPublication.png
index 7d2da1c2..ee608f8a 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_originalPublication.png and b/dist/schema/img/eml-literature_xsd_Element_originalPublication.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_pageRange.png b/dist/schema/img/eml-literature_xsd_Element_pageRange.png
index 84f1fc90..3b1d37ec 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_pageRange.png and b/dist/schema/img/eml-literature_xsd_Element_pageRange.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_pageRange_1.png b/dist/schema/img/eml-literature_xsd_Element_pageRange_1.png
index 58852367..161260ff 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_pageRange_1.png and b/dist/schema/img/eml-literature_xsd_Element_pageRange_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_performer.png b/dist/schema/img/eml-literature_xsd_Element_performer.png
index 01174d64..6bda9354 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_performer.png and b/dist/schema/img/eml-literature_xsd_Element_performer.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_personalCommunication.png b/dist/schema/img/eml-literature_xsd_Element_personalCommunication.png
index 84c1e0cb..e3c2fb46 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_personalCommunication.png and b/dist/schema/img/eml-literature_xsd_Element_personalCommunication.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_presentation.png b/dist/schema/img/eml-literature_xsd_Element_presentation.png
index b866fc2d..f5891f72 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_presentation.png and b/dist/schema/img/eml-literature_xsd_Element_presentation.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publicationPlace.png b/dist/schema/img/eml-literature_xsd_Element_publicationPlace.png
index c52c52d8..72628920 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publicationPlace.png and b/dist/schema/img/eml-literature_xsd_Element_publicationPlace.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_1.png b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_1.png
index c52c52d8..72628920 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_1.png and b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_2.png b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_2.png
index c52c52d8..72628920 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_2.png and b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_2.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_3.png b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_3.png
index c52c52d8..72628920 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_3.png and b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_3.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_4.png b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_4.png
index c52c52d8..72628920 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_4.png and b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_4.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_5.png b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_5.png
index c52c52d8..72628920 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publicationPlace_5.png and b/dist/schema/img/eml-literature_xsd_Element_publicationPlace_5.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publisher.png b/dist/schema/img/eml-literature_xsd_Element_publisher.png
index de21048f..d8961850 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publisher.png and b/dist/schema/img/eml-literature_xsd_Element_publisher.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publisher_1.png b/dist/schema/img/eml-literature_xsd_Element_publisher_1.png
index a1e70770..80d28e77 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publisher_1.png and b/dist/schema/img/eml-literature_xsd_Element_publisher_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publisher_2.png b/dist/schema/img/eml-literature_xsd_Element_publisher_2.png
index 532c4837..b8bd52a2 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publisher_2.png and b/dist/schema/img/eml-literature_xsd_Element_publisher_2.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publisher_3.png b/dist/schema/img/eml-literature_xsd_Element_publisher_3.png
index ff4f47ef..6567c06c 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publisher_3.png and b/dist/schema/img/eml-literature_xsd_Element_publisher_3.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publisher_4.png b/dist/schema/img/eml-literature_xsd_Element_publisher_4.png
index ab892f67..a49adb93 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publisher_4.png and b/dist/schema/img/eml-literature_xsd_Element_publisher_4.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publisher_5.png b/dist/schema/img/eml-literature_xsd_Element_publisher_5.png
index 8f970693..e5b57447 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publisher_5.png and b/dist/schema/img/eml-literature_xsd_Element_publisher_5.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_publisher_6.png b/dist/schema/img/eml-literature_xsd_Element_publisher_6.png
index 1e65b65a..9fc51557 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_publisher_6.png and b/dist/schema/img/eml-literature_xsd_Element_publisher_6.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_recipient.png b/dist/schema/img/eml-literature_xsd_Element_recipient.png
index 2ea6b000..b882b367 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_recipient.png and b/dist/schema/img/eml-literature_xsd_Element_recipient.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_referenceType.png b/dist/schema/img/eml-literature_xsd_Element_referenceType.png
index f02f7b90..d502df7b 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_referenceType.png and b/dist/schema/img/eml-literature_xsd_Element_referenceType.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_report.png b/dist/schema/img/eml-literature_xsd_Element_report.png
index c7292817..678c3135 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_report.png and b/dist/schema/img/eml-literature_xsd_Element_report.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_reportNumber.png b/dist/schema/img/eml-literature_xsd_Element_reportNumber.png
index 3503a6f0..2be00a0d 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_reportNumber.png and b/dist/schema/img/eml-literature_xsd_Element_reportNumber.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_reprintEdition.png b/dist/schema/img/eml-literature_xsd_Element_reprintEdition.png
index 04e0b948..d23e0435 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_reprintEdition.png and b/dist/schema/img/eml-literature_xsd_Element_reprintEdition.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_reviewedItem.png b/dist/schema/img/eml-literature_xsd_Element_reviewedItem.png
index b672629d..6e6579e0 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_reviewedItem.png and b/dist/schema/img/eml-literature_xsd_Element_reviewedItem.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_scale.png b/dist/schema/img/eml-literature_xsd_Element_scale.png
index c70aa7ee..1aafa07b 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_scale.png and b/dist/schema/img/eml-literature_xsd_Element_scale.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_thesis.png b/dist/schema/img/eml-literature_xsd_Element_thesis.png
index 162e2d6d..b84de897 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_thesis.png and b/dist/schema/img/eml-literature_xsd_Element_thesis.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalFigures.png b/dist/schema/img/eml-literature_xsd_Element_totalFigures.png
index b52e8be8..af38107b 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalFigures.png and b/dist/schema/img/eml-literature_xsd_Element_totalFigures.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalFigures_1.png b/dist/schema/img/eml-literature_xsd_Element_totalFigures_1.png
index 9ecd62e6..6f1dadac 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalFigures_1.png and b/dist/schema/img/eml-literature_xsd_Element_totalFigures_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalPages.png b/dist/schema/img/eml-literature_xsd_Element_totalPages.png
index fc1f54da..5c868e32 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalPages.png and b/dist/schema/img/eml-literature_xsd_Element_totalPages.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalPages_1.png b/dist/schema/img/eml-literature_xsd_Element_totalPages_1.png
index 0c69a04b..35419d0c 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalPages_1.png and b/dist/schema/img/eml-literature_xsd_Element_totalPages_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalPages_2.png b/dist/schema/img/eml-literature_xsd_Element_totalPages_2.png
index 847727cc..4e68f4ea 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalPages_2.png and b/dist/schema/img/eml-literature_xsd_Element_totalPages_2.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalPages_3.png b/dist/schema/img/eml-literature_xsd_Element_totalPages_3.png
index 86c1cbdc..6059ccfb 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalPages_3.png and b/dist/schema/img/eml-literature_xsd_Element_totalPages_3.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalPages_4.png b/dist/schema/img/eml-literature_xsd_Element_totalPages_4.png
index 1f8c4588..fc447156 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalPages_4.png and b/dist/schema/img/eml-literature_xsd_Element_totalPages_4.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalTables.png b/dist/schema/img/eml-literature_xsd_Element_totalTables.png
index 78dd4b6c..884c8104 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalTables.png and b/dist/schema/img/eml-literature_xsd_Element_totalTables.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_totalTables_1.png b/dist/schema/img/eml-literature_xsd_Element_totalTables_1.png
index 2f58bffb..9e554811 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_totalTables_1.png and b/dist/schema/img/eml-literature_xsd_Element_totalTables_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_volume.png b/dist/schema/img/eml-literature_xsd_Element_volume.png
index 8668401c..08ed2537 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_volume.png and b/dist/schema/img/eml-literature_xsd_Element_volume.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_volume_1.png b/dist/schema/img/eml-literature_xsd_Element_volume_1.png
index 794df231..c0bb6bd9 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_volume_1.png and b/dist/schema/img/eml-literature_xsd_Element_volume_1.png differ
diff --git a/dist/schema/img/eml-literature_xsd_Element_volume_2.png b/dist/schema/img/eml-literature_xsd_Element_volume_2.png
index e952fed5..18a42495 100644
Binary files a/dist/schema/img/eml-literature_xsd_Element_volume_2.png and b/dist/schema/img/eml-literature_xsd_Element_volume_2.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Complex_Type_MethodsType.png b/dist/schema/img/eml-methods_xsd_Complex_Type_MethodsType.png
index c4841f2c..bd1f8a25 100644
Binary files a/dist/schema/img/eml-methods_xsd_Complex_Type_MethodsType.png and b/dist/schema/img/eml-methods_xsd_Complex_Type_MethodsType.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Complex_Type_ProcedureStepType.png b/dist/schema/img/eml-methods_xsd_Complex_Type_ProcedureStepType.png
index 5b25405d..3eca5d7e 100644
Binary files a/dist/schema/img/eml-methods_xsd_Complex_Type_ProcedureStepType.png and b/dist/schema/img/eml-methods_xsd_Complex_Type_ProcedureStepType.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_citation.png b/dist/schema/img/eml-methods_xsd_Element_citation.png
index 0629f1c8..917f3fbd 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_citation.png and b/dist/schema/img/eml-methods_xsd_Element_citation.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_citation_1.png b/dist/schema/img/eml-methods_xsd_Element_citation_1.png
index 3db1ef65..7105ff19 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_citation_1.png and b/dist/schema/img/eml-methods_xsd_Element_citation_1.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_coverage.png b/dist/schema/img/eml-methods_xsd_Element_coverage.png
index 25685310..69192b72 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_coverage.png and b/dist/schema/img/eml-methods_xsd_Element_coverage.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_coverage_1.png b/dist/schema/img/eml-methods_xsd_Element_coverage_1.png
index 5f54c961..b7e3a114 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_coverage_1.png and b/dist/schema/img/eml-methods_xsd_Element_coverage_1.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_dataSource.png b/dist/schema/img/eml-methods_xsd_Element_dataSource.png
index b7e5e54b..6415d348 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_dataSource.png and b/dist/schema/img/eml-methods_xsd_Element_dataSource.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_description.png b/dist/schema/img/eml-methods_xsd_Element_description.png
index 5a3a4063..30b9d70c 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_description.png and b/dist/schema/img/eml-methods_xsd_Element_description.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_description_1.png b/dist/schema/img/eml-methods_xsd_Element_description_1.png
index bf2c881d..bdbae619 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_description_1.png and b/dist/schema/img/eml-methods_xsd_Element_description_1.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_instrumentation.png b/dist/schema/img/eml-methods_xsd_Element_instrumentation.png
index b33e23d1..6262b5b4 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_instrumentation.png and b/dist/schema/img/eml-methods_xsd_Element_instrumentation.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_methodStep.png b/dist/schema/img/eml-methods_xsd_Element_methodStep.png
index 4f7cd82a..b7a96735 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_methodStep.png and b/dist/schema/img/eml-methods_xsd_Element_methodStep.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_methods.png b/dist/schema/img/eml-methods_xsd_Element_methods.png
index 43e63a36..1959c934 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_methods.png and b/dist/schema/img/eml-methods_xsd_Element_methods.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_protocol.png b/dist/schema/img/eml-methods_xsd_Element_protocol.png
index 7e191655..30e9ce07 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_protocol.png and b/dist/schema/img/eml-methods_xsd_Element_protocol.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_qualityControl.png b/dist/schema/img/eml-methods_xsd_Element_qualityControl.png
index 41893cdd..548dec9d 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_qualityControl.png and b/dist/schema/img/eml-methods_xsd_Element_qualityControl.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_referencedEntityId.png b/dist/schema/img/eml-methods_xsd_Element_referencedEntityId.png
index 59769f74..68593336 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_referencedEntityId.png and b/dist/schema/img/eml-methods_xsd_Element_referencedEntityId.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_sampling.png b/dist/schema/img/eml-methods_xsd_Element_sampling.png
index b015d750..aca0e763 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_sampling.png and b/dist/schema/img/eml-methods_xsd_Element_sampling.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_samplingDescription.png b/dist/schema/img/eml-methods_xsd_Element_samplingDescription.png
index b07a2a61..cb921234 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_samplingDescription.png and b/dist/schema/img/eml-methods_xsd_Element_samplingDescription.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_software.png b/dist/schema/img/eml-methods_xsd_Element_software.png
index a3cefe54..66f7daca 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_software.png and b/dist/schema/img/eml-methods_xsd_Element_software.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_spatialSamplingUnits.png b/dist/schema/img/eml-methods_xsd_Element_spatialSamplingUnits.png
index f2b207c6..2d49a626 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_spatialSamplingUnits.png and b/dist/schema/img/eml-methods_xsd_Element_spatialSamplingUnits.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_studyExtent.png b/dist/schema/img/eml-methods_xsd_Element_studyExtent.png
index 53fd2973..ba080775 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_studyExtent.png and b/dist/schema/img/eml-methods_xsd_Element_studyExtent.png differ
diff --git a/dist/schema/img/eml-methods_xsd_Element_subStep.png b/dist/schema/img/eml-methods_xsd_Element_subStep.png
index c42df77a..f1745f1f 100644
Binary files a/dist/schema/img/eml-methods_xsd_Element_subStep.png and b/dist/schema/img/eml-methods_xsd_Element_subStep.png differ
diff --git a/dist/schema/img/eml-party_xsd_Complex_Type_Address.png b/dist/schema/img/eml-party_xsd_Complex_Type_Address.png
index fa618e32..7ff71c73 100644
Binary files a/dist/schema/img/eml-party_xsd_Complex_Type_Address.png and b/dist/schema/img/eml-party_xsd_Complex_Type_Address.png differ
diff --git a/dist/schema/img/eml-party_xsd_Complex_Type_Person.png b/dist/schema/img/eml-party_xsd_Complex_Type_Person.png
index e33a99d7..9050972f 100644
Binary files a/dist/schema/img/eml-party_xsd_Complex_Type_Person.png and b/dist/schema/img/eml-party_xsd_Complex_Type_Person.png differ
diff --git a/dist/schema/img/eml-party_xsd_Complex_Type_ResponsibleParty.png b/dist/schema/img/eml-party_xsd_Complex_Type_ResponsibleParty.png
index 415c0767..01ab67e3 100644
Binary files a/dist/schema/img/eml-party_xsd_Complex_Type_ResponsibleParty.png and b/dist/schema/img/eml-party_xsd_Complex_Type_ResponsibleParty.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_address.png b/dist/schema/img/eml-party_xsd_Element_address.png
index a21a9c9b..aa9abe90 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_address.png and b/dist/schema/img/eml-party_xsd_Element_address.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_administrativeArea.png b/dist/schema/img/eml-party_xsd_Element_administrativeArea.png
index 25a017db..7c990ff9 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_administrativeArea.png and b/dist/schema/img/eml-party_xsd_Element_administrativeArea.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_city.png b/dist/schema/img/eml-party_xsd_Element_city.png
index 728beb76..46be23cd 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_city.png and b/dist/schema/img/eml-party_xsd_Element_city.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_country.png b/dist/schema/img/eml-party_xsd_Element_country.png
index 22c3dab2..6764d8a5 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_country.png and b/dist/schema/img/eml-party_xsd_Element_country.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_deliveryPoint.png b/dist/schema/img/eml-party_xsd_Element_deliveryPoint.png
index 056cd84b..23363e83 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_deliveryPoint.png and b/dist/schema/img/eml-party_xsd_Element_deliveryPoint.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_electronicMailAddress.png b/dist/schema/img/eml-party_xsd_Element_electronicMailAddress.png
index 5649b23f..fecde56c 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_electronicMailAddress.png and b/dist/schema/img/eml-party_xsd_Element_electronicMailAddress.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_givenName.png b/dist/schema/img/eml-party_xsd_Element_givenName.png
index c12f2622..e244a998 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_givenName.png and b/dist/schema/img/eml-party_xsd_Element_givenName.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_individualName.png b/dist/schema/img/eml-party_xsd_Element_individualName.png
index 151296d5..a859712a 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_individualName.png and b/dist/schema/img/eml-party_xsd_Element_individualName.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_onlineUrl.png b/dist/schema/img/eml-party_xsd_Element_onlineUrl.png
index a6fb41b0..e389200e 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_onlineUrl.png and b/dist/schema/img/eml-party_xsd_Element_onlineUrl.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_organizationName.png b/dist/schema/img/eml-party_xsd_Element_organizationName.png
index ca79087a..709d8ceb 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_organizationName.png and b/dist/schema/img/eml-party_xsd_Element_organizationName.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_party.png b/dist/schema/img/eml-party_xsd_Element_party.png
index 308cae92..b179f394 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_party.png and b/dist/schema/img/eml-party_xsd_Element_party.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_phone.png b/dist/schema/img/eml-party_xsd_Element_phone.png
index a18a13a9..4b6b23de 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_phone.png and b/dist/schema/img/eml-party_xsd_Element_phone.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_positionName.png b/dist/schema/img/eml-party_xsd_Element_positionName.png
index 13109dae..97776c41 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_positionName.png and b/dist/schema/img/eml-party_xsd_Element_positionName.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_postalCode.png b/dist/schema/img/eml-party_xsd_Element_postalCode.png
index d732660a..7d9bf08e 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_postalCode.png and b/dist/schema/img/eml-party_xsd_Element_postalCode.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_salutation.png b/dist/schema/img/eml-party_xsd_Element_salutation.png
index 73b3e499..75b16714 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_salutation.png and b/dist/schema/img/eml-party_xsd_Element_salutation.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_surName.png b/dist/schema/img/eml-party_xsd_Element_surName.png
index d643ab35..c7f7321a 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_surName.png and b/dist/schema/img/eml-party_xsd_Element_surName.png differ
diff --git a/dist/schema/img/eml-party_xsd_Element_userId.png b/dist/schema/img/eml-party_xsd_Element_userId.png
index 7030de81..441ab8b3 100644
Binary files a/dist/schema/img/eml-party_xsd_Element_userId.png and b/dist/schema/img/eml-party_xsd_Element_userId.png differ
diff --git a/dist/schema/img/eml-party_xsd_Simple_Type_RoleType.png b/dist/schema/img/eml-party_xsd_Simple_Type_RoleType.png
index d729dbbd..a2919fd8 100644
Binary files a/dist/schema/img/eml-party_xsd_Simple_Type_RoleType.png and b/dist/schema/img/eml-party_xsd_Simple_Type_RoleType.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalDistributionType.png b/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalDistributionType.png
index ca28565f..8ff2bd59 100644
Binary files a/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalDistributionType.png and b/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalDistributionType.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalOnlineType.png b/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalOnlineType.png
index 01734904..46369755 100644
Binary files a/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalOnlineType.png and b/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalOnlineType.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalType.png b/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalType.png
index 51fecd6c..f68d87c5 100644
Binary files a/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalType.png and b/dist/schema/img/eml-physical_xsd_Complex_Type_PhysicalType.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_access.png b/dist/schema/img/eml-physical_xsd_Element_access.png
index cafcedb3..c92db9ce 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_access.png and b/dist/schema/img/eml-physical_xsd_Element_access.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_attributeOrientation.png b/dist/schema/img/eml-physical_xsd_Element_attributeOrientation.png
index 1874b466..e4da8da1 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_attributeOrientation.png and b/dist/schema/img/eml-physical_xsd_Element_attributeOrientation.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_authentication.png b/dist/schema/img/eml-physical_xsd_Element_authentication.png
index 2a799382..7eb59c31 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_authentication.png and b/dist/schema/img/eml-physical_xsd_Element_authentication.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_bandgapbytes.png b/dist/schema/img/eml-physical_xsd_Element_bandgapbytes.png
index eebdb7da..14219f49 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_bandgapbytes.png and b/dist/schema/img/eml-physical_xsd_Element_bandgapbytes.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_bandrowbytes.png b/dist/schema/img/eml-physical_xsd_Element_bandrowbytes.png
index 7b7a4127..9c7ae5d4 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_bandrowbytes.png and b/dist/schema/img/eml-physical_xsd_Element_bandrowbytes.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_binaryRasterFormat.png b/dist/schema/img/eml-physical_xsd_Element_binaryRasterFormat.png
index baee0766..96212ea6 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_binaryRasterFormat.png and b/dist/schema/img/eml-physical_xsd_Element_binaryRasterFormat.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_byteorder.png b/dist/schema/img/eml-physical_xsd_Element_byteorder.png
index fc3bd6bf..6ca0de1a 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_byteorder.png and b/dist/schema/img/eml-physical_xsd_Element_byteorder.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_characterEncoding.png b/dist/schema/img/eml-physical_xsd_Element_characterEncoding.png
index 8ba43308..12368c29 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_characterEncoding.png and b/dist/schema/img/eml-physical_xsd_Element_characterEncoding.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_citation.png b/dist/schema/img/eml-physical_xsd_Element_citation.png
index f6038574..62d5963c 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_citation.png and b/dist/schema/img/eml-physical_xsd_Element_citation.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_collapseDelimiters.png b/dist/schema/img/eml-physical_xsd_Element_collapseDelimiters.png
index 7df8d701..fc153702 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_collapseDelimiters.png and b/dist/schema/img/eml-physical_xsd_Element_collapseDelimiters.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_collapseDelimiters_1.png b/dist/schema/img/eml-physical_xsd_Element_collapseDelimiters_1.png
index 4447ae9c..6a15792b 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_collapseDelimiters_1.png and b/dist/schema/img/eml-physical_xsd_Element_collapseDelimiters_1.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_complex.png b/dist/schema/img/eml-physical_xsd_Element_complex.png
index 26ac65f1..453c0f36 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_complex.png and b/dist/schema/img/eml-physical_xsd_Element_complex.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_compressionMethod.png b/dist/schema/img/eml-physical_xsd_Element_compressionMethod.png
index e3882346..2788be3c 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_compressionMethod.png and b/dist/schema/img/eml-physical_xsd_Element_compressionMethod.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_connection.png b/dist/schema/img/eml-physical_xsd_Element_connection.png
index 01e84e55..1e995fbd 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_connection.png and b/dist/schema/img/eml-physical_xsd_Element_connection.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_dataFormat.png b/dist/schema/img/eml-physical_xsd_Element_dataFormat.png
index 1314b5d1..b50d05bc 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_dataFormat.png and b/dist/schema/img/eml-physical_xsd_Element_dataFormat.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_distribution.png b/dist/schema/img/eml-physical_xsd_Element_distribution.png
index 588934ce..24eab7ae 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_distribution.png and b/dist/schema/img/eml-physical_xsd_Element_distribution.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_encodingMethod.png b/dist/schema/img/eml-physical_xsd_Element_encodingMethod.png
index 7e234f0d..7f3ac5aa 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_encodingMethod.png and b/dist/schema/img/eml-physical_xsd_Element_encodingMethod.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_externallyDefinedFormat.png b/dist/schema/img/eml-physical_xsd_Element_externallyDefinedFormat.png
index 88098d6c..e4a33e5f 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_externallyDefinedFormat.png and b/dist/schema/img/eml-physical_xsd_Element_externallyDefinedFormat.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_fieldDelimiter.png b/dist/schema/img/eml-physical_xsd_Element_fieldDelimiter.png
index 44c92187..d1836355 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_fieldDelimiter.png and b/dist/schema/img/eml-physical_xsd_Element_fieldDelimiter.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_fieldDelimiter_1.png b/dist/schema/img/eml-physical_xsd_Element_fieldDelimiter_1.png
index b9dbceda..dc0cb605 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_fieldDelimiter_1.png and b/dist/schema/img/eml-physical_xsd_Element_fieldDelimiter_1.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_fieldStartColumn.png b/dist/schema/img/eml-physical_xsd_Element_fieldStartColumn.png
index abdfb8a5..3bf7145c 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_fieldStartColumn.png and b/dist/schema/img/eml-physical_xsd_Element_fieldStartColumn.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_fieldWidth.png b/dist/schema/img/eml-physical_xsd_Element_fieldWidth.png
index 0095029d..ec7a9c04 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_fieldWidth.png and b/dist/schema/img/eml-physical_xsd_Element_fieldWidth.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_formatName.png b/dist/schema/img/eml-physical_xsd_Element_formatName.png
index 174abe37..bde40107 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_formatName.png and b/dist/schema/img/eml-physical_xsd_Element_formatName.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_formatVersion.png b/dist/schema/img/eml-physical_xsd_Element_formatVersion.png
index 696765a4..a0e69437 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_formatVersion.png and b/dist/schema/img/eml-physical_xsd_Element_formatVersion.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_inline.png b/dist/schema/img/eml-physical_xsd_Element_inline.png
index cb50ade9..f4190406 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_inline.png and b/dist/schema/img/eml-physical_xsd_Element_inline.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_layout.png b/dist/schema/img/eml-physical_xsd_Element_layout.png
index b6960a7b..919c72fe 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_layout.png and b/dist/schema/img/eml-physical_xsd_Element_layout.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_lineNumber.png b/dist/schema/img/eml-physical_xsd_Element_lineNumber.png
index f7be84c1..246b9709 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_lineNumber.png and b/dist/schema/img/eml-physical_xsd_Element_lineNumber.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_lineNumber_1.png b/dist/schema/img/eml-physical_xsd_Element_lineNumber_1.png
index f7be84c1..246b9709 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_lineNumber_1.png and b/dist/schema/img/eml-physical_xsd_Element_lineNumber_1.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_literalCharacter.png b/dist/schema/img/eml-physical_xsd_Element_literalCharacter.png
index cfe62fed..c71569f3 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_literalCharacter.png and b/dist/schema/img/eml-physical_xsd_Element_literalCharacter.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_literalCharacter_1.png b/dist/schema/img/eml-physical_xsd_Element_literalCharacter_1.png
index cfe62fed..c71569f3 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_literalCharacter_1.png and b/dist/schema/img/eml-physical_xsd_Element_literalCharacter_1.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_maxRecordLength.png b/dist/schema/img/eml-physical_xsd_Element_maxRecordLength.png
index 80903a64..06eb506d 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_maxRecordLength.png and b/dist/schema/img/eml-physical_xsd_Element_maxRecordLength.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_multiBand.png b/dist/schema/img/eml-physical_xsd_Element_multiBand.png
index f9cb0691..7b83e199 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_multiBand.png and b/dist/schema/img/eml-physical_xsd_Element_multiBand.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_nbands.png b/dist/schema/img/eml-physical_xsd_Element_nbands.png
index fb36073e..f74287cb 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_nbands.png and b/dist/schema/img/eml-physical_xsd_Element_nbands.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_nbits.png b/dist/schema/img/eml-physical_xsd_Element_nbits.png
index e33f6d06..4593391f 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_nbits.png and b/dist/schema/img/eml-physical_xsd_Element_nbits.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_numFooterLines.png b/dist/schema/img/eml-physical_xsd_Element_numFooterLines.png
index 3747d7d5..e61e31d3 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_numFooterLines.png and b/dist/schema/img/eml-physical_xsd_Element_numFooterLines.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_numHeaderLines.png b/dist/schema/img/eml-physical_xsd_Element_numHeaderLines.png
index a7bc4e1a..a8ddd2cc 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_numHeaderLines.png and b/dist/schema/img/eml-physical_xsd_Element_numHeaderLines.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_numPhysicalLinesPerRecord.png b/dist/schema/img/eml-physical_xsd_Element_numPhysicalLinesPerRecord.png
index 1c6fe3ed..7d40d757 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_numPhysicalLinesPerRecord.png and b/dist/schema/img/eml-physical_xsd_Element_numPhysicalLinesPerRecord.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_objectName.png b/dist/schema/img/eml-physical_xsd_Element_objectName.png
index 6afebcd1..55ba9ab7 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_objectName.png and b/dist/schema/img/eml-physical_xsd_Element_objectName.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_offline.png b/dist/schema/img/eml-physical_xsd_Element_offline.png
index f25073b2..741ffc59 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_offline.png and b/dist/schema/img/eml-physical_xsd_Element_offline.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_online.png b/dist/schema/img/eml-physical_xsd_Element_online.png
index 6c3cb5c0..320155bd 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_online.png and b/dist/schema/img/eml-physical_xsd_Element_online.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_onlineDescription.png b/dist/schema/img/eml-physical_xsd_Element_onlineDescription.png
index 5eac320b..01b2535d 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_onlineDescription.png and b/dist/schema/img/eml-physical_xsd_Element_onlineDescription.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_physical.png b/dist/schema/img/eml-physical_xsd_Element_physical.png
index d7590352..7d6eba0a 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_physical.png and b/dist/schema/img/eml-physical_xsd_Element_physical.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_physicalLineDelimiter.png b/dist/schema/img/eml-physical_xsd_Element_physicalLineDelimiter.png
index 553ffab1..d803c02d 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_physicalLineDelimiter.png and b/dist/schema/img/eml-physical_xsd_Element_physicalLineDelimiter.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_quoteCharacter.png b/dist/schema/img/eml-physical_xsd_Element_quoteCharacter.png
index 866ac405..8d9c2ac8 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_quoteCharacter.png and b/dist/schema/img/eml-physical_xsd_Element_quoteCharacter.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_quoteCharacter_1.png b/dist/schema/img/eml-physical_xsd_Element_quoteCharacter_1.png
index 866ac405..8d9c2ac8 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_quoteCharacter_1.png and b/dist/schema/img/eml-physical_xsd_Element_quoteCharacter_1.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_recordDelimiter.png b/dist/schema/img/eml-physical_xsd_Element_recordDelimiter.png
index 1145916a..bfbb622e 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_recordDelimiter.png and b/dist/schema/img/eml-physical_xsd_Element_recordDelimiter.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_rowColumnOrientation.png b/dist/schema/img/eml-physical_xsd_Element_rowColumnOrientation.png
index bb472ae0..a1eacc7c 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_rowColumnOrientation.png and b/dist/schema/img/eml-physical_xsd_Element_rowColumnOrientation.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_simpleDelimited.png b/dist/schema/img/eml-physical_xsd_Element_simpleDelimited.png
index d8818309..9de83251 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_simpleDelimited.png and b/dist/schema/img/eml-physical_xsd_Element_simpleDelimited.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_size.png b/dist/schema/img/eml-physical_xsd_Element_size.png
index 9bbae09c..2871d644 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_size.png and b/dist/schema/img/eml-physical_xsd_Element_size.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_skipbytes.png b/dist/schema/img/eml-physical_xsd_Element_skipbytes.png
index ceea117d..0fead106 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_skipbytes.png and b/dist/schema/img/eml-physical_xsd_Element_skipbytes.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_textDelimited.png b/dist/schema/img/eml-physical_xsd_Element_textDelimited.png
index aff811c8..82fc9535 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_textDelimited.png and b/dist/schema/img/eml-physical_xsd_Element_textDelimited.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_textFixed.png b/dist/schema/img/eml-physical_xsd_Element_textFixed.png
index 8174d9a9..5d73b9cf 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_textFixed.png and b/dist/schema/img/eml-physical_xsd_Element_textFixed.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_textFormat.png b/dist/schema/img/eml-physical_xsd_Element_textFormat.png
index cba5fb3a..1ab4614e 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_textFormat.png and b/dist/schema/img/eml-physical_xsd_Element_textFormat.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_totalrowbytes.png b/dist/schema/img/eml-physical_xsd_Element_totalrowbytes.png
index 3388f78d..1c9fadd0 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_totalrowbytes.png and b/dist/schema/img/eml-physical_xsd_Element_totalrowbytes.png differ
diff --git a/dist/schema/img/eml-physical_xsd_Element_url.png b/dist/schema/img/eml-physical_xsd_Element_url.png
index d2dd3307..3d571208 100644
Binary files a/dist/schema/img/eml-physical_xsd_Element_url.png and b/dist/schema/img/eml-physical_xsd_Element_url.png differ
diff --git a/dist/schema/img/eml-project_xsd_Complex_Type_AwardType.png b/dist/schema/img/eml-project_xsd_Complex_Type_AwardType.png
index e60cdae4..774c80d0 100644
Binary files a/dist/schema/img/eml-project_xsd_Complex_Type_AwardType.png and b/dist/schema/img/eml-project_xsd_Complex_Type_AwardType.png differ
diff --git a/dist/schema/img/eml-project_xsd_Complex_Type_ResearchProjectType.png b/dist/schema/img/eml-project_xsd_Complex_Type_ResearchProjectType.png
index a20d7d0f..23a0b977 100644
Binary files a/dist/schema/img/eml-project_xsd_Complex_Type_ResearchProjectType.png and b/dist/schema/img/eml-project_xsd_Complex_Type_ResearchProjectType.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_abstract.png b/dist/schema/img/eml-project_xsd_Element_abstract.png
index b74a18b7..5812cf37 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_abstract.png and b/dist/schema/img/eml-project_xsd_Element_abstract.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_award.png b/dist/schema/img/eml-project_xsd_Element_award.png
index 4db79684..54e384af 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_award.png and b/dist/schema/img/eml-project_xsd_Element_award.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_awardNumber.png b/dist/schema/img/eml-project_xsd_Element_awardNumber.png
index 09f88d0d..f938d58d 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_awardNumber.png and b/dist/schema/img/eml-project_xsd_Element_awardNumber.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_awardUrl.png b/dist/schema/img/eml-project_xsd_Element_awardUrl.png
index 7a695d2d..1da96b44 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_awardUrl.png and b/dist/schema/img/eml-project_xsd_Element_awardUrl.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_citation.png b/dist/schema/img/eml-project_xsd_Element_citation.png
index b90bfefc..0bfb03f6 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_citation.png and b/dist/schema/img/eml-project_xsd_Element_citation.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_citation_1.png b/dist/schema/img/eml-project_xsd_Element_citation_1.png
index 3960de4d..957b0293 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_citation_1.png and b/dist/schema/img/eml-project_xsd_Element_citation_1.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_citation_2.png b/dist/schema/img/eml-project_xsd_Element_citation_2.png
index e84d6bff..5dffd46d 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_citation_2.png and b/dist/schema/img/eml-project_xsd_Element_citation_2.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_coverage.png b/dist/schema/img/eml-project_xsd_Element_coverage.png
index f5da2c48..8bb481e0 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_coverage.png and b/dist/schema/img/eml-project_xsd_Element_coverage.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_description.png b/dist/schema/img/eml-project_xsd_Element_description.png
index 1f9c539d..51fd7667 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_description.png and b/dist/schema/img/eml-project_xsd_Element_description.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_descriptor.png b/dist/schema/img/eml-project_xsd_Element_descriptor.png
index ec3ae69b..6607303b 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_descriptor.png and b/dist/schema/img/eml-project_xsd_Element_descriptor.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_descriptorValue.png b/dist/schema/img/eml-project_xsd_Element_descriptorValue.png
index b232256a..ab02c299 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_descriptorValue.png and b/dist/schema/img/eml-project_xsd_Element_descriptorValue.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_designDescription.png b/dist/schema/img/eml-project_xsd_Element_designDescription.png
index b1268a2c..de54b6e8 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_designDescription.png and b/dist/schema/img/eml-project_xsd_Element_designDescription.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_funderIdentifier.png b/dist/schema/img/eml-project_xsd_Element_funderIdentifier.png
index 524a1f37..74b233ae 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_funderIdentifier.png and b/dist/schema/img/eml-project_xsd_Element_funderIdentifier.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_funderName.png b/dist/schema/img/eml-project_xsd_Element_funderName.png
index 95652c83..f7173397 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_funderName.png and b/dist/schema/img/eml-project_xsd_Element_funderName.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_funding.png b/dist/schema/img/eml-project_xsd_Element_funding.png
index 5e109082..5ae858f8 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_funding.png and b/dist/schema/img/eml-project_xsd_Element_funding.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_personnel.png b/dist/schema/img/eml-project_xsd_Element_personnel.png
index 8fe986ba..34a537c6 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_personnel.png and b/dist/schema/img/eml-project_xsd_Element_personnel.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_relatedProject.png b/dist/schema/img/eml-project_xsd_Element_relatedProject.png
index f16f847a..6b37131d 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_relatedProject.png and b/dist/schema/img/eml-project_xsd_Element_relatedProject.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_researchProject.png b/dist/schema/img/eml-project_xsd_Element_researchProject.png
index 54c70b83..7025ca05 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_researchProject.png and b/dist/schema/img/eml-project_xsd_Element_researchProject.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_role.png b/dist/schema/img/eml-project_xsd_Element_role.png
index 88de78ca..b3f95c68 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_role.png and b/dist/schema/img/eml-project_xsd_Element_role.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_studyAreaDescription.png b/dist/schema/img/eml-project_xsd_Element_studyAreaDescription.png
index 1a4a0d91..e783f48a 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_studyAreaDescription.png and b/dist/schema/img/eml-project_xsd_Element_studyAreaDescription.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_title.png b/dist/schema/img/eml-project_xsd_Element_title.png
index 68a96217..08d5a837 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_title.png and b/dist/schema/img/eml-project_xsd_Element_title.png differ
diff --git a/dist/schema/img/eml-project_xsd_Element_title_1.png b/dist/schema/img/eml-project_xsd_Element_title_1.png
index b4075c0b..8c0d35df 100644
Binary files a/dist/schema/img/eml-project_xsd_Element_title_1.png and b/dist/schema/img/eml-project_xsd_Element_title_1.png differ
diff --git a/dist/schema/img/eml-project_xsd_Simple_Type_DescriptorType.png b/dist/schema/img/eml-project_xsd_Simple_Type_DescriptorType.png
index 6bb0d28d..01ae620a 100644
Binary files a/dist/schema/img/eml-project_xsd_Simple_Type_DescriptorType.png and b/dist/schema/img/eml-project_xsd_Simple_Type_DescriptorType.png differ
diff --git a/dist/schema/img/eml-protocol_xsd_Complex_Type_ProtocolType.png b/dist/schema/img/eml-protocol_xsd_Complex_Type_ProtocolType.png
index a9b81898..e27a1c61 100644
Binary files a/dist/schema/img/eml-protocol_xsd_Complex_Type_ProtocolType.png and b/dist/schema/img/eml-protocol_xsd_Complex_Type_ProtocolType.png differ
diff --git a/dist/schema/img/eml-protocol_xsd_Element_proceduralStep.png b/dist/schema/img/eml-protocol_xsd_Element_proceduralStep.png
index a4d07315..48dfc247 100644
Binary files a/dist/schema/img/eml-protocol_xsd_Element_proceduralStep.png and b/dist/schema/img/eml-protocol_xsd_Element_proceduralStep.png differ
diff --git a/dist/schema/img/eml-protocol_xsd_Element_protocol.png b/dist/schema/img/eml-protocol_xsd_Element_protocol.png
index efeb6cae..b05a520b 100644
Binary files a/dist/schema/img/eml-protocol_xsd_Element_protocol.png and b/dist/schema/img/eml-protocol_xsd_Element_protocol.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_ConnectionDefinitionType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_ConnectionDefinitionType.png
index e6c3642d..f0276e1a 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_ConnectionDefinitionType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_ConnectionDefinitionType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_ConnectionType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_ConnectionType.png
index 1180d4bc..a13df99d 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_ConnectionType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_ConnectionType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_DistributionType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_DistributionType.png
index 61398c8b..72ae7ffa 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_DistributionType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_DistributionType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_InlineType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_InlineType.png
index c7fb9a1a..75f2d367 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_InlineType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_InlineType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_LicenseType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_LicenseType.png
index 95cb552d..fbb89fc1 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_LicenseType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_LicenseType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_OfflineType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_OfflineType.png
index 88c1973c..c6aa10f1 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_OfflineType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_OfflineType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_OnlineType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_OnlineType.png
index 51be626f..90e9a7f3 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_OnlineType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_OnlineType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_UrlType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_UrlType.png
index 5a769b1d..cec594e4 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_UrlType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_UrlType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Complex_Type_i18nNonEmptyStringType.png b/dist/schema/img/eml-resource_xsd_Complex_Type_i18nNonEmptyStringType.png
index fdad2720..5eb8571e 100644
Binary files a/dist/schema/img/eml-resource_xsd_Complex_Type_i18nNonEmptyStringType.png and b/dist/schema/img/eml-resource_xsd_Complex_Type_i18nNonEmptyStringType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_Group_ReferencesGroup.png b/dist/schema/img/eml-resource_xsd_Element_Group_ReferencesGroup.png
index 6cd49301..a6fa76d2 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_Group_ReferencesGroup.png and b/dist/schema/img/eml-resource_xsd_Element_Group_ReferencesGroup.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_Group_ResourceGroup.png b/dist/schema/img/eml-resource_xsd_Element_Group_ResourceGroup.png
index 257a2dd9..c271f99a 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_Group_ResourceGroup.png and b/dist/schema/img/eml-resource_xsd_Element_Group_ResourceGroup.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_abstract.png b/dist/schema/img/eml-resource_xsd_Element_abstract.png
index b31d7e2a..a102f130 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_abstract.png and b/dist/schema/img/eml-resource_xsd_Element_abstract.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_additionalInfo.png b/dist/schema/img/eml-resource_xsd_Element_additionalInfo.png
index f9b005b6..d1648861 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_additionalInfo.png and b/dist/schema/img/eml-resource_xsd_Element_additionalInfo.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_alternateIdentifier.png b/dist/schema/img/eml-resource_xsd_Element_alternateIdentifier.png
index c8875aff..f8379d28 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_alternateIdentifier.png and b/dist/schema/img/eml-resource_xsd_Element_alternateIdentifier.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_annotation.png b/dist/schema/img/eml-resource_xsd_Element_annotation.png
index 1cb720d3..070c145a 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_annotation.png and b/dist/schema/img/eml-resource_xsd_Element_annotation.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_associatedParty.png b/dist/schema/img/eml-resource_xsd_Element_associatedParty.png
index 5f698f06..67c12808 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_associatedParty.png and b/dist/schema/img/eml-resource_xsd_Element_associatedParty.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_connection.png b/dist/schema/img/eml-resource_xsd_Element_connection.png
index 9488ca80..628e657f 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_connection.png and b/dist/schema/img/eml-resource_xsd_Element_connection.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_connectionDefinition.png b/dist/schema/img/eml-resource_xsd_Element_connectionDefinition.png
index d39e0b2b..a4bd4d28 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_connectionDefinition.png and b/dist/schema/img/eml-resource_xsd_Element_connectionDefinition.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_connectionDefinition_1.png b/dist/schema/img/eml-resource_xsd_Element_connectionDefinition_1.png
index 2980ba78..59727b3c 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_connectionDefinition_1.png and b/dist/schema/img/eml-resource_xsd_Element_connectionDefinition_1.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_coverage.png b/dist/schema/img/eml-resource_xsd_Element_coverage.png
index f60b0c5a..dd42eb77 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_coverage.png and b/dist/schema/img/eml-resource_xsd_Element_coverage.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_creator.png b/dist/schema/img/eml-resource_xsd_Element_creator.png
index 3fd4b315..2c9bddbf 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_creator.png and b/dist/schema/img/eml-resource_xsd_Element_creator.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_defaultValue.png b/dist/schema/img/eml-resource_xsd_Element_defaultValue.png
index b6bcbc7f..e9a12347 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_defaultValue.png and b/dist/schema/img/eml-resource_xsd_Element_defaultValue.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_definition.png b/dist/schema/img/eml-resource_xsd_Element_definition.png
index 76477cbe..048cb492 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_definition.png and b/dist/schema/img/eml-resource_xsd_Element_definition.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_description.png b/dist/schema/img/eml-resource_xsd_Element_description.png
index c19aeca6..23441a71 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_description.png and b/dist/schema/img/eml-resource_xsd_Element_description.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_distribution.png b/dist/schema/img/eml-resource_xsd_Element_distribution.png
index dba79052..2fec5d95 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_distribution.png and b/dist/schema/img/eml-resource_xsd_Element_distribution.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_identifier.png b/dist/schema/img/eml-resource_xsd_Element_identifier.png
index 70085f79..8d9b83a2 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_identifier.png and b/dist/schema/img/eml-resource_xsd_Element_identifier.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_inline.png b/dist/schema/img/eml-resource_xsd_Element_inline.png
index 3b9a05f1..170e24f9 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_inline.png and b/dist/schema/img/eml-resource_xsd_Element_inline.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_intellectualRights.png b/dist/schema/img/eml-resource_xsd_Element_intellectualRights.png
index 6141b3dd..1cd95dc3 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_intellectualRights.png and b/dist/schema/img/eml-resource_xsd_Element_intellectualRights.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_keyword.png b/dist/schema/img/eml-resource_xsd_Element_keyword.png
index 67283ce2..4070e322 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_keyword.png and b/dist/schema/img/eml-resource_xsd_Element_keyword.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_keywordSet.png b/dist/schema/img/eml-resource_xsd_Element_keywordSet.png
index ba93820d..e1be8e41 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_keywordSet.png and b/dist/schema/img/eml-resource_xsd_Element_keywordSet.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_keywordThesaurus.png b/dist/schema/img/eml-resource_xsd_Element_keywordThesaurus.png
index 1395b56c..b25859ef 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_keywordThesaurus.png and b/dist/schema/img/eml-resource_xsd_Element_keywordThesaurus.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_language.png b/dist/schema/img/eml-resource_xsd_Element_language.png
index eefde0ea..eac95c27 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_language.png and b/dist/schema/img/eml-resource_xsd_Element_language.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_licenseName.png b/dist/schema/img/eml-resource_xsd_Element_licenseName.png
index 901a18f1..08619e35 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_licenseName.png and b/dist/schema/img/eml-resource_xsd_Element_licenseName.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_licensed.png b/dist/schema/img/eml-resource_xsd_Element_licensed.png
index 569a5c94..c758c046 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_licensed.png and b/dist/schema/img/eml-resource_xsd_Element_licensed.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_mediumDensity.png b/dist/schema/img/eml-resource_xsd_Element_mediumDensity.png
index 3f8897ef..4c51a599 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_mediumDensity.png and b/dist/schema/img/eml-resource_xsd_Element_mediumDensity.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_mediumDensityUnits.png b/dist/schema/img/eml-resource_xsd_Element_mediumDensityUnits.png
index 94530929..e400601a 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_mediumDensityUnits.png and b/dist/schema/img/eml-resource_xsd_Element_mediumDensityUnits.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_mediumFormat.png b/dist/schema/img/eml-resource_xsd_Element_mediumFormat.png
index 5f9401ec..01c08f46 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_mediumFormat.png and b/dist/schema/img/eml-resource_xsd_Element_mediumFormat.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_mediumName.png b/dist/schema/img/eml-resource_xsd_Element_mediumName.png
index 7e208f38..483145a1 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_mediumName.png and b/dist/schema/img/eml-resource_xsd_Element_mediumName.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_mediumNote.png b/dist/schema/img/eml-resource_xsd_Element_mediumNote.png
index c48f476c..44eea6e3 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_mediumNote.png and b/dist/schema/img/eml-resource_xsd_Element_mediumNote.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_mediumVolume.png b/dist/schema/img/eml-resource_xsd_Element_mediumVolume.png
index 2d88999c..e8fed81b 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_mediumVolume.png and b/dist/schema/img/eml-resource_xsd_Element_mediumVolume.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_metadataProvider.png b/dist/schema/img/eml-resource_xsd_Element_metadataProvider.png
index c085979b..963b9ab2 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_metadataProvider.png and b/dist/schema/img/eml-resource_xsd_Element_metadataProvider.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_name.png b/dist/schema/img/eml-resource_xsd_Element_name.png
index db33d52c..104e9cdc 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_name.png and b/dist/schema/img/eml-resource_xsd_Element_name.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_name_1.png b/dist/schema/img/eml-resource_xsd_Element_name_1.png
index 0f861e21..e28ea5fe 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_name_1.png and b/dist/schema/img/eml-resource_xsd_Element_name_1.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_offline.png b/dist/schema/img/eml-resource_xsd_Element_offline.png
index dca415d7..2670e95c 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_offline.png and b/dist/schema/img/eml-resource_xsd_Element_offline.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_online.png b/dist/schema/img/eml-resource_xsd_Element_online.png
index ac6e86fa..aadacd4e 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_online.png and b/dist/schema/img/eml-resource_xsd_Element_online.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_onlineDescription.png b/dist/schema/img/eml-resource_xsd_Element_onlineDescription.png
index 13d82ecd..b7d896d3 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_onlineDescription.png and b/dist/schema/img/eml-resource_xsd_Element_onlineDescription.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_parameter.png b/dist/schema/img/eml-resource_xsd_Element_parameter.png
index 3bbaeece..bad6d9ac 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_parameter.png and b/dist/schema/img/eml-resource_xsd_Element_parameter.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_parameterDefinition.png b/dist/schema/img/eml-resource_xsd_Element_parameterDefinition.png
index 90ba5637..49a7d9b5 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_parameterDefinition.png and b/dist/schema/img/eml-resource_xsd_Element_parameterDefinition.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_pubDate.png b/dist/schema/img/eml-resource_xsd_Element_pubDate.png
index 58d56140..7fc6a955 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_pubDate.png and b/dist/schema/img/eml-resource_xsd_Element_pubDate.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_references.png b/dist/schema/img/eml-resource_xsd_Element_references.png
index a1a39dfe..ceec4452 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_references.png and b/dist/schema/img/eml-resource_xsd_Element_references.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_role.png b/dist/schema/img/eml-resource_xsd_Element_role.png
index 398ec587..da52e935 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_role.png and b/dist/schema/img/eml-resource_xsd_Element_role.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_schemeName.png b/dist/schema/img/eml-resource_xsd_Element_schemeName.png
index 3b0dbe1b..fad2aa4c 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_schemeName.png and b/dist/schema/img/eml-resource_xsd_Element_schemeName.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_series.png b/dist/schema/img/eml-resource_xsd_Element_series.png
index dce04294..f5ceea3f 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_series.png and b/dist/schema/img/eml-resource_xsd_Element_series.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_shortName.png b/dist/schema/img/eml-resource_xsd_Element_shortName.png
index 8054c50d..55de5a70 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_shortName.png and b/dist/schema/img/eml-resource_xsd_Element_shortName.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_title.png b/dist/schema/img/eml-resource_xsd_Element_title.png
index 7fbf8afe..0d6adeb6 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_title.png and b/dist/schema/img/eml-resource_xsd_Element_title.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_url.png b/dist/schema/img/eml-resource_xsd_Element_url.png
index 49a8f133..8724ac45 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_url.png and b/dist/schema/img/eml-resource_xsd_Element_url.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_url_1.png b/dist/schema/img/eml-resource_xsd_Element_url_1.png
index 2039e10c..664b62fd 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_url_1.png and b/dist/schema/img/eml-resource_xsd_Element_url_1.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_value.png b/dist/schema/img/eml-resource_xsd_Element_value.png
index f395636c..362e501e 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_value.png and b/dist/schema/img/eml-resource_xsd_Element_value.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Element_value_1.png b/dist/schema/img/eml-resource_xsd_Element_value_1.png
index 40526a3d..fd10a4eb 100644
Binary files a/dist/schema/img/eml-resource_xsd_Element_value_1.png and b/dist/schema/img/eml-resource_xsd_Element_value_1.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Simple_Type_FunctionType.png b/dist/schema/img/eml-resource_xsd_Simple_Type_FunctionType.png
index cb80c4c8..b40e5f0a 100644
Binary files a/dist/schema/img/eml-resource_xsd_Simple_Type_FunctionType.png and b/dist/schema/img/eml-resource_xsd_Simple_Type_FunctionType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Simple_Type_IDType.png b/dist/schema/img/eml-resource_xsd_Simple_Type_IDType.png
index 9c022748..8baa6212 100644
Binary files a/dist/schema/img/eml-resource_xsd_Simple_Type_IDType.png and b/dist/schema/img/eml-resource_xsd_Simple_Type_IDType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Simple_Type_KeyTypeCode.png b/dist/schema/img/eml-resource_xsd_Simple_Type_KeyTypeCode.png
index ba782ce9..ca0db20d 100644
Binary files a/dist/schema/img/eml-resource_xsd_Simple_Type_KeyTypeCode.png and b/dist/schema/img/eml-resource_xsd_Simple_Type_KeyTypeCode.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Simple_Type_NonEmptyStringType.png b/dist/schema/img/eml-resource_xsd_Simple_Type_NonEmptyStringType.png
index cc6114e6..f17b3a26 100644
Binary files a/dist/schema/img/eml-resource_xsd_Simple_Type_NonEmptyStringType.png and b/dist/schema/img/eml-resource_xsd_Simple_Type_NonEmptyStringType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Simple_Type_ScopeType.png b/dist/schema/img/eml-resource_xsd_Simple_Type_ScopeType.png
index 00c296d9..34b1de4f 100644
Binary files a/dist/schema/img/eml-resource_xsd_Simple_Type_ScopeType.png and b/dist/schema/img/eml-resource_xsd_Simple_Type_ScopeType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Simple_Type_SystemType.png b/dist/schema/img/eml-resource_xsd_Simple_Type_SystemType.png
index ffc5c1b4..f61c24c0 100644
Binary files a/dist/schema/img/eml-resource_xsd_Simple_Type_SystemType.png and b/dist/schema/img/eml-resource_xsd_Simple_Type_SystemType.png differ
diff --git a/dist/schema/img/eml-resource_xsd_Simple_Type_yearDate.png b/dist/schema/img/eml-resource_xsd_Simple_Type_yearDate.png
index ad86b01a..868ffcd9 100644
Binary files a/dist/schema/img/eml-resource_xsd_Simple_Type_yearDate.png and b/dist/schema/img/eml-resource_xsd_Simple_Type_yearDate.png differ
diff --git a/dist/schema/img/eml-semantics_xsd_Complex_Type_SemanticAnnotation.png b/dist/schema/img/eml-semantics_xsd_Complex_Type_SemanticAnnotation.png
index 22c7428e..0d79edf4 100644
Binary files a/dist/schema/img/eml-semantics_xsd_Complex_Type_SemanticAnnotation.png and b/dist/schema/img/eml-semantics_xsd_Complex_Type_SemanticAnnotation.png differ
diff --git a/dist/schema/img/eml-semantics_xsd_Element_annotation.png b/dist/schema/img/eml-semantics_xsd_Element_annotation.png
index 82dddc6f..82f44000 100644
Binary files a/dist/schema/img/eml-semantics_xsd_Element_annotation.png and b/dist/schema/img/eml-semantics_xsd_Element_annotation.png differ
diff --git a/dist/schema/img/eml-semantics_xsd_Element_propertyURI.png b/dist/schema/img/eml-semantics_xsd_Element_propertyURI.png
index 065dfadb..16f80580 100644
Binary files a/dist/schema/img/eml-semantics_xsd_Element_propertyURI.png and b/dist/schema/img/eml-semantics_xsd_Element_propertyURI.png differ
diff --git a/dist/schema/img/eml-semantics_xsd_Element_valueURI.png b/dist/schema/img/eml-semantics_xsd_Element_valueURI.png
index b5d9f54b..e65f3ee5 100644
Binary files a/dist/schema/img/eml-semantics_xsd_Element_valueURI.png and b/dist/schema/img/eml-semantics_xsd_Element_valueURI.png differ
diff --git a/dist/schema/img/eml-software_xsd_Complex_Type_DependencyType.png b/dist/schema/img/eml-software_xsd_Complex_Type_DependencyType.png
index cc8832be..c8711a63 100644
Binary files a/dist/schema/img/eml-software_xsd_Complex_Type_DependencyType.png and b/dist/schema/img/eml-software_xsd_Complex_Type_DependencyType.png differ
diff --git a/dist/schema/img/eml-software_xsd_Complex_Type_SoftwareType.png b/dist/schema/img/eml-software_xsd_Complex_Type_SoftwareType.png
index 222c7898..227522e6 100644
Binary files a/dist/schema/img/eml-software_xsd_Complex_Type_SoftwareType.png and b/dist/schema/img/eml-software_xsd_Complex_Type_SoftwareType.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_LanguageCodeStandard.png b/dist/schema/img/eml-software_xsd_Element_LanguageCodeStandard.png
index d581d31b..77afe944 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_LanguageCodeStandard.png and b/dist/schema/img/eml-software_xsd_Element_LanguageCodeStandard.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_LanguageValue.png b/dist/schema/img/eml-software_xsd_Element_LanguageValue.png
index c035e94c..ba613ac1 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_LanguageValue.png and b/dist/schema/img/eml-software_xsd_Element_LanguageValue.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_action.png b/dist/schema/img/eml-software_xsd_Element_action.png
index 34f64f38..8596bcae 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_action.png and b/dist/schema/img/eml-software_xsd_Element_action.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_checksum.png b/dist/schema/img/eml-software_xsd_Element_checksum.png
index 097f1168..83fc632a 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_checksum.png and b/dist/schema/img/eml-software_xsd_Element_checksum.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_dependency.png b/dist/schema/img/eml-software_xsd_Element_dependency.png
index 5e33a912..8014361a 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_dependency.png and b/dist/schema/img/eml-software_xsd_Element_dependency.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_dependency_1.png b/dist/schema/img/eml-software_xsd_Element_dependency_1.png
index 21419947..a78ff7d7 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_dependency_1.png and b/dist/schema/img/eml-software_xsd_Element_dependency_1.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_dependency_2.png b/dist/schema/img/eml-software_xsd_Element_dependency_2.png
index 5f8a843e..08a44a10 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_dependency_2.png and b/dist/schema/img/eml-software_xsd_Element_dependency_2.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_diskUsage.png b/dist/schema/img/eml-software_xsd_Element_diskUsage.png
index 537dddfb..542ab5f0 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_diskUsage.png and b/dist/schema/img/eml-software_xsd_Element_diskUsage.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_distribution.png b/dist/schema/img/eml-software_xsd_Element_distribution.png
index 664c6572..8f1e7279 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_distribution.png and b/dist/schema/img/eml-software_xsd_Element_distribution.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_implementation.png b/dist/schema/img/eml-software_xsd_Element_implementation.png
index d0cbaa15..beebd434 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_implementation.png and b/dist/schema/img/eml-software_xsd_Element_implementation.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_language.png b/dist/schema/img/eml-software_xsd_Element_language.png
index 30d5ebbc..b0a60b1b 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_language.png and b/dist/schema/img/eml-software_xsd_Element_language.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_license.png b/dist/schema/img/eml-software_xsd_Element_license.png
index 6213021a..057b1a1f 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_license.png and b/dist/schema/img/eml-software_xsd_Element_license.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_licenseURL.png b/dist/schema/img/eml-software_xsd_Element_licenseURL.png
index 7488db36..766fd43a 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_licenseURL.png and b/dist/schema/img/eml-software_xsd_Element_licenseURL.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_machineProcessor.png b/dist/schema/img/eml-software_xsd_Element_machineProcessor.png
index a11a0796..dec07fac 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_machineProcessor.png and b/dist/schema/img/eml-software_xsd_Element_machineProcessor.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_operatingSystem.png b/dist/schema/img/eml-software_xsd_Element_operatingSystem.png
index 23ec3279..ed625363 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_operatingSystem.png and b/dist/schema/img/eml-software_xsd_Element_operatingSystem.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_programmingLanguage.png b/dist/schema/img/eml-software_xsd_Element_programmingLanguage.png
index d00c2318..065b0957 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_programmingLanguage.png and b/dist/schema/img/eml-software_xsd_Element_programmingLanguage.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_project.png b/dist/schema/img/eml-software_xsd_Element_project.png
index b5decef4..e2645e6d 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_project.png and b/dist/schema/img/eml-software_xsd_Element_project.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_runtimeMemoryUsage.png b/dist/schema/img/eml-software_xsd_Element_runtimeMemoryUsage.png
index cc536c35..a5cd8c05 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_runtimeMemoryUsage.png and b/dist/schema/img/eml-software_xsd_Element_runtimeMemoryUsage.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_size.png b/dist/schema/img/eml-software_xsd_Element_size.png
index 61d6a9be..594ef327 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_size.png and b/dist/schema/img/eml-software_xsd_Element_size.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_software.png b/dist/schema/img/eml-software_xsd_Element_software.png
index 1daca6e0..1a26d8a0 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_software.png and b/dist/schema/img/eml-software_xsd_Element_software.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_software_1.png b/dist/schema/img/eml-software_xsd_Element_software_1.png
index c4f689e3..fa887e0a 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_software_1.png and b/dist/schema/img/eml-software_xsd_Element_software_1.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_version.png b/dist/schema/img/eml-software_xsd_Element_version.png
index 3ada1379..6cdfff15 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_version.png and b/dist/schema/img/eml-software_xsd_Element_version.png differ
diff --git a/dist/schema/img/eml-software_xsd_Element_virtualMachine.png b/dist/schema/img/eml-software_xsd_Element_virtualMachine.png
index b1cae870..1e7fe3b9 100644
Binary files a/dist/schema/img/eml-software_xsd_Element_virtualMachine.png and b/dist/schema/img/eml-software_xsd_Element_virtualMachine.png differ
diff --git a/dist/schema/img/eml-software_xsd_Simple_Type_Action.png b/dist/schema/img/eml-software_xsd_Simple_Type_Action.png
index 1e36816e..8bbc1cd1 100644
Binary files a/dist/schema/img/eml-software_xsd_Simple_Type_Action.png and b/dist/schema/img/eml-software_xsd_Simple_Type_Action.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_BandType.png b/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_BandType.png
index 672daea4..77103150 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_BandType.png and b/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_BandType.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_DataQuality.png b/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_DataQuality.png
index c0993cd3..ef0950bb 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_DataQuality.png and b/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_DataQuality.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_SpatialRasterType.png b/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_SpatialRasterType.png
index b4667c34..ef825f46 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_SpatialRasterType.png and b/dist/schema/img/eml-spatialRaster_xsd_Complex_Type_SpatialRasterType.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_accuracyReport.png b/dist/schema/img/eml-spatialRaster_xsd_Element_accuracyReport.png
index aad67bf2..c864aeec 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_accuracyReport.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_accuracyReport.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_attributeList.png b/dist/schema/img/eml-spatialRaster_xsd_Element_attributeList.png
index 9c6a98c6..66a27bd4 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_attributeList.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_attributeList.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_bandDescription.png b/dist/schema/img/eml-spatialRaster_xsd_Element_bandDescription.png
index ec46ead8..1d3c91d9 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_bandDescription.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_bandDescription.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_bilinearFit.png b/dist/schema/img/eml-spatialRaster_xsd_Element_bilinearFit.png
index e673ade2..e69088ed 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_bilinearFit.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_bilinearFit.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_cameraCalibrationInformationAvailability.png b/dist/schema/img/eml-spatialRaster_xsd_Element_cameraCalibrationInformationAvailability.png
index 7b47751a..d08620ac 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_cameraCalibrationInformationAvailability.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_cameraCalibrationInformationAvailability.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_cellGeometry.png b/dist/schema/img/eml-spatialRaster_xsd_Element_cellGeometry.png
index 35d241db..affa54af 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_cellGeometry.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_cellGeometry.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_cellSizeXDirection.png b/dist/schema/img/eml-spatialRaster_xsd_Element_cellSizeXDirection.png
index fa871158..47f7be14 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_cellSizeXDirection.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_cellSizeXDirection.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_cellSizeYDirection.png b/dist/schema/img/eml-spatialRaster_xsd_Element_cellSizeYDirection.png
index edf15ada..cf8bb27b 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_cellSizeYDirection.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_cellSizeYDirection.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_cloudCoverPercentage.png b/dist/schema/img/eml-spatialRaster_xsd_Element_cloudCoverPercentage.png
index ea9bd5d1..81203c97 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_cloudCoverPercentage.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_cloudCoverPercentage.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_column.png b/dist/schema/img/eml-spatialRaster_xsd_Element_column.png
index e9100260..df0ab733 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_column.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_column.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_columns.png b/dist/schema/img/eml-spatialRaster_xsd_Element_columns.png
index ff317126..d9422dcf 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_columns.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_columns.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_compressionGenerationQuality.png b/dist/schema/img/eml-spatialRaster_xsd_Element_compressionGenerationQuality.png
index 8b4fa6f0..278c4dd4 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_compressionGenerationQuality.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_compressionGenerationQuality.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_constraint.png b/dist/schema/img/eml-spatialRaster_xsd_Element_constraint.png
index 8851d0a0..3faba473 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_constraint.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_constraint.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_controlPoint.png b/dist/schema/img/eml-spatialRaster_xsd_Element_controlPoint.png
index 75c032e4..8e07ee13 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_controlPoint.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_controlPoint.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_corner.png b/dist/schema/img/eml-spatialRaster_xsd_Element_corner.png
index 0e81b107..f8ecb668 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_corner.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_corner.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_cornerPoint.png b/dist/schema/img/eml-spatialRaster_xsd_Element_cornerPoint.png
index eda70fb9..6222743f 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_cornerPoint.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_cornerPoint.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_filmDistortionInformationAvailability.png b/dist/schema/img/eml-spatialRaster_xsd_Element_filmDistortionInformationAvailability.png
index 02e77e51..4f9312b1 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_filmDistortionInformationAvailability.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_filmDistortionInformationAvailability.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_georeferenceInfo.png b/dist/schema/img/eml-spatialRaster_xsd_Element_georeferenceInfo.png
index a4b8fe33..efb98bd7 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_georeferenceInfo.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_georeferenceInfo.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_highWavelength.png b/dist/schema/img/eml-spatialRaster_xsd_Element_highWavelength.png
index 4c93690b..b26a29e0 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_highWavelength.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_highWavelength.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_horizontalAccuracy.png b/dist/schema/img/eml-spatialRaster_xsd_Element_horizontalAccuracy.png
index 8b65cc81..0ee3fea8 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_horizontalAccuracy.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_horizontalAccuracy.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_illuminationAzimuthAngle.png b/dist/schema/img/eml-spatialRaster_xsd_Element_illuminationAzimuthAngle.png
index caa3a9da..8d17fd1c 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_illuminationAzimuthAngle.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_illuminationAzimuthAngle.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_illuminationElevationAngle.png b/dist/schema/img/eml-spatialRaster_xsd_Element_illuminationElevationAngle.png
index 786f39ae..c05a033e 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_illuminationElevationAngle.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_illuminationElevationAngle.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_imageDescription.png b/dist/schema/img/eml-spatialRaster_xsd_Element_imageDescription.png
index 4a544d6d..e25df08a 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_imageDescription.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_imageDescription.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_imageOrientationAngle.png b/dist/schema/img/eml-spatialRaster_xsd_Element_imageOrientationAngle.png
index 17296b87..d229c10b 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_imageOrientationAngle.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_imageOrientationAngle.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_imageQualityCode.png b/dist/schema/img/eml-spatialRaster_xsd_Element_imageQualityCode.png
index 39b20b9a..a5dfa992 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_imageQualityCode.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_imageQualityCode.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_imagingCondition.png b/dist/schema/img/eml-spatialRaster_xsd_Element_imagingCondition.png
index bc7016f7..72d8eaac 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_imagingCondition.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_imagingCondition.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_lensDistortionInformationAvailability.png b/dist/schema/img/eml-spatialRaster_xsd_Element_lensDistortionInformationAvailability.png
index 109e601b..c268157c 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_lensDistortionInformationAvailability.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_lensDistortionInformationAvailability.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_lowWaveLength.png b/dist/schema/img/eml-spatialRaster_xsd_Element_lowWaveLength.png
index 10c26e50..201bc3ca 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_lowWaveLength.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_lowWaveLength.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_numberOfBands.png b/dist/schema/img/eml-spatialRaster_xsd_Element_numberOfBands.png
index 15b00eab..e96013fd 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_numberOfBands.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_numberOfBands.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_offset.png b/dist/schema/img/eml-spatialRaster_xsd_Element_offset.png
index 5203a377..f6c51522 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_offset.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_offset.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_peakResponse.png b/dist/schema/img/eml-spatialRaster_xsd_Element_peakResponse.png
index d5f0f276..6878ba64 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_peakResponse.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_peakResponse.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_pointInPixel.png b/dist/schema/img/eml-spatialRaster_xsd_Element_pointInPixel.png
index ee296654..3929d76f 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_pointInPixel.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_pointInPixel.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_pointInPixel_1.png b/dist/schema/img/eml-spatialRaster_xsd_Element_pointInPixel_1.png
index ee296654..3929d76f 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_pointInPixel_1.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_pointInPixel_1.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_preProcessingTypeCode.png b/dist/schema/img/eml-spatialRaster_xsd_Element_preProcessingTypeCode.png
index 35ef811c..51bed9ab 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_preProcessingTypeCode.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_preProcessingTypeCode.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyMethod.png b/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyMethod.png
index 7ce04187..34dc9265 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyMethod.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyMethod.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyReport.png b/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyReport.png
index e8f87941..a08ba649 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyReport.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyReport.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyValue.png b/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyValue.png
index c1261787..9d7d7f4a 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyValue.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_quantitativeAccuracyValue.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_radiometricDataAvailability.png b/dist/schema/img/eml-spatialRaster_xsd_Element_radiometricDataAvailability.png
index 0db76427..97b74401 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_radiometricDataAvailability.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_radiometricDataAvailability.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_rasterOrigin.png b/dist/schema/img/eml-spatialRaster_xsd_Element_rasterOrigin.png
index 4dad1498..1c081506 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_rasterOrigin.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_rasterOrigin.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_row.png b/dist/schema/img/eml-spatialRaster_xsd_Element_row.png
index 25432be2..505c82f8 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_row.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_row.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_rows.png b/dist/schema/img/eml-spatialRaster_xsd_Element_rows.png
index 89072b22..f0462c4b 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_rows.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_rows.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_scaleFactor.png b/dist/schema/img/eml-spatialRaster_xsd_Element_scaleFactor.png
index 17fa7a20..e2e2bf06 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_scaleFactor.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_scaleFactor.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_sequenceIdentifier.png b/dist/schema/img/eml-spatialRaster_xsd_Element_sequenceIdentifier.png
index a54650f3..32851bfb 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_sequenceIdentifier.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_sequenceIdentifier.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_spatialRaster.png b/dist/schema/img/eml-spatialRaster_xsd_Element_spatialRaster.png
index 1af3d157..bcf05ce0 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_spatialRaster.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_spatialRaster.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_spatialReference.png b/dist/schema/img/eml-spatialRaster_xsd_Element_spatialReference.png
index 2e2bcf27..d9c39164 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_spatialReference.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_spatialReference.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_toneGradation.png b/dist/schema/img/eml-spatialRaster_xsd_Element_toneGradation.png
index 8d03e250..b7629bdd 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_toneGradation.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_toneGradation.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_triangulationIndicator.png b/dist/schema/img/eml-spatialRaster_xsd_Element_triangulationIndicator.png
index b6896bbe..b14b4dd2 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_triangulationIndicator.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_triangulationIndicator.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_verticalAccuracy.png b/dist/schema/img/eml-spatialRaster_xsd_Element_verticalAccuracy.png
index 16fdea90..cad7056d 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_verticalAccuracy.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_verticalAccuracy.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_verticals.png b/dist/schema/img/eml-spatialRaster_xsd_Element_verticals.png
index 33553cb8..b4bb198b 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_verticals.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_verticals.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_waveLengthUnits.png b/dist/schema/img/eml-spatialRaster_xsd_Element_waveLengthUnits.png
index d7b954ab..914dffc7 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_waveLengthUnits.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_waveLengthUnits.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_xCoordinate.png b/dist/schema/img/eml-spatialRaster_xsd_Element_xCoordinate.png
index 6fca2157..4463a71c 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_xCoordinate.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_xCoordinate.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_xCoordinate_1.png b/dist/schema/img/eml-spatialRaster_xsd_Element_xCoordinate_1.png
index 6fca2157..4463a71c 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_xCoordinate_1.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_xCoordinate_1.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_xIntercept.png b/dist/schema/img/eml-spatialRaster_xsd_Element_xIntercept.png
index 2f086520..9ea12a15 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_xIntercept.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_xIntercept.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_xSlope.png b/dist/schema/img/eml-spatialRaster_xsd_Element_xSlope.png
index fb3ec13c..7c0d0f1b 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_xSlope.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_xSlope.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_yCoordinate.png b/dist/schema/img/eml-spatialRaster_xsd_Element_yCoordinate.png
index c50451b0..dc90a87e 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_yCoordinate.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_yCoordinate.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_yCoordinate_1.png b/dist/schema/img/eml-spatialRaster_xsd_Element_yCoordinate_1.png
index c50451b0..dc90a87e 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_yCoordinate_1.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_yCoordinate_1.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_yIntercept.png b/dist/schema/img/eml-spatialRaster_xsd_Element_yIntercept.png
index 1d4100de..d919334c 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_yIntercept.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_yIntercept.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Element_ySlope.png b/dist/schema/img/eml-spatialRaster_xsd_Element_ySlope.png
index f9d21acc..e3a4bf3e 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Element_ySlope.png and b/dist/schema/img/eml-spatialRaster_xsd_Element_ySlope.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_CellGeometryType.png b/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_CellGeometryType.png
index c8a1de34..40cb206a 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_CellGeometryType.png and b/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_CellGeometryType.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_CellValueType.png b/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_CellValueType.png
index 3a6a670f..91d8b925 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_CellValueType.png and b/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_CellValueType.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_ImagingConditionCode.png b/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_ImagingConditionCode.png
index e970daaa..234aad4f 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_ImagingConditionCode.png and b/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_ImagingConditionCode.png differ
diff --git a/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_rasterOriginType.png b/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_rasterOriginType.png
index e7fedfd7..aae322f3 100644
Binary files a/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_rasterOriginType.png and b/dist/schema/img/eml-spatialRaster_xsd_Simple_Type_rasterOriginType.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Complex_Type_SpatialReferenceType.png b/dist/schema/img/eml-spatialReference_xsd_Complex_Type_SpatialReferenceType.png
index 750b8492..50a97eac 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Complex_Type_SpatialReferenceType.png and b/dist/schema/img/eml-spatialReference_xsd_Complex_Type_SpatialReferenceType.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Complex_Type_geogCoordSysType.png b/dist/schema/img/eml-spatialReference_xsd_Complex_Type_geogCoordSysType.png
index d44b8a7a..3eefd2a1 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Complex_Type_geogCoordSysType.png and b/dist/schema/img/eml-spatialReference_xsd_Complex_Type_geogCoordSysType.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Complex_Type_horizCoordSysType.png b/dist/schema/img/eml-spatialReference_xsd_Complex_Type_horizCoordSysType.png
index d7515144..591891b7 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Complex_Type_horizCoordSysType.png and b/dist/schema/img/eml-spatialReference_xsd_Complex_Type_horizCoordSysType.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeDatumName.png b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeDatumName.png
index 6421b346..3d7b3fa0 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeDatumName.png and b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeDatumName.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeDistanceUnits.png b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeDistanceUnits.png
index 8801d2bb..e77e7f6d 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeDistanceUnits.png and b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeDistanceUnits.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeEncodingMethod.png b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeEncodingMethod.png
index c57ff561..2dde1e25 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeEncodingMethod.png and b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeEncodingMethod.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeResolution.png b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeResolution.png
index cc311ffd..d437a829 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeResolution.png and b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeResolution.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeSysDef.png b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeSysDef.png
index 0fadec78..6cffed40 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_altitudeSysDef.png and b/dist/schema/img/eml-spatialReference_xsd_Element_altitudeSysDef.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_datum.png b/dist/schema/img/eml-spatialReference_xsd_Element_datum.png
index 10775fb2..ee55cef3 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_datum.png and b/dist/schema/img/eml-spatialReference_xsd_Element_datum.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_depthDatumName.png b/dist/schema/img/eml-spatialReference_xsd_Element_depthDatumName.png
index 7b1394ea..351a1851 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_depthDatumName.png and b/dist/schema/img/eml-spatialReference_xsd_Element_depthDatumName.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_depthDistanceUnits.png b/dist/schema/img/eml-spatialReference_xsd_Element_depthDistanceUnits.png
index 682ddb41..edaaa026 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_depthDistanceUnits.png and b/dist/schema/img/eml-spatialReference_xsd_Element_depthDistanceUnits.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_depthEncodingMethod.png b/dist/schema/img/eml-spatialReference_xsd_Element_depthEncodingMethod.png
index b62f92fd..8967b7c1 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_depthEncodingMethod.png and b/dist/schema/img/eml-spatialReference_xsd_Element_depthEncodingMethod.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_depthResolution.png b/dist/schema/img/eml-spatialReference_xsd_Element_depthResolution.png
index e6c5000c..17ba51c8 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_depthResolution.png and b/dist/schema/img/eml-spatialReference_xsd_Element_depthResolution.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_depthSysDef.png b/dist/schema/img/eml-spatialReference_xsd_Element_depthSysDef.png
index e0286802..e8ebee79 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_depthSysDef.png and b/dist/schema/img/eml-spatialReference_xsd_Element_depthSysDef.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_geogCoordSys.png b/dist/schema/img/eml-spatialReference_xsd_Element_geogCoordSys.png
index 8f08ce32..d66c0b07 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_geogCoordSys.png and b/dist/schema/img/eml-spatialReference_xsd_Element_geogCoordSys.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_geogCoordSys_1.png b/dist/schema/img/eml-spatialReference_xsd_Element_geogCoordSys_1.png
index 8f08ce32..d66c0b07 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_geogCoordSys_1.png and b/dist/schema/img/eml-spatialReference_xsd_Element_geogCoordSys_1.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysDef.png b/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysDef.png
index faca9577..381cb283 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysDef.png and b/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysDef.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysDef_1.png b/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysDef_1.png
index faca9577..381cb283 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysDef_1.png and b/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysDef_1.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysName.png b/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysName.png
index e80f38d4..a472d30d 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysName.png and b/dist/schema/img/eml-spatialReference_xsd_Element_horizCoordSysName.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_parameter.png b/dist/schema/img/eml-spatialReference_xsd_Element_parameter.png
index a20ffb53..da7440a1 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_parameter.png and b/dist/schema/img/eml-spatialReference_xsd_Element_parameter.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_primeMeridian.png b/dist/schema/img/eml-spatialReference_xsd_Element_primeMeridian.png
index 4fb755c7..58cc3566 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_primeMeridian.png and b/dist/schema/img/eml-spatialReference_xsd_Element_primeMeridian.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_projCoordSys.png b/dist/schema/img/eml-spatialReference_xsd_Element_projCoordSys.png
index e4ef2939..7122ec6c 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_projCoordSys.png and b/dist/schema/img/eml-spatialReference_xsd_Element_projCoordSys.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_projection.png b/dist/schema/img/eml-spatialReference_xsd_Element_projection.png
index 183f29b2..045e1a02 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_projection.png and b/dist/schema/img/eml-spatialReference_xsd_Element_projection.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_projectionList.png b/dist/schema/img/eml-spatialReference_xsd_Element_projectionList.png
index 8cc90191..a13f53f4 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_projectionList.png and b/dist/schema/img/eml-spatialReference_xsd_Element_projectionList.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_spatialReference.png b/dist/schema/img/eml-spatialReference_xsd_Element_spatialReference.png
index 81094df0..c14eb63c 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_spatialReference.png and b/dist/schema/img/eml-spatialReference_xsd_Element_spatialReference.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_spheroid.png b/dist/schema/img/eml-spatialReference_xsd_Element_spheroid.png
index 2914bcac..be685904 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_spheroid.png and b/dist/schema/img/eml-spatialReference_xsd_Element_spheroid.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_unit.png b/dist/schema/img/eml-spatialReference_xsd_Element_unit.png
index 09afe020..7fcaec02 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_unit.png and b/dist/schema/img/eml-spatialReference_xsd_Element_unit.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_unit_1.png b/dist/schema/img/eml-spatialReference_xsd_Element_unit_1.png
index fbeec240..47198f9d 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_unit_1.png and b/dist/schema/img/eml-spatialReference_xsd_Element_unit_1.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Element_vertCoordSys.png b/dist/schema/img/eml-spatialReference_xsd_Element_vertCoordSys.png
index 54a24e44..6f7bdfbc 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Element_vertCoordSys.png and b/dist/schema/img/eml-spatialReference_xsd_Element_vertCoordSys.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Simple_Type_angleUnits.png b/dist/schema/img/eml-spatialReference_xsd_Simple_Type_angleUnits.png
index 4fe76f52..5dc35379 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Simple_Type_angleUnits.png and b/dist/schema/img/eml-spatialReference_xsd_Simple_Type_angleUnits.png differ
diff --git a/dist/schema/img/eml-spatialReference_xsd_Simple_Type_lengthUnits.png b/dist/schema/img/eml-spatialReference_xsd_Simple_Type_lengthUnits.png
index 1e34732e..30a3dd25 100644
Binary files a/dist/schema/img/eml-spatialReference_xsd_Simple_Type_lengthUnits.png and b/dist/schema/img/eml-spatialReference_xsd_Simple_Type_lengthUnits.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Complex_Type_DataQuality.png b/dist/schema/img/eml-spatialVector_xsd_Complex_Type_DataQuality.png
index c0993cd3..ef0950bb 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Complex_Type_DataQuality.png and b/dist/schema/img/eml-spatialVector_xsd_Complex_Type_DataQuality.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Complex_Type_SpatialVectorType.png b/dist/schema/img/eml-spatialVector_xsd_Complex_Type_SpatialVectorType.png
index 421e29f7..ea852860 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Complex_Type_SpatialVectorType.png and b/dist/schema/img/eml-spatialVector_xsd_Complex_Type_SpatialVectorType.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_accuracyReport.png b/dist/schema/img/eml-spatialVector_xsd_Element_accuracyReport.png
index aad67bf2..c864aeec 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_accuracyReport.png and b/dist/schema/img/eml-spatialVector_xsd_Element_accuracyReport.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_attributeList.png b/dist/schema/img/eml-spatialVector_xsd_Element_attributeList.png
index 9c6a98c6..66a27bd4 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_attributeList.png and b/dist/schema/img/eml-spatialVector_xsd_Element_attributeList.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_constraint.png b/dist/schema/img/eml-spatialVector_xsd_Element_constraint.png
index 8851d0a0..3faba473 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_constraint.png and b/dist/schema/img/eml-spatialVector_xsd_Element_constraint.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_geometricObjectCount.png b/dist/schema/img/eml-spatialVector_xsd_Element_geometricObjectCount.png
index c47cb1b3..819626d3 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_geometricObjectCount.png and b/dist/schema/img/eml-spatialVector_xsd_Element_geometricObjectCount.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_geometry.png b/dist/schema/img/eml-spatialVector_xsd_Element_geometry.png
index 9bab5145..397bf71f 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_geometry.png and b/dist/schema/img/eml-spatialVector_xsd_Element_geometry.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_horizontalAccuracy.png b/dist/schema/img/eml-spatialVector_xsd_Element_horizontalAccuracy.png
index e0d14c6d..d0debdea 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_horizontalAccuracy.png and b/dist/schema/img/eml-spatialVector_xsd_Element_horizontalAccuracy.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyMethod.png b/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyMethod.png
index 7ce04187..34dc9265 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyMethod.png and b/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyMethod.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyReport.png b/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyReport.png
index e8f87941..a08ba649 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyReport.png and b/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyReport.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyValue.png b/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyValue.png
index c1261787..9d7d7f4a 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyValue.png and b/dist/schema/img/eml-spatialVector_xsd_Element_quantitativeAccuracyValue.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_spatialReference.png b/dist/schema/img/eml-spatialVector_xsd_Element_spatialReference.png
index 3737f382..e671e317 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_spatialReference.png and b/dist/schema/img/eml-spatialVector_xsd_Element_spatialReference.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_spatialVector.png b/dist/schema/img/eml-spatialVector_xsd_Element_spatialVector.png
index 98eba3e7..77d5a1a6 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_spatialVector.png and b/dist/schema/img/eml-spatialVector_xsd_Element_spatialVector.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_topologyLevel.png b/dist/schema/img/eml-spatialVector_xsd_Element_topologyLevel.png
index ce06fd4a..c2d9fcd7 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_topologyLevel.png and b/dist/schema/img/eml-spatialVector_xsd_Element_topologyLevel.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Element_verticalAccuracy.png b/dist/schema/img/eml-spatialVector_xsd_Element_verticalAccuracy.png
index 935a6461..c4a42829 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Element_verticalAccuracy.png and b/dist/schema/img/eml-spatialVector_xsd_Element_verticalAccuracy.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Simple_Type_GeometryType.png b/dist/schema/img/eml-spatialVector_xsd_Simple_Type_GeometryType.png
index 488b6f9b..7c8a13c2 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Simple_Type_GeometryType.png and b/dist/schema/img/eml-spatialVector_xsd_Simple_Type_GeometryType.png differ
diff --git a/dist/schema/img/eml-spatialVector_xsd_Simple_Type_TopologyLevel.png b/dist/schema/img/eml-spatialVector_xsd_Simple_Type_TopologyLevel.png
index 41a31753..c37fa9ce 100644
Binary files a/dist/schema/img/eml-spatialVector_xsd_Simple_Type_TopologyLevel.png and b/dist/schema/img/eml-spatialVector_xsd_Simple_Type_TopologyLevel.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Complex_Type_ParameterType.png b/dist/schema/img/eml-storedProcedure_xsd_Complex_Type_ParameterType.png
index 3d898776..13f0f784 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Complex_Type_ParameterType.png and b/dist/schema/img/eml-storedProcedure_xsd_Complex_Type_ParameterType.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Complex_Type_StoredProcedureType.png b/dist/schema/img/eml-storedProcedure_xsd_Complex_Type_StoredProcedureType.png
index b41f0d3f..a83535f6 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Complex_Type_StoredProcedureType.png and b/dist/schema/img/eml-storedProcedure_xsd_Complex_Type_StoredProcedureType.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Element_attributeList.png b/dist/schema/img/eml-storedProcedure_xsd_Element_attributeList.png
index 9c6a98c6..66a27bd4 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Element_attributeList.png and b/dist/schema/img/eml-storedProcedure_xsd_Element_attributeList.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Element_constraint.png b/dist/schema/img/eml-storedProcedure_xsd_Element_constraint.png
index 53e6af35..4743f05b 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Element_constraint.png and b/dist/schema/img/eml-storedProcedure_xsd_Element_constraint.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Element_domainDescription.png b/dist/schema/img/eml-storedProcedure_xsd_Element_domainDescription.png
index e4bc3099..9a7de7e9 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Element_domainDescription.png and b/dist/schema/img/eml-storedProcedure_xsd_Element_domainDescription.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Element_name.png b/dist/schema/img/eml-storedProcedure_xsd_Element_name.png
index be34601e..139b9ebc 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Element_name.png and b/dist/schema/img/eml-storedProcedure_xsd_Element_name.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Element_parameter.png b/dist/schema/img/eml-storedProcedure_xsd_Element_parameter.png
index 40a6bd81..c3497b7c 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Element_parameter.png and b/dist/schema/img/eml-storedProcedure_xsd_Element_parameter.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Element_repeats.png b/dist/schema/img/eml-storedProcedure_xsd_Element_repeats.png
index 77d966e6..ea057b20 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Element_repeats.png and b/dist/schema/img/eml-storedProcedure_xsd_Element_repeats.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Element_required.png b/dist/schema/img/eml-storedProcedure_xsd_Element_required.png
index 9aee6292..07bbf6b3 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Element_required.png and b/dist/schema/img/eml-storedProcedure_xsd_Element_required.png differ
diff --git a/dist/schema/img/eml-storedProcedure_xsd_Element_storedProcedure.png b/dist/schema/img/eml-storedProcedure_xsd_Element_storedProcedure.png
index 19d0f6b7..a36661ed 100644
Binary files a/dist/schema/img/eml-storedProcedure_xsd_Element_storedProcedure.png and b/dist/schema/img/eml-storedProcedure_xsd_Element_storedProcedure.png differ
diff --git a/dist/schema/img/eml-text_xsd_Complex_Type_ListType.png b/dist/schema/img/eml-text_xsd_Complex_Type_ListType.png
index bcf23cb3..151697c2 100644
Binary files a/dist/schema/img/eml-text_xsd_Complex_Type_ListType.png and b/dist/schema/img/eml-text_xsd_Complex_Type_ListType.png differ
diff --git a/dist/schema/img/eml-text_xsd_Complex_Type_ParagraphType.png b/dist/schema/img/eml-text_xsd_Complex_Type_ParagraphType.png
index d7d03056..41024439 100644
Binary files a/dist/schema/img/eml-text_xsd_Complex_Type_ParagraphType.png and b/dist/schema/img/eml-text_xsd_Complex_Type_ParagraphType.png differ
diff --git a/dist/schema/img/eml-text_xsd_Complex_Type_SectionType.png b/dist/schema/img/eml-text_xsd_Complex_Type_SectionType.png
index 5f1452cf..98257736 100644
Binary files a/dist/schema/img/eml-text_xsd_Complex_Type_SectionType.png and b/dist/schema/img/eml-text_xsd_Complex_Type_SectionType.png differ
diff --git a/dist/schema/img/eml-text_xsd_Complex_Type_SubSuperScriptType.png b/dist/schema/img/eml-text_xsd_Complex_Type_SubSuperScriptType.png
index 065edb87..4285308d 100644
Binary files a/dist/schema/img/eml-text_xsd_Complex_Type_SubSuperScriptType.png and b/dist/schema/img/eml-text_xsd_Complex_Type_SubSuperScriptType.png differ
diff --git a/dist/schema/img/eml-text_xsd_Complex_Type_TextType.png b/dist/schema/img/eml-text_xsd_Complex_Type_TextType.png
index cd459b2f..d8300481 100644
Binary files a/dist/schema/img/eml-text_xsd_Complex_Type_TextType.png and b/dist/schema/img/eml-text_xsd_Complex_Type_TextType.png differ
diff --git a/dist/schema/img/eml-text_xsd_Complex_Type_i18nString.png b/dist/schema/img/eml-text_xsd_Complex_Type_i18nString.png
index 47898998..caee53ed 100644
Binary files a/dist/schema/img/eml-text_xsd_Complex_Type_i18nString.png and b/dist/schema/img/eml-text_xsd_Complex_Type_i18nString.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_citetitle.png b/dist/schema/img/eml-text_xsd_Element_citetitle.png
index 694bd304..b53ac25f 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_citetitle.png and b/dist/schema/img/eml-text_xsd_Element_citetitle.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_emphasis.png b/dist/schema/img/eml-text_xsd_Element_emphasis.png
index 2eb2f758..63c8ac8d 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_emphasis.png and b/dist/schema/img/eml-text_xsd_Element_emphasis.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_itemizedlist.png b/dist/schema/img/eml-text_xsd_Element_itemizedlist.png
index e4ffcf00..0112c26e 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_itemizedlist.png and b/dist/schema/img/eml-text_xsd_Element_itemizedlist.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_itemizedlist_1.png b/dist/schema/img/eml-text_xsd_Element_itemizedlist_1.png
index e4ffcf00..0112c26e 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_itemizedlist_1.png and b/dist/schema/img/eml-text_xsd_Element_itemizedlist_1.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_listitem.png b/dist/schema/img/eml-text_xsd_Element_listitem.png
index dea62d99..837de279 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_listitem.png and b/dist/schema/img/eml-text_xsd_Element_listitem.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_literalLayout.png b/dist/schema/img/eml-text_xsd_Element_literalLayout.png
index 63799034..2c9d4288 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_literalLayout.png and b/dist/schema/img/eml-text_xsd_Element_literalLayout.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_markdown.png b/dist/schema/img/eml-text_xsd_Element_markdown.png
index fe56223d..69111305 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_markdown.png and b/dist/schema/img/eml-text_xsd_Element_markdown.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_orderedlist.png b/dist/schema/img/eml-text_xsd_Element_orderedlist.png
index 134d7578..44de9614 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_orderedlist.png and b/dist/schema/img/eml-text_xsd_Element_orderedlist.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_orderedlist_1.png b/dist/schema/img/eml-text_xsd_Element_orderedlist_1.png
index 134d7578..44de9614 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_orderedlist_1.png and b/dist/schema/img/eml-text_xsd_Element_orderedlist_1.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_para.png b/dist/schema/img/eml-text_xsd_Element_para.png
index 600b15af..ef91affa 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_para.png and b/dist/schema/img/eml-text_xsd_Element_para.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_para_1.png b/dist/schema/img/eml-text_xsd_Element_para_1.png
index 600b15af..ef91affa 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_para_1.png and b/dist/schema/img/eml-text_xsd_Element_para_1.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_para_2.png b/dist/schema/img/eml-text_xsd_Element_para_2.png
index 11681214..76b41cf0 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_para_2.png and b/dist/schema/img/eml-text_xsd_Element_para_2.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_section.png b/dist/schema/img/eml-text_xsd_Element_section.png
index 73ee40c5..a7f536a9 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_section.png and b/dist/schema/img/eml-text_xsd_Element_section.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_section_1.png b/dist/schema/img/eml-text_xsd_Element_section_1.png
index 49428107..aa70f7b5 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_section_1.png and b/dist/schema/img/eml-text_xsd_Element_section_1.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_subscript.png b/dist/schema/img/eml-text_xsd_Element_subscript.png
index 8cc08416..9a9bfb9b 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_subscript.png and b/dist/schema/img/eml-text_xsd_Element_subscript.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_subscript_1.png b/dist/schema/img/eml-text_xsd_Element_subscript_1.png
index 7b7fc6b4..194b1856 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_subscript_1.png and b/dist/schema/img/eml-text_xsd_Element_subscript_1.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_superscript.png b/dist/schema/img/eml-text_xsd_Element_superscript.png
index d48686e3..7efe862e 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_superscript.png and b/dist/schema/img/eml-text_xsd_Element_superscript.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_superscript_1.png b/dist/schema/img/eml-text_xsd_Element_superscript_1.png
index 8bc58f39..5e6e048e 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_superscript_1.png and b/dist/schema/img/eml-text_xsd_Element_superscript_1.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_text.png b/dist/schema/img/eml-text_xsd_Element_text.png
index e93800f3..3ed8f79d 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_text.png and b/dist/schema/img/eml-text_xsd_Element_text.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_title.png b/dist/schema/img/eml-text_xsd_Element_title.png
index 7646967d..05f502c1 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_title.png and b/dist/schema/img/eml-text_xsd_Element_title.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_ulink.png b/dist/schema/img/eml-text_xsd_Element_ulink.png
index 591292e2..c1411fe5 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_ulink.png and b/dist/schema/img/eml-text_xsd_Element_ulink.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_value.png b/dist/schema/img/eml-text_xsd_Element_value.png
index 3846e2a2..80053cf5 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_value.png and b/dist/schema/img/eml-text_xsd_Element_value.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_value_1.png b/dist/schema/img/eml-text_xsd_Element_value_1.png
index c2a65d4b..3922123b 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_value_1.png and b/dist/schema/img/eml-text_xsd_Element_value_1.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_value_2.png b/dist/schema/img/eml-text_xsd_Element_value_2.png
index 378549ef..7b4d2f2a 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_value_2.png and b/dist/schema/img/eml-text_xsd_Element_value_2.png differ
diff --git a/dist/schema/img/eml-text_xsd_Element_value_3.png b/dist/schema/img/eml-text_xsd_Element_value_3.png
index c2a65d4b..3922123b 100644
Binary files a/dist/schema/img/eml-text_xsd_Element_value_3.png and b/dist/schema/img/eml-text_xsd_Element_value_3.png differ
diff --git a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_LengthUnitType.png b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_LengthUnitType.png
index fef236e9..8933614e 100644
Binary files a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_LengthUnitType.png and b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_LengthUnitType.png differ
diff --git a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_MassUnitType.png b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_MassUnitType.png
index 2b3e6847..22ab10b0 100644
Binary files a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_MassUnitType.png and b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_MassUnitType.png differ
diff --git a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_StandardUnitDictionary.png b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_StandardUnitDictionary.png
index f086015b..4b870ac0 100644
Binary files a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_StandardUnitDictionary.png and b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_StandardUnitDictionary.png differ
diff --git a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_angleUnitType.png b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_angleUnitType.png
index 01aecd45..b24b8a17 100644
Binary files a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_angleUnitType.png and b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_angleUnitType.png differ
diff --git a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_otherUnitType.png b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_otherUnitType.png
index 83ccbe9c..b6e830be 100644
Binary files a/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_otherUnitType.png and b/dist/schema/img/eml-unitTypeDefinitions_xsd_Simple_Type_unit_otherUnitType.png differ
diff --git a/dist/schema/img/eml-view_xsd_Complex_Type_ViewType.png b/dist/schema/img/eml-view_xsd_Complex_Type_ViewType.png
index 02392e5c..131e7434 100644
Binary files a/dist/schema/img/eml-view_xsd_Complex_Type_ViewType.png and b/dist/schema/img/eml-view_xsd_Complex_Type_ViewType.png differ
diff --git a/dist/schema/img/eml-view_xsd_Element_attributeList.png b/dist/schema/img/eml-view_xsd_Element_attributeList.png
index 9c6a98c6..66a27bd4 100644
Binary files a/dist/schema/img/eml-view_xsd_Element_attributeList.png and b/dist/schema/img/eml-view_xsd_Element_attributeList.png differ
diff --git a/dist/schema/img/eml-view_xsd_Element_constraint.png b/dist/schema/img/eml-view_xsd_Element_constraint.png
index 53e6af35..4743f05b 100644
Binary files a/dist/schema/img/eml-view_xsd_Element_constraint.png and b/dist/schema/img/eml-view_xsd_Element_constraint.png differ
diff --git a/dist/schema/img/eml-view_xsd_Element_queryStatement.png b/dist/schema/img/eml-view_xsd_Element_queryStatement.png
index 56629dda..28dd2b84 100644
Binary files a/dist/schema/img/eml-view_xsd_Element_queryStatement.png and b/dist/schema/img/eml-view_xsd_Element_queryStatement.png differ
diff --git a/dist/schema/img/eml-view_xsd_Element_view.png b/dist/schema/img/eml-view_xsd_Element_view.png
index ed9ff0a1..36f611ac 100644
Binary files a/dist/schema/img/eml-view_xsd_Element_view.png and b/dist/schema/img/eml-view_xsd_Element_view.png differ
diff --git a/dist/schema/img/eml_xsd_Element_access.png b/dist/schema/img/eml_xsd_Element_access.png
index d226b2d6..5619b53b 100644
Binary files a/dist/schema/img/eml_xsd_Element_access.png and b/dist/schema/img/eml_xsd_Element_access.png differ
diff --git a/dist/schema/img/eml_xsd_Element_additionalMetadata.png b/dist/schema/img/eml_xsd_Element_additionalMetadata.png
index 7cb491b1..59ddaae6 100644
Binary files a/dist/schema/img/eml_xsd_Element_additionalMetadata.png and b/dist/schema/img/eml_xsd_Element_additionalMetadata.png differ
diff --git a/dist/schema/img/eml_xsd_Element_annotation.png b/dist/schema/img/eml_xsd_Element_annotation.png
index 74c6f537..33d1b281 100644
Binary files a/dist/schema/img/eml_xsd_Element_annotation.png and b/dist/schema/img/eml_xsd_Element_annotation.png differ
diff --git a/dist/schema/img/eml_xsd_Element_annotations.png b/dist/schema/img/eml_xsd_Element_annotations.png
index f699afd9..18e7f8ef 100644
Binary files a/dist/schema/img/eml_xsd_Element_annotations.png and b/dist/schema/img/eml_xsd_Element_annotations.png differ
diff --git a/dist/schema/img/eml_xsd_Element_citation.png b/dist/schema/img/eml_xsd_Element_citation.png
index cd289f07..f42bf541 100644
Binary files a/dist/schema/img/eml_xsd_Element_citation.png and b/dist/schema/img/eml_xsd_Element_citation.png differ
diff --git a/dist/schema/img/eml_xsd_Element_dataset.png b/dist/schema/img/eml_xsd_Element_dataset.png
index 67ab30c0..f4d35f20 100644
Binary files a/dist/schema/img/eml_xsd_Element_dataset.png and b/dist/schema/img/eml_xsd_Element_dataset.png differ
diff --git a/dist/schema/img/eml_xsd_Element_describes.png b/dist/schema/img/eml_xsd_Element_describes.png
index 0a788180..cd3c3eb7 100644
Binary files a/dist/schema/img/eml_xsd_Element_describes.png and b/dist/schema/img/eml_xsd_Element_describes.png differ
diff --git a/dist/schema/img/eml_xsd_Element_eml.png b/dist/schema/img/eml_xsd_Element_eml.png
index a490773b..46dfd384 100644
Binary files a/dist/schema/img/eml_xsd_Element_eml.png and b/dist/schema/img/eml_xsd_Element_eml.png differ
diff --git a/dist/schema/img/eml_xsd_Element_metadata.png b/dist/schema/img/eml_xsd_Element_metadata.png
index 3f1ace44..832e2e5c 100644
Binary files a/dist/schema/img/eml_xsd_Element_metadata.png and b/dist/schema/img/eml_xsd_Element_metadata.png differ
diff --git a/dist/schema/img/eml_xsd_Element_protocol.png b/dist/schema/img/eml_xsd_Element_protocol.png
index 240d0e8f..ed8573a2 100644
Binary files a/dist/schema/img/eml_xsd_Element_protocol.png and b/dist/schema/img/eml_xsd_Element_protocol.png differ
diff --git a/dist/schema/img/eml_xsd_Element_software.png b/dist/schema/img/eml_xsd_Element_software.png
index 23922f3d..d97fad40 100644
Binary files a/dist/schema/img/eml_xsd_Element_software.png and b/dist/schema/img/eml_xsd_Element_software.png differ
diff --git a/dist/schema/index.indexList.html b/dist/schema/index.indexList.html
index 9cd8290a..8eec61f0 100644
--- a/dist/schema/index.indexList.html
+++ b/dist/schema/index.indexList.html
@@ -313,6 +313,58 @@
