November 2005 - oXygen-user - www.oxygenxml.com

XSD Validation Error
by Helder Rossa 01 Dec '05

01 Dec '05

Hi, I've got several errors validating a correct xsd file in oXygen Eclipse Plug-In. Importing a XSD File Error: src-import.3.2: An <import> element information item that had no namespace attribute was found, so the imported document cannot have a targetNamespace attribute. However, the targetNamespace 'uri:namespace' was found in the imported document. @see: http://www.w3.org/TR/xmlschema-1/#src-import Occurs when: <xs:import schemaLocation="anotherfile.xsd" /> Only works when: <xs:import namespace="uri:namespace" schemaLocation="anotherfile.xsd" /> This is incorrect!! Use Attribute in a Element Error: s4s-att-not-allowed: Attribute 'use' cannot appear in element 'attribute'. Occurs when: <xs:attribute name="type" type="xs:string" use="required" /> Only Works when: <xs:attribute name="type" type="xs:string" use="required" /> This is incorrect because use attribute is OK. What I have to configure for oXygen work corrrectly?! Thanx

2 5

Find in Files: exclude paths?
by Lars Huttar 30 Nov '05

30 Nov '05

Hello, I use Oxygen on projects that have source control with Subversion, as I'm sure many do. When I do a "Find in Files" on a folder, I sometimes get a lot of "false positives" because it looks in the .svn folders (Subversion working copy metadata) as well as in the actual files that I edit. I would like to be able to tell the "Find/Replace in Files" dialog to exclude all files with a path containing "/.svn/". Is there any way to do this? If not, consider this a feature request. Thanks, Lars

2 2

OS X menu item
by Timothy Reaves 21 Nov '05

21 Nov '05

I've just notices that I now have 3 entries for oXygen on the Open With context menu. Does the installer not check to see if it is present before adding it? What's the easiest way to remove the extra 2? Thanks.

2 1

Docbook 5.0 Relax Schema and Xpointer Resolution
by Ray Miller 16 Nov '05

16 Nov '05

Attempting to utilize the Docbook 5.01 Relax schema with xsl-1.69.1 and oXygen-6.2. Problem with xpointers. When utilized in conjunction with xincludes, xpointers resolve via absolute positioning but not via id. Could this be an issue with xinclude.mod and the xml:id designation in v5.0 or my misconfiguration? Ray

2 4

Docbook 5.0b1 Left and Right Nav Text and/or Graphics Not Appearing
by Ray Miller 16 Nov '05

16 Nov '05

docbook-rng-5.0b1, xsl-1.69.1 (chunk) saxon-6.5.4 oXygen-6.2 Document consists of a book root with xinclude'd chapters which include nested xinclude'd sections, etc. Html rendering results in left and right navigation text ( and graphics when nav.graphics is set to 1 ) not appearing; home and parent section (up) does appear and function correctly. History: I transitioned a document that successfully validates and transforms with docbook-dtd-4.5CR1 xsl-1.69.1 saxon-6.5.4 and oXygen-6.2, transforming the xml prologs and prototypes to support Docbook-rng-5.0b1. Content was modified to support Docbook-rng ( ulink to link ns1:href, etc ) and successfully validates. The same stylesheet and stringparms are utilized. No images are utilized in the document. Below is the HTML source fragment resulting from the dtd and rng transformations: DTD: }</style><link rel="start" href="index.html" title="Foo Plan"><link rel="up" href="ch01s01.html" title="1.1. Project Summary"><link rel="prev" href="ch01s01.html" title="1.1. Project Summary"><link rel="next" href="ch01s01s01s01.html" title="1.1.1.1. Statement of Purpose"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.1.1. Purpose, Scope and Objectives</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s01.html">Prev</a> </td><th width="60%" align="center">1.1. Project Summary</th><td width="20%" align="right"> <a accesskey="n" href="ch01s01s01s01.html">Next</a></td></tr></table><hr></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="purpScopeObj"></a>1.1.1. Purpose, Scope and Objectives</h3></div> RNG: }</style><link rel="start" href="index.html" title="Foo Plan"><link rel="up" href="ch01s01.html" title="1.1. Project Summary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.1.1. Purpose, Scope and Objectives</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center">1.1. Project Summary</th><td width="20%" align="right"> </td></tr></table><hr></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="purpScopeObj"></a>1.1.1. Purpose, Scope and Objectives</h3></div> Advice please. Ray

2 1

XML Schema validation and XInclude
by Robert Koberg 14 Nov '05

14 Nov '05

Hi, I have some XML Schemas that xs:import the xml namespace attributes (xml:base so I can use XInclude and be able to validate it). I am getting a validation error on the schemas themselves when I try to validate in oxygen saying they can't find the xml.xsd which is in the same directory as the import schema. Here is the error message: Description: W schema_reference.4: Failed to read schema document 'xml.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. URL: http://www.w3.org/TR/xmlschema-1/#schema_reference When I use JARV/MSV the schemas validate (and so does the instance document). Is this a bug in oxygen or perhaps xerces? I am using oxygen 6.1 and Mac OS X. (I have also tried using xs:anyAttribute with the xml namespace and neither oxygen or JARV validates the instance document.) Here is a test schema and a xml.xsd: <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="xml.xsd"/> </xs:schema> <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"> <xsd:attribute name="base"/> </xsd:schema> best, -Rob

2 4

oXygen performance on current Apple Macs?
by David Sewell 13 Nov '05

13 Nov '05

Does anyone have experience running oXygen on current models of the Apple G5 iMac versus a G5 dual PowerMac? I am due for an upgrade from an 800Mhz dual G4 PowerMac and I need to decide between iMac and PowerMac. Speed in parsing/transforming large and complex XML documents (and document collections) is going to be important to me. thanks, DS -- David Sewell, Editorial and Technical Manager Electronic Imprint, The University of Virginia Press PO Box 400318, Charlottesville, VA 22904-4318 USA Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903 Email: dsewell(a)virginia.edu Tel: +1 434 924 9973 Web: http://www.ei.virginia.edu/

2 1

FW: [docbook-apps] Table and Border Columns do not Appear
by Ray Miller 08 Nov '05

08 Nov '05

FYI _____ From: Ray Miller [mailto:millerr@centechgroup.com] Sent: Monday, November 07, 2005 6:16 PM To: docbook-apps(a)lists.oasis-open.org Subject: RE: [docbook-apps] Table and Border Columns do not Appear >> Have you tried it outside of Oxygen?<< That did the trick. I suppose I should read the transformation output once in a while. "Bad attribute border-top-width: Attribute type mismatch: border-before-width.length cannot have value '0.5pt' of type Word" Seems XEP doesn't like the quotes that oXygen-6.2 applies by default to stringparm values . Ray

2 1

Relax and Catalog Resolution
by Ray Miller 02 Nov '05

02 Nov '05

Utilizing Oxygen-6.2, Docbook-5.0b1 and Windoz-XP The following Relax oXygen processing instruction: <?oxygen RNGSchema="file:/// _fooRngBase_/docbookxi.rng" type="xml"?> Does not resolve in the catalog: . . <group prefer="system" xml:base="file:///C:/usr/local/docbook/"> <group xml:base="docbook-xml-5.0b1/"> <rewriteSystem systemIdStartString="file:///_fooRngBase_/" rewritePrefix="rng/"/> <rewriteURI uriStartString="file:///_fooRngBase_/" rewritePrefix="rng/"/> </group> </group> . . When utilizing a dtd, catalog resolution is not a problem. Ray

2 2