Meeting 29/07/2010


  1. Matters arising Tuesday
  2. Paul will have two more profiles ready for the team.


Discussed> the big picture at some length.

Decided> need to seek guidance from above. GJR to send next version TPT delivery plan to EMC

Discussed> Authors. Need further disambiguation

viz structure of Flora of Australia

Flora of Australia editor

(Helen Thompson)

Is the creator of the flora of australia profile structure Meta data about NameSpace?

Acacia Section Editor/Author

(Bruce Maslin)

is an editor of a section probably not recorded at present

Profile Contributor

Joe Miller

contributes information/content metadata about profile = ProfileAuthor?
** though it is frequently the case that a single author/s will be in all roles in this table.

Decided> need a metadata field for namespaces capable of recording the Citation of the work from which the namespace is derived. Authorship & co. not necessary to record. as will be part of the citation or inferrable. NamespaceCitation =>PA

Discussed> Fields in the benthic flora of SA. PA is doing a second pass at this name space

Decided> Thallus, Reproduction, Sphophyte etc are the encoded separately. To preserve the decodability of the text. They are to be defined as descriptive elements as in the mushrooms of oz. And mapped as part of to WC.Description =>PA

Meeting 27/07/2010


  1. Review of scripts & tasks
  2. Finish off the Fungi of Australia
  3. Paul is preparing 2 profiles for the team to work through i.e. original content (definitions and co). Team to supply words & co.


reviewed> The relationship Script i.e. Create Relationship

needs to be reworked when the storage of relationships are in their final form (refactored as a topic per relationship)

Decided> Until refactoring done, a quick jump to topic which holds the relationship under question to be implemented as a link or button =>PA

Discussed> A new script for making/refining relationships.

Script would show relationship under question as a triple + associated happiness rating

Underneath it would show definitions of terms on both sides of the triple and defitintion of the relationship.

Action =>PA to prototype/ implement (depending on the status of the refactoring of the representation of relationships)

rigourously Discussed> Authors in their various guises.

Decided> DISAMBIGUATION required of WC to distinguish nomenclatural authors from Profile or other content authors.

JRC > WC.ProfileAuthor to be same as (based on/exact match ) dc.creator = author of the work =>PA

Decided> need WC.Authority (in profile 'metadata' group ? ) an example of which would be CHAH.. refers/indicates a work has a status of an authority


of a name nomenclatural
of a paper/citation a treatment, article or citation
of this profile / 'metadata' group
Decided> that WC.Author needs to be disambiguated.

WC.Author replaced by



and maybe by WC.CitationAuthor (for citations within a profile)=>PA

DEcided> Benthic Flora. Author to be examined to see if it should be renamed to NameAuthor =>PA

Decided> Need a new field in all profile terms for usage to be recorded =>PA

Decided> that it is possible tho not desirable in general for the headings (labels) used in a profile to be different from the term name we use.

Decided> PA to examine Authors in citation and meta groups to see how they match disambiguation decided above =>PA

Meeting 22/07/2010


  1. A spiffing round of definition poker.
  2. Relationship bingo
  3. identify which relationships which are suitable for indicating hierarchy within WC (internal only relationships)... And tools


Discussed> definitions of skunkworks per .... "As a generic term, it dates from the 1960s. One definition is very much that of the original and the one you describe: a small group of experts who drop out of the mainstream of a company’s operations in order to develop some experimental technology or new application in secrecy or at speed, unhampered by bureaucracy or the strict application of regulations "

which led to kick-a-poo joy juice.... "The original was Skonk Works (skonk is a dialect variant of skunk), the place of unexplained function near which Lonesome Polecat and Hairless Joe brewed their highly illicit bootleg Kickapoo Joy Juice from ingredients such as old shoes and dead skunks"

Discussed >Script built as per last meetings brainstorming

i.e. Create Relationship

some small amount of work to do before it is fully commissioned. Looks good.

Discussed> whether the list of possible relationships should be circumsribed to ONLY the (currently assiged) term group .

Decided >

relationships could be made to WC terms outside the (currently assiged) term group. =>PA to consult and implement.

that this would on principle be not the preferred end point BUT is necessary to record where further work is required.

Discussed> the WC definitions at bottom of page Create Relationship should be populated from
  • only WC terms within the group to which mappings have been made OR
  • a list of any WC terms to which mappings have been made irrespective of which group they belong
GJR cannot recall what meeting decided but prefers later option. =>PA to consult and implement.

Discussed> Null fields for definitions and relationships.

Decided> There should be no BLANK text fields instead

Definitions should contain standard entries indicating state such as either
  • 'Not mapped'
  • 'Not defined'
  • 'None Supplied' =>PA to implement AND RETROFIT existing blank fields.
Discussed> adding a button to Create Relationship to create a new terms as required if there is no corresponding WC term at the time of mapping. Initially, content to be copied on creation. And mapping may be an exact match. But both content and mapping will NEED TO BE REVIEWED. So the new WC term will have a happiness rating of 1 or 0. Thus allowing the newly created term to be put into a list for review. =>PA & PH

Definition Bingo> focussed on a volume of the fungi of Australia. good progress to be continued.

Note> The definition tool might be enhanced by a create term button =>PA to investigate

Clarified > WC will be hierachical. a suitable relator should emerge with time. GJR would like this to be so that it is simple to create triple searches (without additional qualifiers). PH thinks it may be one of the SKOS relationships. =>PA to watch and advise

Meeting 20/07/2010


  1. A spiffing round of definition poker.
  2. Discussion of what should be hidden away..
  3. New profiles - a place to park them? Or a status (not yet)?

New Suggestions.

1. per Donald

NZ Arthropod Collection

The new internet factsheets, Interesting Insects and other Invertebrates, are now available on line at The production of the first 18 factsheets was funded by TFBIS, a DoC?? operated Fund. It was a joint project with Landcare Research who did the IT work. The material in the factsheets can be used by people for their own projects. We welcome feedback about what you like about the factsheets and where improvements can be made. In a few months time we hope to invite members to write their own factsheets and so contribute to the series. Nicholas Martin Entomologist, Honorary Fellow, Plant & Food Research,

2. per David Yeates

This is an Edit scratchpad page. And certainly something we should look to describing. Also, flies.. So politic to do so. Can you create somewhere on the wiki to keep such suggestions (perhaps just as an entry to the Workshop notes)?

3. also per David Yeates

Here is some more information on another set of species pages developed by my collaborator Torsten Dikow.


Concerning the Mydidae species pages, I have two ways of how to provide these in the projects of the grant. One is to publish manuscripts in ZooKeys?? so that the journal automatically provides the species descriptions to EOL (as well as the specimen data to GBIF, nomenclatural changes to ZooBank?? etc.) and therefore species pages are produced. I have submitted a manuscript to ZooKeys?? in May with some new Mydidae from eastern Africa and the Oriental Region and this is also the way that my summer intern Katie will provide species pages for Ectyphus and Parectyphus from Africa.

