[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-315) A Few Editorial Comments/Suggestions Received (against v1.1 CS01 Final)
[ https://issues.oasis-open.org/browse/TOSCA-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lipton updated TOSCA-315:
------------------------------
Description:
From the commenter (Mike Gerdts) received via TOSCA TC comment email portal based on TOSCA-Simple-Profile-YAML-v1.1-csd01-final (comments removed).docx (https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/58781/TOSCA-Simple-Profile-YAML-v1.1-csd01-final%20(comments%20removed).docx):
Line 3: Specification misspelled
Section 11.1.15.3: the wordpress node_template calls "get_input:
context_root". context_root is not a defined input.
Section 11.1.7.3: Parts of the yaml use the Normal style where they should use Code Snippit. This happens in the description and "topology_template:".
I'm not sure how standard the yellow highlight in the "code snippit"
areas is across OASIS documents. A long while back I did the same thing and found that when printed on a black and white printer that the yellow highlight was not distinguishable from the gray background. I solved this by adding a style that did the yellow shading (nice for pdf
viewing) and a wavy underline (distinguishable in b&w print). I don't feel strongly that the document should be changed in this way, just sharing experience in case this improves the usability for tree killers.
was:
From the commenter (Mike Gerdt) based on TOSCA-Simple-Profile-YAML-v1.1-csd01-final (comments removed).docx (https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/58781/TOSCA-Simple-Profile-YAML-v1.1-csd01-final%20(comments%20removed).docx):
Line 3: Specification misspelled
Section 11.1.15.3: the wordpress node_template calls "get_input:
context_root". context_root is not a defined input.
Section 11.1.7.3: Parts of the yaml use the Normal style where they should use Code Snippit. This happens in the description and "topology_template:".
I'm not sure how standard the yellow highlight in the "code snippit"
areas is across OASIS documents. A long while back I did the same thing and found that when printed on a black and white printer that the yellow highlight was not distinguishable from the gray background. I solved this by adding a style that did the yellow shading (nice for pdf
viewing) and a wavy underline (distinguishable in b&w print). I don't feel strongly that the document should be changed in this way, just sharing experience in case this improves the usability for tree killers.
> A Few Editorial Comments/Suggestions Received (against v1.1 CS01 Final)
> -----------------------------------------------------------------------
>
> Key: TOSCA-315
> URL: https://issues.oasis-open.org/browse/TOSCA-315
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Bug
> Reporter: Paul Lipton
> Priority: Minor
>
> From the commenter (Mike Gerdts) received via TOSCA TC comment email portal based on TOSCA-Simple-Profile-YAML-v1.1-csd01-final (comments removed).docx (https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/58781/TOSCA-Simple-Profile-YAML-v1.1-csd01-final%20(comments%20removed).docx):
> Line 3: Specification misspelled
> Section 11.1.15.3: the wordpress node_template calls "get_input:
> context_root". context_root is not a defined input.
> Section 11.1.7.3: Parts of the yaml use the Normal style where they should use Code Snippit. This happens in the description and "topology_template:".
> I'm not sure how standard the yellow highlight in the "code snippit"
> areas is across OASIS documents. A long while back I did the same thing and found that when printed on a black and white printer that the yellow highlight was not distinguishable from the gray background. I solved this by adding a style that did the yellow shading (nice for pdf
> viewing) and a wavy underline (distinguishable in b&w print). I don't feel strongly that the document should be changed in this way, just sharing experience in case this improves the usability for tree killers.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]