- oXygen-user - www.oxygenxml.com

Warning on startup SuSE 9.2
by Sean Wheller 13 Dec '04

13 Dec '04

Hi, Just did an upgrade to SuSE 9.2. On starting Oxygen 5.0 I get the following error: Warning: Cannot convert string "-b&h-lucida-medium-r-normal-sans-*-140-*-*-p-*-iso8859-1" to type FontStruct Oxygen still starts and seems to work fine, but I've never had this error before with upgrades on SuSE. -- Sean Wheller sean(a)enbaya.co.za http://www.enbaya.co.za

2 1

Ugraded JVM---Oxygen can not find new JVM
by Peter Charles 06 Dec '04

06 Dec '04

Hello I upgraded my JVM and Oxygen could not find the new JVM. (All other java apps work fine) I was able to start oxygen using the bat file, but would like to set the jvm properly. I could not find any place to do so. Your instructions on the forum say: - use oxtgen.bat to start the application and eventually edit it to specify the full path to Java Where do I do the "edit" Peter

2 1

Surround In
by Peter Charles 24 Nov '04

24 Nov '04

Hello, I particularly like the "surround in" (although "surround with" makes more sense to me) feature of Oxygen, however, in 5.0 the convenient list of possible xsl elements are now the last items in an extremely long drop down list of possible tags. Is there any way to put the xsl tags first in the drop down list, or just eliminate the other tags, or even make it namespace aware? Also, Is it possible to display elements from different namespaces in different colors? Thanks Peter

2 1

XML formatter: one attribute per line?
by Matthias Gärtner 18 Nov '04

18 Nov '04

Hello, apart from sorting attributes, can I specify that each attribute is to be put on its onl line? Thank you, Matthias

2 1

RE: [oXygen-user] Please help in interpretingan "derivation-ok-restriction.5.4.2:Error for type 'GridDomainType'. The particle of the type is not avalid restriction of the particle of the base."
by John.Hockaday＠ga.gov.au 16 Nov '04

16 Nov '04

