RE: [emergency] update for EDXL DE xsd and Sample xml

["Sylvia Webb" <swebb@gefeg.com>]

I loaded the schema in EDIFIX. It uses Xerces for validation. No errors were
reported. It doesn't validate instance documents but it does create them
from the schema. If someone has a compare tool, they can easily find any
differences. I didn't take the time to key in Dave's sample data to produce
a realistic example.

Sylvia 

-----Original Message-----
From: Ellis, David [mailto:dellis@sandia.gov] 
Sent: Sunday, August 14, 2005 2:31 PM
To: Michelle Raymond; emergency@lists.oasis-open.org
Cc: Ellis, David
Subject: RE: [emergency] update for EDXL DE xsd and Sample xml

EMTC

I have added to my Radiation Example and also done some addition work on the
schema.  I would appreciate everyone with an XML validation tool to examine
them both in detail.  I created them with my Microsoft Visual Studio 2005
Beta 2 software.  I used it because the production Visual Studio 2003 will
not allow a <choice> in a <sequence> of elements.  When I used the <group>
element it validated but was obviously an artifact of the older Microsoft
software.  I am also no expert of XML schema and would still like to provide
flexibility in the EDXLDistribution schema for include namespaces for
validating <ContentObject> XML and wrapping the contents of
<namespacedXMLcontent> with encryption and signature capability.

Please review this and let me know what your tools determine.

David E. Ellis
Information Management Architect
(505) 844-6697

-----Original Message-----
From: Michelle Raymond [mailto:michellearaymond@gmail.com]
Sent: Thursday, August 11, 2005 11:34 PM
To: Emergency_Mgt_TC TC
Subject: [emergency] EDXL DE xsd and Sample xml and latest draft

EMTC,

I'm a bit delayed on sending the full draft due to schema validation issues.
I think they are resolved in the files sent.

Dave did a great job putting the schema together.  I still had issues with
the <group> element followed by a <choice> in three validation tools.  By
removing the <group> as a wrapper, it 'seems' to have resolved the issue.  I
am no expert on xml schema 'model groups', 'partitions' or the like. We're
likely to get (hopefully constructive) comments on the schema format during
review.

In the Specification Draft, Section 3.2: Data Dictionary, Appendix A:
Examples and Appendix B: Schema still need replacing.  I'll do that after a
sleep break.

Best Regards,

Michelle
<?xml version="1.0" encoding="UTF-8"?>
<ed:EDXLDistribution xmlns:xsd="http://www.w3.org/2001/XMLSchema";
    xmlns="http://www.w3.org/2001/XMLSchema";
    xmlns:ed="urn:oasis:names:tc:emergency:EDXL:DE:1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  <ed:distributionID>XXXXXXXXXX</ed:distributionID>
  <ed:senderID>XXXXXXXXXX</ed:senderID>
  <ed:dateTimeSent>2002-07-01T05:10:10</ed:dateTimeSent>
  <ed:distributionStatus>Actual</ed:distributionStatus>
  <ed:distributionType>Ack</ed:distributionType>
  <ed:senderRole>
    <ed:valueListUrn>XXXXXXXXXX</ed:valueListUrn>
    <ed:value>XXXXXXXXXX</ed:value>
  </ed:senderRole>
  <ed:recipientRole>
    <ed:valueListUrn>XXXXXXXXXX</ed:valueListUrn>
    <ed:value>XXXXXXXXXX</ed:value>
  </ed:recipientRole>
  <ed:keyword>
    <ed:valueListUrn>XXXXXXXXXX</ed:valueListUrn>
    <ed:value>XXXXXXXXXX</ed:value>
  </ed:keyword>
  <ed:explicitAddress>XXXXXXXXXX</ed:explicitAddress>
  <ed:distributionReference>XXXXXXXXXX</ed:distributionReference>
  <ed:combinedConfidentiality>XXXXXXXXXX</ed:combinedConfidentiality>
  <ed:targetArea>
    <ed:circle>XXXXXXXXXX</ed:circle>
    <ed:polygon>XXXXXXXXXX</ed:polygon>
    <ed:country>XXXXXXXXXX</ed:country>
    <ed:subdivision>XXXXXXXXXX</ed:subdivision>
    <ed:location>XXXXXXXXXX</ed:location>
  </ed:targetArea>
  <ed:contentObject anyAttribute="Y">
    <ed:contentKeyword>
      <ed:valueListUrn>XXXXXXXXXX</ed:valueListUrn>
      <ed:value>XXXXXXXXXX</ed:value>
    </ed:contentKeyword>
    <ed:keyXMLContent anyAttribute="Y"/>
    <ed:originatorRole>
      <ed:valueListUrn>XXXXXXXXXX</ed:valueListUrn>
      <ed:value>XXXXXXXXXX</ed:value>
    </ed:originatorRole>
    <ed:consumerRole>
      <ed:valueListUrn>XXXXXXXXXX</ed:valueListUrn>
      <ed:value>XXXXXXXXXX</ed:value>
    </ed:consumerRole>
    <ed:confidentiality>XXXXXXXXXX</ed:confidentiality>
    <ed:description>XXXXXXXXXX</ed:description>
    <ed:mimeType>XXXXXXXXXX</ed:mimeType>
    <ed:size>23</ed:size>
    <ed:digest>XXXXXXXXXX</ed:digest>
    <ed:uri>Y</ed:uri>
  </ed:contentObject>
</ed:EDXLDistribution>