April 2008 - oXygen-user - www.oxygenxml.com

Validating XML instance with a Schema which imports another Schema
by Eric Jahn 24 Apr '08

24 Apr '08

I believe this is a bug with Oxygen 9.1, but please correct me if I'm erring in my thoughts or configuration. Here is the scenario: I have a schema which imports a second remote schema. I can validate this schema with its remote schema by configuring a custom validation scenario which declares the remote schema urls, as opposed to using local copies with a SchemaLocation declaration. If I declare local SchemaLocations, this all works and there are no validation errors, so I think I have isolated the problem to an Oxygen 9.1 bug. Now, I wish to perform the next logical step and validate an XML instance of this remote schema. The XML is located here: http://www.hmis.info/schema/2_8/Example_HUD_HMIS_Instance.xml Again, I set up an appropriate custom validation scenario declaring both remote schema (the referred schema) at: http://www.hmis.info/schema/2_8/HUD_HMIS_2_8.xsd and the one it imports at: http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd When I run the Oxygen default validation, I get the following error: "Message:src-resolve: Cannot resolve the name 'airs:tSiteService' to a(n) 'type definition' component." It's complaining about not finding the schema imported by the referred schema. It does find the referred schema aok. This should not happen, as I don't get this error when validating the referred schema, for which Oxygen's validator locates the imported schema when the custom validation scenario is declared. Thanks for either confirming a bug or determining my error. -Eric

2 5

oXygen and EXSLT
by ohaya＠cox.net 22 Apr '08

22 Apr '08

Hi, I was wondering if it's possible to get oXygen 9.1 working with EXSLT? I'm particularly interested in regExp, but when I try that, I get a debugger error "Unknown Saxon extension element: script". If someone has been able to get this working, can you please share how you accomplished this? Thanks, Jim P.S. I can't use XSLT 2.0 because it won't be available in another environment which is the target.

2 1

importation of a remote schema problem
by Eric Jahn 21 Apr '08

21 Apr '08

I have a schema here: http://www.hmis.info/schema/2_8/HUD_HMIS_2_8.xsd which in turn imports this schema: http://www.hmis.info/schema/2_8/AIRS_3_0_draft5_mod.xsd If I copy the latter schemas locally and give a SchemaLocation to the local copies, it validates fine. However, if I remove the local SchemaLocation statement, I get this validation error from Oxygen 9.1: "[Xerces] src-resolve: Cannot resolve the name 'airs:tSiteService' to a(n) 'type definition' component. @see: http://www.w3.org/TR/xmlschema-1/#src-resolve reposHUD/tags/HUD_HMIS_XML_2.8 HUD_HMIS_2_8.xsd line 828 1208818729409 195997" Why can't Xerces/Oxygen validate against the remote copy of the imported schema? I tried declaring it in the XML Catalog in Prferences, but it didn't help. Any insights are very appreciated. Thank you!

1 1

oXygen 9.2 Beta - ditamaps
by Steven Anderson 14 Apr '08

14 Apr '08

Love, love, love the new functionality in oXygen 9.2 related to DITA. On first pass, I noticed three issues: 1. I couldn't figure out how to specify which JDK to use for DITA transforms to PDF. This matters, because RenderX is much faster with JDK 1.6 than 1.5, but I need 1.5 for other tools. 2. The DITA transform doesn't appear to be sensitive to the catalog I've defined in my oXygen preferences, thus it uses the oXygen defaults for everything. 3. In the dita maps manager view, topicgroups, and their descendants, are not displayed. Is this the right forum to post these kinds of issues/questions? Steve

2 1

oXygen 9.2 beta
by George Cristian Bina 11 Apr '08

11 Apr '08

