XSL, namespaces, oh my!

I've searched high and low for an answer, but I suspect my quandary  
is more related to XML parsing than OPS, but if some kind soul has  
some advice I would be grateful.  My application is a modification of  
the bizdoc2 sample and the problem happens when importing documents.  
All is going well, except that I'm now gradually adding in some  
attributes with namespaces.  For example, my imported document has an  
xlink:href attribute in the titleInfo element.  I've declared the  
xlink namespace in every appropriate location, but when importing the  
document I get the following message in std out:

Error reported by XML parser: The prefix "xlink" for attribute  
"xlink:href" associated
   with an element type "titleInfo" is not bound.

The curious thing is that the import works fine, but this appears to  
be an error when reading back the document and creating the summary  
list.  Has anyone ever seen this problem error message before?

Duane



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Could you post the document that's causing the problem?

-----Original Message-----
From: Duane Gran [mailto:[hidden email]]
Sent: 18 January 2006 15:55
To: [hidden email]
Subject: [ops-users] XSL, namespaces, oh my!

I've searched high and low for an answer, but I suspect my quandary  
is more related to XML parsing than OPS, but if some kind soul has  
some advice I would be grateful.  My application is a modification of  
the bizdoc2 sample and the problem happens when importing documents.  
All is going well, except that I'm now gradually adding in some  
attributes with namespaces.  For example, my imported document has an  
xlink:href attribute in the titleInfo element.  I've declared the  
xlink namespace in every appropriate location, but when importing the  
document I get the following message in std out:

Error reported by XML parser: The prefix "xlink" for attribute  
"xlink:href" associated
   with an element type "titleInfo" is not bound.

The curious thing is that the import works fine, but this appears to  
be an error when reading back the document and creating the summary  
list.  Has anyone ever seen this problem error message before?

Duane





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

No problem.  The document is here:

<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xmlns:xlink="http://www.w3.org/1999/xlink"
   xmlns="http://www.loc.gov/mods/v3">
   <titleInfo type="translated" authority="naf" ID="t1"  
displayLabel="" lang="" xml:lang="" script=""
     transliteration="" xlink:href=""/>
</mods>

Duane

On Jan 18, 2006, at 12:06 PM, Stephen Bayliss wrote:



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Nothing wrong there!

Try to identify which process is causing the error, and check your
namespace declarations on everything that process is using.

If you have, for example, mistyped a namespace declaration for xlink
somewhere (eg xmlns:xlink="http://www.w3.org/1999/mistake-here") then
the two xlink prefixes will be treated as entirely different namespaces.

-----Original Message-----
From: Duane Gran [mailto:[hidden email]]
Sent: 18 January 2006 17:29
To: [hidden email]
Subject: Re: [ops-users] XSL, namespaces, oh my!

No problem.  The document is here:

<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xmlns:xlink="http://www.w3.org/1999/xlink"
   xmlns="http://www.loc.gov/mods/v3">
   <titleInfo type="translated" authority="naf" ID="t1"  
displayLabel="" lang="" xml:lang="" script=""
     transliteration="" xlink:href=""/>
</mods>

Duane

On Jan 18, 2006, at 12:06 PM, Stephen Bayliss wrote:





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

You're correct that this is an XML parser error. It means that when
using the namespace prefix "xlink" for your attribute, the XML parser
can't find a namespace declaration that specifies that prefix (i.e.,
xmlns:xlink="http. . ."

So it's either a typo in a namespace declaration or the namespace isn't
declared somewhere - my guess would be the schema that's being used to
validate your document instance.

Hope that helps.

Don

-----Original Message-----
From: Duane Gran [mailto:[hidden email]]
Sent: Wednesday, January 18, 2006 9:55 AM
To: [hidden email]
Subject: [ops-users] XSL, namespaces, oh my!

I've searched high and low for an answer, but I suspect my quandary  
is more related to XML parsing than OPS, but if some kind soul has  
some advice I would be grateful.  My application is a modification of  
the bizdoc2 sample and the problem happens when importing documents.  
All is going well, except that I'm now gradually adding in some  
attributes with namespaces.  For example, my imported document has an  
xlink:href attribute in the titleInfo element.  I've declared the  
xlink namespace in every appropriate location, but when importing the  
document I get the following message in std out:

Error reported by XML parser: The prefix "xlink" for attribute  
"xlink:href" associated
   with an element type "titleInfo" is not bound.

The curious thing is that the import works fine, but this appears to  
be an error when reading back the document and creating the summary  
list.  Has anyone ever seen this problem error message before?

Duane





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Don,

Thank you for the tip.  I did some investigating (grep -r xlink) and  
confirmed that the namespace is declared the same in every instance.  
Also, my debugging output seems to imply that the namespace is  
properly defined.  Below is an example of that output, along with the  
error message in context.

<result>
     <document-info>
         <document-id>84475D56-A529-30E7-C55A-4DC83AD5A9EC</document-id>
         <titleInfo xmlns="http://www.loc.gov/mods/v3"  
type="translated" authority="naf" ID="t1" displayLabel="" lang=""  
xml:lang="" script="" transliteration="" xmlns:xlink="http://
www.w3.org/1999/xlink" xlink:href="">
         </titleInfo>
     </document-info>
