- oXygen-user - www.oxygenxml.com

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