Ah-ha! Radu. That was it. ;--) Thank you very much. John

-----Original Message----- From: Radu Coravu [mailto:radu_coravu@sync.ro] Sent: Monday, 9 August 2010 5:02 PM To: oXygen User ML Subject: Re: [oXygen-user] Can't access external XML documents [SEC=UNCLASSIFIED]

Hi John,

Did you by any change set up a SOCKS Proxy in the "HTTP(S)/(S)FTP/Proxy Configuration" Oxygen preferences page? Is it necessary to you or was it set accidentaAhally? Because the error seems to indicate that a SOCKS Proxy was set up and it responded with an invalid response to the client. You can also find more details about the HTTP connection by adding this line to the "log4j.properties" file:

log4j.category.httpclient.wire=debug

If you have a SOCKS proxy server configured, was it recently updated? Oxygen is a Java program and the Java Virtual Machine seems only to support Socks v4. See this post: http://www.innovation.ch/java/HTTPClient/errors.html

Regards, Radu

-- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

...

Hi all,

I have in the past been able to access external XML documents using Schematron external validation. I set my

On 8/9/2010 2:11 AM, john.hockaday@osdm.gov.au wrote: proxy, username and password in the Options => Preferences. I now can't access the external XML documents when I validate using Schematron external validation. I get the following error:

...

" SystemID: G:\asdd\profileinfo\Camera.xml Description: [ISO Schematron (XSLT 2.0)] org.apache.commons.httpclient.HttpException: Malformed reply from SOCKS server (http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml) "

The errors in the oxygen.log file looks like this:

" ...

Editor,resizable,maximized,defaultCloseOperation=DO_NOTHING_ON _CLOSE,rootPane=javax.swing.JRootPane[,4,23,1280x1005,invalid, layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignme ntY=0.0,border=,flags=> 16777673,maximumSize=,minimumSize=,preferredSize=],rootPaneChe ckingEnabled=true]

...

13990767 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - parent: java.awt.Rectangle[x=1276,y=-4,width=1288,height=1032] 13990767 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - parentDedDevice: 12282778 Bounds: java.awt.Rectangle[x=1280,y=0,width=1280,height=1024] 13990767 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - bestFitDevice: 12282778 Bounds: java.awt.Rectangle[x=1280,y=0,width=1280,height=1024] 14022947 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - The focused window is: ro.sync.ui.application.ApplicationDialog$_B[dialog2,1615,423,6 10x177,invalid,layout=java.awt.BorderLayout,APPLICATION_MODAL,ti> tle=Validate with,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=ro.syn c.ui.application.ApplicationDialog$2[,4,23,602x150,layout=java x.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=> 0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize= ],rootPaneCheckingEnabled=true] 14022947 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - KFM: ro.sync.ui.application.ApplicationDialog$_B[dialog2,1615,423,6 10x177,invalid,layout=java.awt.BorderLayout,APPLICATION_MODAL,ti> tle=Validate with,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=ro.syn c.ui.application.ApplicationDialog$2[,4,23,602x150,layout=java x.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=> 0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize= ],rootPaneCheckingEnabled=true] 14022947 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - The top window: ro.sync.ui.application.ApplicationDialog$_B[dialog2,1615,423,6 10x177,invalid,layout=java.awt.BorderLayout,APPLICATION_MODAL,ti> tle=Validate with,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=ro.syn c.ui.application.ApplicationDialog$2[,4,23,602x150,layout=java x.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=> 0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize= ],rootPaneCheckingEnabled=true] 14200437 INFO [ External Validator ] org.apache.commons.httpclient.HttpMethodDirector - I/O exception (java.net.SocketException) caught when processing request: Malformed reply from SOCKS server 14200437 INFO [ External Validator ] org.apache.commons.httpclient.HttpMethodDirector - Retrying request "

I don't know how to interpret this error but I feel it has something to do with my proxy settings.

Any help would be greatly appreciated.

Thanks.

John Hockaday Spatial Standards Group (OSDM) GPO Box 378 Canberra ACT 2601 (02) 6249 9735 http://www.osdm.gov.au/ john.hockaday\@osdm.gov.au

_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user

Hi John, oNVDL was transformed into the jing-trang project: http://code.google.com/p/jing-trang/ The latest distribution is from 11-11-2009. But to my knowledge support for ISO Schematron was not yet added. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 9/7/2010 9:40 AM, john.hockaday@osdm.gov.au wrote:

Hi All,

I believe that oNVDL now handles ISO Schematron and XSLT 2.0. However, I have only been able to get access to a 2007 version of oNVDL.

Does anyone know where I can get the latest version of oNVDL or is there a different name for this tool?

Thanks.

John Hockaday _______________________________________________ oXygen-user mailing list

Hi Syd, The support for NVDL is implemented in Jing (the latest release is 20091111), with the exception of support for embedded schemas. As Radu mentioned, the NVDL implementation from oNVDL was moved back to Jing. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 9/8/10 4:37 PM, Syd Bauman wrote:

And if you'd like to see ISO Schematron support added, vote for it! Add a star at http://code.google.com/p/jing-trang/issues/list.

(Although I note that the support for ISO Schematron issue is already accepted, and that it already has more stars than the issue in second place by more than a factor of 2. And the issue in second place is no slouch -- support for NVDL!)

...

oNVDL was transformed into the jing-trang project: http://code.google.com/p/jing-trang/ The latest distribution is from 11-11-2009. But to my knowledge support for ISO Schematron was not yet added.

---

oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user

