- oXygen-user - www.oxygenxml.com

Using Catalogs with Saxon8B XQuery Processor
by Eliot Kimber 22 Aug '07

22 Aug '07

I'm trying to use Saxon through Oxygen to query documents that require a catalog for DTD resolution (the DTD system ID is an absolute URI that isn't a real location). I've configured Oxygen's catalog setup to use my catalogs and that works fine. When I try to doc a query like this: Let $docs := collection(iri-to-uri("mydocsdir&recurse=yes;select=*.xml")) I get a "404 Not Found for: {URI of DTD} I didn't see any obvious option for specifying the catalog. Since I'm using Saxon's built-in catalog resolver I'm not sure what to do to make it work with my catalogs. Thanks, Eliot ---- W. Eliot Kimber Senior Solutions Architect Really Strategies, Inc. 512 554 9368

2 2

3-way merge?
by lars 17 Aug '07

17 Aug '07

Hello, The XML Diff/Merge tool that comes with Oxygen looks pretty nice. However there doesn't seem to be provision for a 3-way merge (using a common ancestor). This kind of merge is a common requirement when a repository of XML documents is continually modified by a distributed team or company; users need to keep merging others' changes to documents with their own changes before committing modified documents to the repository. This would tie in well with the Synchro SVN client, which allows you to perform merges in exactly this situation, but apparently without the benefit of common-ancestor-awareness (?), or at least without XML-awareness and common-ancestor-awareness at the same time. Are there any plans to incorporate 3-way (common ancestor) merge into Oxygen Diff/Merge tool? Regards, Lars

2 1

DocBook 5 rng-based documents
by Khaled Aly 13 Aug '07

13 Aug '07

Hi oXygen 8.2 supports both DocBook 4.4 and 5.0. According to Norm Welsh DockBook5 Definitive Guide [quote/unquote]: "The normative schema for DocBook V5.0 is the RELAX NG Grammar with its Schematron annotations. The only reason to use a DTD with DocBook V5.0 is if your editing environment (or other tool) requires one, for example, for syntax directed editing." The sample provided with oXygen 8.2 has this declaration: <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V5.0//EN" "http://www.oasis-open.org/docbook/xml/5.0/docbook.dtd"> Anyone knows what should be the proper DOCTYPE declaration if the document is to be based on the RNG. And is there any specific impact on transformation functions in that case? Thanks for help. ka

3 3

PDF Transformation
by Miller, Ray (Centech) 13 Aug '07

13 Aug '07

xep-4.10 docbook-rng-5.0cr5 xsl-1.73.0 oxygen-8.2.0 (eclipse-3.3 plugin) Receive the following PDF transformation error: [error] Fatal parse error: file:/C:/Documents and Settings/foo/workspace/fooSOP/fooSOPxml/InternalSOPs/trunk/xmlFlowReview .xml_fo: line 2, column 121: Invalid URL C:\Documents and Settings\foo\My Documents\foo\Docbook\docbook-xml\dtd\docbook.dtd (unknown protocol: c) Ray

2 1

unsubscribe
by Dimitri Baeli 13 Aug '07

13 Aug '07

1 0

XSLT coping xsi:schemaLocation?
by Timothy Reaves 09 Aug '07

09 Aug '07

O.K., I think I'm down to the last issue. When I run my transform, my root elements xsi:schemaLocation attribute is not copied over however. As I need to process the root elements children, I have to use copy. I tried using the same technique I use for other attributes, but I can't specify an attribute name with xsi: in the name. Anyone know how to get the location to copy over? I still need it in place to validate the transformed element. I'd even settle for being able to hard-code the value in the XSL file. Thanks.

2 3

validation and custom java extensions
by Hausherr, Jens 09 Aug '07

09 Aug '07

Hello, maybe I have missed it in the documentation: How do I register custom XSLT-extensions implemented in Java so that the editor stops complaining about not finding a matching function? The transform works fine if I register my Jar file as an extension so the error reported by the editor is a little annoying. Mit freundlichen Gruessen / Best Regards / Avec mes meilleures salutations Jens Hausherr Senior Consultant Tel: +49-178-8866-097 Fax: +49-178-998866-097 mailto: jens.hausherr(a)logicacmg.com <blocked::mailto:jens.hausherr@unilog.logicacmg.com> Unilog Avinci - a LogicaCMG company Am Sandtorkai 72 D-20457 Hamburg http://www.unilog-avinci.de <blocked::http://www.unilog-avinci.de/> Unilog Avinci GmbH Zettachring 4, 70567 Stuttgart Amtsgericht Stuttgart HRB 721369 Geschäftsführer: Torsten Straß / Eric Guyot / Rudolf Kuhn / Olaf Scholz / Thomas Elsner This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

2 1

xsl question
by Timothy Reaves 09 Aug '07

09 Aug '07

I have an issue I'm trying to resolve. When I perform an xslt transform in the XSLT Debugger, the output is what I expect. When I execute a transform with the command line: java org.apache.xalan.xslt.Process -in applications\InputTemplate.xml -xsl configxsl\transformer.xsl -out applications\Output.xml the output is not the same. In oXygen, I've specified InputTemplate.xml as the XML, transformer.xsl as the XSL (both open in buffers) and Xalan. The difference I'm seeing is that in the debugger, an XInclude is being included (the output window shows the combined document, and properly transformed. This is what I want). The output when run from the command line leaves the XInclude element alone, but otherwise properly transforms the document. So does oXygen just process in-memory? Is there a way to see the equivalent command line? Thanks.

2 2

Saxon xinclude processing of Xquery
by Christian Wittern 09 Aug '07

09 Aug '07

Dear Oxygen users, The Saxon documentation (http://www.saxonica.com/documentation/changes/intro/xinclude89.html) says that starting with Version 8.9 (Java implementation) there is support for xinclude processing for both XSLT and XQuery. Now, since Oxygen 8.2 already bundles Saxon B 8.9.0.3 and it runs on my Mac with Java 1.5, I assume it should be possible to tell Saxon to expand my xincludes for the query. However, I can't quite figure out if Oxygen has an option somewhere or, failing that, how I can pass a commandline argument for Saxon through the transformer. Any help appreciated, Christian -- Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN

2 3

[bug] printing diagrams is broke
by Timothy Reaves 08 Aug '07

08 Aug '07

I went to print a diagram of a schema I have been working on. So I context-clicked and selected print. The dialog that pops up offers little real options (margin and orientation), so I just pressed OK and walked over to the printer. Where 24 pages of paper were waiting for me. So I'm left wondering what moron thought that was a good thing when designing the print system? What an incredible waste of paper. Plus, like I really have nothing better to do that tape 24 pages (it's a relatively small schema too) together. I'm a big fan of oXygen, and have converted several of my co-workers over to it. This is really the first time I've had to just scratch my head in wonder. For images, the print system should either constrain to a single page (the default), or ask what to do.

2 4