UBIF Reduced xml schema version 1.0 (beta 18)

This documentation is based on html code and graphics generated by the XML Spy schema editor (http://www.altova.com). It has been slightly modified by G. Hagedorn to make it more compact and readable. This is one of several available schema documentations; see the "Overview of available documentation" for further information.

Note that all diagram are hyperlinked; you can click on the symbols to explore elements or types. Use the "back"-button of your browser to return to the previous position. Please read Schema design modeling symbols for explanations of the symbols used in the schema diagrams!

element Datasets

diagram
properties	content  complex
annotation	documentation  Root element for files or data streams. Multiple Dataset objects are completely independent. Potential relationship may be detected by the consumer, but are not expressed in the UBIF format. The sequence of Dataset objects has no semantics and does not have to be preserved. The version of the UBIF standard used is defined in the namespace declaration and needs no separate data element.

element Datasets/Dataset

diagram
properties	isRef  0 content  complex
annotation	documentation  A single file or data stream may consist of multiple data sets

element Datasets/Dataset/Derivation

diagram
type	DerivationMetadata
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation datetime xs:dateTime required documentation  [ATTR: datetime] When did it occur? Date and time (UTC or local time with timezone information) at which the current document or data stream was created by the generator. Using UTC (Universal time coordinates = Greenwich mean time) is recommended. gooduntil xs:dateTime optional documentation  The data in this Dataset are guaranteed not to change until this date. No guarantee is given after this date and a cache should be refreshed. If the provider cannot guarantee that the data will not be changed until a future date, this attribute should be omitted.
annotation	documentation  A history (tree) of all automatic or semi-automatic data derivations (transformations) through computer programs: database export, filtering, merging, or unmodified data provision through portals. The elements immediately in this element describe the process that created the current xml document. [ATTR: datetime (= When was it done?), gooduntil (= caching interval)]

element Datasets/Dataset/ExternalDataInterface

diagram
type	ExternalDataInterface
properties	isRef  0 content  complex
annotation	documentation  Data from other knowledge domains to which the data set refers may be represented by collections of proxy data objects. In the absence of available external databases a proxy object may be used as a local placeholder. The data inside the proxy object usually provide a reduced interface data model that abstracts from a potentially more complex external data model. Examples: persons, publications, geographical localities, media resources, but also class names (biology: taxa) and objects/units (biology: specimens).

element Datasets/Dataset/Metadata

diagram
type	ContentMetadata
properties	isRef  0 content  complex
annotation	documentation  Metadata referring to the principal source of the entire data collection (the metadata scope may be wider than the objects actually contained in the data set).

group AgentInterface

diagram
used by	complexType  AgentProxy
annotation	documentation  Extensions of ProxyBase specific to AgentProxy

element AgentInterface/Organisation

diagram
properties	isRef  0 content  complex
annotation	documentation  (Mostly vCard:Org)

element AgentInterface/Organisation/Name

diagram
type	Label
properties	isRef  0 content  complex
annotation	documentation  Full organization or corporate name in multiple languages (en: 'Botanical Garden of ...', de: 'Botanischer Garten von ...'). (vCard:Org.OrgName) The standard Label mechanism also supports acronyms/abbreviations (no vCard equivalent!). For collections, the organisation abbreviation maps to Darwin Core 2: Institution Code.

element AgentInterface/Organisation/Units

diagram
properties	isRef  0 content  complex
annotation	documentation  If Agent contains no person definition: the unit within the organization the agent represents, else a list of the various organisational units to which a person may belong. (vCard:OrgUnit)

element AgentInterface/Organisation/Units/Unit

diagram
type	StringL
properties	isRef  0 content  complex
facets	minLength  1 whiteSpace  collapse
attributes	Name Type Use Default Fixed Annotation language Language optional documentation  Attribute for Language, used by-reference
annotation	documentation  (vCard:OrgUnit)

element AgentInterface/Person

diagram
properties	isRef  0 content  complex
annotation	documentation  (There is no equivalent to vCard:FN/full name here, this is already covered by proxy Label above). For the problems involved in atomizing names from different cultures compare http://dublincore.org/documents/1998/ 02/03/name-representation/ See also http://efgblade.cs.umb.edu/twiki/bin/ view/SDD/ProxyDataAgentProxy on our own WIKI.

element AgentInterface/Person/SortingName

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  The full name in preferred sorting sequence, i. e. with main name first. Use case: sorting, reporting in sorted lists. Examples: 'Duarte, Amália Mourinha' (pt), 'Pina de Morales, Ana Maria' (es). (vCard:Sort-String)

element AgentInterface/Person/Title

diagram
type	Label
properties	isRef  0 content  complex
annotation	documentation  Professional or academic title of individual person (prefer using Role for job titles!) (vCard:Title)

element AgentInterface/Person/Sex

diagram
type	BasicSexCodeEnum
properties	isRef  0 content  simple
facets	enumeration  M enumeration  F enumeration  U
annotation	documentation  Enumeration of male, female, unknown (vCard no equivalent)

element AgentInterface/Person/Birthdate

diagram
type	xs:dateTime
properties	isRef  0 content  simple
annotation	documentation  Birthday of person. (vCard:BDay, may include time)

element AgentInterface/Person/Deathdate

diagram
type	xs:dateTime
properties	isRef  0 content  simple
annotation	documentation  Death date of a deceased person. (vCard: not surprisingly no equivalent)

element AgentInterface/Software

diagram
properties	isRef  0 content  complex
annotation	documentation  (Software agents are not handled by vCard!)

element AgentInterface/Software/Name

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  (Software agents probably need to be extended in future versions.)

element AgentInterface/Role

diagram
type	Label
properties	isRef  0 content  complex
annotation	documentation  Role of Person or Organization in context. This element can be used to provide a title such as "Database Administrator" or "Curator" even when no individual person is named. (vCard:Role)

element AgentInterface/Contact

diagram
properties	isRef  0 content  complex
annotation	documentation  @@Note gh: I see a problem with the unparsed address proposals in the original ABCD model and in two of the alternatives presented here, in that the Label for the Agent often requires the addition of city/country to disambiguate multiple agents with the same name

element AgentInterface/Contact/Addresses

diagram
properties	isRef  0 content  complex
annotation	documentation  (vCard:Adr)

element AgentInterface/Contact/Telephones

diagram
properties	isRef  0 content  complex
annotation	documentation  Telephone/fax/modem numbers (vCard:Tel)

element AgentInterface/Contact/Telephones/Telephone

diagram
type	TelephoneNumber
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation number String255 required documentation  Numbers should be provided in the ITU Recommendation E.164 international format ("+CountryCode AreaCode Number"). devicetype TelephoneDeviceEnum optional documentation  Note that telephone device types are not necessarily exclusive (voice/fax, mobile/modem, etc.) and vCard 3.0 allows multiple for a single number. However, in UBIF this can be represented by adding a single number multiple times for each device type. This attribute should not have a default value voice, even though this is the most likely case. However, an exporting database may not have properly reported the type, or the type may be indicated only in the usage note. usagenote String255 optional documentation  Free-form text for constraints on use e. g. "weekdays only" or "home number" (partly: vCard:Home/Work flags) preferred xs:boolean optional false documentation  Elements with preferred = true indicate recommendation by the data provider. The consumer may have reasons to make a different choice.
annotation	documentation  [ATTR: number = should be provided in the ITU Recommendation E.164 international format ("+CountryCode AreaCode Number") (vCard:Tel.Number) ATTR: devicetype = voice, fax, mobile, pager, modem (identical with vCard:Tel.Voice etc.; if several are on a single phone number list the phone number with each device type!) ATTR: usagenote = free-form text for constraints on use e. g. "weekdays only" or "home number" (partly: vCard:Tel.Home/Work flags) ATTR: preferred = preferred number, may occur multiple times for different device types (vCard:Tel.Pref)]

element AgentInterface/Contact/Emails

diagram
properties	isRef  0 content  complex
annotation	documentation  E-mail addresses (vCard:Email)

element AgentInterface/Contact/Emails/EmailAddress

diagram
type	StringP255
properties	isRef  0 content  complex
facets	minLength  1 maxLength  255 whiteSpace  collapse
attributes	Name Type Use Default Fixed Annotation preferred xs:boolean optional false documentation  Elements with preferred = true indicate recommendation by the data provider. The consumer may have reasons to make a different choice.
annotation	documentation  E-mail address for contact (vCard:Email.UserID; this also has Home/Work flags not supported here) [ATTR: preferred (vCard:Email.Pref)]

element AgentInterface/Contact/URIs

diagram
properties	isRef  0 content  complex
annotation	documentation  URI pointing to a homepage with further information. Note: If the Agent has a permanent URN representation, it is expected in ObjectLink in the base type. (vCard:URL, vCard supports only 1 URL)

element AgentInterface/Contact/URIs/URI

diagram
type	anyUriP
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation preferred xs:boolean optional false documentation  Elements with preferred = true indicate recommendation by the data provider. The consumer may have reasons to make a different choice.
annotation	documentation  URL for person or organization [ATTR: preferred]

element AgentInterface/LogoURL

diagram
type	xs:anyURI
properties	isRef  0 content  simple
annotation	documentation  URL of logo or icon image; usually of organization but may also be used by a person. (vCard:Logo) (Note: vCard:Note maps to Annotation in the base type!)

group ClassHierarchyInterface

diagram
used by	complexType  ClassHierarchyProxy
annotation	documentation  Extensions of ProxyBase specific to ClassHierarchyProxy

element ClassHierarchyInterface/IsPhylogenetic

diagram
type	xs:boolean
properties	isRef  0 content  simple
annotation	documentation  For example, SDD supports taxonomic (order/family/genus etc.) and non-taxonomic (weed species, diseases, herb/shrub/tree) hierarchies. For many analytical purposes it is relevant whether a hierarchy is based on phylogenetic (= evolutionary) relatedness or whether it is an operational categorization. Note: a conventional taxonomic hierarchy should be considered phylogenetic until proven to be not.

element ClassHierarchyInterface/Node

diagram
type	ClassHierarchyNode
properties	isRef  0 content  complex
annotation	documentation  Root of the recursive tree

group ClassNameInterface

diagram
used by	complexType  ClassNameProxy
annotation	documentation  Extensions of ProxyBase specific to ClassNameProxy

element ClassNameInterface/Rank

diagram
type	TaxonomicRankEnum
properties	isRef  0 content  simple
annotation	documentation  For biological taxonomic names: order, family, species, etc. Derived from an enumerated value list. This element needs to be interoperable; formatting often depends on specific ranks rather than on relative place in the hierarchy alone.

group ContactAddressProposal1

diagram
used by	element  AgentInterface/Contact/Addresses
annotation	documentation  ### To be decided!

element ContactAddressProposal1/Address

diagram
type	StringLP
properties	isRef  0 content  complex
facets	minLength  1 whiteSpace  collapse
attributes	Name Type Use Default Fixed Annotation language Language optional documentation  Attribute for Language, used by-reference preferred xs:boolean optional false documentation  Elements with preferred = true indicate recommendation by the data provider. The consumer may have reasons to make a different choice.
annotation	documentation  Contact address. Each element should be one address; do not use multiple elements for each line! (vCard:Adr.POBox + .ExtAdr + .Street + .Locality + .Region + .PCode + .Ctry) [ATTR: language, preferred (vCard:Pref)] @@vCard defines further attributes: Home/Work, Postal/Parcel, Dom/Intl Also, vCard atomizes the address, see proposal 2 below. Perhaps at least the country should be specified in ISO 2-letter codes?

group ContactAddressProposal2

diagram
used by	element  AgentInterface/Contact/Addresses
annotation	documentation  ### To be decided!

element ContactAddressProposal2/Address

diagram
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation language Language optional documentation  Attribute for Language, used by-reference preferred xs:boolean optional false documentation  Elements with preferred = true indicate recommendation by the data provider. The consumer may have reasons to make a different choice.
annotation	documentation  Contact address. (vCard:Adr.POBox + .ExtAdr + .Street + .Locality + .Region + .PCode + .Ctry) [ATTR: language, preferred (vCard:Pref)]

element ContactAddressProposal2/Address/Line

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  Address line

group ContactAddressProposal3

diagram
used by	element  AgentInterface/Contact/Addresses
annotation	documentation  ### To be decided!

element ContactAddressProposal3/POBox

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  (vCard:Adr.POBox)

element ContactAddressProposal3/ExtAdr

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  (vCard:Adr.ExtAdr)

element ContactAddressProposal3/Street

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  (vCard:Adr.Street)

element ContactAddressProposal3/Locality

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  (vCard:Adr.Locality)

element ContactAddressProposal3/Region

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  (vCard:Adr.Region)

element ContactAddressProposal3/PostalCode

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  (vCard:Adr.PCode)

element ContactAddressProposal3/Country

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  (vCard:Adr.Ctry)

group LocalityInterface

diagram
used by	complexType  LocalityProxy
annotation	documentation  Extensions of ProxyBase specific to LocalityProxy

element LocalityInterface/Coordinates

diagram
type	GeographicalCoordinates
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation latitude DecimalLatitude required longitude DecimalLongitude required documentation  Longitude is expressed from -180 to 180°, East longitude being plus and West longitude being minus. geodeticdatum String255 optional documentation  Where knowledge of the geodetic datum is readily available it should be passed on. However, in most situations no undue resources should be invested into researching the geodetic datum when this is unknown. Many geodetic datum systems result in differences only up to a 100 m, some up to several hundred meters. For many purposes in biodiversity sciences are acceptable. The 'World Geodetic System 1984 (WGS-84)' is the most commonly used geodetic datum. It is used, e. g., by the 'Global Positioning System (GPS)'. Other important systems are used (e. g., ITRF, ETRS89, NZGD2000, OSGB36, ED50, see also http://www.ncgia.ucsb.edu/education/curricula/giscc/units/u015/tables/table03.html or http://www.colorado.edu/geography/gcraft/notes/datum/edlist.html). The differences between WGS-84 and International Terrestrial Reference Frame (ITRF) are in the centimeter range worldwide, and ETRF 89 and NAD 83 are identical to WGS84 for Europe and North America, respectively. -- As an exception to what has been said above are historical coordinates (for most countries up to ca. 1900, much later for France) may be based on a prime meridian other than Greenwich/Airy (e. g., the NTF datum uses Paris as its prime meridian, 2.33723° east of Greenwich). verbatim String255 optional documentation  An uninterpreted text representation of the coordinate data (latitude/longitude, UTM, TRS, etc.), as close as possible to the (digital/printed/handwritten) information source.
annotation	documentation  Geographical coordinates (decimal longitude/latitude) of the location from which the object or observation was collected. Includes geodetic datum and an optional verbatim text representation.

group MeasurementUnitInterface

diagram
used by	complexType  MeasurementUnitProxy
annotation	documentation  Extensions of ProxyBase specific to MeasurementUnitProxy

element MeasurementUnitInterface/InternationalAbbreviation

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  A scientific abbreviation considered language and audience independent. It may contain formatting to express "mm<sup>2</sup>". Note that the Abbreviation element available in most label types does not support formatting!

element MeasurementUnitInterface/IsScientificUnit

diagram
type	xs:boolean
properties	isRef  0 content  simple
annotation	documentation  True if unit is SI unit or a derived unit acceptable in scientific publications. False for local/historical units like feet and velocity in fathoms per fortnight :-).

element MeasurementUnitInterface/IsPrefixUnit

diagram
type	xs:boolean
properties	isRef  0 content  simple default  false
annotation	documentation  True indicates that unit should be output before the value (as in 'pH 7.0'). Default is false.

element MeasurementUnitInterface/Relations

diagram
properties	isRef  0 content  complex
annotation	documentation  Describes relations to other units that can be expressed through a simple multiplication factor (i. e. not cubic meter = meter * meter * meter, or Celsius to Fahrenheit)

element MeasurementUnitInterface/Relations/Relation

diagram
properties	isRef  0 content  complex
annotation	documentation  @@ Do we really need multiple relations or is a single relation to the base unit sufficient? @@

element MeasurementUnitInterface/Relations/Relation/RelatedUnit

diagram
type	MeasurementUnitRef
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation ref required
annotation	documentation  Ideally the relation should always be defined towards the base unit, e. g., km, cm, mm, µm all to meter.

element MeasurementUnitInterface/Relations/Relation/Factor

diagram
type	xs:double
properties	isRef  0 content  simple
annotation	documentation  Multiply current unit with this factor to obtain related unit referenced above.

group MediaResourceInterface

diagram
used by	complexType  MediaResourceProxy
annotation	documentation  Extensions of ProxyBase specific to MediaResourceProxy

element MediaResourceInterface/Type

diagram
type	ResourceTypeEnum
properties	isRef  0 content  simple
facets	enumeration  Collection enumeration  Dataset enumeration  Event enumeration  Image enumeration  InteractiveResource enumeration  MovingImage enumeration  PhysicalObject enumeration  Service enumeration  Software enumeration  Sound enumeration  StillImage enumeration  Text enumeration  Other
annotation	documentation  Type of medium, based on DCMI Type vocabulary (= DC.Type)

element MediaResourceInterface/Caption

diagram
type	Label
properties	isRef  0 content  complex
annotation	documentation  An optional caption for a resource, esp. if it will be presented embedded in another document. Captions can be provided in multiple languages. Differs from the resource Label, wihich is closer related to a 'title'. @@ Issue: captions, even in multiple languages, may be obtained from the service provider. Even then it may be desirable to override them! Do we need two collections: InheritedCaption and CaptionOverride? This seems to be awkward whenever there is no ServiceProvider! Also, Label can contain a "title" only in a single language! @@

element MediaResourceInterface/RevisionData

diagram
type	RevisionData
properties	isRef  0 content  complex
annotation	documentation  Creators, Revision status, and dates for the media resource

element MediaResourceInterface/Owners

diagram
type	OwnerRefs
properties	isRef  0 content  complex
annotation	documentation  Entities having legal possession of the data collection content. Owners are defined only for the entire data collection, not for individual descriptions etc. (= http://www.loc.gov/ marc.relators/own)

element MediaResourceInterface/IPRStatements

diagram
properties	isRef  0 content  complex
annotation	documentation  Copyright, terms of use, license and other IPR-related statements like disclaimer or acknowledgement. Giving a copyright statement and a (if possible public) licence is highly recommended! (=DC.Rights)

element MediaResourceInterface/IPRStatements/Representation

diagram
type	IPRStatementsRepr
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation language Language required documentation  Attribute for Language, used by-reference
annotation	documentation  [ATTR: language]

element MediaResourceInterface/EncodedData

diagram
type	xs:base64Binary
properties	isRef  0 content  simple
annotation	documentation  Optionally the full resource data may be embedded (as an alternative or in addition to defining a URI). Note: A resource like an image should be directly encoded, i.e. not wrapped into a MIME object first.

group MediaResources

diagram
annotation	documentation  [Not yet used] A media resource element embedded in a group is provided solely to allow reuse together with the necessary identity constraints for the ref attribute. Limitations of xml Schema prevent the definition of identity constraints on the MediaResourceReftype itself.

element MediaResources/MediaResource

diagram
type	MediaResourceRef
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation ref RelationID required
annotation	documentation  (the sequence in instances is informative!) [ATTR: ref]

group PersonNameProposal1

diagram
used by	element  AgentInterface/Person
annotation	documentation  ### To be decided!

element PersonNameProposal1/InheritedName

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  Family names, generational names, clan name, parents/grandparents personal names, etc. This (= last name in western cultures) may be compound ('Fischer von Waldheim', 'da Selva', 'Silvano Morales'). Depending on culture it is not necessarily the name of the parents nor common to the married couple and children, thus 'family name' should be avoided even though used in vCard. (vCard:N.Family)

element PersonNameProposal1/Prefix

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  Prefix to name that should be output before name, but is usually not included in sorting. Examples: 'Prof.', 'Dr.', 'von', 'Lord'. (vCard:N.Prefix)

element PersonNameProposal1/Suffix

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  Suffix to name that should be output after name, regardless whether it is in sorting sequence (Inherited, Given) or not. Examples: 'Jun.', 'III.'. (vCard:N.Suffix)

element PersonNameProposal1/GivenNames

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  The name given to a person as a personal name (= first or christian name in western cultures, including 'middle initials') may contain several words ('Ana Maria', 'Jerry B.'). Applicable only to persons. (vCard:N.Given + vCard:N.Middle)

element PersonNameProposal1/PreferredName

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  May differ from the first given name: second given name, nickname ('Bob' for 'Robert'), etc. (vCard:Nickname)

group PersonNameProposal2

diagram
used by	element  AgentInterface/Person
annotation	documentation  ### To be decided!

element PersonNameProposal2/FormalFullName

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  Preferred version of complete name in forward sequence as defined by the culture of the name-bearer. Use case: reporting. Examples: 'Maria Amália Mourinha Duarte' (pt), 'Ana Maria Pina de Morales' (es),

element PersonNameProposal2/InformalFullName

diagram
type	String255
properties	isRef  0 content  simple
facets	minLength  1 maxLength  255 whiteSpace  collapse
annotation	documentation  A version of the name in forward sequence used in informal usage. Use case: reporting. Example: 'Bob Morris' for 'Prof. Dr. Robert Morris', 'Amália Mourinha Duarte' (pt), 'Ana Pina de Morales' (es).

group PublicationInterface

diagram
used by	complexType  PublicationProxy
annotation	documentation  Extensions of ProxyBase specific to PublicationProxy

group PublicationInterface_LinnCore_DivWorkbenchProposal

diagram
used by	group  PublicationInterface
annotation	documentation  Extensions of ProxyBase specific to PublicationProxy

element PublicationInterface_LinnCore_DivWorkbenchProposal/Year

diagram
type	xs:gYear
properties	isRef  0 content  simple
annotation	documentation  Year as appearing on the publication. Compare TruePublicationDate below.

element PublicationInterface_LinnCore_DivWorkbenchProposal/TruePublicationDate

diagram
type	CompositeDate
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation year xs:integer optional documentation  The four digit year in the Gregorian calendar (in Western cultures usually without a suffix or with 'AD/Anno Domini', 'CE/Common Era'; negative years with 'BC/Before Christ', 'BCE/Before Common Era'). Whether a year 0 is used or not differs between a true Gregorian calendar and recent astronomic usage, xml schema is likely to change its position, see xml schema draft 1.1. Thus database designers should not use 0 as a missing value representation for year. month optional day optional documentation  two digit day supplement String255 optional documentation  Text in addition to or modifying the exact date components, e. g., 'end of summer', 'first half or year', 'first decade (of month)', '1888-1892'. verbatim String255 optional documentation  An uninterpreted text representation of the original date information (date range, 'summer', perhaps unreformed Russian dates, etc.); as close as possible to the (digital/printed/handwritten) information source. timezone optional documentation  Timezone expressed in minutes. In the seven property model (http://www.w3.org/TR/2004/WD-xmlschema11-2-20040716/#theSevenPropertyModel) the timezone has a range of +/- 14 hours (14 * 60 = 840 minutes).
annotation	documentation  Effective date of publication; may be different from year stated on/in the publication. Important for taxonomic or other priority. [ATTR: year (required), month, day (optional). Typed as gYear, gMonth, gDay; note that gMonth requires '01' instead of '1' for 'Jan.')

element PublicationInterface_LinnCore_DivWorkbenchProposal/Series

diagram
properties	isRef  0 content  complex
annotation	documentation  Series of books or articles (the latter may be published in edited books. journals, or on the web).

element PublicationInterface_LinnCore_DivWorkbenchProposal/Series/Title

diagram
type	TextWithTranslations
properties	isRef  0 content  complex
annotation	documentation  Series title

element PublicationInterface_LinnCore_DivWorkbenchProposal/Series/Editors

diagram
type	AgentNames
properties	isRef  0 content  complex
annotation	documentation  Series editors

element PublicationInterface_LinnCore_DivWorkbenchProposal/Book

diagram
properties	isRef  0 content  complex
annotation	documentation  Printed book: monograph or edited book with articles

element PublicationInterface_LinnCore_DivWorkbenchProposal/Book/Title

diagram
type	TextWithTranslations
properties	isRef  0 content  complex
annotation	documentation  Book title (monograph or edited book)

element PublicationInterface_LinnCore_DivWorkbenchProposal/Book/EditorsOrAuthors

diagram
type	AgentNames
properties	isRef  0 content  complex
annotation	documentation  Book creators are authors if Book is used alone or in combination with Series or Chapter, but editors if used in combination with article

element PublicationInterface_LinnCore_DivWorkbenchProposal/Book/VolPartInSeries

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Volume or part in a series

element PublicationInterface_LinnCore_DivWorkbenchProposal/Book/Pages

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Total range of pages, including foreword, appendices, index and plates/figures.

element PublicationInterface_LinnCore_DivWorkbenchProposal/Book/ISBN

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  International Standard Book Number

element PublicationInterface_LinnCore_DivWorkbenchProposal/Book/Edition

diagram
type	xs:positiveInteger
properties	isRef  0 content  simple
annotation	documentation  Number of the edition of a book.

element PublicationInterface_LinnCore_DivWorkbenchProposal/Book/ReprintData

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Publisher, reprint year, note, etc. for historical books that are reissued.

element PublicationInterface_LinnCore_DivWorkbenchProposal/Periodical

diagram
properties	isRef  0 content  complex
annotation	documentation  Periodical/magazine /journal information

element PublicationInterface_LinnCore_DivWorkbenchProposal/Periodical/Title

diagram
type	TextWithTranslations
properties	isRef  0 content  complex
annotation	documentation  We really need BPH and TL2 as standard dictionaries to drive these titles

element PublicationInterface_LinnCore_DivWorkbenchProposal/Periodical/AbbreviatedTitle

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Standardized abbreviated form of title

element PublicationInterface_LinnCore_DivWorkbenchProposal/Periodical/Publishers

diagram
type	xs:string
properties	isRef  0 content  simple

element PublicationInterface_LinnCore_DivWorkbenchProposal/Periodical/PublicationPlace

diagram
type	xs:string
properties	isRef  0 content  simple

element PublicationInterface_LinnCore_DivWorkbenchProposal/Periodical/ISSN

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  International Standard Serial Number

element PublicationInterface_LinnCore_DivWorkbenchProposal/Publishers

diagram
properties	isRef  0 content  complex
annotation	documentation  Publishers of a book, periodical, or independently published article.

element PublicationInterface_LinnCore_DivWorkbenchProposal/Publishers/Publisher

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  The name of the publisher (publishing company or institution, including universities or scientific societies).

element PublicationInterface_LinnCore_DivWorkbenchProposal/Publishers/PublicationPlace

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  The location where the item being referenced was published, such as a city and state.

element PublicationInterface_LinnCore_DivWorkbenchProposal/Article

diagram
properties	isRef  0 content  complex
annotation	documentation  Articles may, e. g., be published in periodicals, edited books, the internet.

element PublicationInterface_LinnCore_DivWorkbenchProposal/Article/Title

diagram
type	TextWithTranslations
properties	isRef  0 content  complex

element PublicationInterface_LinnCore_DivWorkbenchProposal/Article/Authors

diagram
type	AgentNames
properties	isRef  0 content  complex

element PublicationInterface_LinnCore_DivWorkbenchProposal/Article/PeriodicalVolume

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Volume of periodical (empty if article appears in edited book)

element PublicationInterface_LinnCore_DivWorkbenchProposal/Article/PeriodicalPart

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Part or issue of a periodical volume (empty if article appears in edited book)

element PublicationInterface_LinnCore_DivWorkbenchProposal/Article/Pages

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Pages of article. This may include table, or figure numbers for the reference. Examples: '23-41', '341 pp.', or '20, 22-24, 32' (for non-consecutive pages).

element PublicationInterface_LinnCore_DivWorkbenchProposal/Part

diagram
properties	isRef  0 content  complex
annotation	documentation  Optional information about a chapter, section, etc. that has the same authors as the publication in which it is contained. Compare Article for authored chapters in edited books.

element PublicationInterface_LinnCore_DivWorkbenchProposal/Part/Title

diagram
type	TextWithTranslations
properties	isRef  0 content  complex

element PublicationInterface_LinnCore_DivWorkbenchProposal/Part/Number

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Number of chapter, section, etc. as used in the publication.

element PublicationInterface_LinnCore_DivWorkbenchProposal/Part/Pages

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Pages of current part ('22-34')

group PublicationInterface_MinimizedProposal

diagram
used by	group  PublicationInterface
annotation	documentation  Extensions of ProxyBase specific to PublicationProxy

element PublicationInterface_MinimizedProposal/Creators

diagram
type	AgentNames
properties	isRef  0 content  complex
annotation	documentation  For article, chapter, or monographic book the authors, for an entire edited book the editors. The editors of the book in which an chapter appears are not listed here, but as part of the Source text string.

element PublicationInterface_MinimizedProposal/Title

diagram
type	TextWithTranslations
properties	isRef  0 content  complex
annotation	documentation  Title of the immediate publication (i.e. title of authored chapter, but not of source book or journal).

element PublicationInterface_MinimizedProposal/Year

diagram
type	xs:positiveInteger
properties	isRef  0 content  simple
annotation	documentation  Year as appearing on the publication. Compare TruePublicationDate below.

element PublicationInterface_MinimizedProposal/TruePublicationDate

diagram
type	CompositeDate
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation year xs:integer optional documentation  The four digit year in the Gregorian calendar (in Western cultures usually without a suffix or with 'AD/Anno Domini', 'CE/Common Era'; negative years with 'BC/Before Christ', 'BCE/Before Common Era'). Whether a year 0 is used or not differs between a true Gregorian calendar and recent astronomic usage, xml schema is likely to change its position, see xml schema draft 1.1. Thus database designers should not use 0 as a missing value representation for year. month optional day optional documentation  two digit day supplement String255 optional documentation  Text in addition to or modifying the exact date components, e. g., 'end of summer', 'first half or year', 'first decade (of month)', '1888-1892'. verbatim String255 optional documentation  An uninterpreted text representation of the original date information (date range, 'summer', perhaps unreformed Russian dates, etc.); as close as possible to the (digital/printed/handwritten) information source. timezone optional documentation  Timezone expressed in minutes. In the seven property model (http://www.w3.org/TR/2004/WD-xmlschema11-2-20040716/#theSevenPropertyModel) the timezone has a range of +/- 14 hours (14 * 60 = 840 minutes).
annotation	documentation  True date of publication, especially if different from stated year. Important for taxonomic or other priority.

element PublicationInterface_MinimizedProposal/Source

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  All remaining information, including Periodical/Volume for articles, or edited book for articles and chapters in a book, with the exceptions of the separate Pages (see below).

element PublicationInterface_MinimizedProposal/Pages

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  Pages of article. This may include table, or figure numbers for the reference. Examples: '23-41', '341 pp.', or '20, 22-24, 32' (for non-consecutive pages).

element PublicationInterface_MinimizedProposal/ISBN

diagram
type	xs:string
properties	isRef  0 content  simple
annotation	documentation  International Standard Book Number. @@Although this is an ideal key, this element may be dropped from the selective structure! Only very few references are covered by entire books with ISBN. Articles in journals are far more frequent and it would be more valuable to be better support those.

group UnitInterface

diagram
used by	complexType  UnitProxy
annotation	documentation  Extensions of ProxyBase specific to UnitProxy

element UnitInterface/ClassName

diagram
type	ClassRef
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation ref RelationID required documentation  Refers to a class name (biology = 'taxon'; ExternalDataInterface/ClassNames/ClassName)
annotation	documentation  Identification of specimen object. The information may come from the service provider. If the service provider only provides a name, this must be compared with and if necessary added to the list of ClassNames so that a ClassName reference may be used here. This may point to a higher taxon (family, order, or even "plantae") to indicate incomplete, broad identifications. [ATTR: ref]

element UnitInterface/IdentificationCertainty

diagram
type	IdentificationCertaintyEnum
properties	isRef  0 content  simple default  Certain
facets	enumeration  Certain enumeration  Uncertain enumeration  SimilarTo enumeration  Unknown
annotation	documentation  Default is 'certain'; 'Abies cf. alba' would be recorded as 'uncertain'.

element UnitInterface/IsPreservedInCollection

diagram
type	xs:boolean
properties	isRef  0 content  simple default  true
annotation	documentation  False = object has not been collected and preserved (it may still be databased in an observation database and have an ExternalID!). The default for this element is true, i. e. if the element is missing the object has been collected/preserved.

group UnitInterface_RoughProposalBasedOnDarwinCore

diagram
annotation	documentation  ### To be decided! Extensions of ProxyBase specific to UnitProxy

element UnitInterface_RoughProposalBasedOnDarwinCore/BasisOfRecord

diagram
type	String
properties	isRef  0 content  simple
facets	minLength  1 whiteSpace  collapse
annotation	documentation  A description indicating whether the record represents an object or observation (e.g., tissue sample, living organism, voucher specimen, germplasm/seed, genetic information, etc.)

element UnitInterface_RoughProposalBasedOnDarwinCore/InstitutionCode

diagram
type	String
properties	isRef  0 content  simple
facets	minLength  1 whiteSpace  collapse
annotation	documentation  The code (or acronym) identifying the institution administering the collection in which the object or observation record is cataloged. No global registry exists for institutional codes; use the code that is "standard" in your discipline. This attribute must contain no spaces.

element UnitInterface_RoughProposalBasedOnDarwinCore/CollectionCode

diagram
type	String
properties	isRef  0 content  simple
facets	minLength  1 whiteSpace  collapse
annotation	documentation  The code (or acronym) identifying the collection within the institution in which the object or observation record is cataloged. This attribute must contain no spaces.

element UnitInterface_RoughProposalBasedOnDarwinCore/CatalogNumberText

diagram
type	String
properties	isRef  0 content  simple
facets	minLength  1 whiteSpace  collapse
annotation	documentation  The alphanumeric value identifying an individual object or observation record within the collection. It is highly recommended that each record is uniquely identified within a collection by this value. It is also recommended that each record is universally uniquely identified by the combination of InstitutionCode, CollectionCode and CatalogNumberText.

element UnitInterface_RoughProposalBasedOnDarwinCore/Collector

diagram
properties	isRef  0 content  complex

element UnitInterface_RoughProposalBasedOnDarwinCore/Collector/Collectors

diagram
type	AgentNames
properties	isRef  0 content  complex
annotation	documentation  The name(s) of the collector(s) of the original data for the object or observation.

element UnitInterface_RoughProposalBasedOnDarwinCore/Collector/CollectionDate

diagram
type	CompositeDateTime
properties	isRef  0 content  complex
attributes	Name Type Use Default Fixed Annotation year xs:integer optional documentation  The four digit year in the Gregorian calendar (in Western cultures usually without a suffix or with 'AD/Anno Domini', 'CE/Common Era'; negative years with 'BC/Before Christ', 'BCE/Before Common Era'). Whether a year 0 is used or not differs between a true Gregorian calendar and recent astronomic usage, xml schema is likely to change its position, see xml schema draft 1.1. Thus database designers should not use 0 as a missing value representation for year. month optional day optional documentation  two digit day supplement String255 optional documentation  Text in addition to or modifying the exact date components, e. g., 'end of summer', 'first half or year', 'first decade (of month)', '1888-1892'. verbatim String255 optional documentation  An uninterpreted text representation of the original date information (date range, 'summer', perhaps unreformed Russian dates, etc.); as close as possible to the (digital/printed/handwritten) information source. timezone optional documentation  Timezone expressed in minutes. In the seven property model (http://www.w3.org/TR/2004/WD-xmlschema11-2-20040716/#theSevenPropertyModel) the timezone has a range of +/- 14 hours (14 * 60 = 840 minutes). hour optional minute optional second optional
annotation	documentation  Date in which the object or observation was collected from the field. Each part of the date may be missing. (= DarwinCore: YearCollected, MonthCollected, DayCollected, VerbatimCollectingDate) ATTR: year = four digit year; month = two digit month of year; day = two digit day of month