George, Well that shows how much I know about the W3C XML Schema specification. ;--) I found DTDs very easy, and RELAXNG not too hard but the XML Schema is just too hard. ;--) I need to attend a course or something to get my head around this one. Thanks for the very good explanation. I think that I followed the explanation in the first archived email hypertext link that you mention below. I know you or someone on this list would know the answer. Thank you again. John > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of > George Cristian Bina > Sent: Monday, 15 November 2004 7:10 PM > To: Hockaday John > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Please help in interpretingan > "derivation-ok-restriction.5.4.2:Error for type > 'GridDomainType'. The particle of the type is not avalid > restriction of the particle of the base." > > > Hi John, > > The above error is not about ambiguity. > The derivation in XML Schema defines an algorithm that causes > some types > that are intuitively derived from others to be considered not > correctly > derived. There are some workarounds in these cases, see for instance > http://lists.w3.org/Archives/Public/xmlschema-dev/2004Oct/0097.html > where surrounding the element with a choice solves the problem. > While Michael Key and Henry Thomson consider that a different > algorithm > than the one described by the specification is ok to allow > these cases > to be considered valid (see the next messages on the thread) Noah > Mendelsohn (one of the XML Schema editors) disagree: > http://lists.w3.org/Archives/Public/xmlschema-dev/2004Nov/0023.html > > Now, if RectifiedGrid is ok to belong in the substitution group with > ImplicitGeometry as head instead of Grid then I guess it is ok. > Otherwise it may be possible to find a solution as the one in > the above > xmlschema-dev message. > > Best Regards, > George > > > John.Hockaday(a)ga.gov.au wrote: > > Hi George, > > > > I'm sorry for not getting back to you earlier. I was sick > all last week. > > Here are some results that was found while I was away: > > > > 1. The GML 3.1.1 is still being developed and that is why > you couldn't find > > it. > > > > 2. one of the team members found out that the error was > caused by the > > grids.xsd which is part of the GML 3.1.1 suite. > > > > 3. The fix is as follows: > > > > Change: > > > > ############ > > <element name="RectifiedGrid" type="gml:RectifiedGridType" > > substitutionGroup="gml:Grid"/> > > ############ > > > > To: > > > > ############ > > <element name="RectifiedGrid" type="gml:RectifiedGridType" > > substitutionGroup="gml:_ImplicitGeometry"> > > <annotation> > > <documentation>Should be > substitutionGroup="gml:Grid" > > but changed in order to accomplish Xerces-J schema > validation</documentation> > > </annotation> > > ############ > > > > This has fixed the ambiguity error. > > > > I want to thank you for answering my email. I'm sure that > you would have > > been able to track down the problem as you have done so in > the past when I > > post to this list but it seems like someone else looking at > GML 3.1.1 beat > > you to it. > > > > Thanks again. > > > > > > John > > > > > >>-----Original Message----- > >>From: George Cristian Bina [mailto:george@oxygenxml.com] > >>Sent: Friday, 5 November 2004 7:41 PM > >>To: Hockaday John > >>Cc: oxygen-user(a)oxygenxml.com > >>Subject: Re: [oXygen-user] Please help in interpreting an > >>"derivation-ok-restriction.5.4.2: Error for type > >>'GridDomainType'. The particle of the type is not a valid > >>restriction of the particle of the base." > >> > >> > >>Hi John, > >> > >>I cannot find GML 3.1.1. Can you point us to that ? > >>The error directs to the GridDomainType and DomainSetType. > The first > >>seems not to be a valid restriction of the second. The > >>rcase-Recurse.2 > >>points you to the following part of the spec that is related > >>with the error: > >>*** > >>2 There is a complete ·order-preserving· functional mapping > from the > >>particles in the {particles} of R to the particles in the > >>{particles} of > >>B such that all of the following must be true: > >>2.1 Each particle in the {particles} of R is a ·valid > restriction· of > >>the particle in the {particles} of B it maps to as defined by > >>Particle > >>Valid (Restriction) (§3.9.6). > >>2.2 All particles in the {particles} of B which are not > >>mapped to by any > >>particle in the {particles} of R are ·emptiable· as defined > >>by Particle > >>Emptiable (§3.9.6). > >>*** > >> > >>The best thing is allow us to reproduce the error. Otherwise > >>send us at > >>least the DomainSetType definition. > >> > >>Best Regards, > >>George > >> > >>John.Hockaday(a)ga.gov.au wrote: > >> > >>>Hi, > >>> > >>>We have been trying to validate the GML version 3.1.1. We > >> > >>have managed to > >> > >>>track down 140 of the 144 errors in the XML Schema. The > >> > >>last four errors are > >> > >>>really puzzling. Could someone please help with > >> > >>interpreting and fixing the > >> > >>>errors? > >>> > >>>The errors are: > >>> > >>>http://www.w3.org/TR/xmlschema-1/#rcase-Recurse E > >> > >>rcase-Recurse.2: There is > >> > >>>not a complete functional mapping between the particles. > >> > >>coverage.xsd > >> > >>>file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd 407:37 > >>>http://www.w3.org/TR/xmlschema-1/#derivation-ok-rest > riction E > >>>derivation-ok-restriction.5.4.2: Error for type > >> > >>'GridDomainType'. The > >> > >>>particle of the type is not a valid restriction of the > >> > >>particle of the base. > >> > >>>coverage.xsd > >> > >>file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd > >> > >>>407:37 > >>>http://www.w3.org/TR/xmlschema-1/#rcase-Recurse E > >> > >>rcase-Recurse.2: There is > >> > >>>not a complete functional mapping between the particles. > >> > >>coverage.xsd > >> > >>>file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd 407:37 > >>>http://www.w3.org/TR/xmlschema-1/#derivation-ok-rest > riction E > >>>derivation-ok-restriction.5.4.2: Error for type > >> > >>'GridDomainType'. The > >> > >>>particle of the type is not a valid restriction of the > >> > >>particle of the base. > >> > >>>coverage.xsd > >> > >>file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd > >> > >>>407:37 > >>> > >>>The section in the coverage.xsd file looks like this: > >>> <complexType name="GridCoverageType"> > >>> <complexContent> > >>> <restriction > >> > >>base="gml:AbstractDiscreteCoverageType"> > >> > >>> <sequence> > >>> <group > >>>ref="gml:StandardObjectProperties"/> > >>> <element ref="gml:boundedBy" > >>>minOccurs="0"/> > >>> <element ref="gml:gridDomain"/> > >>> <element ref="gml:rangeSet"/> > >>> <element > >> > >>ref="gml:coverageFunction" > >> > >>>minOccurs="0"/> > >>> </sequence> > >>> </restriction> > >>> </complexContent> > >>> <element name="gridDomain" type="gml:GridDomainType" > >>>substitutionGroup="gml:domainSet"/> > >>>  > >> > >>> <complexType name="GridDomainType"> > >>> <complexContent> > >>> <restriction base="gml:DomainSetType"> > >>> <sequence minOccurs="0"> > >>> <element ref="gml:Grid"/> > >>> </sequence> > >>> <attributeGroup > >>>ref="gml:AssociationAttributeGroup"/> > >>> </restriction> > >>> </complexContent> > >>> </complexType> > >>> > >>>Can anyone see the problem? > >>> > >>>Thanks > >>> > >>> > >>>John Hockaday > >>>Geoscience Australia > >>>GPO Box 378 > >>>Canberra ACT 2601 > >>>(02) 6249 9735 > >>>http://www.ga.gov.au/ > >>> > >>>_______________________________________________ > >>>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

