Warning:
This wiki has been archived and is now read-only.

2011-02-14 Follow up on Linked Open Data discussion

From W3C Unified Service Description Language
Jump to: navigation, search

General

Minutes


Several Options were discussed to deal with the topic of "USDL and Linked Data"

1 TEXO Service Ontology (Daniel)

  • Pro:
    • Ontological analysis to clarify intended meanings of terms
    • also takes into account other phases of service lifecycle + transactional data
    • legal and pricing modules aligned
  • Con:
    • "less intuitive"
    • heavyweight, uses OWL
    • does hardly take into account existing ontologies

2 Light-weight translation approach (Torsten)

  • Pro:
    • same names, semantics as USDL
    • different serialization of USDL
    • might act as starting point
    • for generating the instance data
  • Con:
    • no schema
    • not really linked data
    • does not consider other linked data schemata

3 Harmonising existing ontologies/microformats (Carlos)

  • Pro:
    • Reuse, alignment of existing ontologies
    • thus reuse of existing data (!)
    • potential users can "grab" that data
    • publication and dissemination for free
    • Web advantages
    • Incremental "mapping" possible by adding links later
  • Con:
    • In-depth analysis of all existing ontologies and USDL required
    • mapping required (can be done in handsight)
    • mapping has to be maintained
    • adds complexity because of ties to other ontologies
    • danger of "remodelling" USDL
    • migration possibilities for "older" descriptions required

Dependencies

There are several dependencies between the three options

  • (2) might reused to generate data according to (3). Put functionality behind "RDF" button (serialization into linked data formats)
  • (1) could inform (3), pricing and legal modules of (1) can be reused if we go (3)

Decision

Telco participants voted clearly for option (3) since it leverages most of the advantages of linked data:

  • Roland: (3)
  • John: (3)
  • Carlos: (3)
  • Torsten: (3)
  • Daniel: (3)
  • Norbert: (3)
  • Axel: (3)
  • Kay: -

Next steps

  • Torsten/Carlos: functional module
  • Daniel/Christian/Carlos: legal module
  • Daniel/Uwe: assist Carlos in USDL questions
  • Roland: tests, use cases