May 2010 - oXygen-user - www.oxygenxml.com

Selecting multiple XML file at once for the Schema Converter (trang)
by mozer 02 Jun '11

02 Jun '11

Hi, Problably I didn't see it, but there is no way for me to select a bunch of XML file and add them to generate a schema The only way is too select the file one by one which is tedious Any idea of how to circumvent that ? Xmlizer

3 10

[ann] oXygen XML editor version 11.2 and some more news
by George Cristian Bina 19 Jan '11

19 Jan '11

Hi, I am pleased to announce that a new version of oXygen is available from our website http://www.oxygenxml.com For the complete list of new features and details please see http://www.oxygenxml.com/index.html#new-version We have an @oxygenxml user on Twitter so you may want to follow that for oXygen related updates http://twitter.com/oxygenxml We plan to have that more active in the future. I also just set up a few hours ago a Facebook page for oXygen: http://www.facebook.com/pages/oXygen-XML-Editor/107247659293674 Until now 17 people registered as oXygen fans, including me :) oXygen was one of the sponsors at XML Prague last week. I had there a presentation on schema-aware editing, and participated in a panel on XML editing tools. If you did not attend the conference you should be able to watch the recordings of the sessions soon, when they will be posted on the conference website http://www.xmlprague.cz/2010/index.html We plan to be a sponsor also at Balisage this year and to exhibit at the DITA Europe conference. We plan also to have a number of online meetings to present some of the oXygen features. It will be great if you can send us feeback on what topics you would find useful to be included in these presentations. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

2 3

better validation of Schematron schema
by Lars Huttar 18 Jun '10

18 Jun '10

Hi, My request here does not have to do with validating an XML document against a Schematron schema, but rather, finding out whether Schematron schema itself is valid. I'm pleased with Oxygen's support for Schematron, including ISO Schematron. Oxygen really has excellent coverage of XML-related tools. However I have the following enhancement request. When I'm editing a schema foo.sch in oXygen, I can press Ctrl+Shift+V and it does something, and says "Document is valid." I guess it's validating the schema against an RNG schema for Schematron? I don't know. What I do know is that its validation is not as complete as the validation for XSLT stylesheets. It helpfully validates the presence of elements and attributes that are dis/allowed in Schematron (old and ISO versions); but it does not validate the XPath in test expressions. Just now I had an assert whose test attribute's value was not well-formed XPath: <sch:assert test="../../row1/thing[@id = current()/transform[@type = 'From']/target/@id"> Note that I'm missing a final square-bracket in the test expression. Yet Oxygen tells me the Schematron schema is valid. It was only when I tried to *use* the Schematron schema that it told me about the missing ']'. And at this point it's quite a bit harder to debug, because often you're using a manually-constructed pipeline where you have an XSLT transforming your Schematron schema to another XSLT, and then the latter is used to validate your XML document. So you have to sort through several layers to figure out where the problem is. So my request is for stronger validation for Schematron schemas. I'm not sure of the best way to accomplish this... Maybe Oxygen could go ahead and transform the schema to an XSLT using e.g. iso_svrl.xsl and iso_schematron_skeleton.xsl (in the case of ISO Schematron); then validate the result as an XSLT stylesheet. This should take care of the above problem, malformed XPath expressions. It may not be straightforward to map any errors back to a particular point in the original schema, but at least we'd know whether the schema was valid or not, and we'd be better off than we are now, catching errors while editing the schema instead of when using the schema. Thanks for your consideration, Lars

4 5

XSLT output root element force namespaces and attributes sequence
by Martijn Van der Graaff 26 May '10

26 May '10