Another approach is to make a LifeDesk?? for Mydidae and upload information about the species. This is what I have done with some Leptogastrinae species on which I have published previously (see a species page in the LifeDesk??

and on the EOL

GJR> of note is sparce content on lifedesk.. consequence of de novo model?

GJR> note opportunity for WC?

Zookeys is the best of the etaxonomy journals that Zoologists use. Automatic Zoobank rego (not sure about LSID’s), species page generation, links to EOL – read about it in their special issue.

4. per John Hook / Donald

Sponge DB.

5. Zookeys per DY

>this details the enhancements to etaxonomy that Zookeys has initiated.

Thanks David. pdf seems to have been mangled enroute. Was it from Lyubo's special issue of Zookeys ?

which has been the cause of much talk here.


GJR> note publishing workflow
GJR> also note collaboration & their model of a TP / treatment.

GJR> also suggestive of a workflow for science and publication of treatments.

play together or compete?


Discussed> New profiles

Decided> to build a suggestions box. @ highest level of Taxon Profile wiki. Details to be kept in child pages of the suggestions box. => PA (to create to suit workflow)

Discussed> workflow for making relationships. Noted the need to open many tabs to make relationships.

Discussed> Simplifying (de skunkifying TPT wiki)

Decided> good idea

GJR wants "data wikis to be visible only to a small group".... and the scripts we are building to become the principle means by which informationa is viewed and changed. => GJR, PA, PH to discuss / plan / trial

Decided> To build a script with functions something like the illustration below. Idea is to provide an interactive view on relationships with a view of currently defined relationships for other terms in the same group. => PA with PH

Nb this gives Term Groups a very specific role. They are a filter to see like terms from other Name Spaces and relationships from WC

nb forgot to include happiness index in this diagram... should be there for relationships and WC definitions.


Discussed> whether terms could be mapped to more than one WC term.

Decided> Sloppy mapping is useful. Terms may be mapped to more than one WC term... as an interim measure to represent terms as they are received.... and then corrected by the creation of a WC term sufficiently broad to be a one to one mapping

Decided> we will need a script which lists terms which map to more than one WC term so that the situation can be remedied. => PA with PH

Discussed> the implied necessity (from above) of a hierachial WC

Decided> this is ok. As we have a separate class of relationships which are suitable for this (internal only relationships)... to be briefly discuss next meeting. => PA wihth PH

Meeting 17/7/2010


  1. Review of Progress towards definitions.
    - scripts
    - difficulties encountered
  2. Definitions


NOTE> EMC overseas from 19th september

Discussed> Scripts listed at TaxonProfile.Builder/FixTerms and the happiness index.

Decided> Looks great. Well done.

Decided> better use of field placement to reduce white space & thus fit more on screen etc. => PA with PH

Admired> Nifty graphviz based visualisation tool implemented for WC definitions.

Decided> move graph above table in WC terms => PA

Decided> add a Guide/Purpose of Scripts to described in TaxonProfile.Builder/FixTerms => PA

Discussed> Definitions.

Decided> PA to change happiness entry for term that is currently 9 to 5 => PA

Reiterated> Consensus (> 2 people) required for happiness to go above 5. This to be noted in style guide (see below). => PA

Decided> Original definitions to be colour coded. So as to be quickly discerned => PA

Decided> Style guide should be developed on basis of ISO definitions and co. It should be on a page in the root Taxon Profile directory.=> PA

Decided> Style guide should also include notes that definitions need to be written to reflect the context in which they are used and seen with respect to the taxon being described => PA to add note on style guide

Decided> copy original definition if it is a good match and then word smith it to style sheet. (note in style guide?) => PA to add note on style guide

Decided> on entering definitions sourced elsewhere. That we need to explicitly indicate where no definition was given for a term. => PA to add note on style guide
  • blank => not entered
  • "None" => the source work did not define the term
Worked> through definitions for fungi down under

via script

Excellent progress. Managed to complete all 10 in an hour. Anticipate it will be even quicker next time.

Decided> that these definitions were now at a stage where they could be shown to a fungi-ologist wink e.g. Heino Lepp ANBG.

Meeting 6/7/10


  1. Show and tell
  2. Scripts
  3. definitions.
  4. more…..


Discussed> Meeting with Tony Rees and Daniel to talk about the use of TPT for fish information to be contributed to the ALA

spoke about getting information in and out.

Indexed by CAAB number; Tony & Daniel to discuss. Interested. Will require CAAB numbers to be exposed in some sort of webservice.

GJR is very happy with the speed and efficacy with which 2 profiles were created. Only need to make it usable for non-initiates.

Discussed> Taxon Profile Categories

looks great.

Decided> that a line is needed to clarify and define. Possibly include example of what sort of profiles goes into each category. => PA

Discussed> Definitions

Decided> to create a style guide page that can be referenced via a link where-ever definitions and links are made. (Ideally should open in another page). This page should include guidlines as written in the ISO guidelines and others we come up with. And eventually, to be used by other people who are adding content. => PA

Discussed> The definition 'script' page

Decided> That 'Original Definition' to be coded as follows => PA
  • blank = not yet entered.
  • 'None given' = no definition
  • the defintion from the orignal work
Decided> 'Happiness' index to be applied to Relationships. => PA

Discussed> Coding The SPRAT profile

Jeff Trantor = may provide a SPRAT profile schema => PA

Decided>There may be a need for a WC term 'status' to code legal status of weeds, endangered status etc . => PA to consider

Decided>Paul to aim to enter original defintions and preliminary definitions for terms in profiles on file. => PA

Discussed> Insects of Australia

Decided>That it is complex. We would leave describing it for later. As a test case

Discussed> happiness index (as a aworking strategy) and determined a rationing rules for happiness. . => PA

0 = not looked at

1 = looked at but unhappy

5 = Paul is Happy, but needs consensus

Decided > We need a script to sort terms and relationships by happiness, where happiness can be adjusted. => PA

Next meeting Thursday week to look at definitions.

Meeting 2 / 7/ 10


  1. Review of past action items
  2. Definition widget. demo
  3. Mapping widget… design
  4. Definitions, Dust, blood and words


Discussed> Questions arising from last meeting

Clarification> Metadata to each profile so that each can be roughly categorised as (provisionally) a formal treatment, a technical compilation, a compendium or a general profile. (as detailed in previous meeting) => PA

Clarification> It is not clear if the organisation (e.g. alphabetical, by taxa ) of profiles within a work is useful. Resolved: along with addition of a field for textually describing the coverage of a profile provision to be made for textual description of organisation and other matters in profile metadata (RTF field). => PA

Clarification > Where profiles are nested, and the fields vary with nesting, these are to be described as separate profiles distinguished by the profile name e.g. BirdsOfNewZealand.Family vs BirdsOfNewZealand.Species and so forth. => PA

Deciced> Where profiles are nested, the link to the profile content to be described by a new field (metadata) in the profile which contains a description of the link and a link to the profile i.e. the term ChildProfile in BirdsOfNewZealand.Family contains a link to the BirdsOfNewZealand.Species profile => PA

Similar process should there be a ParentProfile relationship to describe. Just as with other Profile terms these are only used when required as they are part of a profile explicitly or by inference in the layout.. => PA

Discussed> Rain Forest key Profile

Turns out to be a very simple profile indeed. Most of the fields are in access for another purpose

Decided > PA to describe the Rain Forest key profile. => PA

Discussed> Profile Coverage- have we got a sufficient sample for now of profiles?

Decided > Coverage is sufficient for now.

Discussed> Profile Coverage- two additional profiles suggested by Murray Fagg. DEWHA Weeds and SPRAT

Decided > useful and politically smart to describe both. Should also be quick. Details as follows.... => PA

Weeds - DEWHA profile


Discussed > Evidence & meta data for online profiles

Decided > to record screen shot of profile examples (in the manner in which we are doing so for printed profiles) => PA

Decided > PA to write an overview of the ISO standards for Definitions as a Style guide for definitions

Reviewed> Definitions Script tool

Clarification >Tool to contain a the R/O definition of the WC term to which a relationship has been asserted. With a link to the WC term should its definition need to be reworked. => PA

Discussed > Relationships

it may not be always possible to make an exactmatch or a iscontainedin match.

Decided > need to always document a reason why there is not an exact match in comments

Discussed > Scripts and other workflow enhancements.

Decided > Following requried=> PA

(Wiki topics containing) Data Review Scripts

for a profile
  • show a list of terms for a specified relationship
  • list terms which are not an exact match
For a given WC term
  • list terms in other profiles which are an exact match
  • list terms which are not an exact match but is part of
  • list terms which map to more than one wc term?
For a given term (particularly WC) list relationships with other terms
  • exact match
  • near matches

Discussed> Rules for making relationships

Decided> that tho' it would be useful cannot do it at moment and that they will evolve. Best to keep it loose& document later.

Discussed> workflow for iterating through terms

Decided> need an additional meta data element for terms and relationships. Happiness. Ranging from 0-9 i.e. unknown to bad to perfect=> PA

also a script/page which sorts terms and relationships by Happiness. => PA

Discussed> adding provision to describe labels used with terms as well as names (reflecting the common practice where the term is known as something else)

Decided> to wait and see wrt to labels.

Meeting 26/6/10


  1. Progress.
  2. Mapping of plant profiles (thanks Murray)
  3. Coverage? What's left on the list? Do we have enough?
  4. Problems that Paul A. has encountered.
  5. Groups
  6. Workflow for tightening up definitions.
  7. Mapping


Decided > Rainforest key descriptions to be added. PA to approach frank while he is here (leaving next week). => PA

decided>to add a scanned page of each profile (where possible) and preface (where possible) to each profile described. . => PA

Discussed> issues brought up in the works PA has mapped this week

Decided> to code relationships with nested profile info as meta data.(an example of which would be Dyrandra species profiles which contain details about cultivation of more than one sub-species). Text field = meta data about where a profile sits and what other profiles it may contain. => PA

Discussed> extending metadata attached to Profiles...

Its clear (at least for our own sakes) we should clearly distinguish different classes of taxon profiles. Perhaps this can be metadata. Suggestions that spring to mind are

  • formal taxon treatments - often but maybe not always new taxa
  • Technical compilations (targeted at nomenclaturalists and others in the field) - such as the Flora of Australia/ Marine Benthic Flora etc - principle purpose being to summarise taxonomic information about a group
  • Taxon Compendiums - summaries of taxonomically organised information - compiled for a particular technical ends... Aboriginal food plants, Poisonous Snakes of Australia etc
  • General Species/Taxon Pages - Compendiums targeted at a general audience- recognition, identification, pertinent general facts - often seen in popular works in print and online
I'm attempting to add this type of metadata for each namespace as it surfaces. We can add use/purpose and broadness of taxonomic coverage as characteristics of the profile arrangement .

"taxonomically organised information", others alphabetically, and "Rather than family or genus...arranged by a simple visual key system.".

Decided> to add metadata for both. => PA (To clarify. Metadata will be added to the profile Form? or A new form element called Metadata will be added to the Namespace form PJA to document interprofile relationships. {This is what I was trying to say in the quote above})

Discussed> workflow for defining terms and tightening up mappings.


to build a script to implement a form something as follows. It will allow the definition to be progressively refined. Once a mapping is made to a WC term the defintion of the term will be visible on this page (R/O) and help to refine the mapping, the terms definition or indeed (for those who can) invite refinement of the WC term. => PA to liase with PH (The diagram below implies a new Term:Attribute will be created to accommodate the original text from preface, might this be dcterms:abstract )

wc_def_and_mappingn_workflow.gifMeta Data

22nd June 2010

EMC took notes which PA is acting on

17th June 2010


Any and all of the following as takes the fancy of the Brains trust

1. More brains trust sorting into groups.
- Paul to mop blood
- whereforto place endemic, habitat, abundance, distribution… seem to belong to a supercategory
- perhaps EMC will know

2. Review of Past actions
- new metadata
- new profiles for the mill?

3. Lets look at definitions….
- For stable term groups, can we refine the definition of relevant WC terms?


Discussed> Groups. and terms seemingly that fit in more than one term group

Decided> initially these may go into a special multi-term group that Paul has created. But, ultimately they are to go into only one group. And groups are to be redefined if they are not sufficiently broad. => PA

Decided> to rename 'Distribution' with a suitable definition and name so that it can encompass endemic, habitat, abundance, distribution etc => PA

Discussed> Definitions of terms.

Decided> to use workflow to help. Definitions to be crafted for WC terms by looking at terms in a group and seeking words to encompass them in WC terms => PA to with PH

Discussed> scripting that PA has done with assistance from PH. Looks good

Decided> to add a flag to indicate terms which are new.=> PA with PH

Decided> that pictures, illustrations, and gfx are difficult. Park them in their own category (with notes) for later consideration=> PA

Decided> on lots of term to be moved groups or revised. PA has a detailed list.=> PA
  • Rename TermGroup? WC_Distribution to WC_Extent to be more inclusive
  • Create new TermGroup? WC_Illustrations to include images and image captions
  • Terms are regrouped
  • Notes added to terms that have been discussed. PC_MolecularData to stay in WC_Description TermGroup?

15th June 2010


Not necessarily in order.

  1. the 1st order sort continues
    - Paul to adjucate and mop the floor of blood as required
  2. additional proposed metadata 'coverage' or similar to record how a given profile was/may be applied (to what taxa; to what purpose)
  3. discuss next steps in workflow
    - after grouping …. What next?
    WC term relationship mapping + WC term refinement
  4. applicable scripts for #3?


Discussed> Rank in Profiles.

Decided> where not explicitly listed in a profile Rank is metadata. And (especially in written works) it may be important to record the implied rank of a profile and the rank of the next treatment 'up'/ containing profile. As it is the context in which the text was written. Rank and phylogeny from nameservices may change as thoughts are updated & not be the original context in which it was compiled.

Action> add metadata to profiles for Rank as discussed above=> PA

Discussed> Hierachy in Wallace Core.

Decided> Hierachy required .. need to be kept as flat/shallow as possible.

Discussed> Adding 'coverage' to profiles as described above

Decided> to add the provision for multiple sentences for 'coverage' as metadata for a profile. to be tidied and systematised as required. => PA

Discussed> Taxon profile group Distribution at great length

Decided> Ants. currently 2 works combined namespace needs to be split . => PA

Decided> Need to consider a Habitat group => PA?

Decided> also may need to add hierachy.. endemic, habitat, abundance, distribution... seem to belong to a supercategory.. => PA

Decided> remove / change / revise fleuristics from Cultivar profile. => PA

10th June 2010


1. examing terms which have been placed into groups.

(aka beginning the taxonimic sorting of profile terms sampled to date)

2. Other pressing matters concerning taxon profiles


Most of the work in this meeting was done directly into the wiki. A great success. Terms were effortlessly grouped using a script that PaulH? had knocked together.

Discussed> Cultivar Profile.

Decided> Fleuristics is unfamiliar to Jim. Presumably something to do with flowers. possibly a typo => PA to investigate and correct.

Decided> textual definition of phylogeny gp & WC term to use the definition from SPMI for evolution => PA to amend appropiately

Decided> to delete the CERF profile => PA

Erratum> Fungi-image moved into Ecology Group. => PA to tack down & amend.

8th June 2010


  • Open discussion
  • driven by examination of current state of term lists


Discussed>Plinian core.

Noted the use of the term 'Target Audience' in Plinian Core

Decided> to add target audience as a META DATA field to all profiles & potentially everything else (which ever is most efficient) should be multivalue=>PA to liase with PH

Discussed> Illustrations in profiles. and whether illustrations were content in themselves and allocated a specific term or part of the content that could be in any term. Probably case by case.

Decided> that it would be worth liasing with Cyndy Parr to see how she concieves of the term target audience. => GJR???

proved to be a useful source of terms and concepts not yet mapped. => PA to continue map (2nd priority)

Discussed> Ants. Componutus Discription found in the library. JRC suggested that Camponotus would be worthy of a formal description as part of a TRIN project. => PA

Discussed> Workflow and our loose term Groupings.

Decided> Term groupings were a key ingredient in the workflow.

Decided> terms not prefixed in WC or formal descriptions will be taken to mean their common english forms.

ACTION> as a priority to review existing terms which are ungrouped for discussion NEXT MEETING => PA

ACTION> Need a means to indicate visually whether a wiki page is auto generated or hand editable =>GJR to liase with PH

(could be a visual cue; removal of the edit icon; moving the edit icon ?)

ACTION> alter template to add defintion of groups. ditto in other cases =>GJR to liase with PH

ACTION> clean groups pages to match the editing in the Biology grp page. =>GJR to liase with PH

gjr> more cleaning to come as we de-skunkify.- GJR> removing person last edited from tables and forms - often redundant & misleading.

Discussed> reinstating PH's nifty graphicical graphviz based relationship browser for i) profile relationship definition and ii) wizzard.

2nd June 2010


  1. Reviewing what came of Friday (Acacia / FOA)
  2. status of Actions from past workshops
  3. Multiple attribute meltdown.
  4. Discussion of Environmental Attributes & co.
  5. useful Reference and web service.
  6. ANDS - 'CMD' = Classify my Data Service
  7. Publishing WC


Discussed> Multiple attributes (of same type ) for elements

Decided> Not a problem as previously thought. PH will do refactoring to make it possible. it will be useful. More uniform code and easier export.

PH> plan is that attributes will have a prefix which indicate the meta "layer" e.g. term_label, profile_label & such

Action> GJR to prepare draft MongoDB business case by HubRIS meeting 15th June (Monday is a public holiday), when the team will review it and get it ready to be submitted to the TRIN Management Team. Short inc. executive summary & What it will enable. => GJR

Discussed> Coding of relationships in Wiki WC. Currently a table of triples. OK for now. No forseeable problems.

Discussed> Registration of the Wallace Core. GJR suggested potential to register it with the ANDS Classify my Data Service - they are using SKOS.

Decided> Keep a watching brief on their technology and see how they're doing it. The preferred home for the Wallace Core would be somewhere under the auspices of TDWG.

Discussed> Outcomes of yesterdays APA with PA

Discussed> Profiles to map to the Wallace Core

Actions> PA to formally describe new profiles to increase coverage of profiles formally described and mapped to WC => PA
  • Profiles to use:
    • FoA
    • SPMI
    • Plinian Core (see action below)
    • EoL
    • Fungi of Australia
    • Handbook of Australia and NZ whatevers
    • Benthic Flora
    • Snakes of Australia
    • Sharks of Australia
    • Flies
    • Thrips
  • seek also to formally describe a profile for each of the TRIN Taxonomic Research projects
    • Mayflies
    • Mangrove project - which includes profiles for several taxa
    • Ants of Australia
    • Mammals of Australia
Action> PA to subsequently choose 5-10 additional profiles from web and library and prepare assay of coverage. A simple table. * "We are seeking an asymptote." "We'll know coverage is good when very few terms require the addition of a new supercategory to WC" => PA

Action> EMC to encourage PA and remind him regularly that there is life after term mapping => EMC

Discussed> encoding Ecological Relationships.

For example, the Term might be WC:associatedSpecies, with association relationships needing to be coded in a hierarchy e.g.
  • Eats
  • EatenBy?
  • ParasiteOf?
  • ParasitisedBy?
  • GrowsWith?
  • PollinatedBy?
  • etc.
Decided> this was a secondary problem and should be the matter of further research. The approach should be to collect data from a variety of profiles in sentences and derive the relationships from the data rather than imagine possible relationships beforehand and try to coerce the data into the relationships - "let the data drive the specifications". We should also have a discussion of elements in which we can indicate our preferences for relationships e.g. "if unencumbered by data we would do it like this".

Action> engage with Emma (Mangroves) as a model of the problem. Seek solutions driven by her needs and encourage her to use the "best" relationships whatever we all decide these might be. Keep a tally (on wiki) of similar matters for subsequent. => PA

Discussed> ANDS... CMD service. Possibly useful. chances of adoption? Note use of SKOS. Watch developments.

Discussed> Plinian Core

GBIF has this compilation of related resources:

A search on Plinian Core reveals other resources of various ages,
saying much the same.

It does not look too complicated - the categories are in many cases
broader than ours, and in some cases there are terms that seem to make
sense we may not have encountered yet.

worth a look... no - we really need to account for all of PC if we
are to avoid flak down the line

Action> Add Plinian core to the list of profiles that are to be formally described. => PA
Discussed> Frequency of meetings.

JRC would like to keep things moving. Twice weekly meeting attended by at least GJR and PA => GJR to schedule.

Discussed> direction of the project. JRC wants it to come to a point where content of meeting are only about contentious or interesting mappings into WC and there is no need for notes as app dev and co. are stable.

Discussed> its application to WC as a URI 'ground truth'

On Thu, Jun 3, 2010 at 9:08 AM, <> wrote:
> so we should use it in the TP? Supplemental to Dwc

Short answer, yes... it is one of those TDWGish standards that we will lift from for a wc:term if we can not find a defined term elsewhere...


Discussed> Using TP toolkit as a means to publish primary taxonomy. Steve Donnellan and others may be interested esp in light of changes to the Zoological code (fingers held in scout's salute). => GJR to investigate.

Friday 21st May 2010


  1. prep for EMC
  2. Multiple attribute meltdown.
    1. Multiple Defintions
      • WT?
      • Usage
    2. Options for Implementation of Multiple attributes
  3. Discussion of Environmental Attributes & co.
    1. Project scope.
    2. How much can we and should we record about species associations.
    3. Relevance of EML?
  4. Review of status of Actions from past workshops
      1. Review and attribute forms
BEER (well only wishful thinking)


EMC's presentation for the CERF conference.

Agenda 18 th May 2010

*Landing pages and Nav in main Taxon Profile web => PA; GJR

* Workflow for adding, describing and reviewing WC

GJR's suggestions...

Understand something like as follows (subject to change etc)

Build a Profile
  1. define terms (===> coming.. facility to pick and choose from Existing ones)
  2. build forms
Forking to two separate (relatively independant tasks)

fork 1. Apply profile (if it is to be used for the compilation of information about taxa)
  • add data;
  • use in a wiki form (a la Plume Moths)

Further Mapping of profile to WC
  • less necessary - if previous profiles used a template (need reduced once the facility to pick and choose from WC and friends)
  • essential - if being used to extend WC as a MetaProfile?

* multiple attributes are required for WC terms. => PA; JRC

* see also field to relationships form.

* EMC's prep

* Short Names?

* Claiming WC in semantic world => PA to report on what can be done

Record Tuesday 18/5/2010

Wikipedia Taxon Profiles

Discussed: Wikipedia Community profile projects

  • Analyse. check that profiles under development will map to WC terms. => PA
  • Monitor projects which are part of the Tree of Life Community Profile Projects => PA; GJR; JRC

Action: TRIN Mangroves. Require mappings of various profiles to be completed and mapped to WC => PA


Action: Build a list of domain experts to consult with as WC *& associated applications) matures => PA

  • Helen T.
  • Dave M. / Donald
  • Sensible & tame Zoologists
  • Sensible & tame entomologists- should they exist smile


Discussed: Attributes. Arrived at a general position that we should have the capacity for multiple values for attributes on pretty much any WC term. With some reservations about definition. To some extent this need is driven by our data may be coded in RDF and XML

Decided: to dicsuss with PH re options and cost of retrofitting to existing data. => GJR; (DONE. to discuss Friday)

WC in the semantic World

Discussed: 'Claiming WC' in the semantic world => PA; GJR
  • to be modelled on the way that Darwin Core with EXPLANATORY plain language english
Action: create a URL for WC ... on or for now an automatic referral to the TRIN wiki WC homepage (which is?)

Name Spaces

Discussed: NameSpaces?

Decided: Add category to distinguish Namespaces made for different purposes => PH; PA

  • Reference = are not profiles but included because they are refered to
    • e.g. SKOS, DCMI. SKOS, FOAF, DCTerms, WC etc
  • Instance = taxon profiles which have been described especially in the process of building WC OR as the basis of Taxon Profile content in the wiki
    • SPMI is special in that it plays both roles as an instance and reference but is best placed as an Instance
    • FOA; BenthicFlora?; PlumeMoths? etc

Actions: REview namespaces. Clear away junk & remnants (Biology, etc)=> PA

Decided: Terms in a Reference Profile should as a rule have a means to link to the external source. (& if possible directly to the term under consideration)

Decided: Basis if term reflects the thought processes which led to the WC term being created. There can be multiple entries. Entries will be generally on the basis that they are a CLOSEMATCH for the WC term.


Action: Create a search so that instances of TaxaCreator? in the wiki are listed on the taxon profile wiki. => PA


Just a quick documentation of useful links as current - to be reviewed as project matures (of course)

A profile


xml of Homo Nitpickerus Minor;contenttype=application/xml

Definition of CERF profile


How to specify the contents of a profile (a simple table for the form fields)


and a template for rendering the form


definition of the term


A view of the Attributes of this term

Wallace Core


A related term in WC


Wallace Core Attributes.

TaxonProfile/Definitions.WC_Attributes?===>;;; BAD


WC: attribute definition


WC: Relationships with Profiles



WC Short Names.


'The "short name" of each namespace is already encoded as the name of the
topic holding the metdata about a namespace (including the verbose labels).

For example, The topic'

Another Challenge and Parrallel Project

Mapping the varying wikipedia species profiles.... such as A different approach to taxon profiles. Community developed on Wikipedia

Agenda Friday 14/5


  1. Review gains and implementation of the past few days
  2. application development-stability
  3. & MAC-applification
    Explaining it to others
    - what do we need to do?
    - any changes nav & UI?
  4. Discuss: Documenting guidelines for application of mappings / relationships.
  5. Discuss: levels of meta ness relationships ..
    Any case for more than one set (GJR thinks NO).
    linked data not - multiplicity and resolvability.. Care?
  6. The Challenge…. Vacellia nilotica.. Worth doing?


Discussed: clarifing the application of names, labels and terms to Attribute and Relationship Data Dictionaries.

Changed heading of columns in Attribute Table

Decided: to add a short explanation to Attributes and relationship Data Dictionary to clarify terminology=> PA


Discussed App-ification:
  • Paul H is working on Dashboards for each 'app' being => PH review this list for accuracy
  • TermBuilder?
  • Relationship
  • Terms
  • Attributes
  • Mappings
  • etc
Decided: Review landing pages and Nav in main Taxon Profile web => PA; GJR Monday => Next Meeting.
  • Deeper Hierachy; fewer items on menu Make sure nav Menu is short; add tool tips.
  • links to data dictionary; attributes; terms and builders etc
Check with PH re Tooltips & menu


Decided: Workflow for adding, describing and reviewing WC needs to be discussed => Next Meeting.

Re-iterated: links to definitions need to be on Form fields => PH is working on this already in the form template

Discussed: comments and proceedures.

Decided: Need a way to flag decisions, attributes, and mappings that need clarification. Possibly tags; or just a clever search on the wiki => PA to discuss with PH

WC Attributes

Discussed: whether multiple attributes are required for WC terms. Possible through nested forms but needs to resolved before much more work is done => JRC & PA to review ASAP; => Next Meeting.


Decided: to add a simple see also field to relationships form. This will include text that will list related; similar or different relationships. It is to be kept simple. and should not require any thing else to implement => PA Monday => Next Meeting.


Decided: after nav and landing pages cleared up => PA will email donald re the straw-man; Monday

A challenge..Vacellia nilotica

Came across an interesting case study whilst perusing the World Wide Wattle

One taxon..

Acacia nilotica / Vachellia nilotica

many profiles... all different... and complementary

Can we map it? (into WC)

Record Tuesday 11/5/2010

Present Paul Alexander, Paul Harvey; Jim Croft; Margaret Cawsey & Garry Jolley-Rogers

Reviewed: 'state of the profile' for Margaret.

Discussed: Margaret's upcoming presentation for the CERF Forum. EMC will be coming to seek content, clarification and pretty pictures.

Data Dictionary

Discussed:'Data Dictionary' - some confusion on the application of this terminology.

Action: GJR will address with Paul Alexander in the introductory documentation => PA; GJR

Decided: Need to clarify Column headings in table view of the data dictionary. Group, Term, Label + new column Definition. => PA

Documentation of Proceedures

Decided: PA is to write a guide (on the wiki ) detailing how to make changes to Walllace Core. At both content and meta level i.e. i) how to add content to definitions of WC terms and ii) how to add additional attributes and relationships to WC term framework. Goal being so that Jim can get started adding details. Broader goal to provide a giude for other collaborators. => PA

