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

Re: Issue-34 Back_to_Basics proposal

From: Arnaud Le Hors <lehors@us.ibm.com>
Date: Fri, 8 Feb 2013 15:26:26 -0800
To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Message-ID: <OF248EA243.CBAE589B-ON88257B0C.007F5D7A-88257B0C.0080C3C4@us.ibm.com>
Hi Ashok,

For one thing, in John's proposal POST behaves the same way with 
Containers and Aggregations, i.e., creates a resource and adds it as a 
member. This behavior is inherited.

But the class hierarchy could probably be changed depending on what the 
group prefers.
Arnaud  Le Hors - Software Standards Architect - IBM Software Group

Ashok Malhotra <ashok.malhotra@oracle.com> wrote on 02/08/2013 02:35:04 

> From: Ashok Malhotra <ashok.malhotra@oracle.com>
> To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>, 
> Date: 02/08/2013 02:36 PM
> Subject: Issue-34 Back_to_Basics proposal
> John:
> In your proposal, Aggregation is a subclass of Resource and 
> Container is a subclass of Aggregation.
> I'm wondering why you did not make both Aggregation and Container a 
> subclass of Resource.
> That way they would be at the same level.
> Is there some behaviour of Aggregation that is inherited by Container?
> -- 
> All the best, Ashok
Received on Friday, 8 February 2013 23:26:59 UTC

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