Re: [camp-comment] 4.3.1 General Attributes

[GILBERT PILZ <gilbert.pilz@oracle.com>]

Patrick,

This comment has been captured as Jira issue CAMP-109 and will be processed by the TC. We will inform you when this issue has been resolved.

~ gp

On 9/5/2013 12:41 PM, Patrick Durusau wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

The text of 4.3.1 General Attributes reads:

*****
The following nodes may appear as elements of the Deployment Plan,
Artifact Specifications, or Service Specifications.
*****

Which is puzzling because 4.3 Deployment Plan Schema provides (last
sentence):

*****
Note the description of the structures and
information in this section utilizes YAML’s nomenclature.
*****

In addition to needing to be a note, there is a claim that YAML
nomenclature is being used.

I mention that because of:

"...may appear as elements of the..."

YAML does not use the term "elements."

If keeping the hanging paragraph for 4.3.1 General Attributes is
important, I would say:

*****
Deployment Plans, Artifact Specifications and Service Specifications
may contain the nodes defined in 4.3.1 General Attributes.
*****

Hope everyone is having a great day!

Patrick

- -- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Former Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSKN5zAAoJEAudyeI2QFGoVUsP/3VNyVPLIfykxVlLR74+RlDf
CtibL6vLXyE8hUnB/eCzGWEByFxBC6hueyKAWmtFUlWSOVEI+paxgTjVtDdDAxsb
VEmK1NMWcIYQa49LTtNuWONQ1t8tKlnQDJJdcNkHukNtxXdr/nXX3Kr2Osn0zvnx
JkQV0UD50II4UhI8iTBEVO8sUaD6ox/gyBznDf6jy9BxOANDrK91tyxurRNSL8XL
4ZJnfTUicCZm4ryK9xjPjjcLmzFHPMEscOvovlv5e01i9yReGlCzPFCjOUyjqLby
4D0u0FgcYaEYvfTzKJdvoxZNaA3OUh8tnx9v9S5ViU6BujSwwHUhXGURIDfXsFzF
8VVs5D+GqBORtPpCxWIEYSK7xdcvgd/LI3WzuxAtSbxNzTlOKOrCKtToN7oJPi17
aBBJI5hCwnT5OYawd3EPCmF9xR8JKkBboEmVyonMQWcZa1cOKVF4Fipy/fnMWB00
gudxyGb7UhYJDXYcS8l26YCaZwcYxcfStHTjQssCcF9LPJAFMGq4jgNKg/34fzq3
u+G26t2sy2sGZ8B3y5p2Qid0cbl++ANbAuVQ4C3t2vGWAVaFiMOrpRu0ch7QjGla
XX0ZD31NTzVgAZS3Fhho2QErbdrqpQ4ry7IcfhVBWPThUnWkAMdzJltiXiYOErOw
vpsDSFWLfY13bB87sOn0
=Vjxf
-----END PGP SIGNATURE-----

--

This publicly archived list offers a means to provide input to the

OASIS Cloud Application Management for Platforms (CAMP) TC.



In order to verify user consent to the Feedback License terms and

to minimize spam in the list archive, subscription is required

before posting.



Subscribe: camp-comment-subscribe@lists.oasis-open.org

Unsubscribe: camp-comment-unsubscribe@lists.oasis-open.org

List help: camp-comment-help@lists.oasis-open.org

List archive: http://lists.oasis-open.org/archives/camp-comment/

Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf

List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Committee: http://www.oasis-open.org/committees/camp

Join OASIS: http://www.oasis-open.org/join/