Quisiera correr el download
by Alvaro G. Gonzalez 15 Nov '04

15 Nov '04

Quisiera saber que es lo que hay que poner en la parte de registracion del oxigen 5.0 pues no me deja registrarme, y poder usar el programa. Desde ya muchas gracias A/P Alvaro G. Gonzalez Direccion General de Registros 18 de julio 1730 Piso 4 Tel. 4025638 Fax. 4006583 alvaro(a)mercurio.dgr.gub.uy

2 1

RE: [oXygen-user] Please help in interpreting an "derivation-ok-restriction.5.4.2: Error for type 'GridDomainType'. The particle of the type is not a valid restriction of the particle of the base."
by John.Hockaday＠ga.gov.au 15 Nov '04

15 Nov '04

Hi George, I'm sorry for not getting back to you earlier. I was sick all last week. Here are some results that was found while I was away: 1. The GML 3.1.1 is still being developed and that is why you couldn't find it. 2. one of the team members found out that the error was caused by the grids.xsd which is part of the GML 3.1.1 suite. 3. The fix is as follows: Change: ############ <element name="RectifiedGrid" type="gml:RectifiedGridType" substitutionGroup="gml:Grid"/> ############ To: ############ <element name="RectifiedGrid" type="gml:RectifiedGridType" substitutionGroup="gml:_ImplicitGeometry"> <annotation> <documentation>Should be substitutionGroup="gml:Grid" but changed in order to accomplish Xerces-J schema validation</documentation> </annotation> ############ This has fixed the ambiguity error. I want to thank you for answering my email. I'm sure that you would have been able to track down the problem as you have done so in the past when I post to this list but it seems like someone else looking at GML 3.1.1 beat you to it. Thanks again. John > -----Original Message----- > From: George Cristian Bina [mailto:george@oxygenxml.com] > Sent: Friday, 5 November 2004 7:41 PM > To: Hockaday John > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Please help in interpreting an > "derivation-ok-restriction.5.4.2: Error for type > 'GridDomainType'. The particle of the type is not a valid > restriction of the particle of the base." > > > Hi John, > > I cannot find GML 3.1.1. Can you point us to that ? > The error directs to the GridDomainType and DomainSetType. The first > seems not to be a valid restriction of the second. The > rcase-Recurse.2 > points you to the following part of the spec that is related > with the error: > *** > 2 There is a complete ·order-preserving· functional mapping from the > particles in the {particles} of R to the particles in the > {particles} of > B such that all of the following must be true: > 2.1 Each particle in the {particles} of R is a ·valid restriction· of > the particle in the {particles} of B it maps to as defined by > Particle > Valid (Restriction) (§3.9.6). > 2.2 All particles in the {particles} of B which are not > mapped to by any > particle in the {particles} of R are ·emptiable· as defined > by Particle > Emptiable (§3.9.6). > *** > > The best thing is allow us to reproduce the error. Otherwise > send us at > least the DomainSetType definition. > > Best Regards, > George > > John.Hockaday(a)ga.gov.au wrote: > > Hi, > > > > We have been trying to validate the GML version 3.1.1. We > have managed to > > track down 140 of the 144 errors in the XML Schema. The > last four errors are > > really puzzling. Could someone please help with > interpreting and fixing the > > errors? > > > > The errors are: > > > > http://www.w3.org/TR/xmlschema-1/#rcase-Recurse E > rcase-Recurse.2: There is > > not a complete functional mapping between the particles. > coverage.xsd > > file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd 407:37 > > http://www.w3.org/TR/xmlschema-1/#derivation-ok-restriction E > > derivation-ok-restriction.5.4.2: Error for type > 'GridDomainType'. The > > particle of the type is not a valid restriction of the > particle of the base. > > coverage.xsd > file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd > > 407:37 > > http://www.w3.org/TR/xmlschema-1/#rcase-Recurse E > rcase-Recurse.2: There is > > not a complete functional mapping between the particles. > coverage.xsd > > file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd 407:37 > > http://www.w3.org/TR/xmlschema-1/#derivation-ok-restriction E > > derivation-ok-restriction.5.4.2: Error for type > 'GridDomainType'. The > > particle of the type is not a valid restriction of the > particle of the base. > > coverage.xsd > file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd > > 407:37 > > > > The section in the coverage.xsd file looks like this: > > <complexType name="GridCoverageType"> > > <complexContent> > > <restriction > base="gml:AbstractDiscreteCoverageType"> > > <sequence> > > <group > > ref="gml:StandardObjectProperties"/> > > <element ref="gml:boundedBy" > > minOccurs="0"/> > > <element ref="gml:gridDomain"/> > > <element ref="gml:rangeSet"/> > > <element > ref="gml:coverageFunction" > > minOccurs="0"/> > > </sequence> > > </restriction> > > </complexContent> > > <element name="gridDomain" type="gml:GridDomainType" > > substitutionGroup="gml:domainSet"/> > >  > > <complexType name="GridDomainType"> > > <complexContent> > > <restriction base="gml:DomainSetType"> > > <sequence minOccurs="0"> > > <element ref="gml:Grid"/> > > </sequence> > > <attributeGroup > > ref="gml:AssociationAttributeGroup"/> > > </restriction> > > </complexContent> > > </complexType> > > > > Can anyone see the problem? > > > > Thanks > > > > > > John Hockaday > > Geoscience Australia > > GPO Box 378 > > Canberra ACT 2601 > > (02) 6249 9735 > > http://www.ga.gov.au/ > > > > _______________________________________________ > > oXygen-user mailing list > > oXygen-user(a)oxygenxml.com > > http://www.oxygenxml.com/mailman/listinfo/oxygen-user >

