This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Ecoterm"
Jump to navigation
Jump to search
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] === |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
---- | ---- | ||
Revision as of 19:35, 22 April 2005
Contents
Action Points for the Following Year
The following points are based on a presentation by Alistair Miles at the 2005 Berlin Ecoinformatics meeting.
[[Ecoterm Identity|Identity]
Construction
- Standards for building a ‘good’ terminological/conceptual thing …
- Relevant because if two things constructed according to the same basic principles then likely improve interoperability
- Two new proposed standards …
- BS 8723
- "Structured Vocabularies for Information Retrieval"
- Intended to replace
- ISO 2788-1986 Guidelines for the establishment and development of monolingual thesauri = BS 5723:1987
- ISO 5964-1985 Guidelines for the establishment and development of multilingual thesauri = BS 6723:1985
- Parts relevant to construction …
- Part 2: thesauri
- Part 3: other types of vocabulary
- (Other parts …)
- Part 1: glossary
- Part 4: mapping
- Part 5: “interoperability with applications”
- BS 8723
- ANSI Z39.19
- Guidelines for the Construction, Format, and Management of Monolingual Controlled Vocabularies
- Ballot period April 11 – May 25, 2005
- Abstract
- ANSI Z39.19
- Also …
- Ontology Engineering Patterns TF (SWBPD-WG)
- OWL
- Published various documents:
- Classes as values
- N-ary relations
- Value partitions/value sets
- Simple part-whole relations
- Qualified cardinality constraints
- Ontology Engineering Patterns TF (SWBPD-WG)
- Construction methodology...
- Wiki based, e.g. GEMET?
- Wikipedia
- Decentralised development paradigm
- SkosWiki
Data Model
- Data model influences design of
- data publication formats
- programmatic interfaces
- Data model also determines management and maintenance strategies and procedures
- Data model often implicit in a standard, not formally specified …
- E.g. BS 8723, ANSI Z39.19
- Some ‘standards’ to consider …
- ANSI Z39.19, BS 8723
- "Traditional thesaurus" ...
- model described in prose by BS 8723, ANSI Z39.19
- Only terms reified, concepts implicit
- ANSI Z39.19, BS 8723
- SKOS Core
- Explicitly concept-oriented data model
- Specified formally using RDFS/OWL
- SKOS Core
- OWL
- Class/instance-oriented model (“ontologies”)
- Formally specified via model-theoretic semantics
- OWL
- TMF - Terminology Markup Framework ISO 16642 (ISO TC 37)
- Concept-oriented
- Specified using UML
- Really a framework for designing XML formats
- TMF - Terminology Markup Framework ISO 16642 (ISO TC 37)
- ISO Topic Maps
- Topics, Associations, Occurrences, Roles...
- ISO Topic Maps
Comments:
- ANSI Z39.19, BS 8723, SKOS Core, TMF broadly aligned …
- (I.e. T-O vs. C-O not necessarily at odds)
- however N.B. choice of T-O vs. C-O model as foundation has implications for management/maintenance and URI use.
- Relationship to ontologies (OWL) … ?
- Topic maps … ?
Publication
- General principle: publish data
- XML
- Thesaurus tradition (e.g. Zthes …)
- Terminology (I.e. TC 37) tradition (e.g. TBX, implementation of TMF)
- Topic maps tradition … XTM
- RDF
- SKOS Core
- RDFS/OWL
- OWL
- Based on RDF
- Ontologies for the web
- W3C recommendation
- Comments
- N.B. XTM and anything based on RDF (I.e. SKOS Core, OWL) designed for a distributed information environment
- I.e. use URIs, support data linking, merging
- Others not (designed for point-to-point transfer)
- N.B. XTM and anything based on RDF (I.e. SKOS Core, OWL) designed for a distributed information environment
Services
- Service Oriented Architecture (SOA)
- Important software engineering paradigm
- Web services
- WSDL, SOAP (W3C)
- Web service interface to conceptual/terminological resource …
Lots of individual projects (EOS, UNEP.Net …)
- Standardisation initiatives …
- Some recent work on implementing the SKOS API …
- … but still plenty of issues.
- OMG lexicon query service?
- HL7 Common Terminology Services (CTS)
- ANSI terminology services API?
- XMDR?
- Other attempts to build consensus?
- N.B.
- SOA & WS architecture for distributing programmatic components
- Semantic Web machinery architecture for distributing data
- Complementary
- E.g. a service that provides efficient programmatic access to an aggregation of data harvested from multiple published sources