[OASIS Issue Tracker] Commented: (CAMP-25) Refine link structure

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CAMP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31993#action_31993 ] 

Gilbert Pilz commented on CAMP-25:
----------------------------------

The main problem that I see with the current specification of Link is that, with only the href attribute, there is no information about the resource that the Link is referencing other than what you can infer by the array in which it is contained. For example, if I were interested in working with the "sample.war" Application Component Template (ACT) of a particular Assembly Template, the following:

{
  ...
  "applicationComponentTemplates" : [
    { "href" : "http://platypus.com/camp/ACT/asdf"; },
    { "href" : "http://platypus.com/camp/ACT/sdfl"; },
    { "href" : "http://platypus.com/camp/ACT/rtqw"; }
    { "href" : "http://platypus.com/camp/ACT/xspf"; }
  ]
  ...
}

I would have to iteratively GET each of the ACTs until I found the named "sample.war".

I have put together a proposal (as a red-line diff from WD 02) that adds the mandatory "name" attribute to Link. "name" echoes the value of the "name" attribute of the resource reference by the Link, can be changed by the platform and is *not* writeable by the client.

https://www.oasis-open.org/apps/org/workgroup/camp/download.php/47752/camp-25-2012-12-19.doc

> Refine link structure
> ---------------------
>
>                 Key: CAMP-25
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-25
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Anish Karmarkar
>
> The current standard defines links as a structure that "must contain 'href' and may contain more" such as 'rel', 'type', etc. Depending on the level of HATEOAS support we envision, we may need a more extensive structure that supports "write" operations like POST or PUT and on-the-fly URL construction as in the proposal below.
> [This is drupal issue # 1058 raised by Tobias Kunze]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira