- oXygen-user - www.oxygenxml.com

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

XInclude and Entities
by Sean Wheller 23 Aug '04

23 Aug '04

Hi, A document with the following DocDecl <!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_entities SYSTEM "global.ent"> %global_entities; ]> With XIncludes that use Entities provided by gobal.net <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="&prt02_supplychain;"> <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <para> <emphasis>FIXME: MISSING XINCLUDE CONTENT</emphasis> </para> </xi:fallback> </xi:include> I get an error, but to best of my knowledge the value of an attribute is allowed to be an entity F The external entity reference "&prt02_supplychain;" is not permitted in an attribute value. Any ideas where the problem is? -- Sean Wheller 084-8549408 sean(a)enbaya.co.za http://www.enbaya.co.za

2 1

RE: [oXygen-user] Some help please with interpreting error messages
by John.Hockaday＠ga.gov.au 19 Aug '04

19 Aug '04

George, Thank you so much for your response. I made the changes as you suggested and it fixed the errors that I reported in my email. Unfortunately, I have other errors which I will try to resolve before I consult this very good list. Your mention of the "schema-full-checking" switch allowed me to show all of the GML XML Schemas validated. Previously there were multitude validation errors before I switched off the "schema-full-checking". I tried looking up "schema-full-checking" in the Oxygen documentation but there wasn't enough for me to understand what it is. Can anyone point me to some documentation that explains what the "schema-full-checking" is? If not can someone explain to me, in simple terms, what it means? It seems to me that there are different levels of XML Schema validation but I'm not quite sure. If there are different validation levels what are the consequences of each level? Thanks in advance for any reply. John > -----Original Message----- > From: George Cristian Bina [mailto:george@oxygenxml.com] > Sent: Wednesday, 18 August 2004 1:49 AM > To: Hockaday John; oXygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Some help please with interpreting > error messages > > > Dear John, > > The error message means that there is no declaration for that > type in the > included/imported schemas. > > You should add change the > <include schemaLocation="gmlBase.xsd"/> > to > <include > schemaLocation="../../GML3.1/GML-3.1.0-Draft-Schemas/base/gmlB > ase.xsd"/> > in your ISO19139/2004-08-11/temporal.xsd file. > > Also you need to import the XLink schema in your > ISO19139/2004-08-11/basicTypes.xsd file. > > <xs:import namespace="http://www.w3.org/1999/xlink" > schemaLocation="xlinks.xsd"/> > > Then the following document should be reported valid (with schema full > checking feature disabled): > > <?xml version="1.0" encoding="UTF-8"?> > <xs:schema targetNamespace="http://www.isotc211.org/stXML" > xmlns:stXML="http://www.isotc211.org/stXML" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > xmlns:xlink="http://www.w3.org/1999/xlink" > xmlns:scXML="http://www.isotc211.org/scXML" > xmlns:gml="http://www.opengis.net/gml" version="0.1"> >  > <xs:import namespace="http://www.opengis.net/gml" > schemaLocation="ISO19139/2004-08-11/temporal.xsd"/> > <xs:import namespace="http://www.isotc211.org/scXML" > schemaLocation="ISO19139/2004-08-11/basicTypes.xsd"/> >  >  > <xs:element name="TM_Primitive" type="gml:AbstractTimePrimitiveType" > substitutionGroup="stXML:TM_Object"/> >  > <xs:complexType name="TM_Primitive_PropertyType"> > <xs:sequence> > <xs:element ref="gml:_TimePrimitive" minOccurs="0"/> > </xs:sequence> > <xs:attributeGroup ref="scXML:ObjectReference"/> > </xs:complexType> >  >  > <xs:element name="TM_Object" type="gml:AbstractTimeObjectType"/> >  > <xs:complexType name="TM_Object_PropertyType"> > <xs:sequence> > <xs:element ref="gml:_TimeObject" minOccurs="0"/> > </xs:sequence> > <xs:attributeGroup ref="scXML:ObjectReference"/> > </xs:complexType> > </xs:schema> > > Hope that helps, > 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: Tuesday, August 17, 2004 2:30 AM > Subject: RE: [oXygen-user] Some help please with interpreting > error messages > > > > Sorin, > > > > Thank you very much for replying to my email. The XSDs > that you ask for > are > > about 1MB so I have tarred and gzipped them into a file called > > ISO19139GML.tar.gz. I have loaded this file onto a test > web site. The > URL > > is: > > > > http://www-test.ga.gov.au/asdd/work/ISO19139GML.tar.gz > > > > If you can't access this file then I will send it directly > to you rather > than > > fill up everyone's mailbox on this list. > > > > The version of Oxygen that I am using is 3.1. I have asked for our > systems > > administrators to load up version 4.2 and I expect that to > happen within > the > > next day or two. Maybe this will fix some of the validation errors. > > > > Thanks again for replying to my email. > > > > > > John > > > > > -----Original Message----- > > > From: Sorin Ristache [mailto:sorin@oxygenxml.com] > > > Sent: Monday, 16 August 2004 6:01 PM > > > To: Hockaday John > > > Cc: oXygen-user(a)oxygenxml.com > > > Subject: Re: [oXygen-user] Some help please with interpreting > > > error messages > > > > > > > > > Hello, > > > > > > Can you send your version of the files basicTypes.xsd, > temporal.xsd, > > > gmlBase.xsd and xlinks.xsd and your complete XSD file that you are > > > trying to validate ? If I use the GML schema files from > > > http://schemas.opengis.net/ I get a completely different set of > > > validation errors. What <oXygen/> version are you using for > > > validation ? > > > > > > Best regards, > > > Sorin Ristache > > > > > > http://www.oxygenxml.com/ > > > Syncro Soft ltd. > > > > > > > > > John.Hockaday(a)ga.gov.au wrote: > > > > > > >Hi All, > > > > > > > >At the bottom of this email is an extract from an W3C XML > > > Schema file. When > > > >I try to validate this XSD I get the following error: > > > > > > > >"E src-resolve: Cannot resolve the name > > > 'gml:AbstractGeometryType' to a(n) > > > >'type definition' component." > > > > > > > >The line to which this errors refers is: > > > > > > > >" <xs:element name="TM_Object" > type="gml:AbstractTimeObjectType"/>" > > > > > > > >I'm not quite sure what this error message means. I have > > > tried looking at > > > >the relevant W3C XML Schema documentation but it doesn't > > > make sense to me. I > > > >have looked at the temporal.xsd, which is the file referred > > > to by the "gml" > > > >namespace. The relevant code looks like this: > > > > > > > >" > > > > <complexType name="AbstractTimeObjectType" abstract="true"> > > > > <annotation> > > > > <documentation xml:lang="en"> > > > > The abstract supertype for temporal objects. > > > > </documentation> > > > > </annotation> > > > > <complexContent> > > > > <extension base="gml:AbstractGMLType"/> > > > > </complexContent> > > > > </complexType> > > > >" > > > > > > > >All I can think of is that the complexType name mentioned > > > above should be > > > >"gml:AbstractTimeObjectType" to make it relate to the "gml" > > > namespace. > > > > > > > >Can anyone tell me how I must change the code below to get > > > rid of the error? > > > > > > > >Thanks in advance for any help. > > > > > > > > > > > > > > > >John > > > > > > > > > > > ><?xml version="1.0" encoding="UTF-8"?> > > > ><xs:schema targetNamespace="http://www.isotc211.org/stXML" > > > >xmlns:stXML="http://www.isotc211.org/stXML" > > > >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > > >xmlns:xs="http://www.w3.org/2001/XMLSchema" > > > >xmlns:xlink="http://www.w3.org/1999/xlink" > > > >xmlns:scXML="http://www.isotc211.org/scXML" > > > >xmlns:gml="http://www.opengis.net/gml" version="0.1"> > > > >  > > > > <xs:import namespace="http://www.opengis.net/gml" > > > >schemaLocation="../../GML3.1/GML-3.1.0-Draft-Schemas/base/tem > > > poral.xsd"/> > > > > <xs:import namespace="http://www.isotc211.org/scXML" > > > >schemaLocation="basicTypes.xsd"/> > > > >  > > > >  > > > > <xs:element name="TM_Primitive" > > > type="gml:AbstractTimePrimitiveType" > > > >substitutionGroup="stXML:TM_Object"/> > > > >  > > > > <xs:complexType name="TM_Primitive_PropertyType"> > > > > <xs:sequence> > > > > <xs:element ref="gml:_TimePrimitive" minOccurs="0"/> > > > > </xs:sequence> > > > > <xs:attributeGroup ref="scXML:ObjectReference"/> > > > > </xs:complexType> > > > >  > > > >  > > > > <xs:element name="TM_Object" > type="gml:AbstractTimeObjectType"/> > > > >  > > > > <xs:complexType name="TM_Object_PropertyType"> > > > > <xs:sequence> > > > > <xs:element ref="gml:_TimeObject" minOccurs="0"/> > > > > </xs:sequence> > > > > <xs:attributeGroup ref="scXML:ObjectReference"/> > > > > </xs:complexType> > > > > > > > > > > > >_______________________________________________ > > > >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 > > > >