Hi All, I have a ISO 19139 metadata record that someone has cut and paste M$ word content into one of the CharacterString fields. According to the Validome XML online validator these characters (â~@~T or M$ long hyphens) are invalid. Also, when we use SAXON to translate this metadata record into XHTML, SAXON says that there is a validation error. When I load this document into Oxygen, version 10.0 build 2008102212, it validates OK. Is there some way for me to catch these invalid characters during validation? Thanks. John Hockaday Spatial Standards Group (OSDM) http://www.osdm.gov.au/ john.hockaday\@osdm.gov.au

Hi George, Here is a snippet of the offending content: <gmd:abstract> <gco:CharacterString>The Housing Rental Vacancy Rates Brief summarises data from a quarterly survey of Queensland real estate agencies. The data presented relates to vacancy rates of residential rental detached houses and units, and is broken down by 5 regions: Inner Brisbane, Remainder of Brisbane LGA, Brisbane Surrounds, Gold Coast and Rest of Queensland. Information on each quarter is posted on the website according to the following schedule: March Quarter-first week of April June Quarter-first week of July September Quarter-first week of October December Quarter-first week of January . Surveys have been conducted in 2002-2003, 2003-2004, 2004-2005, 2005-2006, and 2006-2007. </gco:CharacterString> </gmd:abstract> Note that the hyphens are of the format: â~@~T when viewed in a vi editor on a Solaris platform. Our XML declaration is: <?xml version="1.0" encoding="UTF-8"?> Other validator report these as invalid characters. So I would like to set Oxygen so that it detects and reports these characters. Thanks. John

-----Original Message----- From: George Cristian Bina [mailto:george@oxygenxml.com] Sent: Thursday, 31 March 2011 10:22 AM To: Hockaday John Cc: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] How to I get Oxygen to identify invalid characters? [SEC=UNCLASSIFIED]

Dear John,

Can you please provide a cut down sample file and a short description of the exact steps we should follow to reproduce this issue.

Thank you, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

...

Hi All,

I have a ISO 19139 metadata record that someone has cut and

On 3/31/11 1:50 AM, john.hockaday@osdm.gov.au wrote: paste M$ word content into one of the CharacterString fields. According to the Validome XML online validator these characters (â~@~T or M$ long hyphens) are invalid. Also, when we use SAXON to translate this metadata record into XHTML, SAXON says that there is a validation error.

...

When I load this document into Oxygen, version 10.0 build

2008102212, it validates OK. Is there some way for me to catch these invalid characters during validation?

...

Thanks.

John Hockaday Spatial Standards Group (OSDM) http://www.osdm.gov.au/ john.hockaday\@osdm.gov.au _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user

Dear John, There is nothing wrong with the "—" character in an XML document, this is allowed so oXygen cannot report an error when there is none. If you want to check if your document contains such characters then you can pass it though a Schematron validation using a Schematron schema like below: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.ascc.net/xml/schematron"> <pattern name="testInvalidCharacter"> <rule context="*"> <assert test="not(exists(text()[contains(., '—')]))"> The "—" character is not allowed! </assert> </rule> </pattern> </schema> Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 3/31/11 9:01 AM, john.hockaday@osdm.gov.au wrote:

Hi George,

I notice that the content below doesn't include the M$ characters. I expect it is because I have sent the email in plain text. I have temporarily loaded the document up onto the following URL:

http://asdd.ga.gov.au/asdd/work/OESRexmple.xml

Uploading the file seems to have changed the characters from â~@~T to \342\200\224 or my editor is showing it differently on a different machine.

I hope that this helps.

Thanks.

John

...

-----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Hockaday John Sent: Thursday, 31 March 2011 4:24 PM To: george@oxygenxml.com Cc: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] How to I get Oxygen to identify invalid characters? [SEC=UNCLASSIFIED]

Hi George,

Here is a snippet of the offending content:

<gmd:abstract> <gco:CharacterString>The Housing Rental Vacancy Rates Brief summarises data from a quarterly survey of Queensland real estate agencies. The data presented relates to vacancy rates of residential rental detached houses and units, and is broken down by 5 regions: Inner Brisbane, Remainder of Brisbane LGA, Brisbane Surrounds, Gold Coast and Rest of Queensland. Information on each quarter is posted on the website according to the following schedule: March Quarter-first week of April June Quarter-first week of July September Quarter-first week of October December Quarter-first week of January . Surveys have been conducted in 2002-2003, 2003-2004, 2004-2005, 2005-2006, and 2006-2007. </gco:CharacterString> </gmd:abstract>

Note that the hyphens are of the format: â~@~T when viewed in a vi editor on a Solaris platform. Our XML declaration is:

<?xml version="1.0" encoding="UTF-8"?>

Other validator report these as invalid characters. So I would like to set Oxygen so that it detects and reports these characters.

Thanks.

John

...

-----Original Message----- From: George Cristian Bina [mailto:george@oxygenxml.com] Sent: Thursday, 31 March 2011 10:22 AM To: Hockaday John Cc: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] How to I get Oxygen to identify invalid characters? [SEC=UNCLASSIFIED]

Dear John,

Can you please provide a cut down sample file and a short description of the exact steps we should follow to reproduce this issue.

Thank you, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

...

Hi All,

I have a ISO 19139 metadata record that someone has cut and

On 3/31/11 1:50 AM, john.hockaday@osdm.gov.au wrote: paste M$ word content into one of the CharacterString fields. According to the Validome XML online validator these characters (â~@~T or M$ long hyphens) are invalid. Also, when we use SAXON to translate this metadata record into XHTML, SAXON says that there is a validation error.

...

When I load this document into Oxygen, version 10.0 build

2008102212, it validates OK. Is there some way for me to catch these invalid characters during validation?

...

Thanks.

John Hockaday Spatial Standards Group (OSDM) http://www.osdm.gov.au/ john.hockaday\@osdm.gov.au _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user

_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user