W3C home > Mailing lists > Public > public-ldp-wg@w3.org > January 2013

Interaction model vs data model

From: Arnaud Le Hors <lehors@us.ibm.com>
Date: Wed, 23 Jan 2013 17:08:32 -0800
To: public-ldp-wg@w3.org
Message-ID: <OFFC29E658.871E018D-ON88257AFD.00030B12-88257AFD.000646F2@us.ibm.com>
There seems to be some confusion in the discussions as to what we can do 
and what we can't which comes from different views of what LDP is about.

Discussing whether LDPCs are a subclass of LDPRs, Henry wrote [1]: "they 
are not, since POSTing a Graph on an LDPR is very different from POSTing 
on an LDPC, and since RDF is a logical vocabulary that does not work with 
the concept of method overloading. "

I have to admit not to understand this statement at all and, maybe it's 
just me but, I actually believe that clarifying this might help us a great 
deal with the ongoing discussions around the interaction and data models.

RDF doesn't have the concept of methods, so it certainly doesn't have the 
concept of method overloading, but this merely concerns the data model. I 
don't understand why this would prevent us from defining different ways of 
handling HTTP verbs depending on the type of LDP resource we deal with - 
an LDPR or LDPC. I would say this only concerns the interaction model and 
the RDF data model doesn't prevent us from doing so.

For what it's worth, section 5.2.1 of the LDP spec [2] states that "A 
Linked Data Platform Container must also be a conformant Linked Data 
Platform Resource." I've always read that as meaning that an LDPC is an 

What am I missing?

[2] http://www.w3.org/TR/2012/WD-ldp-20121025/#general-1
Arnaud  Le Hors - Software Standards Architect - IBM Software Group
Received on Thursday, 24 January 2013 01:09:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:44 UTC