Xerces and keyrefs 2003-08-12 - By david.shontz@(protected)
I realized my last post was a bit off. I just checked Apache's website and
Xerces 2.5.0 is indeed the latest release.
Here's a snippet that shows how we're using keyrefs.
<xs:element name="VaporComposition" type
="VaporCompositionType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="LiquidComposition"
type="LiquidCompositionType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="CompositeComposition"
type="CompositeCompositionType" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="stepNumber" type="
xs:positiveInteger"/>
</xs:complexType>
<xs:keyref name="cceVaporPhaseComponentRef"
refer="componentName">
<xs:selector xpath="./VaporComposition"/>
<xs:field xpath="@(protected)"/>
</xs:keyref>
<xs:keyref name="cceLiquidPhaseComponentRef"
refer="componentName">
<xs:selector xpath="./LiquidComposition"/>
<xs:field xpath="@(protected)"/>
</xs:keyref>
<xs:keyref name="
cceCompositePhaseComponentRef" refer="componentName">
<xs:selector xpath="./CompositeComposition
"/>
<xs:field xpath="@(protected)"/>
</xs:keyref>
Thanks Sandy and Adam, for looking
David Shontz
ExxonMobil Exploration UTC
Application Support/Application and Data Integration
CORP-RR-603
281-654-7214
Email: David Shontz/U-Houston/ExxonMobil
Internet Email: david.shontz@(protected)
|---------+----------------------------->
| | "Sandy Gao" |
| | <sandygao@(protected)|
| | om> |
| | |
| | |
| | 08/12/03 08:06 AM |
| | Please respond to |
| | xerces-j-user |
| | |
|---------+----------------------------->
>----------------------------------------------------------------------------
------------------------------------------|
|
|
| To: xerces-j-user@(protected)
|
| cc:
|
| Subject: Re: Xerces and keyrefs
|
>----------------------------------------------------------------------------
------------------------------------------|
First of all, where did you get Xerces 2.5.1? (I only know 2.5.0.) If you
could share it with us, it would save us the work of a whole release. :-)
It's hard to say whether it's a problem in Xerces or in your xml/schema
without seeing some concrete examples. Could you post a cut-down example?
Thanks,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
sandygao@(protected)
david.shontz@(protected)
nmobil.com To:
xerces-j-user@(protected)
cc:
08/12/2003 08:46 Subject: Xerces and keyrefs
AM
Please respond to
xerces-j-user
We've been developing a schema that uses keys and keyrefs for internal
consistency. We developed it using XMLSpy's parser, where it validates
documents without complaint. However, when we moved to Xerces-J 2.5.1, it
declared every keyref out of scope. Is this a known issue, or are we doing
something wrong?
Thanks,
David Shontz
ExxonMobil Exploration UTC
Application Support/Application and Data Integration
CORP-RR-603
281-654-7214
Email: David Shontz/U-Houston/ExxonMobil
Internet Email: david.shontz@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
|
|