Hi I need to generate a root element in a output file that contains some attributes and namespaces. It should like this: <?xml version="1.0" encoding="UTF-8"?> <enfinity xsi:schemaLocation="http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex catalog.xsd http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt dt.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:dt="http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt" major="6" minor="1" family="enfinity" branch="enterprise" build="6.3.1.2.5"> what I get is this: <enfinity xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex" xmlns:dt="http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt" xsi:schemaLocation="http://www.intershop.com/xml/ns/enfinity/6.1/xcs/impex catalog.xsd http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt dt.xsd" major="6" minor="1" family="enfinity" branch="enterprise" build="6.3.1.2.5"> How can I force in XSLT that (xmlns:xml="http://www.w3.org/XML/1998/namespace") is always added to the root element and how can I force on where the attributes are sorted. My xslt snippet is: <xsl:template match="/"... <xsl:element name="enfinity" namespace="http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex"> <xsl:attribute name="xsi:schemaLocation">http://www.intershop.com/xml/ns/enfinity/6.1/xcs/impex catalog.xsd http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt dt.xsd</xsl:attribute> <xsl:namespace name="xsi">http://www.w3.org/2001/XMLSchema-instance</xsl:namespace> <xsl:namespace name="">http://www.intershop.com/xml/ns/enfinity/6.2.2/xcs/impex</xsl:namespace> <xsl:namespace name="xml">http://www.w3.org/XML/1998/namespace</xsl:namespace> <xsl:namespace name="dt">http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt</xsl:namespace> <xsl:attribute name="major" select="$major"/> <xsl:attribute name="minor" select="$minor"/> <xsl:attribute name="family" select="$family"/> <xsl:attribute name="branch" select="$branch"/> <xsl:attribute name="build" select="$build"/> Yours, Martijn

3 3

Attribute name dt:dt
by Martijn Van der Graaff 26 May '10

26 May '10

Hi, I need to create an array of elements with several attributes: <a name="aa" dt:dt="string">aValue</a> dt is a namespace " "htttp://www.dt.com" By using xslt: <custom-attributes> <xsl:for-each select="$custom-attributes"> <xsl:variable name="markCode" select="string(lower-case(./@MarkCode))"/> <xsl:variable name="dtType">string</xsl:variable> <xsl:variable name="markCodeValue" select="./@MarkValue"/> <xsl:element name="custom-attribute" inherit-namespaces="no"> <xsl:attribute name="name" select="$markCode"/> <xsl:attribute name="dt" select="$dtType/text()"/> <xsl:value-of select="$markCodeValue/text()"/> </xsl:element> </xsl:for-each> </custom-attributes> I get in the result <custom-attribute xmlns:dt="http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt" name="brand" dt:dt="string">TITANFLX</custom-attribute> I need to get the xmlns:dt="http://www.intershop.com/xml/ns/enfinity/6.1/core/impex-dt" out of the attribute, The result should be: <custom-attribute name="brand" dt:dt="string">TITANFLX</custom-attribute> Yours, Martijn

2 1

Getting locked out of a project
by Loreti, Wendy 24 May '10

24 May '10

I'm getting this problem when I try to open my workspace. "Tree element '/hardware_help/hardware.ditamap' not found." The file is clearly there and completely healthy and valid. What might this mean otherwise? As a secondary question, how compatible are Oxygen versions with each other? Wendy Loreti Senior Technical Writer Vocollect, Inc. 703 Rodi Rd. Pittsburgh, PA 15235 www.vocollect.com <http://www.vocollect.com/> CONFIDENTIALITY NOTICE This message, together with any attachments, may be legally privileged and is confidential information intended only for the use of the individual or entity to which it is addressed. It is exempt from disclosure under applicable law including court orders. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender and delete this message, along with any attachments, from your computer.

2 1

Find ahead
by Karl Stubsjoen 24 May '10

24 May '10

What is the shortcut key for find ahead (I think that is what it is called). The find feature responds to your keystrokes and quickly jumps forward in the document highlight the first found result.

2 1

Re: [oXygen-user] Schema documentation from specific root element
by Adrian Buza 21 May '10

21 May '10

Hi, We already have the clean schema feature request added to our issue tracking tool. It will be implemented in the long term so it's going to take a while. I've added your vote for it. Regards, Adrian Adrian Buza Oxygen XML Editor support Ingo Freitag wrote: > Hi, > > thank you for your quick answer. > > The best solution would be something complete automatic, but it is also possible, that I remove the other root elements before. > > But one problem is, that the schema uses global types (simple and complex) very intensive, which means for me to manually remove all those elements as well. > This is a huge work. > > I already read in former posts, that you were asked to add a function to 'clean' a schema from unused types and other elements. > In my case such a function would do the trick very well :) So my vote to implement it as soon as possible. > > Best regards, > > Ingo > > -----Original Message----- > From: Adrian Buza [mailto:adrian@sync.ro] > Sent: Thursday, May 20, 2010 10:47 AM > To: Ingo Freitag > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific root element > > Hello, > > The schema documentation tool is not contextual, it generates the > documentation for the entire schema so I'm afraid you cannot simply > generate the documentation starting from a given root element. > > But there may be a few options that could help you break it down into > smaller parts. > For example if you generate HTML you can split the output in multiple > files by component(in the Output tab). Other than that there are the > generic filters from the Settings tab, but I'm not sure if they're > useful to you in this case. > > There's also the possibility to trim the schema and remove the unwanted > root elements before generating the documentation, but I'm guessing you > were looking for something automatic to do this. > > Regards, > Adrian Buza > Oxygen XML Editor support > > Ingo Freitag wrote: > >> Hi, >> >> I have a very huge schema file with several root elements included. >> Now I want to create a documentation out of one of those root elements only. >> >> Is this somehow possible? >> Of course all linked and referenced types shall also be included in the documentation. >> >> Ingo >> >> >> >> _______________________________________________ >> 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

