[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (CAMP-125) 4.3.5 ContentSpecification - type defines content? use of SHALL
[ http://tools.oasis-open.org/issues/browse/CAMP-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Chapman updated CAMP-125:
---------------------------------
Description:
4.3.5, first line reads:
*****
This type defines the content of a component. Content Specifications SHALL declare either a String attribute "href" that references the content or a String attribute "data" whose value is the data or, but not both. [PDP-25] It has the following, general representation:
*****
The general representation is misleading. Or at least I think it is. ;-)
It implies href: URI or data: string.
But, from 4.3.3.2 content, we learn it should be:
content: href or
content: data
Yes? True they are both holders for particular types but given the overlap of model and syntax, it is rather confusing.
Assuming that makes sense, suggest something like:
The ContentSpecification type has one of two, mutually exclusive, values: href or data.
BTW, I would not mix type discussions with nodes. Too easy to slip from one to another.
> 4.3.5 ContentSpecification - type defines content? use of SHALL
> ---------------------------------------------------------------
>
> Key: CAMP-125
> URL: http://tools.oasis-open.org/issues/browse/CAMP-125
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Bug
> Components: Public Review
> Reporter: Gilbert Pilz
>
> 4.3.5, first line reads:
> *****
> This type defines the content of a component. Content Specifications SHALL declare either a String attribute "href" that references the content or a String attribute "data" whose value is the data or, but not both. [PDP-25] It has the following, general representation:
> *****
> The general representation is misleading. Or at least I think it is. ;-)
> It implies href: URI or data: string.
> But, from 4.3.3.2 content, we learn it should be:
> content: href or
> content: data
> Yes? True they are both holders for particular types but given the overlap of model and syntax, it is rather confusing.
> Assuming that makes sense, suggest something like:
> The ContentSpecification type has one of two, mutually exclusive, values: href or data.
> BTW, I would not mix type discussions with nodes. Too easy to slip from one to another.
--
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]