Materials for Online Flora Information Systems

From Hiscom
Jump to: navigation, search


As agreed at the Adelaide workshop, the schema documentation from the Flora of Australia Online was used as a starting point. The files have been updated and are appended here:

Discussion of Online Flora Schema

  • Online Flora XML Schema 20081128 - this is an alternative version of schema for the taxonType element based on the version from the Adelaide workshop (Online Flora XML Schema). This version is provided for discussion - it is not complete and there are a number of issues that still need to be resolved (for both these schema). Changes from the previous version include (but are not limited to):
    • reducing complex types definitions to those that are reused
    • addition of a paragraphs type to permit nesting of multiple paragraphs and tables (tables is not fully developed)
    • addition of paragraph type - this includes elements for font and taxonomic names, but perhaps should also include elements for other linkage types (e.g., literature citations, specimen citations)
    • Moving elements from within TaxonDescription where the use of choice model may not be appropriate e.g., the name element has been moved to make it required.
    • Started the introduction of id attribute to some of the elements to permit referencing/linking to specific content within an xml instance
    • adopted upper camel case for elements, lower camel case for attributes

Interchange elements (from word file above)

Follow up in September 2008 to E-flora workshop

held in Adelaide, Dec. 2007

Structure of Descriptive Data (SDD) in progress

Element Sub-element Tag Comment
chromosome information <chromosome> e.g. 2n, diploid etc
conservation Empty field with 3 attributes
conservation status <conservation_status_description> Free text
conservation status code <conservation_status_code> An agreed set of codes
conservation status-related act <conservation_legislative> Name of legislation
contributor of the treatment <contributor> The name of the person who contributed the treament/information. To be added at all descriptive levels (family, genus, species, infraspecific etc)
description <description> Empty field with 3 attributes
full description of plant <description_full> One text description (e.g. Flora of Australia)
an atomised description of plant In the form of <description_habit>
for bark, flowers, fruit, habit, inflorescence, leaves, ovary, roots Possible examples only, based on suggestion that some atomisation of internal <description> data required.
List required to standardise
diagnostic description <description_diagnostic> One text description, but just with diagnostic characters
distribution <distribution> Empty field with 2 attributes
region occurring in <distribution_regional>
number of taxa <no_taxa> The number of taxa. A suggestion that this should also be an element within distribution region (not done as yet)
flowering/fruiting times <phenology> will be adapted depending on plant type being described
group <group name=\"your text here\"> This is theWrap required for the whole group in the xml schema
Element Sub-element Tag Comment
habitat <habitat> Of the plant. Free text
image Empty field with 2 attributes
image text <image_identifier> e.g. the figure no. from the published Flora of Australia, or another descriptive identifier (not the image caption)
image url <image_url> Links to static line art/map
identification keys (dichotomous) <identification> Empty field with key coding attributes
key row <kr> Empty field, begins each key row
each key couplet <kn> <kn>1:</kn>
descriptive key data <kd> <kd>Leaves green</kd>
key-go-to <key_to> Direct to next couplet if a taxon not keyed out
key-taxon <kt> The taxon name e.g. <kt>baileyana</kt> Flexibility required for name. Ability to use taxon name from SDD, TCS or ‘other’
key rank <key_rank> The rank of the taxon. Ability to use rank of taxon name from SDD, TCS or ‘other’?
licence/right of use <licence>
notes In the form of <note kind=”ecology”> and including agricultural, biology, contributor, ecology, habit, host-parasite, key, misc, morphology, name, protologue, taxonomic.
These attributes also need to be able to contain elements/sub-attributes e.g. might be better to include ‘fire’ to within ‘ecology’ Various fields that were determined at the meeting would fit better as elements of a Notes tag.
name qualifier <qualifier> e.g. cf or aff (requires the use of <rank_qualified> for the placement (i.e. cf species name).
Element Sub-element Tag Comment
rank to be qualified by the name <qualifier> tag <rank qualified> required to specify which rank is being qualified (for formatting to enable correct placement of the qualifier such as a question mark) e.g. ?smithii
scope (geographically of the flora treatment <scope_geography> regional/State/Territory/national etc
source of the data <source> e.g. <source>Data derived from Flora of Australia Volume 12 (1998)
source date <source_date> The date the data was most recently sourced/modified. To be added at all descriptive levels (family, genus, species, infraspecific etc)
specimen citation <specimens> Vetted by expert, but ideally the updated specimens that were cited should be available via TCS/ABCD. Need flexibility to also have in SDD
weed status (proclaimed) i Empty field, includes 3 attributes
proclaimed weed status-descriptive <weed_status_text> Descriptive text about the weed status
proclaimed weed status-related act <weed_legislative_code> The legislative code
proclaimed weed status-related act <weed_legislative> The legislative Act declaring the weed status as used in <weed_legislative_code)

Taxonomic Names and Concepts TCS

Element Tag Misc.
all name components (incl. parents for hierarchy, including hybrids), orthographic variants, synonymy, typification, common name/s, indigenous name/s
author of plant name
rank of plant
bibliographic/reference important works, protologue, other references, illustration citations, date of publication of reference, author of reference