2 1

Model view and Relax NG
by Paul 12 Nov '04

12 Nov '04

Just checking if the model view doesn't work with Relax NG schema's (XML and compact). Or is this something to be configured? Paul

2 1

Please help in interpreting an "derivation-ok-restriction.5.4.2: Error for type 'GridDomainType'. The particle of the type is not a valid restriction of the particle of the base."
by John.Hockaday＠ga.gov.au 05 Nov '04

05 Nov '04

Hi, We have been trying to validate the GML version 3.1.1. We have managed to track down 140 of the 144 errors in the XML Schema. The last four errors are really puzzling. Could someone please help with interpreting and fixing the errors? The errors are: http://www.w3.org/TR/xmlschema-1/#rcase-Recurse E rcase-Recurse.2: There is not a complete functional mapping between the particles. coverage.xsd file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd 407:37 http://www.w3.org/TR/xmlschema-1/#derivation-ok-restriction E derivation-ok-restriction.5.4.2: Error for type 'GridDomainType'. The particle of the type is not a valid restriction of the particle of the base. coverage.xsd file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd 407:37 http://www.w3.org/TR/xmlschema-1/#rcase-Recurse E rcase-Recurse.2: There is not a complete functional mapping between the particles. coverage.xsd file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd 407:37 http://www.w3.org/TR/xmlschema-1/#derivation-ok-restriction E derivation-ok-restriction.5.4.2: Error for type 'GridDomainType'. The particle of the type is not a valid restriction of the particle of the base. coverage.xsd file:/E:/downloads/GML3.1/GML2004-10-29/base/coverage.xsd 407:37 The section in the coverage.xsd file looks like this: <complexType name="GridCoverageType"> <complexContent> <restriction base="gml:AbstractDiscreteCoverageType"> <sequence> <group ref="gml:StandardObjectProperties"/> <element ref="gml:boundedBy" minOccurs="0"/> <element ref="gml:gridDomain"/> <element ref="gml:rangeSet"/> <element ref="gml:coverageFunction" minOccurs="0"/> </sequence> </restriction> </complexContent> <element name="gridDomain" type="gml:GridDomainType" substitutionGroup="gml:domainSet"/>  <complexType name="GridDomainType"> <complexContent> <restriction base="gml:DomainSetType"> <sequence minOccurs="0"> <element ref="gml:Grid"/> </sequence> <attributeGroup ref="gml:AssociationAttributeGroup"/> </restriction> </complexContent> </complexType> Can anyone see the problem? Thanks John Hockaday Geoscience Australia GPO Box 378 Canberra ACT 2601 (02) 6249 9735 http://www.ga.gov.au/

2 1

wish: reindenting without rewrapping
by Lars Huttar 29 Oct '04

29 Oct '04

Dear Oxygen folks, I'm not sure if this is the right mailing list for feature wishes, but here's one. I love the pretty-printing ("Format and indent") feature as a way to fix indentation. However, I also like to include blank lines in my stylesheets to make them more readable, e.g. to separate one template from the next. But when I use Format-and-indent, the blank lines are eliminated. I also sometimes like to have comments following an XSLT instruction on the same line. So it would be nice to have a way to reindent without affecting line breaks. E.g. just a "reindent" command. (Ctrl+Alt+P? Ctrl+Shift+I?) It would be possible to offer this functionality as a Preferences option for the Format-and-indent command, but that would not be ideal since there are often times that you DO want to rewrap long lines and so on. Switching a preferences option on and off would be annoying. The ideal would be to have a separate command. Regards, Lars

2 2

Version 5
by Peter Charles 27 Oct '04

27 Oct '04

Does this require and upgrade license and if it does how do you disable the pop up window telling me there is an upgrade available? Thanks

2 1

Eclipse open external file bug
by Perez Carmona, David 11 Oct '04

