[oXygen-user] problem with xlink in METS files

[Christian Wittern]

Hi Sorin,

Thanks for spotting this!  I knew it had to be simple, but it was just
too late yesterday.  Glad to know that it works as expected now!

All the best,

Christian

On 01/09/06, Sorin Ristache <> wrote:
> Hello Christian,
>
> In your XML document the prefix "xlink" is associated to the
> "http://www.w3.org/TR/xlink" namespace while the mets.xsd schema imports
> xlink.xsd with the target namespace "http://www.w3.org/1999/xlink".
> oXygen looks in your document for a prefix associated to the target
> namespace of the schema and it does not find one so it provides a
> default prefix (ns1, ns2, etc) instead of the declared prefix "xlink".
>
>
> Regards,
> Sorin
>
>
> Christian Wittern wrote:
> > Hi there,
> >
> > I am having a strange problem with editing / validating METS
> > instances.  Using the schema from
> > http://www.loc.gov/standards/mets/mets.xsd (which imports xlink.xsd at
> > the same location),
> > I am editing a file with the following root:
> >
> > <mets xmlns="http://www.loc.gov/METS/"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >    xsi:schemaLocation="http://www.loc.gov/METS/ file:mets.xsd"
> >    xmlns:gdm="http://sunsite.berkeley.edu/GDM/"
> >    xmlns:xlink="http://www.w3.org/TR/xlink">
> > </mets>
> >
> > i.e. I am defining a NS prefix xlink for the xlink namespace.
> > Nevertheless, when I place attributes from this namespace on elements
> > (e.g. on Flocat), oXygen claims they are not valid there and instead
> > offers the very same attributes, but with namespace prefixes like ns1,
> > ns2 etc.  This seems to be wrong, but I am at a loss how to fix this.
> > Is this a bug in oXygen or am I doing something wrong?
> >
> > Any help appreciated,
> >
> > Christian Wittern
> _______________________________________________
> oXygen-user mailing list
> 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>


-- 
Christian Wittern, Kyoto