I'm looking at the feasibility of using an Excel file for loading data into the EPA GHG schema (ghg_subpartp_inputs_v1.0.xsd) for defining the XML Subpartp Inputs data.
I'm not well versed or practiced in using Excel and xml-schemas.
The SubpartP schema has nested complex elements, and it won't be accepted into Excel via the XML Maps facility.
Error message: "Cannot Load the specified XML or schema source."
I'm thinking it is because it is a partial schema that is meant to be included in others?
Here is the schema itself:
Schema Name : ghg_subpartp_inputs_v1.0.xsd
Description : Inputs Verifier Tool - XML schema for Subpart P inputs
<xsd:complexType name="SubpartPInputsType">
<xsd:sequence>
<xsd:element name="SubpartPUnitInputs" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="UnitName" type="xsd:string"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EquationP1FeedstockInputs" type="EquationP1FeedstockInputsType" minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="EquationP2FeedstockInputs" type="EquationP2FeedstockInputsType" minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="EquationP3FeedstockInputs" type="EquationP3FeedstockInputsType" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:unique name="UniqueSubpartPFeedstockName">
<xsd:selector xpath="Values/*"/>
<xsd:field xpath="FeedstockName"/>
</xsd:unique>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EquationP1FeedstockInputsType">
<xsd:sequence>
<xsd:element name="FeedstockName" type="xsd:string"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MassOrVolume" type="MassOrVolumeIndicatorType"/>
<xsd:element name="EquationP1MonthlyInputs" minOccurs="0" maxOccurs="12">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MonthName" type="MonthNameList"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Mass" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Volume" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: scf (at standard conditions of 68 degrees F and atmospheric pressure) of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CarbonContent" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg C per kg of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MolecularWeight" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg/kg-mole</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:unique name="UniqueEquationP1MonthName">
<xsd:selector xpath="*"/>
<xsd:field xpath="MonthName"/>
</xsd:unique>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EquationP2FeedstockInputsType">
<xsd:sequence>
<xsd:element name="FeedstockName" type="xsd:string"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MassOrVolume" type="MassOrVolumeIndicatorType"/>
<xsd:element name="EquationP2MonthlyInputs" minOccurs="0" maxOccurs="12">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MonthName" type="MonthNameList"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Mass" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Volume" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: gallons of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CarbonContent" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg C per kg of fuel or feedstock if measured as mass, or kg C per gallon of fuel or feedstock if measured as volume</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:unique name="UniqueEquationP2MonthName">
<xsd:selector xpath="*"/>
<xsd:field xpath="MonthName"/>
</xsd:unique>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EquationP3FeedstockInputsType">
<xsd:sequence>
<xsd:element name="FeedstockName" type="xsd:string"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EquationP3MonthlyInputs" minOccurs="0" maxOccurs="12">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MonthName" type="MonthNameList"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Mass" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg of fuel and feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CarbonContent" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg C per kg of fuel and feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:unique name="UniqueEquationP3MonthName">
<xsd:selector xpath="*"/>
<xsd:field xpath="MonthName"/>
</xsd:unique>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
What should I be doing to create the Excel file that will create an acceptible XML for this schema?
Related
I have the following XSD template for the following:
<xsd:choice>
<xsd:element name="NilReport" type="ftc:CorrectableNilReport_Type">
<xsd:annotation>
<xsd:documentation xml:lang="en">Nil Report indicates that financial institution does not have accounts to report</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:sequence >
<xsd:element name="AccountReport" type="ftc:CorrectableAccountReport_Type" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Detailed information for account report, such as account number and account balance</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="PoolReport" type="ftc:CorrectablePoolReport_Type" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Information about the pool of account holders with similar characteristics</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
But the result so far doesn't go as it supposes to be.
Unexpected result
Here is my wanted result:
Expected result
How could i archive the expected result ? Please advice me.
Please note that both and are optional in this case.
Currently your choice lets you pick between the NilReport element and the sequence with the other two elements.
If you want to have the two other elements as children of the "sequence" you will have to create a containing element, and you need to define them as children of that element as follows.
<xsd:choice>
<xsd:element name="NilReport" type="ftc:CorrectableNilReport_Type">
<xsd:annotation>
<xsd:documentation xml:lang="en">Nil Report indicates
that financial institution does not have accounts to report</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="NotNilReport">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AccountReport" type="ftc:CorrectableAccountReport_Type"
minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Detailed information for account report, such
as account number and account balance</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="PoolReport" type="ftc:CorrectablePoolReport_Type"
minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Information about the pool of account holders
with similar characteristics</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:choice>
I am writing a schema for EMF to describe general graphs. The problem is that if this is directed graph, then the edge should have properties of src_node and dst_node, otherwise it has node_one and node_two. I tried to use "choice" to have mutally exclusive elements but in EMF it functions the same as "sequence". e.g a similar problem for NodeProperty
<xsd:complexType name="NodeProperty">
<xsd:choice>
<xsd:element name="StringValue" type="xsd:string"/>
<xsd:element name="IntValue" type="xsd:int"/>
<xsd:element name="DoubleValue" type="xsd:double"/>
</xsd:choice>
<xsd:attribute name="Property" type="xsd:string"/>
</xsd:complexType>
Another problem in substitutionGroup is that src_node and dst_node are claimed be to unresolved by EMF. The complete code:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:simpleType name="GraphType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Directed"/>
<xsd:enumeration value="Undirected"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="NodeProperty">
<xsd:choice>
<xsd:element name="StringValue" type="xsd:string"/>
<xsd:element name="IntValue" type="xsd:int"/>
<xsd:element name="DoubleValue" type="xsd:double"/>
</xsd:choice>
<xsd:attribute name="Property" type="xsd:string"/>
</xsd:complexType>
<xsd:complexType name="Node">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0"
name="Node" type="lib:NodeProperty"/>
</xsd:sequence>
<xsd:attribute name="NodeName" type="xsd:string" />
</xsd:complexType>
<xsd:element name="src_node" type="xsd:anyURI" ecore:reference="lib:Node"/>
<xsd:element name="node_one" type="xsd:anyURI" substitutionGroup="src_node"/>
<xsd:element name="dst_node" type="xsd:anyURI" ecore:reference="lib:Node"/>
<xsd:element name="node_two" type="xsd:anyURI" substitutionGroup="dst_node"/>
<xsd:complexType name="Edge">
<xsd:sequence>
<xsd:element ref="src_node"/>
<xsd:element ref="dst_node"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="GeneralGraph">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="type" type="lib:GraphType"/>
<xsd:element name="NodeList">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0"
name="Node" type="lib:Node"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EdgeList">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0"
name="Edge" type="lib:Edge"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Yes. Substitution groups apply to global elements. So move your elements out of your type and reference to them in the type.
<xsd:element name="src_node" type="xsd:anyURI" ecore:reference="lib:Node"/>
<xsd:element name="node_one" type="xsd:anyURI" substitutionGroup="src_node"/>
<xsd:element name="dst_node" type="xsd:anyURI" ecore:reference="lib:Node"/>
<xsd:element name="node_two" type="xsd:anyURI" substitutionGroup="dst_node"/>
<xsd:complexType name="Edge">
<xsd:sequence>
<xsd:element ref="src_node"/>
<xsd:element ref="dst_node"/>
</xsd:sequence>
</xsd:complexType>
Untested.
The idea is that now node_one could be used instead src_node in Edge and node_two instead of node_two.
Note that type of the substitutable must be derived from the type of the substitution group element. So I used anyURI just for example. You'll probably want to rework it.
By the way I generally discourage usage of subsitition groups. Makes your XML unpredictable.
I have a task where I need to create an element "Worker" which has 0 or more subelements "subordinate". I have to use key and keyref to create the references. I can't figure out how make the references "work". Here's what I've written so far:
<xsd:element name="Workers">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Worker" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="subordinate" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="identyfikator" type="PESEL" use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:key name="id">
<xsd:selector xpath="Worker"/>
<xsd:field xpath="#identyfikator"/>
</xsd:key>
<xsd:keyref name="subordinate_ref" refer="id">
<xsd:selector xpath="Worker/subordinate"/>
<xsd:field xpath="#identyfikator"/>
</xsd:keyref>
</xsd:element>
PESEL is my own type and the key restriction works well as I am unable to create two workers with the same key in XML document. However, I can create anything as "subordinate" element and no warnings will be displayed. As I understand, in case of such reference I should be only able to add workers as subordinates if they already exist, right? How do I create proper reference?
This is my first time working with XMLSchema so sorry if the code is messy.
Thanks in advance!
Make a Worker ComplexType and have Worker and Subordinate both be of that type.
Approximately like so:
<!-- Define the below where appropriate. -->
<xsd:element name="Worker" type="WorkerType" />
<xsd:complexType name="WorkerType">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="subordinate" type="WorkerType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="identyfikator" type="PESEL" use="required"/>
</xsd:complexType>
Also, if you want items to have a unique id, then consider using (or extending) the xsd:ID datatype. This gives you free uniqueness and referential checks using xsd:IDREF.
<xsd:attribute name="identyfikator" type="xsd:ID" use="required"/>
I am trying to create an XSD, which allows child elements to be in any order. But each child element has its own minOccurs and maxOccurs.
My XSD:
<xsd:complexType name="Samples">
<xsd:sequence >
<xsd:element name="Sample1" minOccurs="1" maxOccurs="1">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:boolean" />
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="Sample2" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string" />
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
For Example a valid XML:
<Samples>
<Sample2></Sample2>
<Sample1></Sample1>
<Sample2></Sample2>
</Samples>
For Example a not valid XML (Sample1 can be choose only one time):
<Samples>
<Sample2></Sample2>
<Sample1></Sample1>
<Sample2></Sample2>
<Sample1></Sample1>
</Samples>
But i don't know, how i can mix the order, while all elements have its own constraint.
Thanks for help
What if you try this:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Samples">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Sample2" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Sample1" minOccurs="1" maxOccurs="1"/>
<xsd:element name="Sample2" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
Of course, you should add your restrictions to each element:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="Sample1Type">
<xsd:simpleContent>
<xsd:extension base="xsd:boolean" />
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Sample2Type">
<xsd:simpleContent>
<xsd:extension base="xsd:string" />
</xsd:simpleContent>
</xsd:complexType>
<xsd:element name="Samples">
<xsd:complexType>
<xsd:sequence>
<xsd:element type="Sample2Type" name="Sample2" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element type="Sample1Type" name="Sample1" minOccurs="1" maxOccurs="1"/>
<xsd:element type="Sample2Type" name="Sample2" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
OR even shorter for simple types:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Samples">
<xsd:complexType>
<xsd:sequence>
<xsd:element type="xsd:string" name="Sample2" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element type="xsd:boolean" name="Sample1" minOccurs="1" maxOccurs="1"/>
<xsd:element type="xsd:string" name="Sample2" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
P.S.::
There are unfortunately no XSD elements like xsd:sequence, which will allow, what you ask.
What you want looks like xsd:all; however, since xsd:all only works for elements for which maxOccurs is 1, it will not work here. If you can combine choices and sequences to constrain your content, one way to go around duplication of definition (avoid defining twice) is to define Sample1 and Sample 2 as global elements and then ref them under your compositors. If defining global elements is not an option except for your root elements, then you could at least define the types globally - this way you maximize the reuse, and somewhat getting closer to your requirement "without defining twice"...
I have a complex type defined which doesn't currently contain any minOccurs restrictions. When I use this comlpex type as an element type I sometimes want the elements to have minOccurs 0, other times 1. E.g.
<xsd:complexType name="Identifier">
<xsd:sequence>
<xsd:element name="Id" type="xsd:string"/>
<xsd:element name="Version" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Wibble">
<xsd:sequence>
<xsd:element name="Id" type="Identifier"/> <!-- I want all elements of Identifier to be mandatory when used as part of a 'Wibble' -->
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Wobble">
<xsd:sequence>
<xsd:element name="Id" type="Identifier"/> <!-- I want all elements of Identifier to be optional when used as part of a 'Wobble' -->
</xsd:sequence>
</xsd:complexType>
Is this possible?
Thanks in advance.
Groups are your friend, e.g.
<xsd:group name="IdentifierGroup">
<xsd:sequence>
<xsd:element name="Id" type="Identifier"/>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="Wibble">
<xsd:sequence>
<xsd:group ref="IdentifierGroup" minOccurs="1"/>
<!-- more elements for Wibble here -->
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Wobble">
<xsd:sequence>
<xsd:group ref="IdentifierGroup" minOccurs="0"/>
<!-- more elements for Wobble here -->
</xsd:sequence>
</xsd:complexType>