Re: [camp-comment] 1.6 Terminology - normative text

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

Patrick,

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

~ gp

On 9/5/2013 8:12 AM, Patrick Durusau wrote:

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

Greetings!

In 1.6 Terminology, the following text is embedded in the second
paragraph of that section:

*****
All text except examples, unless otherwise labeled, is normative. All
examples are non-normative.
*****

Rather than embedding this text in the terminology section, I would
suggest a separate section on normative text.

For example:

Normative Text

All the text of this specification is normative with the following
exceptions:

1) Sections or sub-sections that are labeled: (Non-Normative).

2) All examples are non-normative without labeling.

?

I have questions about other items or sections being non-normative or
not but I will raise those as appropriate.

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/

iQIcBAEBAgAGBQJSKJ9EAAoJEAudyeI2QFGoE6UQAOTBXduHWPmn3oJXpvBH9NHX
849hHN+2YJlwdVyU8MhWZTf7BI17/02lAcUXmxwF1j2eDFYLDbCy2yJ7iOyZw7G2
nzJDdHAIvBFLm4LGpuuYcbQtiOR0CNklTUyKyZ8JM8OauFawLBmZiz+QWLwnzTAi
Uf3Gp17eNNVmntjd8A3sa5ptADkjN51coaVUchXRtDSKF2gzxbQpYTIzEzl1MYqh
Oy2dLqAIVoO8LfcaD11KmtMr8tUldfjJX0QT15cVZZfa350tGthVTX9UcpYUc/z9
fZOYswXzCueSioZWBFSFmYWr2bXxr+Ik7tE8B2nLTyvf6Hhyay0uGbD96a9eox7j
2RkzeBAE5LwTywvgt7D9zFOi2GNPEQjdjXd/GZmlEYtP6Lc/hBAveWXYXY3fXC3D
GC4RVFkJSh7FPUuQqspIC1MEOAIeMGwYc7jJkFFjIEjEF8WA+NrQWsSJOibLzAtn
jNTHXkBWO/gFk781YKyvcxvG+vRcFBqGFnwB/EH8s2+ElRLigqGxNSWjpicX6Ztp
7eQbWyvuOuEq0Tp0wjZRi/5cn1QNIatFPAYaL/wR+5zZHYCVeWVGFlnxKMbmlW+c
q2aweSJPc2DXV1f/SP2FdaitWzsnA9hJyU4E78e6Ch8g70HbGwsDyynBAQpW2PTS
sBkjTKL2vMGiymK7C3t5
=4io2
-----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/