===== START of TaxonName-related identity constraints ==== ===== START of Location-related identity constraints ==== @@@See also ChecklistByTaxonType, which is not annotated as much. Should both be provided or should one be provided and XSLT spec'd to transform one to the other? That would be more robust against changes. BobMorris 22February2006 A globally unique identifier for the entire data collection the present dataset was derived from. The exact format and/or semantics are still under discussion. @@@If in a container of checklists, GUIDing is odd... BobMorris 2/22/2006 Each checklist must have metadata of its own @@@Could include "World" in case there are global Taxa with globa biostatus and facts. But note that cannot enforce the "truth" of whether a biostatus or fact belongs to a particular location. Does this make XSLT tricky?...BobMorris 22February2006 Maybe TDWG-GIG has something better??? one or more taxon/location/fact triplets. TCS GUID and/or locally stored elements derived from IAS dbs Factsheet can be modeled here by use of location "Earth", Name, Commentaries, and various "unspecified" attributes in the Biostatus element attributes. @@@@@@Name here is necessarily associated with location, but except for common names this is unlikely to be desired. Probably this implies need decomposition of TaxonT into location independent and location dependent data ...BobMorris 22Feb2006 Oct 25: need to appeal to TDWG-TAG standard for names when it exists. A location has a structured LocationName or a GeoReference or both Currently from darwinCore. This should be revisited if a TDWG standard emerges. ram 6aug2006. Linkage to referenced data - not enumerated here URI of an external reference cached elements of a reference - not enumerated here. Structures exist elsewhere. External namespace? keywords to match profile component decriptors. Third party comment@@@###what does this mean?BobMorris. In its simplest form this is a URL. The image provider to ensure appropriate image metadata in the web form referenced. A TDWG group is being formed to deal with image metadata standards. Could be expanded here - structures exist elsewhere.@@@@@@ram where/how to treat images. They are needed in many places, probably. Certainly needed in taxa, maybe in locations. There may be embedded images. Does UBIF specify media resources? See enumeration See attr "type" for enums Free text description in addition to, or (discouraged) instead of Habitat(@type) See enumeration For pathogens, parasites, etc., habitat type may be coded as "Host" or "Vector" For pathogens, parasites, etc., habitat type may be coded as "Host" or "Vector" See enumeration @@@###Needs work @@@### need temp units? @@@###Needs work Requires val, unitTime, units @@@May need refactoring at least because Biostatus is separate for checklists. BobMorris; Hannu: generally may need factoring if to be useful for other checklist contexts@@@@@a few things MUST be location specific and this may now be lost since we don't model LocationSpecificFacts anymore. Needs scientists to revisit which must be, which may be and which must not be location specific. This might be only Name Metadata for this object. If absent it is inherrited from parent object Decimal years XML elements in a sequence are considered as ordered. XML elements in a sequence are considered as ordered. Statements of Distribution are always relative to the size of the Location for which the presence of this taxon is being documented. free text.Where to put Population dynamic terms such as growth rate, age, stable, expanding, numerous, few, trend? c.f. distribution and occurrence @@@ram stopped here. need percentage?? need relative abundance??? This particular element is discouraged. See "recommended" attribute. The Pathways of the introduction of this taxon same elements as 'Introduction' but different vocabulary. Better way to handle this? Project or case study @@@###Needs work. Contents of the elements will be put to the IAS community via Aliens-L for review...ram, mjtb, Oct 23 2006 @@###Needs work Interaction and distribution of hosts. Mechanims here is poor and will repeat identical host data for different taxa? Needs to refer to an agent model. Not enumerated here. experts in these set of taxa (at any rank) Geographic Range Status of organims being impacted, e.g. rare, endangred, threatened. think about relationship with requirements @@@###Needs work @@@###S\Enumeration?? @@@###Needs annotation. Should be numeric range? @@@###??? @@@###??? e.g. disease cycle Position in the food chain, determined by the number of energy-transfer steps to that level. Good traveller, Persistence, Capacity to establish and spread, Capable of securing and ingesting a wide range of food, Tolerant of physical conditions, Pioneering in disturbed or vacant habitats...Gregarious??? @@###why are there multiples?? One for each development stage?? ...ram What triggers growth #NeedsWork @@@Terminology group must model the four impact types and possibly their enumerations @@@###Needs work @@@###Is this needed? Isn't the TaxonImpacted the one containing this impact element? Michael and I discussed in Agadir and I think I still don't understan. BobMorris See Enumeration @@@###removed 'Other' from this. Did its presence mean there was supposed to be an external schema? BobMorris, Agadir @@@ram remodel this as attributes on empty element? @@@ram put in enum!!! Alleopathic Causes allergic response Competition-Monopolising resources Competition-Shading Competition-Smothering Competition -Strangling Competition-Other Disease transmission Filtration Fouling Herbivory/Grazing/Browsing Hybridisation Induces hypersensitivity Interaction with other invasive species Parisitism Pathogenic Poisoning Pollen swamping Predation Rapid growth Rooting Trampling @@@ram remodel as enum e.g. high, moderate, minor or potential @@@###Needs work @@@ram and michael: refactor to separate things common to both management and impacts, and let others be in separate extensions of that.... Are there any other extensions? @@@ why is this here since the information is also in the mandatory Location? ...ram GUID issued by GISIN If no taxa this is presumably a project about a Pathway. @@@ram this may want an attribute that says it is a Pathway.@@@ If the project addresses multiple IAS' what to do??? @@@ram Is this meant to be a vector or an entire PathwayT object Oh,oh, this is recursive May include links to relevant feasibility study and/or implementation.Was it peer reviewed, etc. (reinvasion risk, follow-up recommendations, lessons learnt @@@What about humane methods??? See enumeration Free text Describes an authority for the values in an element. This is inherited by any element below the element on which an element of type AttributionT is an immediate child. Metadata referring to the principal source of the entire data collection (thus the metadata scope may be wider than the objects actually contained in the data set). If a history of the data collection (revised or expanded in various projects or at different institutions) exist, this must be reflected in the IPR statements and possibly in the list of Owners. Dublin Core conformant elements describing the content of the data source queried, representation in different languages possible The description in a specified language. Only one representation should be delivered for each language. [ATTR: language] The URI of an icon/logo symbolizing the project. Keyword lists of geographical, taxonomic, etc. scopes. In the case of projects in progress, 'scope' may define the planned or intended, rather than the achieved scope (or coverage). If scope is given, the content available should be entirely within scope, because this item is for resource discovery purposes. Compare also Coverage in DC.Description (which is language-specific). (Items from Scope may be added to DC.Coverage)@@@###needs work A collection of terms describing the geoecological scope of the source queried by means of area names (e.g. 'Worldl', 'Germany', 'Atlantic Ocean', 'Andes', 'Mountains'. A list of recommended terms should be developed. A collection of taxon names of higher rank describing the taxonomic scope of the source queried. A list of recommended terms should be developed. Number and date of current version (particularly for citing purposes) The major version number ('1' in 1.2) as defined by the content creators. An optional minor version number ('2' in 1.2) Unconstrained text specifying status + optional number, e. g., 'beta', 'alpha', 'rc/release candidate', 'internal'. If missing, release status is assumed. Source for Dublin-Core standard element Date.Issued: Citable 'publication date' of the current version (comp. RevisionData/DateCreated and DateModified for version- independent dates). This date should be missing if the current version is not yet published! Creators, Revision status, and dates of the entire data collection from which the current dataset is derived. Entities having legal possession of the data collection content. Here defined for the entire data collection, not for individual units. If an owner statement is present on the unit level, it should override this dataset-level statement. Entitiy having legal possession of the data collection content. 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) @@@Enumerate Tropical Subtropical Temperate Boreal Polar, All @@@###feels like this should be a singleton which is a choice, each one also being a singleton representing a single Management activity, and those should be in a container wherever used. Hiw di you tell the difference between a single management with may objects, e.g. DiffucultyEfficacy and severak Management activities with one object? BobMorris @@@###needs work Where/when to look for it, how to attract/trap it, where to find a diagnostic key/expert to identify it, etc. how to collect it, who to send sample to, warning statements etc. Flag as post or pre Hosts, enemies, etc? Host taxon location Native in this location or not @@@TWG: To be enumerated @@@ram: model this as time interval?? Intentional Intentional, illegally by natural means Unintentional Unknown @@@ @@@There is possible confusion/replication/conflict with DatesOf/FirstIntroduction and SubsequentIntroductions See enumeration @@@###There is something wrong with the container here. Maybe this should be a choice and represent a single activity with each choice singleton, and the object of type ActtivityT should be in a container. BobMorris @@@###Feels like sthis should be a singleton choice of signletons, and users of it should implement the container. BobMorris Community needs to provide advice here e.g. mechanical individuals/Organiztions/ contacts etc. Elsewhere Below ABCD elements normalized string required to contain at least 1 character (this removes the xml string anomaly, i. e. either element/attribute may be optional, but if they are required the content may not be an empty string) Text, optional Details (both free-form text) and optional URI. A concise representation of a statement, recommended to be as short as possible, but actual length is unconstrained. Optional text of unconstrained length, elaborating details of the ShortText An optional resource on the net providing details on the statement (may be used as an alternative to the long text).@@@###Maybe should be a GUID. Even DOI would be meaningful here. A sequence of statements related to Intellectual Property Rights, credit and acknoledgement. Container element for one to several statements, normally representing different language representations of the same content. Used where the IPR declaration cannot be parsed into the specific items or for forms of IPR declaration not yet covered (e.g. database rights), Container element for one to several statements, normally representing different language representations of the same content. Copyright may include the information that the data has been released to the public domain. Container element for one to several statements, normally representing different language representations of the same content. To be used if data are placed under a public license (GPL, GFDL, OpenDocument). Placing data under a public license while maintaining copyright is recommended! Container element for one to several statements, normally representing different language representations of the same content. Defines conditions under which the data may be analised, distributed or changed. "Terms of use" includes concepts like "Usage conditions" and "Specific Restrictions". Container element for one to several statements, normally representing different language representations of the same content. Disclaimer statement, e. g. concerning responsibility for data quality or legal implications. Container element for one to several statements, normally representing different language representations of the same content. A free form text acknowledging support (e. g. grant money, help, permission to reuse published material, etc.) Container element for one to several statements, normally representing different language representations of the same content. Indicates how this dataset or record should be attributed if used [OBIF 1.0] Language-specific content metadata (title, description, etc.) with *required* Language attribute added. Source for Dublin-Core standard element "Title": A short, concise title. General Note on DublinCore translation: In addition to those that can bee transformed from UBIF metadata, an additional DC.Type='dataset' should be added. Source for Dublin-Core standard element "Description": Free-form text containing a longer description of the project. Source for Dublin-Core standard element "Coverage": Free-form text describing geographic, taxonomic, or other coverage aspects of terminology or descriptions available in the current project. URL pointing to an online source related to the current project, which may or may not serve an updated version of the description data. normalized string restricted to 1..255 character length (i. e. required, may not be empty string) Language-specific simple label, using simple formatted text Label text in a specific language. Restricted to 50 characters maximum length, including blanks (recommended to be shorter!). Label abbreviations are especially important when displaying information in a tabular format. String255 (i.e. xs:string with length 1-255), extended with language attribute Name of an individual person Preferred form of personal name for display as a string. The full name with the elements in preferred sorting sequence (vCard: Sort-String). 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) Prefix to inherited name that should be output before name, but is usually not included in sorting. Examples: 'von', 'Lord'. Compare Title for 'Prof', 'Dr.' (vCard:N.Prefix) 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) 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) May differ from the first given name: second given name, nickname ('Bob' for 'Robert'), etc. (vCard:Nickname) String (i. e. xs:string with minimum length=1) extended with language attribute String (i. e. xs:string with minimum length=1) extended with language and preferred attribute xs:anyURI extended with Preferred attribute String255 (i.e. xs:string with length 1-255), extended with preferred attribute normalized string restricted to 1..50 character length to be used for abbreviations (the recommended length of abbreviations is usually much shorter, but 50 characters should be a Collection of language-specific label representations Language-specific label representation [ATTR: language] Full organization or corporate name in multiple languages (en: 'Botanical Garden of ...', de: 'Botanischer Garten von ...'). vCard:Org.OrgName). The Label mechanism also supports acronyms / abbreviations (no vCard equivalent!). @@@###Feels like this needs some unique prefered label--else can't compare Name objects...BobMorris If the contact 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)@@@###as above, maybe needs a unique label fir comparison of OrgUnits BobMorris (vCard:OrgUnit) Type of device reached by telephone number, e.g. voice, fax, voice/fax Telephone or Fax number Full number in standard international format Free text for constraints on use e.g. "weekdays only" or "home number" RevisionData (creators, dates, revision) for the entire project/data set or individual objects. Source for Dublin-Core standard element "Creators", i.e. Author or editor. Source for Dublin-Core standard element"Contributors": General contributors, or translators. Source for Dublin-Core standard element "Date.Created": Date/time when the intellectual content (project, term, description, etc.) was created. Applications may initially set this to the system date for new data objects, but authors must be able to change it to an earlier date if necessary. If for legacy data this is imprecisely known, it may be missing here. Earlier versions in other data formats should then be mentioned in the copyright or acknowl. statements. Source for Dublin-Core standard element Date.Modified: Date/time when the last modification of the object was made. If in online data sources the provider can not assess this, the current date/time may be substituted. For legacy data this may be set to the file date of imported data, or estimated. marine - trophic level? @@@Need enumeration? See enumerationin attribute "type" Enumerations need audit by Terminology Group Groups traditionally studied by mycologists and the ICBN Brief synopsis of species' invasiveness, significance, interesting facts. NB This is a mixed bag of elements. Species level descriptive data should be provided by SpeciesBank sources with its own descriptive schema. Morphological data should be provided through SDD elements. Again this component is acting as a cache for data best delivered elsewhere or for reflecting the actual content of profile dbs. @@@###Needs work Not sure how far GBIF SpeciesBank has got with data standards TDWG SDD container reference @@@???What is this? @@@???What is this Below borrowed from TCS used for long text @@@doc: If use html e.g. &lt;b&lt; for bold. Do not embed "<" or ">" literals. @@@ @@@A string that provides a value not in the enumeration list. There should be a way to discourage its use, e.g. it must come from a resolvable external list. Otherwise, provider must map to one of the given ones. This is not enforcable in XML Schema. Should there be an "other" in the Enumeration?@@@@This is the idea of "defined schema" root container @@@ Attr says how you get it. The GUID whose resolution produces a list from which a given string is chosen. TBD: in what form and where, when in the document is this list? What queries against it? How does it compare to the elements in some other list, e.g. an enumeration? Maybe a key to a separate section? That's the SDD model? Should be a controlled patttern? Checklist will support FactSheet information (Location = World) but this is not its primary purpose @@@ram possibly need key/keyref mechanism so that anything can refer to an image. Also no model yet of image metadata. @@@doc key/keyref mechanism is subtle and will confuse naive schema readers. @@@Maybe there should be a mechanism for access to the European Daisy Register of Experts The biostatus of this Taxon@@@###Much work to do See enumeration in "state" attribute. You must map to the required enumeration, but you may add your own Defined schema See state enumeration See enumeration in "state" attribute. You must map to the required enumeration, but you may add your own Defined schema See state enumeration See enumeration in "state" attribute. You must map to the required enumeration, but you may add your own Defined schemations might ignore.Some people want modifiers on these states, e.g. "dominant" but this is not presently supported See state enumeration geospatial or temporal scope for which an element is valid reference to a locality related by the relation specified in @relation See enumeration. If there is a DefinedSchema providing the name, then choose localityTypeName="Defined" and insure that the DefinedSchema has a Property named "localityTypeName" with value the desired name and the PV pair has an @applies="true" If the value is "Defined" then there must be a DefinedSchema with one or more Property-Value pairs with property="LocalityType" and Value = the desired locality type needs to be hierarchical to avoid ambiguity, e.g. Lake Geneva in the town of Geneva, New York, U.S. This is accomplished in the RelatedLocalities Gazetteers that may give information about this LocationName Need to assure compliance with geospatial standards @@@from greenwich? 0-360? -180-+180 I think we need accuracy and uncertainty