true: strongly encouraged; false: discouraged in favor of atomized content For property lists in defined schemas Generic user defined classification scheme @@@Meant as a simple extension mechanism for lists given as an enumeration. Applications are not guaranteed to be able to parse this list, or even resolve it. But if they can, it is required that that searches and comparisons and other TAPIR stuff against these and the original enumeration should work... If true, this PV pair applies to the current element for which a DefinedSchema is offered. It is application dependent what to do about this. contains a mandatory attribute telling this is recommended element The provider of the object to which this Source is associated One of Agent or Publication is required The person or agency that provided this object, and an assertion about its origin A publication which the provider of this object asserts as the source of the data in the object The optional date at which this data was provided GISIN encourages a text entry here GISIN discourages a text entry here, usually because it is also atomized For the DiscouragedText type, this attribute is set false. if this attribute is set true, GISIN strongly encourages the use of this element. If it is set talse, GISIN discourage the use of this element in favor of atomized content. If you can find terms or elements and their enumerations within the schema that allow you to present some or all of your free text information, it is better to do that so that many different applications can make use of your information and compare to that of others. LSID type. @@@Should have a Pattern? Oct 25 2006: this is likely to be just LSID since that is now TDWG standard. That entails GISIN(?) operating an LSID issuance and resolution service, unless TDWG operates generic services Linkage to TCS data with some minimal local caching. Note that source dbs containing detailed and authoritative taxonomic data should share that data via the TaxonConceptSchema.;...@@Should we use dc:HigherLevelTaxon??...ram, mjb The GUID of the taxon concept - even if nominal concept - within an akcknowldeged taxon name catalogue - the ECATGUID (superset of ITIS/COL/Species2000/GSD/RSD s) Critical to capture these data from IAS dbs; @@@consider a defined schema here also... ram 19aug 2006 who or what is the source of the name of this taxon. See Enumeration @@@See Agadir minutes either "increasing" or "decreasing" Enumerated time units A numeric quantity expressed as a decimal number. Fractional part is optional. If optional unitTime attribute is provided, the quantity is increasing or decreasing, depending on the value of @change, which must be "increasing" or "decreasing". units Enumerated length units A length with mandatory units from enumeration in attribute group "Unit of length and an optional measure of time to express rate of increase/decrase An area or change of area (depending on whether optional @change is given (restricted to "increasing" or "decreasing" A range of areas, optionally over time. Requires units attribute taken from the AreaUnits/units attribute enumeration. Examples: codes "area 15000 - 30000 hectares" 15000 300000 or 15000-30000 hectares per year" Measure of mass, with mandatory enumerated units, and optional measure of time to denote change in mass A range of volumesoptionally over time. Requires units attribute taken from the VolumeUnits/units attribute enumeration. An instance identifier identifies a specific representation. This value is used when referencing an object (using 'ref'-attributes). It may be a value unique only within a dataset and derived object type, or within elements of the dataset, or a global id such as a uri. ID for internal cross-referencing within document, unique only within object-type. This is non-persistent data: consuming applications may discard or rewrite values after resolving all references to it. Debuglabel is intended to simplify debugging by adding a human-readable equivalent to the primary identity value. Values may be discarded or updated at any time and should not normally be included in exports by applications; they may be generated using xslt (based on labels, abbreviations, xpath+label, etc.). General Note: The use of attribute groups instead of globally defined and referred attributes is a work-around for problems occurring with attribute definitions in included library schemata. Normally one would use global attributes by ref; this however causes problems when attempting to use a library with no target namespace in multiple namespaces (chameleon pattern). Spy 2004.4 says, e. g., "... attributes need to be qualified because your schema uses attributeForm = qualified or global attributes. You must specify a prefix for your schema namespace." --- Local (referring to id) or uri-based attribute groups used for referencing: Refers to an id attribute in an instance of the corresponding object type. Existence of referenced object within xml document is usually guaranteed by identity constraints (= referential integrity). Debuglabel is intended to simplify debugging by adding a human-readable equivalent to the ref value. Values would normally be those from the corresponding debugkey. They may be discarded or updated at any time and should not normally be included in exports by applications. Refers to an id attribute in an instance of the corresponding object type. Existence of referenced object within xml document is usually guaranteed by identity constraints (= referential integrity). Debuglabel is intended to simplify debugging by adding a human-readable equivalent to the ref value. Values would normally be those from the corresponding debugkey. They may be discarded or updated at any time and should not normally be included in exports by applications. -- URI references: URIs are primarily identifiers; they may - but are not required to - allow data retrieval. URIs should not change. Recommended URI schemata for linking to related objects or abstract/ conceptual objects (like character concepts) are: 1) Conventional URLs (persistent URLs = purls are recommended). URLs may be a query like "http://x.y.fr/p/au=smith?yr=1998". 2) DOI, digital object identifier (used by the publishing industry). Example: doi:10.47198/923347' 3) Perhaps also LSID. Ideally, URIs should remain unchanged to enable data comparisons. Social reasons may prevent this, especially where authors working at organisation are not allowed to use the organisations DNS address after they stop working there. Other options (sci. societies, GBIF) should then be investigated. Further, the path within the URI of the organisation should be constructed so that uniqueness can be expected for social reasons, especially by including a personal or team-name. Example: http://xyz.de/g.hage/ coelomycetes, but not. xyz.de/plants. Resource media type (MIME, "text/html", "image/png", etc.). Compare www.w3.org/TR/xml-media-type. External reference using a retrievable uri (url, doi, lsid, etc.) (~=html and atom: link/@href) If href attribute is used, this preserves a short human readable text, capturing the semantics of the href uri reference (which may be temporarily or permanently not resolvable). In some contexts, this may be required through external validation If href is used. Media type of object to which href is pointing, e. g., text/html, application/rss+xml. etc. (~= html and atom:link/@type) External reference using a uri (url, doi, lsid, etc.) If href attribute is used, this preserves a short human-readable text, capturing the semantics of the uri reference (uri may be temporarily or permanently not resolvable). (Using 'label' as attribute name was rejected because unrelated to xlink:label!) Media type of object to which href is pointing, e. g., text/html, application/rss+xml. etc. (~= html and atom:link/@type) === References to objects should use either the ref (pointer to an id in same document) or href (= pointer to a uri) attribute. The name of element name should differ from the object name, to allow designs that offer a choice of providing a full object or an object reference (xml schema can not use different attributes content to detect the type!) Base type for all reference types (derived by restriction) Local, within-document reference. A required human readable string (label, title, name) as free-format, long-length string in the attribute 'literal'; plus optional local ref / global href attributes. Used where strings/names are often ambiguous, but may occasionally be identified as an object (e.g. publication, genus names, or taxon authors). Whereas the label attribute contains a label (= name, title) of the resource referenced by href, literal contains an unchanging literal text that is interpreted or explained by the href. Example: an author may be given in the publication as "L. Smith", the href may point to http/x.y.net/au/l-n-smith-NY, and the label of this agent/person object may be "Dr. L. N. Smith (New York)". Similar cases of literla plus optional href/label occur for publication citations or taxon names. A required human readable string (label, title, name) as free-format, limited-length string in the attribute 'literal'; plus optional local ref / global href attributes. Like Like AbstractLongStringPlusRef, except that the literal may only be a ShortString. Whereas the label attribute contains a label (= name, title) of the resource referenced by href, literal contains an unchanging literal text that is interpreted or explained by the href. Example: an author may be given in the publication as "L. Smith", the href may point to http/x.y.net/au/l-n-smith-NY, and the label of this agent/person object may be "Dr. L. N. Smith (New York)". Similar cases of literla plus optional href/label occur for publication citations or taxon names. Global href reference to a URI (used in derivations for specific resources types but also directly, i.e. non-abstract). External reference using a retrievable uri (url, doi, lsid, etc.) (~=html and atom: link/@href) -- derived types based on URIRef These types are used by id/ref attributes. The use of a type derivation allows to redefine the value type throughout the schema. Currently we decide to use document-wide IDs, but initial designs called only for within-object class identifiers (similar to database primary keys). Even with document-wide IDs, the standard version of the schema uses NCName as base type. Software designers using xslt may whish to change this to xs:ID and xs:IDREF in a local version of their schema to simplify the use of xslt (e.g. id() and idref() functions). However, using IDREF in the primary schema version would prevent using the schema for object or fragment interchange (the xs:IDREF values would always require a corresponding xs:ID value in the same document). Invasion vector. See enumeration