ISSUE-16 (subjectMap cardinality): Should we allow multiple subjects for a logical table row? Also, what if no subject is specified? [R2RML]

ISSUE-16 (subjectMap cardinality): Should we allow multiple subjects for a logical table row? Also, what if no subject is specified? [R2RML]

http://www.w3.org/2001/sw/rdb2rdf/track/issues/16

Raised by: Ivan Herman
On product: R2RML

Ivan asked this question in his comments [1]. (See the email exchanges since then [2] [3] for more info.):

"
---
Issue (maybe to be labelled as suchy in the tracker and added to the text?): what happens exactly when, say, SubjectMapClass is missing for a TriplesMapClass instance? We may not have to answer this in the document, but label that as an issue to be solved (and I guess those are the connection point to the direct mapping!)

---
Similar question: what happens if the user adds more than one subjectMaps? I know there is a table at the end of the document that sets maximum cardinality for things. But there is no statements on what the error response of an R2RML processor should be if those cardinality constraints are breached. Taking into account that an R2RML instance is in RDF, we cannot rely on, say, the order within the specification (ie, something like the second coming wins). 

We may just open an issue and label it as such in the document for now, b.t.w.
"

[1] http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2010Dec/0017.html
[2] http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2010Dec/0025.html
[3] http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2010Dec/0028.html

Received on Monday, 24 January 2011 18:10:04 UTC