</result>
Error on line 5 column 200
   Error reported by XML parser: The prefix "xlink" for attribute  
"xlink:href" associated
   with an element type "titleInfo" is not bound.

As far as I can tell, the xlink namespace is declared properly.  Per  
your second hypothesis, about a problem in the schema, it all appears  
to be correct.  For good measure I reproduce it below:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
   xmlns:mods="http://www.loc.gov/mods/v3"
   xmlns:xlink="http://www.w3.org/1999/xlink"
   elementFormDefault="qualified">
   <xs:import namespace="http://www.loc.gov/mods/v3"  
schemaLocation="../schema/mods-3-0.xsd"/>
   <xs:import namespace="http://www.w3.org/1999/xlink"  
schemaLocation="http://www.loc.gov/standards/mods/xlink.xsd"/>

   <xs:element name="result">
     <xs:complexType>
       <xs:sequence minOccurs="0" maxOccurs="unbounded">
         <xs:element name="document-info">
           <xs:complexType>
             <xs:sequence>
               <xs:element name="document-id" type="xs:string"/>
               <xs:element ref="mods:titleInfo"/>
             </xs:sequence>
           </xs:complexType>
         </xs:element>
       </xs:sequence>
     </xs:complexType>
   </xs:element>
</xs:schema>

I must be overlooking something obvious here, but it all looks in  
order to me.

Duane

On Jan 18, 2006, at 4:36 PM, Smith, Donald wrote:



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Duane,

Namespace are such a nightmare.

In the reproduction of your result element I notice that the namespace
declaration for "xlink" has a space between the second "/" and the first
"w". I assume that's getting in via e-mail and isn't in your source doc,
right?

If you'll send me the doc and all the schemas, I'll try validating it
with a different parser, just to see if we get the same result. I'm
wondering if the schema imports are doing something we're not realizing
and causing the failure.

Don

-----Original Message-----
From: Duane Gran [mailto:[hidden email]]
Sent: Thursday, January 19, 2006 8:26 AM
To: [hidden email]
Subject: Re: [ops-users] XSL, namespaces, oh my!

Don,

Thank you for the tip.  I did some investigating (grep -r xlink) and  
confirmed that the namespace is declared the same in every instance.  
Also, my debugging output seems to imply that the namespace is  
properly defined.  Below is an example of that output, along with the  
error message in context.

<result>
     <document-info>
         <document-id>84475D56-A529-30E7-C55A-4DC83AD5A9EC</document-id>
         <titleInfo xmlns="http://www.loc.gov/mods/v3"  
type="translated" authority="naf" ID="t1" displayLabel="" lang=""  
xml:lang="" script="" transliteration="" xmlns:xlink="http://
www.w3.org/1999/xlink" xlink:href="">
         </titleInfo>
     </document-info>
</result>
Error on line 5 column 200
   Error reported by XML parser: The prefix "xlink" for attribute  
"xlink:href" associated
   with an element type "titleInfo" is not bound.

As far as I can tell, the xlink namespace is declared properly.  Per  
your second hypothesis, about a problem in the schema, it all appears  
to be correct.  For good measure I reproduce it below:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
   xmlns:mods="http://www.loc.gov/mods/v3"
   xmlns:xlink="http://www.w3.org/1999/xlink"
   elementFormDefault="qualified">
   <xs:import namespace="http://www.loc.gov/mods/v3"  
schemaLocation="../schema/mods-3-0.xsd"/>
   <xs:import namespace="http://www.w3.org/1999/xlink"  
schemaLocation="http://www.loc.gov/standards/mods/xlink.xsd"/>

   <xs:element name="result">
     <xs:complexType>
       <xs:sequence minOccurs="0" maxOccurs="unbounded">
         <xs:element name="document-info">
           <xs:complexType>
             <xs:sequence>
               <xs:element name="document-id" type="xs:string"/>
               <xs:element ref="mods:titleInfo"/>
             </xs:sequence>
           </xs:complexType>
         </xs:element>
       </xs:sequence>
     </xs:complexType>
   </xs:element>
</xs:schema>

I must be overlooking something obvious here, but it all looks in  
order to me.

Duane

On Jan 18, 2006, at 4:36 PM, Smith, Donald wrote:





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Duane,

Do you still have the problem? I fear that if so, it won't be possible
to figure it out without having a reproducible example at hand.

-Erik

Duane Gran wrote:


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Erik,

Yes, I am, but I think I believe I'm limited in my experience to  
describe it, especially since it involves a chain of about six  
pipelines, exist and XSL.  I'll try to create a simpler error  
condition and put it into the sandbox, but barring this I may raise  
the topic directly with you on a support basis.

As an aside to the members of the list, I hope that you consider  
engaging the Orbeon group in paid support as well.  I've found Erik  
in particular to be most helpful and attentive -- even to an OPS  
newbie like myself.

Duane

On Jan 24, 2006, at 9:58 AM, Erik Bruchez wrote:



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Duane Gran wrote: Well, thanks a lot for the kind words :-)

-Erik




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws