You make a good point here Roger, but I definitely think there is benefit in having both approaches - ie a complete model of our domain that people can reuse and base their specific use cases on, and the higher level architecture (the "map") for building bridges etc.
We are currently working on a "semantic" technologies project here at Landcare, and we are currently drawing up a (brief) high level ontology for our domain (ie biodiversity informatics in general, really). We are using SKOS to do this. I could put this on a wiki page as an example - when we have completed it - then we could build on it from there?? Did you have something like SKOS in mind (ie the domain topics are instances) or something more like an ontology of the domain (where the "topics" are classes themselves)?
Kevin
From: tdwg-tag-bounces@lists.tdwg.org [mailto:tdwg-tag-bounces@lists.tdwg.org] On Behalf Of Roger Hyam Sent: Thursday, 14 May 2009 10:52 p.m. To: lynette.woodburn@csiro.au Cc: tdwg-tag@lists.tdwg.org Subject: Re: [tdwg-tag] TDWG ontology revisited ... a newcomer's perspective
Hi Lynette,
Thanks for your comments ( and Greg and Gregor).
I think you raise an interesting point here that needs cleared up. It is something we have got wrong in the past.
Some people think the TDWG ontology should be a model of the biodiversity domain (particularly taxonomy) as it exists today, incorporating actual working practices and what is in the literature. "Just represent what we do today"
This is *NOT* what I am interested in building. A good analogy is that of a map. What I am interested in doing is building the a map for the major highways with enough detail in it to enable *machines* (not humans) to do sensible stuff with the data so as to facilitates our understanding of biodiversity. There should only be enough detail in the map to make data exchange work.
It may be worthwhile building a big, detailed ontology/map of the biodiversity domain for human consumption and this should inform the machine readable map but I think there is a big danger of conflating (great word) the two. This is what we have done in the past.
Anyone want to volunteer to run a wiki that describes the biodiversity informatics domain? This would be a great resource.
All the best,
Roger
For two reasons:
1) It gets us precisely nowhere.
On 14 May 2009, at 04:30, lynette.woodburn@csiro.aumailto:lynette.woodburn@csiro.au wrote:
Back to basics ...
Anyone new to biodiversity informatics (in general) and TDWG (in particular) might be expected, as a first step, to seek a broad understanding of the scope of the knowledge domain which is of interest to the community they've just joined. Next, they're likely to want to gain an understanding of each of the main concepts and to discover how those concepts relate to one other. Delving yet deeper, curiosity will lead them to seek details about features used by the community to characterise each of those main concepts. So, gradually, it is anticipated that newcomers will gain an understanding of the meaning associated by their fellow community members with elements (concepts, features, relationships) within the knowledge domain. (Those elements are, after all, the chief subjects of discourse amongst community members.)
This fantastic voyage of discovery, these first steps into Aladdin's Cave, ought to be made easy for any newcomer. Instead, TDWG presents a dizzying array of perspectives on disparate subsets of elements within the knowledge domain, often with only cryptic, tenuous links binding them together. 'Horses-for-courses'-drivers clearly exist for these subsets, but where is the common community understanding of where each element fits into the broader, shared knowledge domain which is TDWG's scope?
I fully support any initiative which more effectively leads newcomers (and not-so-newcomers) to that place: that place where I would hope to find, in plain expressions devoid of techno-speak, a description of each real world element (concept, feature, relationship), together with a simple representation (a label?) by which the TDWG community prefers each to be referred; that place which evolves, but endures, independently of technological fashions and particular implementations; that place I can visit to paint a picture in my mind's eye of TDWG's own Aladdin's Cave.
Lynette Woodburn Atlas of Living Australia
_______________________________________________ tdwg-tag mailing list tdwg-tag@lists.tdwg.orgmailto:tdwg-tag@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tag
------------------------------------------------------------- Roger Hyam Roger@BiodiversityCollectionsIndex.orgmailto:Roger@BiodiversityCollectionsIndex.org http://www.BiodiversityCollectionsIndex.orghttp://www.BiodiversityCollectionsIndex.org/ ------------------------------------------------------------- Royal Botanic Garden Edinburgh 20A Inverleith Row, Edinburgh, EH3 5LR, UK Tel: +44 131 552 7171 ext 3015 Fax: +44 131 248 2901 http://www.rbge.org.uk/ -------------------------------------------------------------
________________________________ Please consider the environment before printing this email Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails. The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz