Closed rchenatjpl closed 2 years ago
Please answer quickly whether xml namespaces must be http://... If they must, I'll write that in my review. If not, I'll still suggest they change over. Thanks. I don't badly need validate to be fixed.
@rchenatjpl doubtful, but I will check. I will poke at this today and hopefully have an answer for you by end lunchtime
per some offline discussions, this was an HTTPS certificate issue, not a validate issue. that issue has been fixed and these products validate as expected
Am I wrong? In xml, namespaces are allowed to begin https://... Attachment co1.xml is a trimmed version of a file I'm reviewing. It really has xmlns:epn="https://voparis-ns.obspm.fr/... The .xsd and .sch use the same weird namespace - check https://voparis-ns.pages.obspm.fr/pds4/epn/v1/VESPA_EPN_1A00.xsd and sch
validate complains.
To show the problem is the weird namespace, validate the attached co2.xml
To test validate on the normal namespace, I downloaded and modified the .sch and .xsd to use the normal namespace as well. They're attached as VES.. The PDS4_PDS_1H00. are attached as P.*. Then
Archive.zip
Engineering Details
Per initial triage, it appears their is an issue with the SSL certificates at sslpoke.java.txt sslpoke.py.txt https://voparis-ns.obspm.fr/, the following Python and Java snippets both raise errors.