Christian Wittern | 1 Sep 14:50 2006
Picon

problem with xlink in METS files

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

--

-- 
Christian Wittern, Kyoto
Sorin Ristache | 1 Sep 15:31 2006

Re: problem with xlink in METS files

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
(Continue reading)

Christian Wittern | 2 Sep 01:43 2006
Picon

Re: problem with xlink in METS files

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 <sorin@...> 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
(Continue reading)

Chris Chiasson | 3 Sep 10:38 2006

end of line character change

Is there a way to force oXygen for Eclipse to terminate ant xml build
file lines with LF instead of CR LF?

--

-- 
http://chris.chiasson.name/
Sorin Ristache | 4 Sep 09:26 2006

Re: end of line character change

Hello Chris,

The <oXygen/> plugin does not handle the end of lines of saved files but 
Eclipse does that. For new files created in Eclipse you can set the end 
of line character for the whole workspace in Window -> Preferences -> 
General -> Workspace -> New text file line delimiter. To convert the EOL 
characters of the currently edited files go to menu File -> Convert Line 
Delimiters To and select Unix instead of Windows.

Regards,
Sorin

Chris Chiasson wrote:
> Is there a way to force oXygen for Eclipse to terminate ant xml build
> file lines with LF instead of CR LF?
> 
Chris Chiasson | 6 Sep 16:38 2006

\\machinename\username SAMBA shares

Hi,

oXygen for Eclipse declines to transform any of my XML files on my
SAMBA share. It works fine when I copy the entire workspace to my hard
disk and then try it. I just recently moved my workspace to my SAMBA
share so I could build with ant on Linux. The error came up when I was
trying a manual transformation to diagnose an XEP problem...

I am using the right click->transformation->configure transformation method.

The error is:
Configure Transformation Scenario
Configure transformation skipped.
Content type not handled for resource:
Engineering_Optimization.xml

--

-- 
http://chris.chiasson.name/
Sorin Ristache | 6 Sep 17:00 2006

Re: \\machinename\username SAMBA shares

Hello,

Until we fix the problem please apply the main method of 
configuring/running the transform: open Engineering_Optimization.xml for 
editing using the editor contributed by the oXygen plugin and use the 
toolbar buttons/XML menu actions called "Configure Transformation 
Scenario" and "Apply Transformation Scenario". They work correctly even 
in workspaces located on a Samba share.

Best regards,
Sorin

http://www.oxygenxml.com/

Chris Chiasson wrote:
> Hi,
> 
> oXygen for Eclipse declines to transform any of my XML files on my
> SAMBA share. It works fine when I copy the entire workspace to my hard
> disk and then try it. I just recently moved my workspace to my SAMBA
> share so I could build with ant on Linux. The error came up when I was
> trying a manual transformation to diagnose an XEP problem...
> 
> I am using the right click->transformation->configure transformation 
> method.
> 
> The error is:
> Configure Transformation Scenario
> Configure transformation skipped.
> Content type not handled for resource:
(Continue reading)

Chris Chiasson | 6 Sep 18:53 2006

Re: \\machinename\username SAMBA shares

This does work to bring up the dialog. However, the transformation
fails. The message is is "Failed to compile stylesheet. 1 error
detected" and the file indicated is the entry point to my
customization layer.  I think this is because my customization layer
is in the project, which is on the SAMBA share.

On 9/6/06, Sorin Ristache <sorin@...> wrote:
> Hello,
>
> Until we fix the problem please apply the main method of
> configuring/running the transform: open Engineering_Optimization.xml for
> editing using the editor contributed by the oXygen plugin and use the
> toolbar buttons/XML menu actions called "Configure Transformation
> Scenario" and "Apply Transformation Scenario". They work correctly even
> in workspaces located on a Samba share.
>
>
> Best regards,
> Sorin
>
> http://www.oxygenxml.com/
>
>
> Chris Chiasson wrote:
> > Hi,
> >
> > oXygen for Eclipse declines to transform any of my XML files on my
> > SAMBA share. It works fine when I copy the entire workspace to my hard
> > disk and then try it. I just recently moved my workspace to my SAMBA
> > share so I could build with ant on Linux. The error came up when I was
(Continue reading)

Sorin Ristache | 7 Sep 08:42 2006

Re: \\machinename\username SAMBA shares

Hello Chris,

The message "Failed to compile stylesheet." is issued by the XSLT 
processor, so your stylesheet was retrieved correctly from the Samba 
share. I think there is an error in your stylesheet but without seeing 
it I cannot be of more help.

Regards,
Sorin

http://www.oxygenxml.com/

Chris Chiasson wrote:
> This does work to bring up the dialog. However, the transformation
> fails. The message is is "Failed to compile stylesheet. 1 error
> detected" and the file indicated is the entry point to my
> customization layer.  I think this is because my customization layer
> is in the project, which is on the SAMBA share.
Achim Oehlenschlaeger | 8 Sep 11:06 2006

areaspec feature in docbook


Hello,
I'm using Oxygen 7.2 and want to use the areaspec feature to define linkable
areas in a graphics object.
I tried the example from http://www.docbook.org/tdg/en/html/mediaobjectco.html
but don't get the desired result.

I did read and follow the readme file in:
 ...\Oxygen XML Editor 7.2\frameworks\docbook\xsl\extensions

I tried the Docbook transformation scenario as delivered with oxygen first,
than I also added the DocBook extension to the scenario, than I switched to Xalan
(I also switched the extension) but the result is always the same as shown below.
Thanks,
Achim


Input:
------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mediaobjectco PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"  "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<mediaobjectco>
    <imageobjectco>
        <areaspec units="calspair">
            <areaset id="oneway" coords="">
                <area id="oneway1" coords="300 400"/>
                <area id="oneway2" coords="325 340"/>
            </areaset>
            <area id="myhouse" coords="425 590"/>
        </areaspec>
        <imageobject>
            <imagedata fileref="http://maps.example.com/EARTH?USA?MA?01007"/>
        </imageobject>
    </imageobjectco>
</mediaobjectco>


Output:
-------
<html>
    <head>
        <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></title>
         <meta content="DocBook XSL Stylesheets V1.70.1" name="generator">
    </head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
        <div class="mediaobjectco">
            <img border="0" usemap="N10003" src="http://maps.example.com/EARTH?USA?MA?01007">
                <map name="N10003"><area shape="rect" coords="NaN,NaN,NaN,NaN">
                    <area shape="rect" coords="NaN,NaN,NaN,NaN">
                        <area shape="rect" coords="NaN,NaN,NaN,NaN">
                </map>
        </div>
    </body>
</html>
_______________________________________________
oXygen-user mailing list
oXygen-user@...
http://www.oxygenxml.com/mailman/listinfo/oxygen-user

Gmane