2 1

RE: [oXygen-user] Some help please with interpreting error messages
by John.Hockaday＠ga.gov.au 17 Aug '04

17 Aug '04

Sorin, Thank you very much for replying to my email. The XSDs that you ask for are about 1MB so I have tarred and gzipped them into a file called ISO19139GML.tar.gz. I have loaded this file onto a test web site. The URL is: http://www-test.ga.gov.au/asdd/work/ISO19139GML.tar.gz If you can't access this file then I will send it directly to you rather than fill up everyone's mailbox on this list. The version of Oxygen that I am using is 3.1. I have asked for our systems administrators to load up version 4.2 and I expect that to happen within the next day or two. Maybe this will fix some of the validation errors. Thanks again for replying to my email. John > -----Original Message----- > From: Sorin Ristache [mailto:sorin@oxygenxml.com] > Sent: Monday, 16 August 2004 6:01 PM > To: Hockaday John > Cc: oXygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Some help please with interpreting > error messages > > > Hello, > > Can you send your version of the files basicTypes.xsd, temporal.xsd, > gmlBase.xsd and xlinks.xsd and your complete XSD file that you are > trying to validate ? If I use the GML schema files from > http://schemas.opengis.net/ I get a completely different set of > validation errors. What <oXygen/> version are you using for > validation ? > > Best regards, > Sorin Ristache > > http://www.oxygenxml.com/ > Syncro Soft ltd. > > > John.Hockaday(a)ga.gov.au wrote: > > >Hi All, > > > >At the bottom of this email is an extract from an W3C XML > Schema file. When > >I try to validate this XSD I get the following error: > > > >"E src-resolve: Cannot resolve the name > 'gml:AbstractGeometryType' to a(n) > >'type definition' component." > > > >The line to which this errors refers is: > > > >" <xs:element name="TM_Object" type="gml:AbstractTimeObjectType"/>" > > > >I'm not quite sure what this error message means. I have > tried looking at > >the relevant W3C XML Schema documentation but it doesn't > make sense to me. I > >have looked at the temporal.xsd, which is the file referred > to by the "gml" > >namespace. The relevant code looks like this: > > > >" > > <complexType name="AbstractTimeObjectType" abstract="true"> > > <annotation> > > <documentation xml:lang="en"> > > The abstract supertype for temporal objects. > > </documentation> > > </annotation> > > <complexContent> > > <extension base="gml:AbstractGMLType"/> > > </complexContent> > > </complexType> > >" > > > >All I can think of is that the complexType name mentioned > above should be > >"gml:AbstractTimeObjectType" to make it relate to the "gml" > namespace. > > > >Can anyone tell me how I must change the code below to get > rid of the error? > > > >Thanks in advance for any help. > > > > > > > >John > > > > > ><?xml version="1.0" encoding="UTF-8"?> > ><xs:schema targetNamespace="http://www.isotc211.org/stXML" > >xmlns:stXML="http://www.isotc211.org/stXML" > >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > >xmlns:xs="http://www.w3.org/2001/XMLSchema" > >xmlns:xlink="http://www.w3.org/1999/xlink" > >xmlns:scXML="http://www.isotc211.org/scXML" > >xmlns:gml="http://www.opengis.net/gml" version="0.1"> > >  > > <xs:import namespace="http://www.opengis.net/gml" > >schemaLocation="../../GML3.1/GML-3.1.0-Draft-Schemas/base/tem > poral.xsd"/> > > <xs:import namespace="http://www.isotc211.org/scXML" > >schemaLocation="basicTypes.xsd"/> > >  > >  > > <xs:element name="TM_Primitive" > type="gml:AbstractTimePrimitiveType" > >substitutionGroup="stXML:TM_Object"/> > >  > > <xs:complexType name="TM_Primitive_PropertyType"> > > <xs:sequence> > > <xs:element ref="gml:_TimePrimitive" minOccurs="0"/> > > </xs:sequence> > > <xs:attributeGroup ref="scXML:ObjectReference"/> > > </xs:complexType> > >  > >  > > <xs:element name="TM_Object" type="gml:AbstractTimeObjectType"/> > >  > > <xs:complexType name="TM_Object_PropertyType"> > > <xs:sequence> > > <xs:element ref="gml:_TimeObject" minOccurs="0"/> > > </xs:sequence> > > <xs:attributeGroup ref="scXML:ObjectReference"/> > > </xs:complexType> > > > > > >_______________________________________________ > >oXygen-user mailing list > >oXygen-user(a)oxygenxml.com > >http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > > >

2 1

attrib polulation on DTDless document
by Sean Wheller 17 Aug '04

17 Aug '04

I notice when the DocDecl is commented that the docbook xref element is inserted as <xref></xref> instead of <xref/> Then I notice when inserting an attribute the inline completion mode is auto populated with the values of all other attributes of that type in the current document. This is a great feature, I never saw it before, it save soooo much time. Now why does it not work when the DocDecl is uncommented? -- Sean Wheller sean(a)enbaya.co.za http://www.enbaya.co.za

2 4