This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Ecoterm"

From HL7Wiki
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
=== [[Ecoterm:Publication|Publication]] ===
 
=== [[Ecoterm:Publication|Publication]] ===
  
=== Services ===
+
=== [[Ecoterm:Services|Services]] ===
* Service Oriented Architecture (SOA)
+
----
** Important software engineering paradigm
+
=== Steps toward interoperability ===
* Web services
+
 
** WSDL, SOAP (W3C)
+
[http://ftp.ics.uci.edu/pub/ietf/uri/rfc2396.txt URI's]
* Web service interface to conceptual/terminological resource …
+
----
Lots of individual projects (EOS, UNEP.Net …)
+
# Use URIs
* Standardisation initiatives …
+
# Use URIs well (consistency, persistence, articulated management & maintenance policies etc.)
** Some recent work on implementing the SKOS API …
+
# Be clear about what a URI identifies
** … but still plenty of issues.
+
#* Concepts? Classes? Something else?
** OMG lexicon query service?
+
# Publish [http://www.w3.org/RDF/ RDF] descriptions of the things you are identifying
** HL7 Common Terminology Services (CTS)
+
# Use ‘well-established’ RDF vocabularies as far as possible, extend as appropriate
** ANSI terminology services API?
+
# make commitments to maintaining RDF descriptions, and publish maintenance policies and procedures
** XMDR?
+
 
** Other attempts to build consensus?
+
Establish a semantic web of terminological / conceptual / ontological data relating to the environment
* N.B.  
+
 
** SOA & WS architecture for distributing programmatic components
+
[[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>
** Semantic Web machinery architecture for distributing data
+
[[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>
** Complementary
+
 
*** E.g. a service that provides efficient programmatic access to an aggregation of data harvested from multiple published sources
+
 
 +
 
 +
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