This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Ecoterm"

From HL7Wiki
Jump to navigation Jump to search
 
(22 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Action Points for the Following Year ==
 
== Action Points for the Following Year ==
 
The following points are based on a [http://eea.eionet.eu.int/Public/irc/envirowindows/jad/library?l=/ecoinformatics_indicator/ecoterm_1542005/alistairmilesecoterm2005/_EN_1.0_&a=d presentation] by Alistair Miles at the 2005 Berlin [http://ecoinfo.eionet.eu.int/ Ecoinformatics] meeting.
 
The following points are based on a [http://eea.eionet.eu.int/Public/irc/envirowindows/jad/library?l=/ecoinformatics_indicator/ecoterm_1542005/alistairmilesecoterm2005/_EN_1.0_&a=d presentation] by Alistair Miles at the 2005 Berlin [http://ecoinfo.eionet.eu.int/ Ecoinformatics] meeting.
=== Identity ===
+
=== [[Ecoterm Identity|Identity]] ===
* Ecoterm members are a community within a global information environment
+
 
* → When choosing standards and designing systems for interoperability, should anticipate and allow for …
+
=== [[Ecoterm:Construction|Construction]] ===
** Unlimited expansion
 
** Novel interaction
 
* A standard mechanism for identifying things independent of context is key to scalable interoperability
 
* Principles of good URI use
 
** Architecture of the WWW Volume One
 
*** W3C Recommendation
 
*** http://www.w3.org/TR/webarch/
 
* Managing URIs
 
** [http://esw.w3.org/topic/VocabManagementNote SWBPD-WG Vocabulary Management TF]
 
*** Publish soon (hopefully)
 
----
 
  
=== Construction ===
+
=== [[Ecoterm:Data Model|Data Model]] ===
  
* Standards for building a ‘good’ terminological/conceptual thing …
+
=== [[Ecoterm:Publication|Publication]] ===
** Relevant because if two things constructed according to the same basic principles then likely improve interoperability
 
* Two new proposed standards …
 
** BS 8723
 
** ANSI Z39.19
 
* Also …
 
** [http://www.w3.org/2001/sw/BestPractices/OEP/ Ontology Engineering Patterns TF (SWBPD-WG)]
 
  
 +
=== [[Ecoterm:Services|Services]] ===
 
----
 
----
 +
=== Steps toward interoperability ===
  
=== Data Model ===
+
[http://ftp.ics.uci.edu/pub/ietf/uri/rfc2396.txt URI's]
 
----
 
----
=== Publication ===
+
# Use URIs
 +
# Use URIs well (consistency, persistence, articulated management & maintenance policies etc.)
 +
# Be clear about what a URI identifies
 +
#* Concepts? Classes? Something else?
 +
# Publish [http://www.w3.org/RDF/ RDF] descriptions of the things you are identifying
 +
# Use ‘well-established’ RDF vocabularies as far as possible, extend as appropriate
 +
# make commitments to maintaining RDF descriptions, and publish maintenance policies and procedures
 +
 
 +
Establish a semantic web of terminological / conceptual / ontological data relating to the environment
 +
 
 +
[[User:Hsolbrig|Hsolbrig]] N.B. [http://lists.w3.org/Archives/Public/public-swls-ws/2004Sep/att-0013/MayoBMIPosition.html Mayo Position Paper on LSID's] describes how URI's are described in HL7 and elsewhere<br>
 +
[[User:Hsolbrig|Hsolbrig]] N.B. The [http://www.bio-itworld.com/archive/011204/lsid.html Life Sciences Identifier (LSID)] and the [[http://lsid.sourceforge.net/] LSID Project] are different, but related.<br>
 +
 
 +
 
 +
 
 +
Services
 
----
 
----
=== Services ===
+
* With a web of data in place, the role of services becomes extremely clear: to provide efficient, convenient, programmatic Interaction with subsets of that web of data.
 +
* Build a service-oriented architecture on top of a web of data
 +
 
 +
* Steps to achieving this:
 +
 
 +
# Analyse and publish functional requirements for service types (I.e. what do I want a service to do?)
 +
# Study functional requirements within this community, identify and publish sets of common requirements (basis for standardisation work)
 +
# Take a look at [http://www.w3.org/TR/2004/WD-rdf-sparql-query-20041012/ SPARQL] services & protocol (v. cheap)
 +
 
 +
** N.B. true standardisation of a service interface requires a (lightweight, informal, open) community-driven process for developing a web-service specification and building consensus

Latest revision as of 20:27, 22 April 2005

Action Points for the Following Year

The following points are based on a presentation by Alistair Miles at the 2005 Berlin Ecoinformatics meeting.

Identity

Construction

Data Model

Publication

Services


Steps toward interoperability

URI's


  1. Use URIs
  2. Use URIs well (consistency, persistence, articulated management & maintenance policies etc.)
  3. Be clear about what a URI identifies
    • Concepts? Classes? Something else?
  4. Publish RDF descriptions of the things you are identifying
  5. Use ‘well-established’ RDF vocabularies as far as possible, extend as appropriate
  6. make commitments to maintaining RDF descriptions, and publish maintenance policies and procedures

Establish a semantic web of terminological / conceptual / ontological data relating to the environment

Hsolbrig N.B. Mayo Position Paper on LSID's describes how URI's are described in HL7 and elsewhere
Hsolbrig N.B. The Life Sciences Identifier (LSID) and the [[1] LSID Project] are different, but related.


Services


  • With a web of data in place, the role of services becomes extremely clear: to provide efficient, convenient, programmatic Interaction with subsets of that web of data.
  • Build a service-oriented architecture on top of a web of data
  • Steps to achieving this:
  1. Analyse and publish functional requirements for service types (I.e. what do I want a service to do?)
  2. Study functional requirements within this community, identify and publish sets of common requirements (basis for standardisation work)
  3. Take a look at SPARQL services & protocol (v. cheap)
    • N.B. true standardisation of a service interface requires a (lightweight, informal, open) community-driven process for developing a web-service specification and building consensus