Decided: Tables of WC attributes and Relationships to be applied to WC terms MUST have the same headings & co. => PA


Decided: PH to adjust edit template ( when time allows) to add => PH

Discussed: PH's workload. Comment <=== this is dealt with ELSEWHERE see 1, 2 and 3. Action: GJR to write up notes of last Wednesday's meeting with PH and place on 2 => GJR

Resolved: to start using Google Wave 1 again for defects & desiderata

NOTE: prepending a namespace + a colon to a term e.g. FOA:Description will be automatically expanded ( using an interwiki link) to link to the outside namespace (in principle/ eventually etc). Rex Croft's implementation of the Benthic Flora might be useful as a test case if Rex makes the labels available (currently, believed to be implemented as a part of Perl scripts etc)

Actions: PA to report on alignment of Taxon Profile attributes decided upon previously with those seen on the forms. Is there full correspondence now. => PA

Next Meeting to be scheduled. Perhaps coming Thursday.

Record Friday 7/5/2010


Decisions: forms to use label for WC attributes
  • labels to be used on form
  • labels to be as Wiki Words. Presented with spaces using a Macro
  • Forms to contain links to full discussion of Attributes.
  • Namespace of attribute to be displayed on FORM
Decisons: Auto generated table of WC Attributes to be sortable by column=> PA

