Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Regarding XML schema validation (XSD)

From: Danny Vint <dvint@----.---------.--->
To: merryla martina <merryla@-----.--->
Date: 1/3/2007 12:21:00 AM

Please inform the staff at ACORD of this problem. They are there to make 
sure the schemas work. Also as Michael pointed out, various tools have 
various levels of compliance or even testing of the rules. In general 
ACORD has used Xerces-J and MS-xml (com version) to validate thier schemas=
 
as they were found to be the most stable, complete and one from each of 
the MS and Java camps. Recently the P&C standard found a problem in the 
way extensions were to be handled (or thought to be) due to XMLSpy">XMLSpy 
improving their parser and Xerces not checking the error in the same way.

The only way ACORD is going to correct problems is if they know about 
them.

=2E.dan


---------------------------------------------------------------------------
Danny Vint

Specializing in Panoramic Images of California and the West
http://www.dvint.com

Voice:510:522-4703
FAX: 801-749-3229

On Wed, 3 Jan 2007, merryla martina wrote:

> Hi Michael Kay,
>
> Thanks a lot. The validation works fine for Life Specifications and
> Documentation Final 2.15.0
> <http://acord.org/standards/life_downloads/Life_Standards_Public_Spec_2.1=
5.01.zip>
> .
>
>
>
> But the thing is that, I need to perform validation directly from the sit=
e
> http://www.xyz.com/acord/txlife2-9-00.xsd
>
> I tried both the way for validation. First by downloading the related fil=
e
> from the site http://www.xyz.com/acord/xmlife2-9-00.xsd  and then, by
> directly connecting to the site to perform validation.
>
> Both the way, throws the same error message.
>
>
>
>
>
> The error description looks like this
>
> Validating C:\Schema\sample10.xml
>
> http://www.xyz .com/acord/xmlife2-9-00.xsd#/schema [1]/complexType[positi=
on
>
> () = 293 and @name = 'OLI_LU_VARIANT']/complexContent [1]/extension [=
1]
>
> Derived type and the base type must have the same content type.
>
> Base type: '{http://www.w3.org/2001/XMLSchema } anyType'
>
> Derived type: '{http://ACORD.org/Standards/Life/2
> <http://acord.org/Standards/Life/2>} OLI_LU_VARIANT'
>
> Unspecified error. Validate failed because the root element had no
> associated DTD/
>
> Schema.
>
>
>
> Please help me to find solution.
>
> Thanks
> Merryla Martina
>
>
>
> On 1/2/07, Michael Kay <mike@s...> wrote:
>> 
>>  I'm not sure what you mean by "the Sample txlife.xsd file".
>> 
>> At http://acord.org/standards/life_downloads.aspx you can download "Life
>> Specifications and Documentation Final 
>> 2.15.01<http://acord.org/standards/life_downloads/Life_Standards_Public_=
Spec_2.15.01.zip>"
>> which contains a set of four schema documents including one named
>> TXLife2.15.01.xsd. The definition of ACORD_TYPE_CODE is at line 216 of
>> XLifeBase2.15.01.xsd, which is reached via a chain of includes. Starting
>> at TXLife2.15.01.xsd, the schemas validate OK in Saxon.
>> 
>> Note that 
>> *http://ACORD.org/Standards/Life/2<http://acord.org/Standards/Life/2>
>> *  is a namespace URI. In general you shouldn't expect to find any
>> resource when you try to dereference a namespace URI - it's just a
>> distinguishing character string, not the location of any document.
>> 
>> 
>> Michael Kay
>> http://www.saxonica.com/
>> 
>>  ------------------------------
>> *From:* xmlschema-dev-request@w... [mailto:xmlschema-dev-request@w...=
g]
>> *On Behalf Of *merryla martina
>> *Sent:* 02 January 2007 05:28
>> *To:* xmlschema-dev@w...
>> *Subject:* Regarding XML schema validation (XSD)
>> 
>> 
>> 
>> Hi,
>> 
>> 
>> 
>> I tried to perform schema validation. The code works well. But when I
>> tried with the Sample txlife.xsd file from http://acord.org/ I got error
>> in associating the namespace with the xsd i.e. in the add () method. The
>> add () method returned E_FALSE.
>> 
>> 
>> 
>> When I referred the MSDN library, it states that
>> 
>> 
>> 
>> "E_FAIL is returned if:
>> 
>> 
>> 
>> =B7          The collection is read-only
>> 
>> =B7          The document is not a recognized schema
>> 
>> =B7          An error occurs when compiling the schema
>> 
>> =B7          The ready state of the document is not 4. "
>> 
>> 
>> 
>> After referring MSDN library, I tried to catch the error description.
>> 
>> 
>> 
>> The error descriptions look like this
>> 
>> Undeclared XSD type: '{ 
>> http://ACORD.org/Standards/Life/2<http://acord.org/Standards/Life/2>}
>> ACORD_TYPE_CODE'.
>> 
>> 
>> 
>> So I referred the txlife.xsd schema, I found that ACORD_TYPE_CODE was
>> referred but not defined. After that I tried to view the site
>> http://ACORD.org/Standards/Life/2 <http://acord.org/Standards/Life/2> fo=
r
>> the definition of
>> 
>> ACORD_TYPE_CODE.I found "page not found " error.
>> 
>> 
>> 
>> Here I can't understand why this error description, which is highted
>> above, comes, as this xsd file is a standard one.
>> 
>> 
>> 
>> The sample txlife.xsd file starts like this
>> 
>> 
>> 
>> <xsd: schema targetNamespace=" 
>> http://ACORD.org/Standards/Life/2<http://acord.org/Standards/Life/2>"
>> xmlns="http://ACORD.org/Standards/Life/2<http://acord.org/Standards/Li=
fe/2>"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema "
>> elementFormDefault="unqualified" attributeFormDefault="unqualified"
>> version="2.9.00">
>> 
>> 
>>  Thanks
>> Merryla
>> 
>> 
>

From scott.tsao@b... Wed Jan 03 19:46:06 2007
Received: from lisa.w3.org ([128.30.52.41])
	by frink.w3.org with esmtp (Exim 4.50)
	id 1H2C3p-0002vq-WC
	for xmlschema-dev@l...; Wed, 03 Jan 2007 19:46:06 +0000
Rece


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