[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-117) 4.3.3 Artifact Specification
[ http://tools.oasis-open.org/issues/browse/CAMP-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35215#action_35215 ]
Tom Rutt commented on CAMP-117:
-------------------------------
Issue 117 Triage:
On 1) The wording of the first two sentences is inconsistent with other descriptions worded as:
"This type describes an artifact .." followed later in the paragraph by "This node has the following general representation: .."
4.3.3 uses the word "type" instead of "node" in the latter sentence.
Editorial Fix would be to change third sentence in 4.3.3 to read: "This node has the following general representation:"
Should discuss editorial clarification on use of the YAML concept of "node" with the concept of "type" in 4.2.1 TC should ensure we are consistent in the usage of these two terms, node and type, throughout the descriptions in the PDP section.
On 2) this is referring to some other issue, may be related to point 3) as part of this resolution
On 3) He is asking to put the name of the node type in the pseudo-schema.
Is there a justification for our pseudo-schema format to not put a type name at the top line of each description box?
On 4) Is ordering of YAML nodes as described in our pseudo-schema significant for the serialization?
On 5) In 4.3.2 the pseudo-schema for DeploymentPlan lists ArtifactSpecification as +, one or more. The second sentence of 4.3.3 refers to PDP not DP and uses the MAY keyword.
Should discuss a clarification for the conformance requirements in the second sentence in 4.3.3, given the requirement stated in 4.3.2..
> 4.3.3 Artifact Specification
> ----------------------------
>
> Key: CAMP-117
> URL: http://tools.oasis-open.org/issues/browse/CAMP-117
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Bug
> Components: Public Review
> Reporter: Martin Chapman
>
> 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-92
> Currently reads:
> *****
> This type describes an artifact of the application.
> *****
> 1) type -> node? Yes?
> 2) cf my comments on "general representation"
> 3) It isn't clear if this is a production or an example. BTW, I was confused by the example not including the ArtifactSpecification node so I could judge my location in the PDP.
> You write:
> *****
> name: String ?
> description: String ?
> tags: ?
> - String +
> artifactType: String
> content: ContentSpecification
> requirements: ?
> -
> RequirementSpecification +
> *****
> When:
> *****
> ArtifactSpecification
> name: String ?
> description: String ?
> tags: ?
> - String +
> artifactType: String
> content: ContentSpecification
> requirements: ?
> -
> RequirementSpecification +
> *****
> Would be clearer, given the similarity in syntaxes, at least to me.
> For that matter, I would have put the production (if that is what it is) at the end of 4.3.3 and not at the front. So I have all the definitions before it.
> 4) BTW, since artifactType and content are both true, can I then have:
> *****
> ArtifactSpecification
> name: String ?
> description: String ?
> tags: ?
> - String +
> artifactType: String
> requirements: ?
> -
> RequirementSpecification +
> content: ContentSpecification
> *****
> ?
> The ordering of nodes question that I posed earlier in another context.
> 5) The "production" in 4.3.2 DeploymentPlan indicates that ArtifactSpecification occurs at least once or more times. (+) But the language in 4.3.3, addresses an artifact described by the ArtifactSpecification with MAY be located language. Better to move the MAY language elsewhere, say as 4.3.3.4 Location of Artifacts.
--
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]