OASIS Emergency Management TC

  • 1.  schemaLocation for validating local copies of standards

    Posted 03-25-2007 14:28
    Hi Everyone,
    
    One of my action items from last week's TC meeting was to post a 
    message detailing how to provide and specify a locally stored copy of 
    an XMS Schema from a standard rather than requiring a parser to find 
    the document on the web in order to validate it.
    
    The problematic part of validating The XML Schema from standards is 
    that you must cite the namespace. This is specified as a URN (Uniform 
    Resource NAME), which is pretty straightforward since we are 
    specifying a NAMEspace. However, a urn just specifies the legal 
    provenance of the NAME.
    
    This is the point that is usually missed.
    
    You should also specify a URL to the "schemaLocation." If you specify 
    the location where the standard is supposedly, or is supposed to be 
    kept you can get into trouble if the site is down for maintenance or 
    under a denial-of-service attack. Plus you would be wasting bandwidth 
    that is especially important during an emergency incident.
    
    If your system's validator can't validate the schema from the remote 
    location, your system could break. So it is better to keep a local 
    version, which also gives you complete control over the correct 
    versioning for your applications.
    
    You should keep a correct version of any standard or set of standards 
    your system uses, or that are included within other standards your 
    system uses. However, you still need the schema(s) as separate .xsd 
    files because these are the files you specify in the "schemaLocation" 
    which allows your validator to validate the schema locally and 
    prevent inadvertent failures of the kind mentioned above.
    
    For reference, here's an example:
    
    http://www.stylusstudio.com/w3c/schema0/schemaLocation.htm
    
    For CAPv1.1Errata you need the file: cap1.1.xsd
    
    Here's a sample of what I would use:
    
    


  • 2.  RE: [emergency] schemaLocation for validating local copies of standards

    Posted 03-27-2007 13:22
    Hey Rex (any everyone else),
    
      The Adoption SC would love any ideas or content you'd like to work on
    as part of an instructional cookbook.  I'm planning on putting together
    some coding examples for the .NET platform of standard operations that
    are part of working with the standards.  If there are any other coders
    out there that would like to contribute examples for other platforms
    please let me know. (Java would be a big help).  Some ideas I've had for
    examples are:
    
    1. Generating proxy classes from a schema.
    2. Validating an xml string against a schema.
    3. Consuming a web service that uses one of the standards.  DM OPEN
    would probably be the first choice. 
    
    --Josh
    
    Joshua Shows
    
    Software Engineer
    
    Emergency Services integrators (ESi)
    
    699 Broad St, Suite 1011
    
    Augusta, GA 30901
    
    706-823-0911
    
    jshows@esi911.com
    
    
    


  • 3.  RE: [emergency] schemaLocation for validating local copies of standards

    Posted 03-27-2007 14:56
    Josh,
    
    I think that's a great idea. I'll try to round up some Java for you.
    
    Patti
    
    Patti Iles Aymond, PhD 
    Senior Scientist, Research & Development 
    Innovative Emergency Management, Inc.
    Managing Risk in a Complex World
    
    8555 United Plaza Blvd.   Suite 100 
    Baton Rouge, LA 70809 
    (225) 952-8228 (phone) 
    (225) 952-8122 (fax) 
    
    


  • 4.  RE: [emergency] schemaLocation for validating local copies of standards

    Posted 03-27-2007 19:10
    I am also updating my code samples.  I use Arts caplib for parsing the
    XML in CAP.  I also use Joda-time (this is new as of today) to do any
    time related calculations as well as proper ISO string formatting.  Joda
    Time get around all the BS of the Java Calendar class AND lets you
    import from and export to a Calendar. Joda-time will be useful for all
    Java users  of our standards regardless of whether they also connect to
    DM-OPEN.  I have already found it immensely useful for debugging our
    time related query issues.  (I find the Java Calendar to be almost
    useless in that its results when dealing with multiple time zones seem
    to me to be incomprehensible and inconsistent. Maybe it is just me. But
    Joda time works and is designed for ISO 8601) 
    
    The link:
    
    http://joda-time.sourceforge.net/index.html
       
    
    
    Gary A. Ham 
    Senior Research Scientist
    Battelle Memorial Institute
    540-288-5611 (office)
    703-869-6241 (cell)
    "You would be surprised what you can accomplish when you do not care who
    gets the credit." - Harry S. Truman