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] (CAMP-223) 4.2.1 Types "encouraged" -> SHOULD?

    [ https://issues.oasis-open.org/browse/CAMP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67218#comment-67218 ] 

Anish Karmarkar commented on CAMP-223:

The TC agreed that this required no change. We don't quite know what kinds of "namespaces" will be used. Will have to wait till best practices emerge.
See https://www.oasis-open.org/apps/org/workgroup/camp/download.php/61273/20170720Minutes.txt

> 4.2.1 Types "encouraged" -> SHOULD?
> -----------------------------------
>                 Key: CAMP-223
>                 URL: https://issues.oasis-open.org/browse/CAMP-223
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>         Environment: Normative
>            Reporter: Chet Ensign
> 4.2.1 in addition to being a disclaimer of what CAMP (this specification?) does not define, contains the following:
> "...To promote portability, both providers and consumers of the CAMP API are encouraged to namespace-qualify the types that they use....."
> Isn't that a normative SHOULD?

This message was sent by Atlassian JIRA

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