[OASIS Issue Tracker] Commented: (CAMP-15) Use message-id and profile rather than uri and namespace

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

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

Adrian Otto commented on CAMP-15:
---------------------------------

This change refers to the expression of error messages in section 5.4. I am requesting two changes:

1) The "uri" attribute implies that each individual error message should be uniquely identified and accessible with a GET request, rather than each error message simply having an identifier that would presumably be logged on the server, but need not be individually accessible by a client at a later time. The payload of the error message should be sufficient, as error messages need not be persisted. They should only need to be returned to clients as a rejection of the requested operation. We should use the filed name "message-id" for this purpose, rather than "uri" to avoid the ambiguity relating to the name "uri".

Instead of the row:

| uri | URI | 0..1 | A unique URI that reference this particular message |

I propose:

| message-id | String | 0..1 | A string containing a unique uuid or error number that references this particular message |

2) The "namespace" attribute should be renamed to "profile". Because http://tools.ietf.org/html/draft-wilde-profile-link, is still a draft, and does not have an RFC number yet, I am reluctant to suggest referencing that until it has one. The content in Table 3 in section 5.4 may be easily confused with the use of the word "namespace" in a different context in Table 4 of section 5.4

Instead of the row:

| namespace | URI | 0..1 | A reference to the standard URI to indicate the meaning of this message |

I propose:

| profile | URI | 0..1 | A reference to the standard URI to indicate the meaning of this message |

Also all content between Table 3 and Table 4, including the content of Table 4 should refer to "profile" instead of "namespace".

> Use message-id and profile rather than uri and namespace
> --------------------------------------------------------
>
>                 Key: CAMP-15
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-15
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Anish Karmarkar
>            Assignee: Adrian Otto
>
> The generic message fields table (line 584 [of v032]) includes "uri" and "namespace." These are both very confusing terms to use; I'd suggest "message-id" and "profile" (see http://tools.ietf.org/html/draft-wilde-profile-link, which is codifying common practice, e.g., from HTML).
> This issue was raised by Adrian Otto and was drupal issue 1080
> This table 3 section 5.4 of the contribution.

-- 
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