- oXygen-user - www.oxygenxml.com

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

Re: [oXygen-user] Feature requests
by Francois Jordaan 28 Mar '08

28 Mar '08

I appreciate the considerate response, Sorin. > We will modify the double click action. A double click on an > attribute name or an attribute value will select the whole > the attribute. A double click on a single tag will select > the whole tag including the '<' and '> characters. Thanks, that sounds good. I'm unsure whether everyone else will agree with this, so it should probably be an option in Preferences. > > You are the only user that requested to clear the clipboard when > > nothing is selected in the editor panel. > I don't think FJ was requesting the clipboard be cleared, I think he > was complaining about it. Syd is correct: I was complaining. Cmd-V is an awkward chord on a Mac keyboard, and I often accidentally hit Cmd-C when I intended to paste. My clipboard is then cleared, an annoyance that's impossible to undo. > In version 9.2 we will add the option "Cut/Copy whole > line when nothing is selected" for the text editor in > Options -> Preferences -> Editor. With this option the > function of cut/copy the whole line can be disabled. Thanks, that will fix my problem. > Now I understand. We will make the tag inserted by the > previous Surround operation the default item selected in the > combo box of the Tag dialog invoked by Ctrl-E. For example > if the previous Surround operation inserted <link> when > Ctrl-E is pressed the "link" item will be selected by > default in the combo box. If the dropdown list of the combo > does not contain "link" the first item of the list will be > selected. That will be perfect. Thanks again! francois -- francois(a)isotoma.com / Isotoma, Open Source Software Consulting Tel: 01904 567349 / Mobile: 07872 394273 / Fax: 020 79006980 Skype: fjordaan / http://www.isotoma.com Postal Address: Tower House, Fishergate, York, YO10 4UA, UK Registered in England. Company No 5171172. VAT GB843570325. Registered Office: 19a Goodge Street, London, W1T 2PH

1 0

Feature requests
by Francois Jordaan 28 Mar '08

28 Mar '08