Added Notes column to attributes table => PA

Decision: Add notes column to the table of Relationships applied in WC => PA

Decided to Review: Pete de Vries tweets and URI-burned data on profiles. => PA

Meta & wiki TP Implementation

discussed: 4 levels of review next meeting with PH => ***** next meeting?

Require: explanatory notes on how to edit profiles

Decided: Groups to be implemented Simply. NOT as hierarchy, nor as terms. Using a simplified structure. An arbitrary assosciation for presentation. Ordering 'like with like' => PA


Reworked Canonical form on front page as a basis for groups ... something like Canonical Form of a profile


Decided to re-work Relationship table: One row per relationship. Column to indicate whether it is to be applied within profiles, across profiles or both. => PA

  • Relationships BT / NT - JRC 'guide mapping of terms when there is a decision THAT MATTERS'
  • Thesaurus like relationships to be used for disambiguation
  • Too many options for relationships. Need Guidelines => ***** next meeting?

Data Dictionary

Decided Data Dictionary => PA

  • should be a table ordered by group
  • columns Group, term, label
Decided: PA to work up term of choice for discussion on Tuesday => PA

Linkages to Other Profiles

Decided: to describe SPM - with a view to encorporating all SPM terms and also to building a WC -> SPM exporter => PA

Record Thursday 6/5/2010