11 Oct '04

Please, see this bug report I have made against the latest version of Oxygen: https://bugs.eclipse.org/bugs/show_bug.cgi?id=75877 You can contact me if you need further info. Best regards, David

2 1

Failure to properly start
by Peter Charles 11 Oct '04

11 Oct '04

Hello, Why is it that Oxygen sometimes fails to start? The process is running the splash screen is shown but the application window never opens. Very annoying. Peter -----<CDE/>----- Center for Document Engineering University of California, Berkeley cde.berkeley.edu

3 2

Failure to properly start
by Peter Charles 10 Oct '04

10 Oct '04

Oh and when it fails to start a message is flashed so fast that it is almost impossible to read. "can not transfer the parameter to the running ..." -----<CDE/>----- Center for Document Engineering University of California, Berkeley cde.berkeley.edu

2 1

Oxygen Eclipse plugin XPath evaluator not handling default namespaces...
by John O'Shea 01 Oct '04

01 Oct '04

Hi, I've got an XML doc that looks like this: <?xml version="1.0" ?> <EXAMPLE_COMMIT_NOTICE xmlns="http://example.com/services/b2b" xmlns:example="http://example.com/services/b2b"> <Partner_ID>abcdef</Partner_ID> <File_Name>abcdef</File_Name> <Transmission_Date>abcdef</Transmission_Date> <Commit_Notice_Detail> <Order_Number>abcdef</Order_Number> <Partner_Web_Order_Number>abcdef</Partner_Web_Order_Number> <Line_Number>abcdef</Line_Number> <Product_ID>abcdef</Product_ID> <Quantity_Committed>abcdef</Quantity_Committed> <Committed_Ship_Date>abcdef</Committed_Ship_Date> </Commit_Notice_Detail> </EXAMPLE_COMMIT_NOTICE> When editing in the Oxygen XML, if I choose the XPath Expression evaluator and enter: /example:EXAMPLE_COMMIT_NOTICE/example:Commit_Notice_Detail/example:Order_Number then I get an error dialog back from the oXygen plugin: "Exception ro.sync.goto.do Prefix must resolve to a namespace: example" despite the fact that the example prefix is correctly bound to a namespace. I've tried various tricks to get an XPath query that can find elements in this document but nothing will work. I've dropping the proxy of the default namespace and trying /:EXAMPLE_COMMIT_NOTICE/:Commit_Notice_Detail/:Order_Number but it gives the same erri (with nothing after the 'Prefix must resolve to a namespace: ' message. Note, if I do something like: <?xml version="1.0" ?> <EXAMPLE_COMMIT_NOTICE xmlns="http://example.com/services/b2b" xmlns:example="http://example.com/services/b2b"> <Partner_ID>abcdef</Partner_ID> <File_Name>abcdef</File_Name> <Transmission_Date>abcdef</Transmission_Date> <Commit_Notice_Detail xmlns=""> ^^^^^^^^ <Order_Number>abcdef</Order_Number> <Partner_Web_Order_Number>abcdef</Partner_Web_Order_Number> <Line_Number>abcdef</Line_Number> <Product_ID>abcdef</Product_ID> <Quantity_Committed>abcdef</Quantity_Committed> <Committed_Ship_Date>abcdef</Committed_Ship_Date> </Commit_Notice_Detail> </EXAMPLE_COMMIT_NOTICE> and then use a query string of '//Commit_Notice_Detail' it correctly returns '/EXAMPLE_COMMIT_NOTICE[1]/Commit_Notice_Detail[1]' However, that's of no use to me - all of the elements in the document must be from the default or a named namespace. Note the posting on the Oxygen message board at http://www.oxygenxml.com/forum/viewtopic.php?p=21 suggests this approach (proxying the default namespace) should work. Can you let me know what I've missed, or is this a know fault with the plugin (or Xalan)?????

2 1

Validate xref when XInclude
by Sean Wheller 28 Sep '04

28 Sep '04

