- oXygen-user - www.oxygenxml.com

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

Failed to create InputSource
by Kai Mütz 06 Aug '07

06 Aug '07

Hi, I use oXygenxml 7.2 within Eclipse 3.2.1 and want to resolve a path to a XML schema file using a catalog file whiche I have registered in oxygen preferences. The verbose output tells me that oxygen resolves the systemid correctly (Resolved System: http://.... file://.....) but cannot load the schema file from the resolved location: Failed to create InputSource: file://.... The resolved location is definitly correct and points to a valid schema file. Can anyone help me? Regards, Kai

2 2

Is It PossibleTo Assign Shortcuts Keys For Code Template
by Jeff Sese 27 Jul '07

27 Jul '07

Hi, Is it possible to assign shortcut keys for custom code template? Or is it possible to assign shortcut keys for commonly used unicode characters? It nice that oxygen has the character map dialog so that insertion of unicode characters can be easy, but it would really be nice if I can assign shortcut keys to commonly type/inserted unicode characters. I workaround that I did was assign code templates for these characters but the feedback that I got from other possible user of the editor is that it would be better if shortcut keys can be assigned. Also, when I assigned a code template like this: "ó${caret}", when I execute it using the ctrl+space the caret position moves back to the start of the character, I was assuming that it would be at the end of the character. Is this a bug? Thanks, Jeff -- *Jeferson L. Sese* Asiatype Incorporated Suite 114, Columbia Tower, Ortigas Ave., Greenhills, Mandaluyong City 1550 Philippines

2 3

XML Schema and empty elements
by Timothy Reaves 26 Jul '07

26 Jul '07

I'd like to have my schema specify that not only are certain elements required, but that they can't be blank. I can't seem to find how to specify this. I thought it was the nillable attribute, but that doesn't prevent blank elements.

2 2

XML Schema & XInclude ?
by Timothy Reaves 26 Jul '07

26 Jul '07

I have an xml schema I've created. I'd like to have several XML documents that are combined into a larger one (I do this with DocBook & chapters). But I can't figure out how to do this with XMLSchema. Basically what I have is one xml document per environment (it's for configuration information). I'd like to have a parent document that has elements from the schema that are generic to the overall base, then includes the several smaller environment xml documents. Any ideas? Thanks!

2 6

iso schematron reports cause validation failure
by lars 24 Jul '07

24 Jul '07

Hello, I'm using Schematron to validate XML documents in Oxygen 8.2. My Schematron schema includes "asserts" (as usual) and also "reports." When a "report" is triggered, the message is displayed by oxygen (as it should be), but Oxygen also says "Validation failed: n errors", which I think is incorrect. My understanding from the Schematron spec is that "asserts" are for detecting validation errors, while reports are for giving the user neutral information. I couldn't find a very authoritative source for this, but these two articles support it: http://www.xml.com/pub/a/2000/11/22/schematron.html?page=2 (The general intent is that /assert/ is used to detect errors, while /report/ can be used to report affirmative qualities of an instance.) http://www.ldodds.com/papers/schematron_xsltuk.html#c35e2592b6b3 While reports and asserts are effectively the inverse of one another, the intended uses of the two elements are quite different. An assert is used to test whether a document conforms to a particular schema, generating actions if deviations are encountered. A report is used to highlight features of the underlying data: *Example 6. A simple report* <report test="not(roof)">This house does not have a roof</assert> The distinction may seem subtle, especially when grapplying with a constraint which may be expressed simpler in one way or the other. However Schematron itself does not define the action which must be taken on a failed assert, or successful report, this is implementation specific. The default behaviour is to simply provide the user with the provided message. An implementation may choose to handle these two cases differently. So, it seems to me that when a "report" is triggered, oxygen should display the message but should not say that validation failed unless some "assert"s have failed. Lars

3 4