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

Re: Issue-34 Back_to_Basics proposal

From: Ashok Malhotra <ashok.malhotra@oracle.com>
Date: Fri, 08 Feb 2013 18:37:57 -0500
Message-ID: <51158C55.8070307@oracle.com>
To: public-ldp-wg@w3.org
Right!   But the deletion behavior is different and not inherited.
That's why is was thinking of Aggregation and Containers at the same level.
All the best, Ashok

On 2/8/2013 6:26 PM, Arnaud Le Hors wrote:
> 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 PM:
>
> > 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:38:33 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 May 2013 13:44:29 UTC