Re: [camp] Groups - camp-spec-v1.1-wd45-173.doc uploaded

[Alex Heneveld <alex.heneveld@cloudsoftcorp.com>]

Hi Michael,

My reasoning is that the philosophy of REST is to include links to 
context so if you are looking at something you can with a single link, 
find out what it pertains to.  Outwith REST you'd usually do this by 
peeling back the path segments of the URL.

We could have sensor_resource point to sensors_resource instead, and 
sensors_resource point to camp_resource, but that felt less useful than 
having the camp_resource that the sensors list, or a sensor, (or an op 
or the ops list) referenced as a link.

Or we could do away with the context, there is no technical requirement, 
but in practice I find it helpful.

--A


On 28/07/2014 16:50, Gilbert Pilz wrote:
> Michael,
>
> This is one of those conversations that I remember having, but whose content and conclusion I can't recall. If I'm not mistaken, Alex Heneveld had some compelling arguments but, again, I can't remember what they were.
>
> ~ gp
>
> On Jul 28, 2014, at 8:09 AM, "Behrens, Michael V CTR DISA PEO-C2C (US)" <michael.v.behrens.ctr@mail.mil> wrote:
>
> > Good points about back pointers Tom, I was not suggesting that however.
> >
> > I'm just wondering about the sensors (plural) to camp_resource as shown in the diagram.   The attribute target_resource is available from both the sensors and the sensor class.  Would having it available from just the sensor be sufficient?  Same question would apply to the link from operations (plural) to camp_resource.
> >
> > ________________________________________
> > From: Tom Rutt [TRutt@us.fujitsu.com]
> > Sent: Friday, July 25, 2014 6:23 PM
> > To: Behrens, Michael V CTR DISA PEO-C2C (US); Gilbert Pilz; camp@lists.oasis-open.org
> > Subject: RE: [camp] Groups - camp-spec-v1.1-wd45-173.doc uploaded
> >
> > Almost all of our associations have navigation in only one direction
> >
> > Maintaining an array of back pointers from CampResource pointing at all its sensors is difficult and unnecessary.
> >
> > The part of the UML model for sensors and operations is attached as a pdf file.
> >
> > We do not put pointers in both directions unless there is a strong need.
> >
> > Tom Rutt
> > ________________________________________
> > From: camp@lists.oasis-open.org [camp@lists.oasis-open.org] On Behalf Of Behrens, Michael V CTR DISA PEO-C2C (US) [michael.v.behrens.ctr@mail.mil]
> > Sent: Friday, July 25, 2014 8:34 PM
> > To: Gilbert Pilz; camp@lists.oasis-open.org
> > Subject: RE: [camp] Groups - camp-spec-v1.1-wd45-173.doc uploaded
> >
> > Looks good Gil.
> >
> > Is the model available?
> >
> > Also, what is the require for the sensors (plural) to have a one to many link to the target resource vice just sensor to resource?  Just checking because the JSON sample seems to have just one link from Sensors to a target resource.  Maybe just having the individual sensor relationship to target resource is sufficient?
> >
> > - Michael
> >
> >
> >
> > ________________________________
> > From: camp@lists.oasis-open.org [camp@lists.oasis-open.org] on behalf of Gilbert Pilz [gilbert.pilz@oracle.com]
> > Sent: Wednesday, July 23, 2014 4:18 PM
> > To: camp@lists.oasis-open.org
> > Subject: [camp] Groups - camp-spec-v1.1-wd45-173.doc uploaded
> >
> > Submitter's message
> > Initial proposal lacking Tom's changes to the UML diagrams. Please check the description of the "characteristics" attribute of the "service resource" as that is the crucial piece of this proposal.
> > -- Mr. Gilbert Pilz
> > Document Name: camp-spec-v1.1-wd45-173.doc<https://www.oasis-open.org/apps/org/workgroup/camp/document.php?document_id=53653>
> > ________________________________
> > Description
> > Proposal for CAMP-173.
> > Download Latest Revision<https://www.oasis-open.org/apps/org/workgroup/camp/download.php/53653/latest/camp-spec-v1.1-wd45-173.doc>
> > Public Download Link<https://www.oasis-open.org/committees/document.php?document_id=53653&wg_abbrev=camp>
> > ________________________________
> > Submitter: Mr. Gilbert Pilz
> > Group: OASIS Cloud Application Management for Platforms (CAMP) TC
> > Folder: Proposals
> > Date submitted: 2014-07-23 13:18:34