Hi, We are getting close to a new oXygen release. This will be a version 9 maintenance release, oXygen 9.2. We made available a beta build from the links below: Windows http://www.oxygenxml.com/update/9.2/Oxygen/Windows/VM/oxygen.exe http://www.oxygenxml.com/update/9.2/Oxygen/Windows/NoVM/oxygen.exe Linux http://www.oxygenxml.com/update/9.2/Oxygen/Linux/VM/oxygen.sh MacOS X http://www.oxygenxml.com/update/9.2/Oxygen/MacOSX/oxygen.tar.gz Eclipse 3.3 update site http://www.oxygenxml.com/update/9.2/Oxygen/Eclipse/site.xml What is new in 9.2... There are more than 450 issues that were recorded as fixed in 9.2 already and probably the number will grow near 500 when it will become generally available. I will try to enumerate a few from the most important additions below. * oXygen Author =============== There are people that are not developers or there are times when you are not interested in the development features of oXygen and you want just to do XML editing. The oXygen Author removes the development features offering a more simple interface for XML editing. To start the oXygen Author you can use the author executable or the author batch script from your oXygen installation. The oXygen Author is available also as a separate product, both as a standalone application and as an Eclipse plugin. The separate oXygen Author installation kits are below. The license key for oXygen works also with the oXygen Author: Windows http://www.oxygenxml.com/update/9.2/Author/Windows/VM/author.exe http://www.oxygenxml.com/update/9.2/Author/Windows/NoVM/author.exe Linux http://www.oxygenxml.com/update/9.2/Author/Linux/VM/author.sh MacOS X http://www.oxygenxml.com/update/9.2/Author/MacOSX/author.tar.gz All http://www.oxygenxml.com/update/9.2/Author/All/author.tar.gz Eclipse 3.3 update site http://www.oxygenxml.com/update/9.2/Author/EclipseAuthor/site.xml * Navigation support ==================== The visual editing (Author mode) supports now links. The links are specified in the associated CSS using a link property. oXygen will render them and will open the referred document when you click on a link. We updated the DITA, TEI and DocBook CSS stylesheets to add link support for the specific linking elements in each framework. The link support works also with DITA conrefs and XInclude. * In place view of the included/referenced content ================================================== The included content (with XInclude for instance) or the referred content is presented in place as a read only block that can be collapsed/expanded. This gives the view of the result document with the inclusions and references resolved. * Inline tags - new visual rendering in Author ============================================== In this rendering mode the block tags are hidden and the inline tags are presented. This is available from the Author toolbar and from the Author menu and gives a compact visual view while showing the inline elements' tags. * DITA maps manager =================== This allows viewing and editing DITA map files. It acts also similar with a project manager allowing to easily open different topics/concepts for editing. You should get the DITA maps manager visible automatically if you open a .ditamap file in oXygen. It will appear as a tab in the same stack with the Project. The toolbar, the contextual menu and drag and drop actions will allow to easily edit the map content. Double click to open a referenced file for editing. * Closely integration of the DITA Open Toolkit for transformations ================================================================== This allows to easily configure and execute specific DITA transformations from the DITA Maps manager to different formats (XHTML, PDF, HTML, JavaHelp, Eclipse Help, DocBook, etc.). These are DITA specific using the DITA Open Toolkit and providing more options than the standard XSLT transformation scenarios, see the Filters and Advanced tabs when editing a scenario. * DITA conref support ===================== You can easily insert conrefs using the "Insert a DITA Content Reference" action from the DITA toolbar or from the contextual menu Insert->Insert Content Reference. * Synchronize the end tag with the start tag changes ==================================================== If the start tag is changed oXygen will automatically change also the end tag, thus keeping the document well formed and saving you a few keystrokes. * ISO Schematron improvements ============================= Allowing foreign elements in ISO Schematron schemas is controllable from the oXygen Schematron options. These are useful for instance when you want to access an XSLT 2.0 function from a Schematron rule. Also it is possible to specify that Schematron should be executed with Saxon SA (schema aware) and thus be able to use schema aware checks inside the Schematron rules. Internationalization improvements ================================= The wrapping of CJK (Chinese Japanese Korean) text takes into account punctuation marks. The Author and XML Source pages display on-the-spot the composed text (for instance when editing CJK text). The composed text is shown in the context of the document that it will eventually belong to, in a style that indicates that the text still needs to be converted or confirmed by the input method. Latest Saxon 9 ============== oXygen 9.2 supports the latest version of Saxon 9.0.0.4. Latest DocBook 5 schemas and stylesheets ======================================== The DocBook 5 final release schemas are included. The stylesheets were updated to docbook-xsl-ns-1.73.2. Latest XQDoc ============ XQDoc version 1.6 was integrated for generating XQuery documentation from within oXygen. We have also 2 DITA video demonstrations showing the DITA Maps manager and the DITA editing: http://www.oxygenxml.com/update/ditamapsmanager/ditaMapsManager.html http://www.oxygenxml.com/update/ditaediting/ditaEditing.html Best Regards, George --------------------------------------------------------------------- George Cristian Bina - http://aboutxml.blogspot.com/ <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

2 2

Add XSLStyle by default in OxygenXML
by mozer 08 Apr '08

08 Apr '08

Dear, I ask for a new integration to add by default XSLStyle inside OxygenXML Regards, Xmlizer

3 2

xml:space="preserve" and IDE space preserve
by Robert Koberg 04 Apr '08

04 Apr '08

Hi, Let's say I have this is one page: <div> <script xml:space="preserve"> if (true) { alert("boo"); } </script> </div> If I paste that with the xml:space *or* with the element included IDE's Options Preference for 'Preserve Space elements (XPath)' the result of the past is: <div> <script xml:space="preserve"> if (true) { alert("boo"); } </script> </div> Is this a bug? best, -Rob

2 1