Preliminary thoughts on a few of Jacob's latest comments

> 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.

--

--