Re: Interaction model vs data model

>>> 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
>>> LDPR.
>> 
>> 
>> In the data model,
>> 
>> LDPR:
>>    - has a RDF representation
>> 
>> LDPC:
>>    - has a RDF representation
>>    - has a set of reserved properties with their semantics defined by the
>> protocol
>>    - contains some protocol data
>> 
>> so LDPC is a specialization of LDPR.
>> 
>> In the interaction model,
>> 
>> GET:
>>   LDPR - returns the current state.
>>   LDPC - returns the current state. In addition, provides mechanisms to
>> retrieve only part of the state (non-member properties) and provides
>> additional features like paging, ordering based a special property
>> (membership predicate).
>> 
>> PUT:
>>   LDPR - updates the current state
>>   LDPC - Only part of the state may be updated via
>> <containerURL>?non-member-properties. The rest of the state is managed by
>> the server.
>> 
>> POST:
>>   LDPR - updates it's state by appending new triples ?
>>   LDPC - creates new resources
> 
> and adds it to the membership
> 
>> 
>> DELETE:
>>   LDPR - deletes itself
>>   LDPC - deletes itself and any resources contained by it
>> 
>> LDPC and LDPR have different interaction models but I suppose a
>> specialization can have a different interaction model.
>> 
>> Best Regards,
>> Nandana
> 
> This is simple and clear to me, then again it is the current state of
> the spec (mostly). Nice summary

It could be that I am reading the spec wrong, but, my understanding is that when a LDPR has only one LDPC, it can be that both are the same resource. In that case where does that leave the HTTP operations in the above - esp. PUT and POST ?

Roger

> 
> 
> --
> - Steve Speicher
>