[OASIS Issue Tracker] Created: (CAMP-131) 4.3.5 ContentSpecification - URI schemes...

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

4.3.5 ContentSpecification - URI schemes...
-------------------------------------------

                 Key: CAMP-131
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-131
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Bug
          Components: Public Review
            Reporter: Gilbert Pilz


From the comment list: https://lists.oasis-open.org/archives/camp-comment/201309/msg00078.html 
TAB issue: https://tools.oasis-open.org/issues/browse/TAB-106

4.3.5 ContentSpecification reads in part: 

***** 
For IANA-assigned URI schemes (e.g. "http", "https", "ftp", etc.) the Provider SHALL engage the protocol as per the relevant spec. [PDP-26] Providers SHALL support the "http" and "https" URI schemes. [PDP-27] A Provider MAY support additional URI schemes. [PDP-28] 
***** 

The first two sentences are confusing. 

First, we have an incomplete list of IANA-assigned URI schemes, ..."the Provider SHALL engage the protocol..." 

Second, we have http and https as "Providers shall support.." 

At least redundant, vague by omission of current IANA-assigned URI schemes, and what other URI schemes do you have in mind?

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