GJR working from top down on document; PA working from bottom up.

Require page defining anatomy of a WC term.

  • added columns about WC attributes & Relations so allow Definitions AND 'intent and usage'
  • Clarify: Need to clarify WC term attribute rdfs:comment. definition seems appropiate but is confusing nonetheless (for its current usage herein). Is there a better attribute?
  • Add a column to WC attributes table to record references alternatives for WC label attributes
  • need a comments attribute (distinct from rdfs:comment which is for a different purpose = name/label of term)
  • A new attribute WCTermGroup?. contains another WC term. => PA
Decided: Separate provision required to record details of releases for each WC term (as opposed to edit-versions). Technical nature Release strucure to be clarified.

Decided: check terms suggested by DH incorporated in to profile => PA

DH's list
  • Classification (includes Names, Phylogeny)
  • Description (includes Identification)
  • Biology (includes Ecology)
  • Distribution (includes Specimens/Observations, Population)
  • Molecular
  • ....
GJR to respond to Donald

Reviewed Forms

for entering WC TERMS. Name Spaces must always be displayed in labels and forms. => PA

WC terms to be grouped. No more than one level deep. => PA

A new attribute WCTermGroup?. contains another WC term. => PA

Data Dictionary Page

2 forms
  • comprehensive with page per term showing all attributes => PA
  • report form. listing terms & some relevant attributes in tabular form => PA
  • Terms to be grouped by via WCTermGroup? in at least one view of the Data Dictionary. => PA