Hi, I'm a very satisfied oXygen user (primarily working in XHTML and CSS), but I'd be happier still if it had the following simple enhancements: (I'm using oXygen 9.1 build 2007122116 on OS X Tiger) 1. Remember last Ctrl-E (wrap tags) value -- currently always defaults to 'a' 2. Improve Ctrl-E (wrap tags) to allow .class and #id attribute specification (e.g. I could Ctrl-E span.active and get <span class="active"></span> 3. Major annoyance (and arguably a bug): Don't clear clipboard when copying nothing (hitting Ctrl-C or X with nothing selected.) 4. Need shortcuts to make it easier to select attribute/value pairs and single tags (so that you don't have to drag-select around <tag> or attribute="value") Triple-click is already taken, so maybe Ctrl-click or something. 5. Cursor movement up/down: always remember x position from line to line, even after pasting. This is a little harder to explain. Basically, I'd like oXygen to behave like Textpad. Imagine you have a number of lines and you want to paste "<li>" in front of each. If I position the cursor in the right place for the first line, paste, then press down, I expect to be in the right place for the next line. But in oXygen, I'll be 4 characters to the right (from the end of the <li>) Bug fixes: 6. The "Delete Tag" keyboard shortcut on Mac (Cmd-Opt-X) doesn't work 7. The CSS validator doesn't recognise unitless line-height I'd appreciate it if you could consider these for a minor upgrade! (And anyone else reading this -- if you agree or disagree please say so.) francois -- francois(a)isotoma.com / Isotoma, Open Source Software Consulting Tel: 01904 567349 / Mobile: 07872 394273 / Fax: 020 79006980 Skype: fjordaan / http://www.isotoma.com Postal Address: Tower House, Fishergate, York, YO10 4UA, UK Registered in England. Company No 5171172. VAT GB843570325. Registered Office: 19a Goodge Street, London, W1T 2PH

7 12

Caching doc() calls
by Andrew Welch 28 Mar '08

28 Mar '08

It seems oXygen caches the XML from calls to doc() between runs? If you run a transform with doc('foo.xml') and then delete foo.xml, you can still run the transform! The doc() call works without causing an error... It's just taken me a while to figure out why a transform run from inside oXygen produced different result from the same transform run outside of oXygen - it was because a referenced doc() had been updated while oXygen was open and oXygen wasn't fetching it each time. Shouldn't oXygen's caching resolvers (if that's where the problem lies) only cache per transform run? -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/

3 3

RE: [oXygen-user] Feature requests
by Wendell Piez 28 Mar '08

28 Mar '08

Hi, Or that insert element window could allow a little XPath: phrase[@condition] gets <phrase condition="">...</phrase> phrase[@condition='active'] gets <phrase condition="active">...</phrase> (Just brainstorming here) Cheers, Wendell At 01:55 PM 3/26/2008, Barton wrote: >It might be more useful for oXygen's Ctrl-E to accept any tag >appended with a dot as an attribute name for the selected element. >Thus, to take a DocBook example, if I select phrase in the Ctrl-E >dialog and then type an extra .condition (the dialog now reads >phrase.condition), oXygen could know to translate this as <phrase >condition="">selected text</phrase>. I still have to back up and >fill in the condition name, but it's a timesaver even so. A pair of >options in Preferences for CSS files could be: > For Ctrl-E, use .name to mean class="name" > For Ctrl-E, use .name to mean name="" (default if enabled > with the above preference) ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

1 0

[xsl] Transformation from XSL1 to XSL2 error
by Dam's 28 Mar '08

28 Mar '08

Hi, I need to transform some XSL1 stylesheets to XSL 2 to use them with Saxon 8.7.3. I changed the version in the declaration and some little other things, but, obviously, it's not enough... I have an error which's making me crazy... > An attribute node (color) cannot be created after the children of the > containing element > The transformation failed due to an XML parsing or transformation error. > It seems to be about this part of my XSLs : > <xsl:template name="process.change"> > <xsl:param name="CHG"></xsl:param> > <xsl:if test="$CHG='ADD'"> > *<xsl:attribute name="color">red</xsl:attribute> (Especially this line!)* > </xsl:if> > <xsl:if test="$CHG='MOD'"> > <xsl:attribute name="color">orange</xsl:attribute> > </xsl:if> > </xsl:template> I don't understand what's the problem with color attribute node... I searched again and again with google... Some users have the same error but I don't understand how to resolve it in my case. Someone could help me, please? Thanks!!! Damien G.

2 1

Regular Expression That Matches Across Newlines?
by Eliot Kimber 26 Mar '08

26 Mar '08

Is the following possible using a regex search and replace? I have data that looks like this: 1. Some text? blah blah 2. Some more text second line? blah blah What I want to do is match on everything from the start of lines starting with "[0-9]+\." through the "?", Capturing the text between the initial "." and the "?". Is this possible with Oxygen? I can't figure it out. Thanks, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

1 1

RE: [oXygen-user] When will oNVDL handle ISO Schematron, XSLT 2.0and XPATH 2.0 [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 18 Mar '08

18 Mar '08

Hi George, Thanks for your reply. There was talk of it being released late last year but that time line has passed. ;--) Thanks. John > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of > George Cristian Bina > Sent: Tuesday, 18 March 2008 5:31 PM > To: Hockaday John > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] When will oNVDL handle ISO > Schematron, XSLT 2.0and XPATH 2.0 [SEC=UNCLASSIFIED] > > > Hi John, > > That is my question but I do not have an exact answer... > I will try to schedule some more work on that soon. > > Best Regards, > George > --------------------------------------------------------------------- > George Cristian Bina - http://aboutxml.blogspot.com/ > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > > > John.Hockaday(a)ga.gov.au wrote: > > Hi all, > > > > I'm not sure if this is the right list to ask about oNVDL > but I couldn't find > > another one. > > > > When will oNVDL be able to handle (via Saxon 9) ISO > Schematron, XSLT 2.0 and > > XPATH 2.0? > > > > Thanks. > > > > > > John > > _______________________________________________ > > oXygen-user mailing list > > oXygen-user(a)oxygenxml.com > > http://www.oxygenxml.com/mailman/listinfo/oxygen-user > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user >

1 0

When will oNVDL handle ISO Schematron, XSLT 2.0 and XPATH 2.0 [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 18 Mar '08

18 Mar '08

Hi all, I'm not sure if this is the right list to ask about oNVDL but I couldn't find another one. When will oNVDL be able to handle (via Saxon 9) ISO Schematron, XSLT 2.0 and XPATH 2.0? Thanks. John

2 1

Can't increase stack size.
by Gavin Kistner 17 Mar '08

17 Mar '08

Oxygen is overflowing the stack trying to validate one of my XML files against its schema. However, if I modify this file: C:\Program Files\Oxygen XML Editor 9\oxygen.vmoptions from this: -Xmx700m to this: -Xmx700m -Xss1024k Oxygen fails to start. I select it from the Start Menu and get this message: Error The JVM could not be started. The main method may have thrown an exception. If I delete the Xss option again it works. I've tried values of 512k, 512 and 1024k. This is on XP SP2 with Oxygen build 2007121417 Should the options be on multiple lines? Any help on how I can increase the stack size? FWIW, the failure seems to be on this attribute: <xs:attribute name="values"> <xs:simpleType><xs:restriction base="xs:string"> <xs:pattern value="(-?(\d+|\d*\.\d+)(,-?(\d+|\d*\.\d+))?;)*-?(\d+|\d*\.\d+)(,-?(\d+|\d*\.\d+))?"></xs:pattern> </xs:restriction></xs:simpleType> </xs:attribute> with this value: values="0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109;0.114,0.114;0.129,0.129;0.154,0.154;0.187,0.187;0.226,0.226;0.271,0.271;0.319,0.319;0.368,0.368;0.416,0.416;0.461,0.461;0.500,0.500;0.533,0.533;0.558,0.558;0.573,0.573;0.578,0.578;0.573,0.573;0.558,0.558;0.533,0.533;0.500,0.500;0.461,0.461;0.416,0.416;0.368,0.368;0.319,0.319;0.271,0.271;0.226,0.226;0.187,0.187;0.154,0.154;0.129,0.129;0.114,0.114;0.109,0.109" Is there any way to turn off backtracking for the regexp, which presumably would help here?

3 3

Confusing Message When Schema Cannot Be Found
by Eliot Kimber 11 Mar '08

11 Mar '08

In testing my catalog's ability to resolve this document's schema: <?xml version="1.0" encoding="UTF-8"?> <test xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:foo:/schemas/test.xsd" ></test> When the catalog was not correctly configured Oxygen 9.1 reported "There is no schema or DTD associated with the document". But what it really needed to say is "cannot find schema at schema location "urn:foo:/schemas/test.xsd". I thought it was complaining about the form of my schema attributes. Cheers, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

2 1

xml database
by Boojum 11 Mar '08

11 Mar '08

Anybody have any experience using / integrating Oxygen with a native XML database like Exist, Sedna or Xindice? How about with an XML content management system?

2 1

How Does Oxygen Validate This Dublin Core Schema?
by Eliot Kimber 10 Mar '08

10 Mar '08

In testing our own schema-based validation features in our RSuite product we discovered that as far as we can tell Xerxes 2.9.x fails to validate the valid Dublin Core schema given below. This is a documented problem with Xerces in that it doesn't handle the particular pattern of restriction and substitution groups used in this schema. However, Oxygen happily (and correctly) validates documents using this schema (that is, our test case fails when we parse it with our Xerces-based code but Oxygen reports it as valid). My understanding was that Oxygen used Xerces for its schema processing, so my question is: what does Oxygen do special that allows it to process this case, or is our understanding of Xerces flawed? The failure we get is than an instance of e.g., dc:title is reported by Xerces as not allowing character data content when of course it does. The original discussion of this issue from the Dublin Core people is here: http://dublincore.org/schemas/xmls/qdc/2008/02/11/notes/ Very near the bottom is this: This derivation of a complexType with simpleContent by restriction of a base complexType with complexContent is valid under section 3.4.6 of XML Schema Part 1: Structures, specifically item 5.1.2 of the section "Schema Component Constraint: Derivation Valid (Restriction, Complex)", because the base complexContent is mixed and emptiable. This was confirmed by Henry Thompson, see e.g. http://www.w3.org/2001/05/xmlschema-rec-comments#pfiSimpleContent http://lists.w3.org/Archives/Public/xmlschema-dev/2002Oct/0005.html http://lists.w3.org/Archives/Public/xmlschema-dev/2002Oct/0008.html Conclusion: Xerces appears to be behaving incorrectly in rejecting this derivation. Thanks, Eliot <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://purl.org/dc/elements/1.1/" targetNamespace="http://purl.org/dc/elements/1.1/" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:annotation> <xs:documentation xml:lang="en"> DCMES 1.1 XML Schema XML Schema for http://purl.org/dc/elements/1.1/ namespace Created 2003-04-02 Created by Tim Cole (t-cole3(a)uiuc.edu) Tom Habing (thabing(a)uiuc.edu) Jane Hunter (jane(a)dstc.edu.au) Pete Johnston (p.johnston(a)ukoln.ac.uk) Carl Lagoze (lagoze(a)cs.cornell.edu) This schema declares XML elements for the 15 DC elements from the http://purl.org/dc/elements/1.1/ namespace. It defines a complexType SimpleLiteral which permits mixed content and makes the xml:lang attribute available. It disallows child elements by use of minOcccurs/maxOccurs. However, this complexType does permit the derivation of other complexTypes which would permit child elements. All elements are declared as substitutable for the abstract element any, which means that the default type for all elements is dc:SimpleLiteral. </xs:documentation> </xs:annotation> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/03/xml.xsd"> </xs:import> <xs:complexType name="SimpleLiteral"> <xs:annotation> <xs:documentation xml:lang="en"> This is the default type for all of the DC elements. It permits text content only with optional xml:lang attribute. Text is allowed because mixed="true", but sub-elements are disallowed because minOccurs="0" and maxOccurs="0" are on the xs:any tag. This complexType allows for restriction or extension permitting child elements. </xs:documentation> </xs:annotation> <xs:complexContent mixed="true"> <xs:restriction base="xs:anyType"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="0"/> </xs:sequence> <xs:attribute ref="xml:lang" use="optional"/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:element name="any" type="SimpleLiteral" abstract="true"/> <xs:element name="title" substitutionGroup="any"/> <xs:element name="creator" substitutionGroup="any"/> <xs:element name="subject" substitutionGroup="any"/> <xs:element name="description" substitutionGroup="any"/> <xs:element name="publisher" substitutionGroup="any"/> <xs:element name="contributor" substitutionGroup="any"/> <xs:element name="date" substitutionGroup="any"/> <xs:element name="type" substitutionGroup="any"/> <xs:element name="format" substitutionGroup="any"/> <xs:element name="identifier" substitutionGroup="any"/> <xs:element name="source" substitutionGroup="any"/> <xs:element name="language" substitutionGroup="any"/> <xs:element name="relation" substitutionGroup="any"/> <xs:element name="coverage" substitutionGroup="any"/> <xs:element name="rights" substitutionGroup="any"/> <xs:group name="elementsGroup"> <xs:annotation> <xs:documentation xml:lang="en"> This group is included as a convenience for schema authors who need to refer to all the elements in the http://purl.org/dc/elements/1.1/ namespace. </xs:documentation> </xs:annotation> <xs:sequence> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element ref="any"/> </xs:choice> </xs:sequence> </xs:group> <xs:complexType name="elementContainer"> <xs:annotation> <xs:documentation xml:lang="en"> This complexType is included as a convenience for schema authors who need to define a root or container element for all of the DC elements. </xs:documentation> </xs:annotation> <xs:choice> <xs:group ref="elementsGroup"/> </xs:choice> </xs:complexType> </xs:schema> -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

2 3

browser
by Boojum 03 Mar '08

03 Mar '08

When I selected XML Document --> Open in Browser, nothing is displayed in the browser (my default browser is Firefox).

2 1

Feature Request: Allow Insertion of Inline Markup Within CDATA Marked Sections in Author Mode
by Eliot Kimber 29 Feb '08

29 Feb '08

This may not be either doable or worth the effort, but in doing markup samples for DTD documentation, I've started using CDATA marked sections to hold the examples and then breaking them to insert <b></b> pairs around parts of the example, e.g.: <pre> <![CDATA[<sometag> <more-markup> ]]><b><![CDATA[<this-is-bold/>]]</b><![CDATA[ </more-markup> </sometag>]]> </pre> In theory it should be possible for the editor to automatically adjust the marked section markup to allow the real markup within what was a single CDATA marked section. At the moment I have to bounce in and out of Author mode in order to adjust the highlighting in my examples. Not a big deal but it could be more convenient. Cheers, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

1 1

Problem generating XML document from schema
by Bradley, Peter 20 Feb '08

20 Feb '08

Hi, I'm involved in writing an application that will obtain data from and send data to the UK Student Loan Company via a Web service that is planned to be available shortly. The necessary schema information is contained in the Database Schema and Database Types xsd files available from: http://www.ucisa.ac.uk/groups/cisg/misgdocs/HEICourseDatabase I've downloaded the files and opened them in <oXygen/>. In order to get an idea of the kind of document I will need to be able to write into and generate from our database, I have tried to generate a sample XML file. With the HEICourseDatabaseSchema.xsd file open in <oXygen/> I do Tools --> Generate Sample XML Files ... In the dialog, I browse to the HEICourseDatabaseSchema.xsd file, for the URL. I then try to set a document root, but the Document root drop down list is empty. The HEICourseDatabaseTypes.xsd file is in the same directory as the HEICourseDatabaseSchema.xsd file and should therefore be available, so it's not that. Can anyone point out to me the obvious point that I'm missing, please? I've never had trouble generating sample files before, so I just don't see what I'm doing wrong. Many thanks Peter

4 6

xinclude
by Boojum 20 Feb '08

20 Feb '08

Posted this to the forum, too. Sorry for the dupe. I'm learning OxygenXML's 9.1 support for Xinclude. I have two files, with one pointing by means of Xinclude to the other - no Xpointer, just want the contents of the entire second file. Validation succeeds with no errors, so I assume that the Xinclude is correct. Next--how can I view the resulting document, with the contents of the second file displayed in the first? Must I perform a transformation to see the results, or is there some other way?

4 3

Re: [oXygen-user] Re: [dita-users] All possible Xpath generator?
by Wendell Piez 15 Feb '08

15 Feb '08

Hedley, Unfortunately the list of "all possible XPaths to a text file" is infinite in many cases, due to the possibility of recursive structures such as nested div or section elements, lists inside lists, or inline elements that may have arbitrary inline elements in their content. Do you really want a path such as "/doc/body/div/div/div/div/list/item/list/item/list/item/p/figure/caption/p/b/i/mono/i/b" even such a path points to an element that could be valid? I think Dan is right that the requirement needs some refinement. Cheers, Wendell At 08:42 PM 2/12/2008, you wrote: >Dan: > >>At Wednesday, 13/02/2008, 12:16 PM;, Dan wrote: >>your post is a bit confusing, and some better details/explanations >>would be nice to see. What do you mean by "write a list of all >>possible absolute Xpaths to a text file." > >Rephrasing my original request: >I am developing a CSS implementation for [instance documents that >conform to] an XML schema. It would really help to check if all >[required CSS class matches] have been covered if I could find a >utility that would scan a DTD (including *.mod inclusions) or XML >Schema to write a list of all absolute -- not including wildcards -- >[Xpaths from the root element to each possible leaf element] ... to >a text file. For example, using a possible path from a DITA DTD: > > /reference/refbody/section/p > >This would help determine what class definitions can be generic >no matter in what context an element apppears (e.g. <i>) and what >may need different treatment depending on context >(e.g. */section/title). Oh, and if the generator could list the >Xpath in reverse, from leaf node to root, as well that would be pleasant: > > p\section\refbody\reference\ > >Then I could sort the list of paths so that all instances where <p> >was a leaf would be together and I could decide which contexts could >share a CSS class and which would need context-specific classes. > >I've tried using the <oXygen/> instance generator on the DITA >task.xsd, but even limiting recursion depth and number of >repetitions, it produces very large files, possibly not completing >in my lifetime. And then there is the problem of extracting the Xpaths. > >Hope that makes it clearer, >Hedley > > >-- >Hedley Stewart Finger >28 Regent Street Camberwell VIC 3124 Australia >Tel. +61 3 9809 1229 Mobile +61 412 461 558, >E-mail <mailto:hfinger@handholding.com.au> > > >_______________________________________________ >oXygen-user mailing list >oXygen-user(a)oxygenxml.com >http://www.oxygenxml.com/mailman/listinfo/oxygen-user ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

2 1

Re: [dita-users] All possible Xpath generator?
by Hedley Finger 12 Feb '08

12 Feb '08

Dan: >At Wednesday, 13/02/2008, 12:16 PM;, Dan wrote: >your post is a bit confusing, and some better details/explanations >would be nice to see. What do you mean by "write a list of all >possible absolute Xpaths to a text file." Rephrasing my original request: I am developing a CSS implementation for [instance documents that conform to] an XML schema. It would really help to check if all [required CSS class matches] have been covered if I could find a utility that would scan a DTD (including *.mod inclusions) or XML Schema to write a list of all absolute -- not including wildcards -- [Xpaths from the root element to each possible leaf element] ... to a text file. For example, using a possible path from a DITA DTD: /reference/refbody/section/p This would help determine what class definitions can be generic no matter in what context an element apppears (e.g. <i>) and what may need different treatment depending on context (e.g. */section/title). Oh, and if the generator could list the Xpath in reverse, from leaf node to root, as well that would be pleasant: p\section\refbody\reference\ Then I could sort the list of paths so that all instances where <p> was a leaf would be together and I could decide which contexts could share a CSS class and which would need context-specific classes. I've tried using the <oXygen/> instance generator on the DITA task.xsd, but even limiting recursion depth and number of repetitions, it produces very large files, possibly not completing in my lifetime. And then there is the problem of extracting the Xpaths. Hope that makes it clearer, Hedley -- Hedley Stewart Finger 28 Regent Street Camberwell VIC 3124 Australia Tel. +61 3 9809 1229 Mobile +61 412 461 558, E-mail <mailto:hfinger@handholding.com.au>

1 0

All possible Xpath generator?
by Hedley Finger 12 Feb '08

12 Feb '08

XML/Xpath/CSS heavy hitters: I am developing a CSS implementation for an XML schema. It would really help to check if all possibilities have been covered if I could find a utility that would scan a DTD (including *.mod inclusions) or XML Schema to write a list of all possible absolute Xpaths to a text file. This would help determine what class definitions can be generic no matter in what context an element apppears (e.g. <i>) and what may need different treatment depending on context (e.g. */section/title). Oh, and if the generator could list the Xpath in reverse, from leaf node to root, as well that would be pleasant: p/section/refbody/reference. Trawling through the Help for <oXygen/> 9.1 didn't give any joy, likewise Google. Regards, Hedley -- Hedley Stewart Finger 28 Regent Street Camberwell VIC 3124 Australia Tel. +61 3 9809 1229 Mobile +61 412 461 558, E-mail <mailto:hfinger@handholding.com.au>

1 0

CSS alternatives?
by Wendell Piez 11 Feb '08

11 Feb '08

Hi, Not exactly a bug, but a glitch. When xml-stylesheet PIs are being used, "CSS Alternatives" appears not to work unless the CSS files are provided with title pseudo-attributes in their respective PIs. I guess this is not unreasonable, if you need a label for the pull-down menu. But the "Associate XSLT/CSS Stylesheet" dialog box doesn't offer a place to enter a title; it has to be done by hand. Maybe: (1) the dialog box should offer a field for a CSS title, and possibly (2) if one isn't given, the CSS Alternatives pull-down should fall back to the stylesheet href? What do you think? Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

3 8

Reporting of Imported/Included XSLT Component in Error Messages
by Eliot Kimber 07 Feb '08

07 Feb '08

I have a complext XSLT made up of many parts. In running it from inside Oxygen using Saxon 9, I was getting an error message but the message was reported against a line number in the top-level style sheet. When I run the same script outside Oxygen the error messages is associated with the correct component file (not the top-level). Is this a limitation in Oxygen's integration with Saxon or a bug? The message in this case was a run-time error reporting that a template's parameter was not set by the caller and the default was not consistent with the declared data type of the parameter. Thanks, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

2 2