Use DITA 1.1 instead of 1.2?
by Yves Barbion 21 May '10

21 May '10

Hi again group I see that oXygen already supports DITA 1.2, which is great! However, this can be a problem in "mixed editor" environments as long as the other editors don't support DITA 1.2 yet. Is there an easy way in oXygen to make sure that the authors don't use the elements and attributes of the DITA 1.2 standard, for example <hazardstatement>, for the time being? Thanks -- Yves Barbion www.scripto.nu

2 1

Re: [oXygen-user] Schema documentation from specific root element
by Mark Baker 20 May '10

20 May '10

I think it should be noted that there is a big difference between schema documentation and doctype documentation. * A schema may define 0, 1, or many root elements, and therefore 0, 1, or many document types. Multiple document types defined by the same schema may have nothing in common with each other. * A document type may contain elements defined in one or more schemas, and even allow content that is not governed by any schema. For instance, a particular document type may allow the use of MathML or SVG within the document. The documentation of any one schema, therefore, would not constitute documentation for the entire document type. * A document type may reuse a complex type defined in a schema at different points in a document type while assigning substantially different document semantics to that type in each of the locations in which it is used. Schema documentation tools necessarily follow the structure of schemas. They describe the structure of the schemas themselves, but the structures of the document types defined by the schemas may be much more complex and varied than the structures of the schemas themselves (or vice versa -- a complex schema may define a simple document type). Generating schema documentation from one root element of a schema, therefore, is not at all equivalent to creating document type documentation for documents that have that root element. We produce a lot of document type references. We have two different document type reference composition and build processes for different types of document. (Data oriented document types and text oriented document types are significantly different in their documentation needs.) Schema documentation, generated by standard schema documentation tools, as good as some of them are, would not come close to meeting our user's needs. I think you may need to figure out if what you really need is document type documentation, rather than schema documentation. If so, you will need a different process to create it. Mark > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Ingo Freitag > Sent: May 20, 2010 12:07 PM > To: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific > root element > > Hi, > > thank you for your quick answer. > > The best solution would be something complete automatic, but > it is also possible, that I remove the other root elements before. > > But one problem is, that the schema uses global types (simple > and complex) very intensive, which means for me to manually > remove all those elements as well. > This is a huge work. > > I already read in former posts, that you were asked to add a > function to 'clean' a schema from unused types and other elements. > In my case such a function would do the trick very well :) So > my vote to implement it as soon as possible. > > Best regards, > > Ingo > > -----Original Message----- > From: Adrian Buza [mailto:adrian@sync.ro] > Sent: Thursday, May 20, 2010 10:47 AM > To: Ingo Freitag > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific > root element > > Hello, > > The schema documentation tool is not contextual, it generates > the documentation for the entire schema so I'm afraid you > cannot simply generate the documentation starting from a > given root element. > > But there may be a few options that could help you break it > down into smaller parts. > For example if you generate HTML you can split the output in > multiple files by component(in the Output tab). Other than > that there are the generic filters from the Settings tab, but > I'm not sure if they're useful to you in this case. > > There's also the possibility to trim the schema and remove > the unwanted root elements before generating the > documentation, but I'm guessing you were looking for > something automatic to do this. > > Regards, > Adrian Buza > Oxygen XML Editor support > > Ingo Freitag wrote: > > Hi, > > > > I have a very huge schema file with several root elements included. > > Now I want to create a documentation out of one of those > root elements only. > > > > Is this somehow possible? > > Of course all linked and referenced types shall also be > included in the documentation. > > > > Ingo

1 0