Re: [camp-comment] 3.2 Creating an Assembly Template from a PDP (Is Secton 3 normative?)

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

Patrick,

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

~ gp

On 9/5/2013 10:16 AM, Patrick Durusau wrote:

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

Greetings!

At the end of the first paragraph under 3.2 Creating an Assembly
Template from a PDP, I read:

*****
The model might then appear as follows:
*****

In normative text?

I understand the need for informal explanation of possible uses but
those are usually consigned to notes (for brief explanations) and/or
non-normative appendices for longer explanations.

It enables implementers to distinguish between the requirements (the
MUST, SHOULD, MAY, etc.) and the prose that gives them meaning, from
the non-binding and informal explanations about the creation of
implementations that follow those requirements.

Not a good idea to mix the two.

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/

iQIcBAEBAgAGBQJSKLx3AAoJEAudyeI2QFGoRi8P/jTyKm15CuVV7bW9SzmvArEi
G0RQzzqe6dna9kTtRXKiGmZ+53FH6pTnbrg239q6Pe8XtY7XMWuzUXmEfYAOTSQA
DqalKVkgX8gonocD/tmNTQddUXfq/U6E9LMWNQ17CzWvieN2276OxALwtPYaUwuG
kjo6Lz5bwFWipefiI/3q9Kc0Jz3qffmpzCALEwcuZGbG0nBmivfPq09L3PSth1FR
ROpc0D2CM86VFW5G/7Z3lQ1bckdECosWkqSUNEk7E4DIuHoEIisjniRQ/lddYd4p
gfoDKut0TBFDqgtmnOl0ONZ+EnwEpiAReREdxIQrp3eIWbNQLvkOTgDEhgVQ0grm
98lbJyyESgHrlyyIQNe7RfPcuBIxk9XGu35XRGiGcs83kCUOw/MVQEpTeldquvAv
xbKKwj7r6LYnjwuDXD/HxaQ/4Z4vZo3TLidmdx5BuhDyWHgYlZpsM6k59/VtdP3x
mRmh65rapp+ZrnCnRYq8irw0o5bVngMYqK4LJGXOGUHeR88WKwoS3SmhG9oJ6Tuf
MUzydUJalyjOmf9Dqk5s3fUSH/+Lul3eGpqxvkmzwo3mypvgr8H1fnfMmRghF04e
EqW4zmsq8xlO/g/LCWWBiD8y9XFqiyTz45SHE+gy3tCOynwEbYgpHd6yHAoXYwJn
2DwGQhOKMUx1BL0Cej7/
=32+Y
-----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/