OASIS Emergency Management TC

Identifier, Sender and References appear to clash in V1.1 (Also, what about whitespace?)

  • 1.  Identifier, Sender and References appear to clash in V1.1 (Also, what about whitespace?)

    Posted 01-31-2005 18:26
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    emergency message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: Identifier, Sender and References appear to clash in V1.1 (Also, what about whitespace?)


    It appears that alert:identifier and alert:sender in both CAP V1.0 and the
    draft V1.1 are underspecified.
    
    alert:identifier is defined in part as: "MUST NOT include spaces or
    restricted characters (< and &)"
    alert:sender is similarly defined. 
    
    alert:references is defined in part as: "The extended message identifier(s)
    (in the form identifier/ sender) of an earlier message or messages
    referenced by this one."
    
    The problem here is that it appears that "/" is a valid character for use in
    both alert:identifier and alert:sender, however, "/" has semantic meaning
    when included in alert:references. Given this conflict, it would be most
    sensible to include "/" in the list of restricted characters that cannot be
    used in either alert:identifier or alert:sender. Without such a restriction,
    it is not possible to parse alert:references to pick out the identifier and
    sender portions. This will make it exceptionally difficult for some systems
    to identify which message is being updated, cancelled, etc.
    
    If identifier is "message/1" and sender is "tom/bombadil@foo.bar" the
    extended message identifier would be:
    	message/1/tom/bombadil@foo.bar
    It is not possible to determine which part of that extended identifier is
    the identifier and which part is the sender...
    
    One more question: In the text definition of the extended message identifier
    of alert:references, there is a space following the "/" between "identifier"
    and "sender". Is this space required or otherwise meaningful? Is it
    permitted? This also raises a question concerning whitespace in
    alert:identifier and alert:sender. Is leading, trailing or embedded
    whitespace permitted in these elements? If so, is leading or trailing
    whitespace significant? Note: A "normal" Internet specification would
    include ABNF specifications for these bits and thus eliminate questions such
    as these... Grumble...
    
    		bob wyman
    
    
    
    
    


    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]