OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (CAMP-71) optionality of 'pdpURI' attribute in AssemblyTemplate is inconsistent

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

Gilbert Pilz commented on CAMP-71:

As of WD21, this would be Section 5.9.4. Also, in the spirit of CAMP-83, we should make this a normative statement:

Platforms are allowed to support, via extensions, packaging formats and registration methods not specified in this specification. Therefore this attribute is not required to be present in the general case. However, when a PDP is used to create an Assembly Template, as specified in Section 6.11, this is a attribute SHALL be present in that Assembly Template.

We also need to apply an analogous change to Section 5.9.5 for dpURI.

> optionality of 'pdpURI' attribute in AssemblyTemplate is inconsistent
> ---------------------------------------------------------------------
>                 Key: CAMP-71
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-71
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Gilbert Pilz
>            Assignee: Gilbert Pilz
>            Priority: Minor
> WD13 specifies the 'pdpURI' attribute of the AssemblyTemplate resource (section 5.8.3) as "Required: false". However, the two mechanisms for creating an AssemblyTemplate described in 6.12 both say: "The server shall include the pdpUri attribute, which identifies the PDP from which the template was created, in the newly created AssemblyTemplate resource." It is inconsistent to describe an attribute as being optional yet require (using normative statements) every implementation to include it.

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]