- oXygen-user - www.oxygenxml.com

oXygen 5.1 beta
by George Cristian Bina 07 Jan '05

07 Jan '05

Hi everybody! First of all I would like to wish you all a Happy New Year! We have almost ready a new version of oXygen and we made available a couple of distributions of a beta version of oXygen 5.1. Windows without a JVM: http://www.oxygenxml.com/v5.1beta/InstData/Windows/NoVM/oxygen.exe All platforms: http://www.oxygenxml.com/v5.1beta/InstData/All/oxygen.tar.gz Eclipse site URL: http://www.oxygenxml.com/v5.1beta/InstData/Eclipse/site.xml I would like to invite you to try it out and let us know if you find any problem with it. Although it is a minor release it contains a lot of new additions and improvements. I will mention the most important features below: * Folding support oXygen has a light folding implementation and offers more that collapse/expand actions. The most useful action is IMO collapse child folds (CTRL + Numpad-) which will collapse the child fold elements of the current fold (that is it will present the children elements of the current element collapsed). Using this starting from the root element and going down to the element of interest will have as result the document presented with all the elements collapsed except the element of interest. Also the folding structure is preserved after a format and indent action and even if you close the file and reopen it. * Really improved Relax NG support (I think this will make a lot of people happy :) ) The content completion support for Relax NG was rewritten from scratch to offer context sensitive proposals and it is not almost at the same level as the support for XML Schema and DTD. Also we have now an implementation of the Model View based on the Relax NG schema associated with the instance document that shows the element model and the possible attributes. The most important missing part that we plan to address in a future release is the annotation support, that is to present the annotations in the content completion documentation window and in the Model View. * Schematron support oXygen will offer full support for Schematron 1.5. This includes editing and validating Schematron schemas, validating XML documents with Schematron schemas, with Relax NG schemas with embedded Schematron rules and with XML Schemas with embedded Schematron rules. * Support for XSLTProc, MSXML 3.0, MSXML 4.0 and MSXML.Net as XSLT transformers. * Support for ID values on content completion oXygen will present the ID values collected in the last validate action on the content completion proposals where an IDREF or an IDREFS type is specified. This works not only with documents that have a DTD associated but also with documents that have an XML Schema or a Relax NG schema associated. * Code templates The content completion support can be enhanced with code templates. oXygen already ships with some code templates for XSLT (thanks to M. David Peterson) and XSD. One example is typing cwto and pressing CTRL+Space will get into an XSLT document something like: <xsl:choose> <xsl:when test="|"> </xsl:when> <xsl:otherwise> </xsl:otherwise> </xsl:choose> where | represents the caret position. The code templates are triggered with CTRL+Space and they are presented together with eventual content completion proposals. * Automatic detection of formatting settings There are two options that control this feature. The first (true by default) controls the detection of indent size and indent characters. The second (false by default) controls the detection of line width. * Hard line wrap as you edit This is a time saving option. When editing content one needs to use almost at every line the format and indent action in order to get the content wrapped. Now the wrapping can be triggered automatically (if the option is enabled) and one can issue a format and indent action eventually when he finishes the editing of that content. There are more features, I will just mention their short description below: * Content completion support also on element values (for elements with XML Schema simple type content) * Saving of WSDL SOAP Requests * Open Web Service Call Result into the Editor * Extended Go to Options * Optional Content in new XML Document Creation * Scenario based XSLT debugging session * Save the Debug Trace * Extended Batch Validation * Saxon 8.SA can be used as XQuery Processor * Annotation Tooltips * Sortable Tables * Option for saving all files before validation or transformation * Project improvements * Fixed the bidirectional editing support * Better undo support * Updated the TEI framework * File properties page Best Regards, George --------------------------------------------------------------------- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 1

Associating and validating with xsd
by Mark Peyer 05 Jan '05

05 Jan '05

Hi, I am exporting data out of FileMaker Pro's XML function, converting them with XSL to comply with an .xsd-file. I can associate the .xsd, and Oxygen 5 will insert xsi:schemaLocation="http://www.xmlData.ch/xmlInvoice/XSD filepath/schemafile.xsd" Then I can validate the .xml-file. The receiver of my .xml-files wants the schemaLocation in the form xsi:schemaLocation="http://www.xmlData.ch/xmlInvoice/XSD schemafile.xsd" If I associate the .xsd-file without the filepath, I cannot validate it. In Project mode, I can validate one or all .xml-files using "Validate selection with...". Here validation functions with or without filepath, but the line xsi:schemaLocation="http://www.xmlData.ch/xmlInvoice/XSD schemafile.xsd" Is not inserted. As far as I can see, there is no possibility to batch associate a schema file. Are there any workarounds? Am I missing something? Thanks for your help. -- Mark A. Peyer

2 1

DocBook Table Problems
by Ray Miller 04 Jan '05

04 Jan '05

I believe this question has been submitted before, I am unable to locate a suitable resolution. Current version of oXygen on JDK15; Fedora2 platform. Docbook DTD is 4.4b2 XSL is version supplied with oXygen Transformer is Saxon 6.5.3 <table width="1224" border="0" cellpadding="0" cellspacing="0"> <title>Test table</title> <tgroup cols="3"> <colspec colwidth="796" colnum="1" colname="c1"/> <colspec colwidth="74" colnum="2" colname="c2"/> <colspec colwidth="354" colnum="3" colname="c3"/> <spanspec namest="c1" nameend="c2" spanname="s1"/> <tbody> <row valign="top"> <entry spanname="s1"><para>cols 1 and 2</para></entry> <entry><para>col 3</para></entry> </row> </tbody> </tgroup> </table> The colwidth attribute does not function; cannot create a DocBook rendering of an OpenOffice text document. Help please. Ray

2 1

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