OASIS Emergency Management TC

  • 1.  IPAWS Profile Schema

    Posted 02-16-2009 15:38
    Hi,
    	The IPAWS Profile draft submitted to the TC for consideration has some comments in the included XML Schema that I want to bring up.  The profile schema is a derivative of CAP 1.1 in that it uses the same base schema and adds additional profile constraints.  There are some profile requirements that cannot be expressed using a schema and are not present.  Others can be expressed easily, and some require further levels of detail and complexity.  The comments in the schema note that some requirements such as timezones in the dateTime values could be expressed using regular expressions but would add some complexity not normally found in previous TC schemas.
    	I support adding these requirements to the schema as regular expressions to clearly articulate the additional constraints of the profile versus CAP 1.1.  Are there any concerns from other members about doing this, or perhaps an alternate method of achieving the same goal in the schema?
    
    -- 
    jake@jpw.biz
    --
    


  • 2.  Re: [emergency] IPAWS Profile Schema

    Posted 02-16-2009 16:02
    Thanks Jacob,
    
    I just sent a message that includes this, along with the invitation 
    for corrections, comments, suggestions. You beat me to the send 
    button. ;-)
    
    Cheers,
    Rex
    
    At 10:35 AM -0500 2/16/09, Jacob Westfall wrote:
    >Hi,
    >	The IPAWS Profile draft submitted to the TC for consideration 
    >has some comments in the included XML Schema that I want to bring 
    >up.  The profile schema is a derivative of CAP 1.1 in that it uses 
    >the same base schema and adds additional profile constraints.  There 
    >are some profile requirements that cannot be expressed using a 
    >schema and are not present.  Others can be expressed easily, and 
    >some require further levels of detail and complexity.  The comments 
    >in the schema note that some requirements such as timezones in the 
    >dateTime values could be expressed using regular expressions but 
    >would add some complexity not normally found in previous TC schemas.
    >	I support adding these requirements to the schema as regular 
    >expressions to clearly articulate the additional constraints of the 
    >profile versus CAP 1.1.  Are there any concerns from other members 
    >about doing this, or perhaps an alternate method of achieving the 
    >same goal in the schema?
    >
    >--
    >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
    


  • 3.  Re: [emergency] IPAWS Profile Schema

    Posted 02-16-2009 16:02
    Thanks Jacob,
    
    I just sent a message that includes this, along with the invitation 
    for corrections, comments, suggestions. You beat me to the send 
    button. ;-)
    
    Cheers,
    Rex
    
    At 10:35 AM -0500 2/16/09, Jacob Westfall wrote:
    >Hi,
    >	The IPAWS Profile draft submitted to the TC for consideration 
    >has some comments in the included XML Schema that I want to bring 
    >up.  The profile schema is a derivative of CAP 1.1 in that it uses 
    >the same base schema and adds additional profile constraints.  There 
    >are some profile requirements that cannot be expressed using a 
    >schema and are not present.  Others can be expressed easily, and 
    >some require further levels of detail and complexity.  The comments 
    >in the schema note that some requirements such as timezones in the 
    >dateTime values could be expressed using regular expressions but 
    >would add some complexity not normally found in previous TC schemas.
    >	I support adding these requirements to the schema as regular 
    >expressions to clearly articulate the additional constraints of the 
    >profile versus CAP 1.1.  Are there any concerns from other members 
    >about doing this, or perhaps an alternate method of achieving the 
    >same goal in the schema?
    >
    >--
    >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