Record Tuesday 4/5/2010

Discussed documentation of taxon profiles and WC on the wiki


work to be divided as follows
  • GJR will use presentations and co. to start high level restructuring of Taxon profile wiki. (Please put your 0.02c in as required)
  • PA will pull together summary documents which describe
    • the Framework used to specify Wallace core terms (aka the logical framework of WC )
      • an overview of attributes & relationships and modus operandi
    • A wallace core data dictionary
      • including framing and orientating text as per DC.
    • To do this Paul will review the workshop notes and places in the wiki where WC is discussed and compile a review of the current form of WC.
Progress to be reported on Thursday.

Record 30/4/2010

Present: Paul Alexander, Garry Jolley-Rogers, Jim Croft

Scribe: GJR

Issues and decision arising from discussion of Profiles in SA benthic Flora

A reading of the prologue in Volume one gives a very simple structure.

SA benthic floras structure includes
  • typification separately encoded
  • Description (in the technical sense a GBIF:circumscription) contains one to three paragraphs which are typographically distinguished by three keywords. These keywords indicate structure that we might later on ( usefully) describe as sub elements of a description
    • Thallus
    • Reproduction
    • Sporophyte (sp?)

General principles

  • Say what the Author said in the prologue clarify only it is unclear or absent.
  • Rex Croft's OCR of the Benthic flora is a NEW WORK distinct in principle from the original published work.
  • Provision should be made in WC for such Distribution maps included by Rex Croft. These need to indicate that these are POST HOC and not part of the original work.
  • Provision needs to be made to place GBIF:typification and species examined in profiles AS WRITTEN in the original work. Otherwise we are re-writting the work. Of course, profiles once digital will be linked in with services such as APNI and AFD which also provide typification details. It is important to preserve what the author wrote.

Canononical Form of a profile

