Folks,
I had though that only CAP messages of <scope> ="Public" could be IPAWS Profile compatible.
It was recently pointed out to me that the public pronouncement in the IPAWS Profile spec only applies to the <info> block, to wit: " All <info> blocks SHALL be appropriate
for immediate public release."
Does this mean that I could create a IPAWS CAP profile message of scope <private> or <restricted> to control who gets the CAP message itself so long as the <info> block of the message is defined to be publicly usable as desired by the prescribed recipients? Or did we just leave out the requirement for <scope> = "Public"?
R/s