Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Problems restricting UBL's AddressType complexType

From: George Cristian Bina <george@---------.--->
To: Allison Bloodworth <abloodworth@--------.--->
Date: 1/10/2006 9:25:00 AM
Hi Allison,

These are in general quite hard to spot errors. In your case the problem 
is with the local defined elements, ID and CountrySubentityCode. They 
are defined in the  UBL-CommonAggregateComponents.xsd schema as local 
elements inside the AddressType type and the schema/@elementFormDefault 
for that schema document is set to qualified, that means the local 
elements belong to the schema target namespace which is 
urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-1.0.

Now in your schema you define ID and CountrySubentityCode also as local 
elements, you have elementFormDefault as qualified but no target 
namespace, that means the ID and CountrySubentityCode elements will be 
placed in no namespace. These elements from no namespace cannot be 
mapped to the elements with the same name but from the 
urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-1.0 
namespace, thus the error.

The only thing you can do is to remove them, and if you remove both ID 
and CountrySubentityCode from your UCBAddressType type you will see that 
the schema is valid.

Hope that helps,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
www.---.com


Allison Bloodworth wrote:
> Hi, 
> 
> I've spent several hours trying to figure out why I can't restrict UBL's
> AddressType
> (http://docs.oasis-open.org/ubl/cd-UBL-1.0/xsd/common/UBL-CommonAggregateCom
> ponents-1.0.xsd) to remove certain elements. My (currently invalid) schema
> attempting to do this is here:
> http://groups.sims.berkeley.edu/EventCalendar/UCBAddress.xsd. I am only
> trying use restriction to remove elements that are minOccurs="0", and many I
> was successfully able to remove. However, when trying to remove elements
> that are part of AddressType which look like this:
> 
> <xs:element name="ID" type="udt:IdentifierType" minOccurs="0" maxOccurs="1">
> 
> I'm told by Oxygen that: 
> 
> Description: E derivation-ok-restriction.5.4.2: Error for type
> 'UCBAddressType'.  The particle of the type is not a valid restriction of
> the particle of the base.
> 
> URL: http://www.w3.org/TR/xmlschema-1/#derivation-ok-restriction
> 
> AND
> 
> Description: E rcase-Recurse.2: There is not a complete functional mapping
> between the particles.
> 
> URL: http://www.w3.org/TR/xmlschema-1/#rcase-Recurse 
> 
> 
> I read the spec and it *seems* that I've met all the requirements, but the
> spec is a bit hard to read. I simply copied AddressType from the UBL schema
> to begin building my restriction so I'm not sure what I could be missing.
> Any help would be much appreciated!
>  
> Allison Bloodworth
> Principal Administrative Analyst
> e-Berkeley Program Office
> University of California, Berkeley
> (415) 377-8243
> abloodworth@b...
> 
> 
> 
> 
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> 
> The list archives are at http://lists.xml.org/archives/xml-dev/
> 
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent