[emergency-cap-profiles] Re: parameter valueNames

[Rex Brooks <rexb@starbourne.com>]

Thanks Jacob,

This is what I was thinking, and should have put into the doc, but I 
decided it was better to get it out this morning so folks have it to 
chew over before Thursday. However, I forgot that I would be 
unavailable Thursday with the all-day Connectivity Week 
adoption-related event.

I will write to the SC in a separate note about that to get the 
Subject Line correctly identifying the subject.

I would suggest that we include the two sentences in a Profile Note, 
perhaps in the column of the row that refers to Table 2 since it does 
not specifically relate to the four <parameter> rows, which still 
need to be given some thought in terms of how the specific issues are 
presented.

Cheers,
Rex

At 11:43 AM -0400 6/8/09, Jacob Westfall wrote:
>  > down to just what should be used for the "reserved" parameter
>>  valueNames? It would also be helpful if this came with a suggestion
>>  of where to put it in the Table 2 >parameter> details that I've
>
>I was thinking some wording on reserved valueNames would be put in 
>an "Implementation Notes" section versus in the table itself.  There 
>may be other items that could fit better in a new section like this 
>as well.  Here is some wording I'd sent through before,
>
>The valueNames "SAME", "EAS-ORG", "EAS-Must-Carry", and "CMAMtext" 
>are reserved by the profile.  Implementers intending to use the 
>IPAWS Profile should ensure that conflicting uses for these 
>valueNames does not occur.
>
>--
>jake@jpw.biz
>--
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  Follow this link to all your TCs in OASIS at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670