(as listed quickly by JRC - some parts ommitted as GJR's writing illigible)
  • Name
  • typification
  • Synonyms
  • description (in a circumscriptive sense) - we need an alternative word for this as it is overused with different meanings.
  • Specimens Examined
  • Distribution
  • Aftermarket maps & other value adds

Other matters

  • PaulA?> commented that his workspace in the namespaces.
  • decided relationships of a profile to WC encoded in the profile not WC. (such as 'SABF.Thallus' ispartof 'WC.Description' )
  • decided to move notes on structure of TP wiki documentation to TP wiki (DONE)
  • Some comments from JRC on wiki documentaion of TP added to these notes. TaxonProfileWikiDoc
    • Jim would prefer to come up with a logical division of topics - a typical website architecture.
    • Suggested a workshop is held to come up with this architecture.
  • Need to dig out and compare SPM with WC.

Record 29/4/2010

Present: Paul Alexander, Garry Jolley-Rogers

  • actions to be taken to clear up documentation and wiki web for Taxon profiles. Notes are in TaxonProfileWikiDoc
  • PA to do-convolve SA Vascular plants and Algea - fruits and infleurescnce etc
  • Examined form of SA benthic flora. Decided that it was really very simple e.g. Thallus, reproduction etc were really just subsets of technical description/circumsription. They are CONTAINED within a description
  • PA to finish description nof benthic flora on wiki
  • talked about types of specimens listings in a taxon profile being type, specimens examined, and co. Decided these are essentially different in function/purpose if not content. and should be treated separatly
  • Decided: If a given profile has a term which we think is contained within an element of WC (but not equivalent) e.g. Thallus. We will use the relation 'Contains'
  • Decided: WC.term 'Contains' means that the term is wholly within the term. i.e. the WC term is a superset.
  • Decided: use of; element.source; element.value to be deprecated.
  • Undecided: whether 'ispartof' is requried. or whether it is exactly complementary to 'Contains'. If so, we will discard it. However, it may be useful in another context.
  • Next: assess what work is required to get a polished process for defining WC terms? what work is required to document this process

Record 3/03/2010

Present: Jim Croft, Paul Alexander, Garry Jolley-Rogers


  • Annotate Attibute list below with explicatory comments as to how each attribute is to be used. ( Paul Alexander)
  • Add Attributes to current wiki forms ( Paul Alexander)
  • Document relationships between WWW & FOAF in wiki ( Paul Alexander)
  • Implementation of relation operators ( Paul Alexander, GarryJR , Paul Harvey to discuss best means)
  • Next waypoint (just after Forum)?

FOAF and World Wide Wattle

Compared contents and structure.

near 100% correspondence. Excepting that labels are different and Presentation. Need to map any significant differences in labels. Not significant here. Nonetheless, worth mapping for acacia project and as a 1st exercise

General Principle : for the moment NOT to go for a complete survey of extant profiles. Rather look for adequacy of coverage of WC terms for profiles of interest. An adequate survey may be something we aim to achieve later on.


  • Our expectation is that profiles for Higher level taxon should match Species Profiles.
  • Nomenclatural entries in extant profiles to be documented BUT not to be implemented in Wallace Core.
  • Similarly for dichotomous keys, Name References, and protologues.
  • Species examined is to be treated as a block of text because it should reflect what the researcher wrote.
  • Essential principle is that WC should not go into any depth specifying things which are handled elsewhere especially services exist (APNI / APC/ APII/ Identify Life etc) e.g. If the nomenclature or the synonymy differs the authors should correct it in APNI
  • Explicitly make DC.title and rdfs.label synonymous so as to make it easier to treat WC terms as resources
  • List below is close to the order of presentation
  • All are attributes are mandatory - if Left blank taken to be a null
  • ALL terms are Resources



dc.source replaces BasisOfTerm?


Attributes will be drawn from Dublin Core

Primary source to be rfds definitions of DC terms

A second property with the same name as this property has been declared in the dcterms: namespace ( See the Introduction to the document "DCMI Metadata Terms" ( for an explanation.



Attribute Intent and usege Example Content Source
rdfs:label What is the identifier of this resource Title
rdfs:comment definition and explicatory text "A name given to the resource."
rdfs:isDefinedBy URI rdf:resource=""
dc.source One to many references for why this term came to b Created on basis of entry in the Fllora of Australia profile
dcterms:issued   1999-07-02
dcterms:modified   2008-01-14
rdf:type rdf:resource   ""
dcterms:hasVersion   rdf:resource=""
SKOS:note   A second property with the same name as this property has been declared in the dcterms: namespace ( See the Introduction to the document "DCMI Metadata Terms" ( for an explanation.
Term Name: contributor
Term Name: creator
Term Name: coverage
Title A name given to the resource. 1999-07-02 2008-01-14 − A second property with the same name as this property has been declared in the dcterms: namespace ( See the Introduction to the document "DCMI Metadata Terms" ( for an explanation.

An example of original rdfs as follows

A name given to the resource.


A second property with the same name as this property has been declared in the dcterms: namespace ( See the Introduction to the document "DCMI Metadata Terms" ( for an explanation.

Discarded DCMI Terms

Term Name: date, Term Name: description, Term Name: format, Term Name: identifier, Term Name: language, Term Name: publisher, Term Name: relation, Term Name: rights, Term Name: source, Term Name: subject, Term Name: title, Term Name: type

Record of Taxon Profile Workshop 25/02/2010

Present: Jim Croft, Paul Alexander, Margaret Cawsey, Garry Jolley-Rogers, Paul Harvey


Draft relationship set

DC:Resource every term component of a taxon profile is a DC:Resource
Internal, between WC terms (internal links within a concept scheme) Both External, between WC. and Other namespace terms (mapping links between concept schemes) Meaning
- - DC:source (Not WC:termBasis any more)
SKOS:related - SKOS:relatedMatch The property SKOS:relatedMatch is used to state an associative mapping link between two concepts.
SKOS:broader - SKOS:broadMatch The properties SKOS:broadMatch and SKOS:narrowMatch are used to state a hierarchical mapping link between two concepts.
SKOS:narrower - SKOS:narrowMatch The properties SKOS:broadMatch and SKOS:narrowMatch are used to state a hierarchical mapping link between two concepts.
- - SKOS:exactMatch The property SKOS:exactMatch is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. SKOS:exactMatch is a transitive property, and is a sub-property of SKOS:closeMatch.
SKOS:exactMatch is disjoint with each of the properties SKOS:broadMatch, SKOS:narrowMatch and SKOS:relatedMatch.
- - SKOS:closematch The property SKOS:closeMatch is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, SKOS:closeMatch is not declared to be a transitive property.
- DC:isPartOf Contains DC:isPartOf -> A related resource in which the described resource is physically or logically included.
- DC:hasPart isContainedBy DC:hasPart -> A related resource that is included either physically or logically in the described resource.
- - OWL2:differentFrom (to distinguish confusing terms)

  • Paul to extract equivalent relationships for the RDFS namespace and see if they are better that the SKOS ones we have chosen (see above)
  • Paul to define the relationships between Flora of Australia and WWWattle
  • Paul to make a start on the list of attribute terms which will describe each WC.Term e.g.

Record of Taxon Profile Workshop 18/02/2010

Present: Jim Croft, Paul Alexander, Margaret Cawsey, Garry Jolley-Rogers, Paul Harvey


  1. The Wallace Core (WC) is our 'workbench' i.e. Reference Profile. All terms which end up in the reference profile, regardless of where we got them i.e. namespace of origin, will end up in the WC (ha, ha, joke).
  2. The WC is thus the equivalent of a data dictionary of Taxon Profile terms
  3. We should set out the descriptive framework for each WC term in a similar manner as has been done for the Darwin Core
  4. Leave the Type field blank for now, unless we really know what it is
  5. Basic Attributes are described on the photocopy of the whiteboard work, and that is listed here.

  • Name (Ours) *
  • Description, definition (Ours) *
  • Term basis (≥ 1)
  • Relationship(s) to other terms in this namespace (≥ 0)
  • Relationship(s) to other terms in other namespace(s) (≥ 0)
  • Domain/ Range/Values
  • Format
  • -
  • -
  • -
  • Comments (≥ 0) (? = notes)
  • Discussion
  • (Metadata for this record - Date, Contributions, etc.)


All by next Thursday 25th Feb 2010
  • All FoA? terms accepted in the first pass to be placed into the WC framework (see points 3-5 above) with the appropriate metadata e.g. name, definition, termBasis
  • The appropriate syntax for describing relationships to be determined e.g. is it WC.Identification OWL.sameAs FoA?.Identification or something else?
  • Relationships between these (now) WC terms and the World Wide Wattle profile terms to be placed into the framework; the namespace for World Wide Wattle is currently set at either 3W or W3, whichever Paul A prefers
  • The Pauls and Garry to brainstorm the kinds of data structures which will be required to manage this framework
  • Paul A. to nail down a starting list of preferred relationships in the appropriate syntax form e.g. they might be something like
    • SKOS.closeMatch
    • SKOS.broader
    • SKOS.narrower
    • SKOS.exactMatch or OWL.sameAs
    • RDF.seeAlso
    • RDF.comment
    • RDF.domain
    • etc.?

Record of Taxon Profile Workshop 11/02/2010

Present: Jim Croft, Paul Alexander, Margaret Cawsey, Garry Jolley-Rogers


  1. We have our own Namespace: the Wallace Core, or WC for abbreviation. This will provide the basis for a generic Reference Profile.
  2. We will build the Reference Profile by selecting elements/terms from other namespaces, choosing each term on the basis of our own decision that we like it and its definition e.g. WC.Habitat may well be selected from the Flora of Australia list of terms
  3. We would then define the relationships between the WC Reference Profile element WC.Habitat and other related terms in other namespaces e.g. SameAs FoA.Habitat, SimilarTo TDWGSPM.Distribution or whatever
  4. We continue to adopt terms from other namespaces as they become relevant to the taxon profiles our collaborators are interested in building, mapping the relationships between each term in the Wallace Core Reference Profile to related terms in other namespaces.
  5. If we can't find a term we like in any namespace, we make one up and map its relationships as per point 4. above.
  6. Thus, the Wallace Core will provide a reference point for all other taxon profile namespaces
  7. Because no other namespace has everything we want in it.

Goals of the Taxon Profile Project

  1. To represent (all) existing Species Profile Models
  2. To provide the capacity to represent any new SPM
  3. Improve searchability across taxon profile models


By next Thursday 18/02/2010, Paul Alexander to mock up a particular WC reference profile element
  • Put a definition on it
  • Cherry-pick the relationships we think will be the most informative, regardless of whether they are regarded, sensu stricto, as 'relationships' within the originating namespace
  • Map the term to terms in other common profiles
  • Make up our own relationships
  • Find out whether we've invented any relationships; if one turns out to be the same as something else, in some other namespace, make ours the same as theirs
  • Don't have any confusing redundancy.

Record of Taxon Profile Workshop 16/07/2009

Present: Jim Croft, Paul Alexander, Margaret Cawsey, Garry Jolley-Rogers



Taxon Profile definitions

A taxon profile is the structure of a description of distinguishing traits of a defined taxon (e.g. Family, Genus, Species), which includes information as to the who, what and where of this taxon.


A resource is the source of a particular profile, or an instance of a taxon profile class, e.g. a species page providing a profile of a particular taxon e.g. the Shovel-nosed Snipe. A resource can be anything that might be identified as such, e.g. a book, a species page, an electronic document, the Flora of Australia, a website, a service (DCMI).


An element is a property of a specific aspect, characteristic or relation used to describe resources.


A class is a category of elements things e.g. Locality is a class of Locality elements in the Darwin Core set.

Design Rule #1

We will choose our elements such that each belongs to only one class. We will revisit this if we hit the wall somewhere as the design of the Taxon Profile structure proceeds.


Elements are defined by attributes , which include Dublin Core elements such as: dc.Name dc.Label dc.URI dc.Definition dc.TypeOfTerm dc.Comments dc.NarrowerThan etc.


Elements may be described through a variety of representations in the way the information for that element may be presented. There may be more than one representation of information for any given element. \x{2003}


Class: Spatial Distribution


Where we find it in space and time. dc:Coverage The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. Note: Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.

See also:

i.e. does NOT include: biophysical, ecological, climatic, seasonal distribution


Geographic Extent


Where we find the taxon in horizontal space: An equivalent schema would be Darwin Core Geospatial Extension schema>

GeographicalExtent?.Text; Definition: dcTermsDescription? An account of the resource. Note: Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.

GeographicalExtent?.Box; Definition: dcTermsBox The set of regions in space defined by their geographic coordinates according to the DCMI Box Encoding Scheme.

GeographicalExtent?.Image; Definition:

GeographicalExtent?.GISfile Definition:

Vertical Extent


Where we find the taxon in vertical space

VerticalExtent?.Text; Definition:

VerticalExtent?.Range; Definition:

Temporal Extent


Where we find the taxon in time

TemporalExtent?.Text; Definition:

DateRange?; Definition: dcTermsPeriod? The set of time intervals defined by their limits according to the DCMI Period Encoding Scheme.

Record of Taxon Profile Workshop 4/08/2009

Present: Jim Croft, Paul Alexander, Margaret Cawsey, Garry Jolley-Rogers


Taxon Profile Framework

What does Jim perceive to be a community need (Paul A's fundamental niche)
Agile approach

Testing Process

All the following points feed into one another

  • Recommend vocab for taxon Profile
  • Terminology mapped across taxa (i.e. accommodating alternative vocabularies)
  • I.e. suitable at a broad level for all taxa
  • Templates for using the recommended vocab to produce cute species pages
  • Suite of taxon forms based on the vocab

Community needs

  1. A way to document existing profiles
  2. Record new ones
  3. Place to store and render
  4. So need standards - structure and recommendations


  • Standards
  • Reuse (not reinvent)
  • Explicit (defined well)
  • Framework is DCMI
  • Dealing with broad blocks of text rather than codified, atomised pot points
Focus of domain is:
  1. Fact sheets
  2. Floras
  3. Interactive keys
  4. Species pages
Focus of domain is not:
  1. atomised descriptive data
  2. the key matrix