Hi, I can't validate xref's when using XInclude. Though as I understand it should be possible with Apache Xerces-J. Comment out xref's and all is valid. When I transform the document the xref's (uncommented), are resolved correctly. Validation returns: "An element with the identifier "docbookxsl" must appear in the document. preface.xml" Any ideas? Following is relevant info from files. BOOK.XML --------------------------- <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ <!ENTITY % xinclude SYSTEM "/home/sean/apps/oxygen/docbook/dtd/xinclude.mod"> %xinclude; <!ENTITY % global_ents SYSTEM "global.ent"> %global_ents; ]>  <book> ... <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="preface.xml"> <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">FIX ME</xi:fallback> </xi:include> ... <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="biblio.xml"> <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">FIX ME</xi:fallback> </xi:include> </book> XREF IN PREFACE.XML --------------------------- <para>The first, "Docbook - The Definitive Guide" <xref linkend="docbookxsl"/> is about the Docbook Document Type Definition (DTD).</para> <para>The second, "Docbook XSL - The Complete Guide" <xref linkend="docbooktdg"/> is about the Docbook Stylesheets (XSL's).</para> BIBLIOENTRY in BIBLIO.XML --------------------------- <biblioentry id="docbookxsl"> <authorgroup> <author> <firstname>Bob</firstname> <surname>Stayton</surname> </author> </authorgroup> ... </biblioentry> <biblioentry id="docbooktdg"> <authorgroup> <author> <firstname>Norman</firstname> <surname>Walsh</surname> </author> <author> <firstname>Leonard</firstname> <surname>Muellner</surname> </author> </authorgroup> ... </biblioentry> .......................... Oxygen 4.2 Apache Xerces-J 2.6.2 Apache Xalan Java 2.5.1 SAXON 6.5.3 Apache FOP 0.20.5 OASIS DocBook XML DTD 4.2 DocBook XSL 1.64.1 -- Sean Wheller sean(a)enbaya.co.za http://www.enbaya.co.za

2 1

Character display problem
by T Reaves 23 Sep '04

23 Sep '04

Hello all. I have this problem of how a particular character combination is displayed. I'm using the Eclipse plugin. In an XML file I'll be typing a Java path like this: '.../model/Item' The problem is as soon as I type the '/' after the 'l', it is not displayed as 'l/' but as a single character. In the Outline view it displays correctly. Is this a know problem, and does it have a solution?

2 2

Saxon version and xsl:document
by Peter Charles 07 Sep '04

07 Sep '04

Hello, What version of saxon is distributed with Oxygen 4.2? The auto complete feature does not support xsl:document. Is that because the distributed version of saxon does not support xsl:document? Peter

3 2

Validating merged grammars
by Paul Everitt 07 Sep '04

07 Sep '04

Hi. The first example in the Relax-NG tutorial under 9.3 "Merging Grammars" looks like this: <grammar xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"> <define name="inline"> <zeroOrMore> <ref name="inline.class"/> </zeroOrMore> </define> <define name="inline.class"> <choice> <text/> <element name="bold"> <ref name="inline"/> </element> <element name="italic"> <ref name="inline"/> </element> </choice> </define> </grammar> However, <oxygen/> fails to validate, claiming it requires a <start> element. --Paul

2 3

Debugger Suggestions
by Peter Charles 03 Sep '04

03 Sep '04

Hello, A suggestion for the debugger: Allow users to either save or copy the results of the trace. When trying to debug why similar documents behave differently this would be an extremely useful feature. Peter

2 1

Any news on .js support yet?
by Ian Tindale 27 Aug '04

27 Aug '04

Any news on supporting external .js javascript files yet? At the very least, some sort of syntax highlighting upon recognistion of the file would be extremely useful. -- Ian K Tindale http://tindale.dyn.nu/

2 1

RE: [oXygen-user] Some more help with interpreting validations errorsplease
by John.Hockaday＠ga.gov.au 26 Aug '04

26 Aug '04

George, Thank you very much for replying to my email. It took me a while to work out what to do. Probably because of my lack of understanding of the W3C XML Schema standard. ;--) I fixed the problem by tracking down that feature.xsd is the base XML Schema for GML (as you suggested that I look for). Once I imported that schema under the gml namespace into the applicationSchema.xsd, Geometry.xsd and TemporalObjects.xsd and fixed a couple of spelling mistakes then everything validated. It even validated after checking the "schema-full-checking" option except for a repeating error in the GML Schema. Thank you very much for all your help. John > -----Original Message----- > From: George Cristian Bina [mailto:george@oxygenxml.com] > Sent: Wednesday, 25 August 2004 5:45 PM > To: Hockaday John; oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Some more help with interpreting > validations errorsplease > > > Hi John, > > As you know oXygen uses Xerces for XML Schema validation. > Xerces follows a > one schema file per namespace rule, that is if you import a > schema in one > place then the following import statements will be disregarded and the > schema in the first encountered import will be used. > Therefore you should > always refer to your schema master file in an import > statement otherwise you > may get errors like the ones you quoted below. > > In your case I found that you import the http://www.opengis.net/gml > namespace refering to two different schemas: > > <xs:import namespace="http://www.opengis.net/gml" Geometry.xsd > file:/D:/test/current/ISO19139/2004-08-17/ssXML/Geometry.xsd 10:23 > <xs:import namespace="http://www.opengis.net/gml" > schemaLocation="../../../GML3.1/GML-3.1.0-Draft-Schemas/base/g > eometryComplex > es.xsd"/> > > and > > <xs:import namespace="http://www.opengis.net/gml" > schemaLocation="../../../GML3.1/GML-3.1.0-Draft-Schemas/base/t > emporal.xsd"/> > TemporalObjects.xsd > file:/D:/test/current/ISO19139/2004-08-17/stXML/TemporalObject > s.xsd 8:23 > <xs:import namespace="http://www.opengis.net/gml" > schemaLocation="../../../GML3.1/GML-3.1.0-Draft-Schemas/base/t > emporal.xsd"/> > > I guess this causes the errors. > > If there is not a master schema for your namespace then you > can just define > a schema with that target namespace and include all the files > that define > components of that namespace and use that as the main schema file. > > Best Regards, > George > ------------------------------------------------------------- > George Cristian Bina mailto:george@oxygenxml.com > <oXygen/> XML Editor - http://www.oxygenxml.com/ > > > ----- Original Message ----- > From: <John.Hockaday(a)ga.gov.au> > To: <oxygen-user(a)oxygenxml.com> > Sent: Wednesday, August 25, 2004 6:29 AM > Subject: [oXygen-user] Some more help with interpreting validations > errorsplease > > > > Hi Everyone, > > > > First of all a big thanks to Sorin and George for helping fix my > validation > > errors that I sent to this list. > > > > Secondly, I have tried to apply my (limited) understanding > of those fixes > to > > the rest of the XML Schema. I unfortunately can't work > through what I > think > > is a complex structure to work out where I need to add the > "import" and > > "include" statements. > > > > I have tarred and gzipped the GML and ISO 19139 schema that > I am using and > > made them available at the following URL: > > > > http://www-test.ga.gov.au/asdd/work/ISO19139GML.tar.gz > > > > I have generated an Oxygen project called smXML.xpr and loaded the > following > > XML Schema into that project: > > > > Geometry.xsd > > TemporalObjects.xsd > > applicationSchema.xsd bad > > basicTypes.xsd > > citation.xsd bad > > constraints.xsd > > content.xsd bad > > dataQuality.xsd bad > > distribution.xsd bad > > extent.xsd bad > > generalFeatureModel.xsd > > identification.xsd bad > > maintenance.xsd bad > > metadataApplication.xsd bad > > metadataEntity.xsd bad > > metadataExtension.xsd bad > > portrayalCatalogue.xsd bad > > referenceSystem.xsd bad > > scXMLbase.xsd > > spatialRepresentation.xsd bad > > > > I have also noted which files do not *individually* > validate by putting > the > > word "bad" next to the above file list. The Geometry.xsd validates > > individually. However, if I validate some XML Schema that "import" > > Geometry.xsd then Geometry.xsd has the following errors: > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:AbstractGeometryType' to a(n) 'type > definition' component. > > Geometry.xsd > file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd > > 37:80" > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:AbstractGeometricPrimitiveType' to a(n) 'type > definition' > > component. Geometry.xsd > > file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 27:39" > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:PointType' to a(n) 'type definition' > component. Geometry.xsd > > file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 16:91" > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:Point' to a(n) 'element declaration' > component. Geometry.xsd > > file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 20:44" > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:_GeometricPrimitive' to a(n) 'element declaration' > component. > > Geometry.xsd > file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd > > 31:58" > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:_Geometry' to a(n) 'element declaration' component. > > Geometry.xsd > file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd > > 41:48" > > > > > > Similarly, if I validate TemporalObjects.xsd there are no > errors yet if I > > validate XML Schema in the project then those XML Schema > that "import" > > TemporalObjects.xsd indicate that TemporalObjects.xsd has > the following > > errors: > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:AbstractTimeObjectType' to a(n) 'type > definition' component. > > TemporalObjects.xsd > > file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd > > 23:65" > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:AbstractTimePrimitiveType' to a(n) 'type definition' > component. > > TemporalObjects.xsd > > file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd > > 13:38" > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:_TimePrimitive' to a(n) 'element declaration' > component. > > TemporalObjects.xsd > > file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd > > 17:53" > > > > "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot > resolve > > the name 'gml:_TimeObject' to a(n) 'element declaration' component. > > TemporalObjects.xsd > > file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd > > 27:50" > > > > > > I believe that the problem has something to do with the > link between the > > ISO19139 XML Schema files and the GML XML Schema files. I > have somehow > come > > to this conclusion because of the following commonly > occurring validation > > error: > > > > "E src-resolve: Cannot resolve the name 'gml:......' to a(n) 'type > > definition' component." > > > > Please note that the "......" represents different GML types and > elements. > > > > > > "E src-resolve: Cannot resolve the name > 'gml:AbstractTimeObjectType' to > a(n) > > 'type definition' component. TemporalObjects.xsd > > file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd > > 23:65" > > > > How can a file be valid and also invalid? Can anyone help > me track down > > which files need the "import" or "include" statements? > > > > Thanks. > > > > > > John Hockaday > > Geoscience Australia > > GPO Box 378 > > Canberra ACT 2601 > > (02) 6249 9735 > > http://www.ga.gov.au/ > > john.hockaday(a)ga.gov.au > > > > _______________________________________________ > > oXygen-user mailing list > > oXygen-user(a)oxygenxml.com > > http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > >

