<Ashok> chait Ashok Malhotra

Ashok: Continue our work

<scribe> scribenick: mhausenblas

<scribe> chair: Ashok

<scribe> Meeting: RDB2RDF XG F2F Karlsruhe

Creating Identifiers

Ashok: Add requirement 'The language must allow for a mechanism to create identifiers for DB entities'

Themis: liasion with the OKKAM project that do ENS

Orri: should promote the reuse of identifiers

Themis: use unquie IDs, that is one URI for an entity rather than minting own URIs and connecting it via owl:sameAs

Orri: though owl:sameAs is not a good thing it is necessary

Michael: I have an action on this

Ashok: reuse for 'long-lived' entities such as persons, corporations
... propose to phrase the requirement as follows
... 'The language must allow for a mechanism to create identifiers for DB entities. Where possible, the language will encourage the reuse of public identifiers for long-lived entities such as persons, corporations.'

RESOLUTION: 'The language must allow for a mechanism to create identifiers for DB entities. Where possible, the language will encourage the reuse of public identifiers for long-lived entities such as persons, corporations.'

Ashok: we will coopertate with OKKAM on that

Other Language Requirements

Ashok: propose to state that we will 'standardize a language for mapping RDB languages to RDF/OWL'

Soeren: learning curve should be low

Juan: Should have different levels/profiles

Michael: +1

Ashok: 'The language will have a human-readable syntax as well as an XML or RDF syntax'

Orri: add to this that 'the output will be described by of an RDFS/OWL schema'

<juan> Juan: +1

Michael: important to offer different levels of expressivity for different use cases

Ashok: so we add 'It should be possible to subset the language for simple applications such as Web 2.0. The language will be validated by creating a library of mappings for widely used apps such as Drupal, Wordpress, phpBB.'

Michael: the lib can then be used for our test cases as well (volunteer to take over that part ;)

Jenny: So we are not being explicit about XML or RDF?

Michael: could use GRDDL to connect these both

Orri: using XML as a base and provide a possibly non-complete mapping to RDF

Ashok: 'The language will have a human-readable syntax as well as an XML and RDF representation for purposes of discovery and automatic generation'

Michael: +1

<juan> Juan: +1

RESOLUTION: The language will have a human-readable syntax as well as an XML and RDF representation for purposes of discovery and automatic generation.

Ivan: we should add 'language should be complete regarding the expressivity of relational algebra'

Ashok: ok, let's move on ... 'the language will allow customization wrt names, data manipulation.'

Orri: extensibility is important

Ashok: 'the language must be able to expose vendor specific SQL features such as full-text, spatial support, user-defined datatypes.'

Michael: +1

Ashok: 'The mapping should allow the introduction of additional semantics, for example sub-classes, sub-properties, transitivity by utilising logics such as rules or DL languages.'

Michael: +1

<Cathy> +1

<juan> Juan: +1

RESOLUTION: 'The mapping should allow the introduction of additional semantics, for example sub-classes, sub-properties, transitivity by utilising logics such as rules or DL languages.'

Ashok: Two more issues left
... include non-relational data?

[[Discussion of possible use cases such as spreadsheets, etc. - the XG thinks that we will not address this]]

Ashok: last (motivated by Bijan's presentation)
... 'language spec should include guidance to mapping to a sbu-set of OWL such as OQL/QL or OWL/RL'

Michael: If we want to include that we need to be aware of the fact that the test cases are actually for agreeing on the concrete impact of a certain language feature. The spec is human-readable, implementors have some freedom in implementing it.

Ashok: 'the WG must track the evolution of SPARQL and liaise with the DAWG'

Michael: +1
... what about linked data?

Orri: propose to add 'the language should be designed to support the implementation of the linked data principles http://www.w3.org/DesignIssues/LinkedData.html'

<scribe> ACTION: Ashok to produce a summary of the agreed issues (requirements) on the Wiki and send it to the XG for reviewing [recorded in http://www.w3.org/2008/10/31-RDB2RDF-minutes.html#action01]

This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/defined in terms/described by/
Succeeded: s/princinpes/principles/
Found ScribeNick: mhausenblas
Inferring Scribes: mhausenblas
Present: Cathy Ashok Juan Jenny Michael Matthias Ivan Yrjana Soeren Orri
Got date from IRC log name: 31 Oct 2008
Guessing minutes URL: http://www.w3.org/2008/10/31-RDB2RDF-minutes.html
People with action items: ashok