1 0

XSLT Debugger
by Peter Charles 26 Aug '04

26 Aug '04

Hello, Is there any way to configure the XSLT Debugger to halt before entering all templates? This would allow the user to run through the xml document and observe the execution of the stylesheet(s). Thanks Peter

2 1

Some more help with interpreting validations errors please
by John.Hockaday＠ga.gov.au 25 Aug '04

25 Aug '04

Hi Everyone, First of all a big thanks to Sorin and George for helping fix my validation errors that I sent to this list. Secondly, I have tried to apply my (limited) understanding of those fixes to the rest of the XML Schema. I unfortunately can't work through what I think is a complex structure to work out where I need to add the "import" and "include" statements. I have tarred and gzipped the GML and ISO 19139 schema that I am using and made them available at the following URL: http://www-test.ga.gov.au/asdd/work/ISO19139GML.tar.gz I have generated an Oxygen project called smXML.xpr and loaded the following XML Schema into that project: Geometry.xsd TemporalObjects.xsd applicationSchema.xsd bad basicTypes.xsd citation.xsd bad constraints.xsd content.xsd bad dataQuality.xsd bad distribution.xsd bad extent.xsd bad generalFeatureModel.xsd identification.xsd bad maintenance.xsd bad metadataApplication.xsd bad metadataEntity.xsd bad metadataExtension.xsd bad portrayalCatalogue.xsd bad referenceSystem.xsd bad scXMLbase.xsd spatialRepresentation.xsd bad I have also noted which files do not *individually* validate by putting the word "bad" next to the above file list. The Geometry.xsd validates individually. However, if I validate some XML Schema that "import" Geometry.xsd then Geometry.xsd has the following errors: "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:AbstractGeometryType' to a(n) 'type definition' component. Geometry.xsd file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 37:80" "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:AbstractGeometricPrimitiveType' to a(n) 'type definition' component. Geometry.xsd file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 27:39" "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:PointType' to a(n) 'type definition' component. Geometry.xsd file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 16:91" "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:Point' to a(n) 'element declaration' component. Geometry.xsd file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 20:44" "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:_GeometricPrimitive' to a(n) 'element declaration' component. Geometry.xsd file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 31:58" "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:_Geometry' to a(n) 'element declaration' component. Geometry.xsd file:/E:/downloads/ISO19139/2004-08-17/ssXML/Geometry.xsd 41:48" Similarly, if I validate TemporalObjects.xsd there are no errors yet if I validate XML Schema in the project then those XML Schema that "import" TemporalObjects.xsd indicate that TemporalObjects.xsd has the following errors: "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:AbstractTimeObjectType' to a(n) 'type definition' component. TemporalObjects.xsd file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd 23:65" "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:AbstractTimePrimitiveType' to a(n) 'type definition' component. TemporalObjects.xsd file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd 13:38" "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:_TimePrimitive' to a(n) 'element declaration' component. TemporalObjects.xsd file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd 17:53" "http://www.w3.org/TR/xmlschema-1/#src-resolve E src-resolve: Cannot resolve the name 'gml:_TimeObject' to a(n) 'element declaration' component. TemporalObjects.xsd file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd 27:50" I believe that the problem has something to do with the link between the ISO19139 XML Schema files and the GML XML Schema files. I have somehow come to this conclusion because of the following commonly occurring validation error: "E src-resolve: Cannot resolve the name 'gml:......' to a(n) 'type definition' component." Please note that the "......" represents different GML types and elements. "E src-resolve: Cannot resolve the name 'gml:AbstractTimeObjectType' to a(n) 'type definition' component. TemporalObjects.xsd file:/E:/downloads/ISO19139/2004-08-17/stXML/TemporalObjects.xsd 23:65" How can a file be valid and also invalid? Can anyone help me track down which files need the "import" or "include" statements? Thanks. John Hockaday Geoscience Australia GPO Box 378 Canberra ACT 2601 (02) 6249 9735 http://www.ga.gov.au/ john.hockaday(a)ga.gov.au

2 1

Big files
by Perez Carmona, David 24 Aug '04

24 Aug '04

Hi, What about the support with large XML files? I've tried to open a 10 Mb file with Oxygen and Eclipse has died. I give 210 Mb to Eclipse, and have 1 Gb of RAM. Any hint to improve this behavior? David ************************************************************* Este correo ha sido procesado por el Antivirus del Grupo FCC *************************************************************

3 2