OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

URI references [was: XML 1.0 Conformance Test Results




i am not concerned with escaped characters, but with URI forms which are
a. syntactically suspect:
   i had understood the file scheme to always require a host
b. instances of unknown schemes:
   the scheme "scheme" is undefined, and thus have no specified method
to parse,
   and thus no means to resolve it relative to a base
c. instances of a host-specific syntax:
   the "scheme" "d" is in the same ballpark...

the list follows below.

John Cowan wrote:
> 
> james anderson wrote:
> 
> > During conformance tests I observed that numerous test cases include
> > system identifiers which are not valid URI references. Yet the documents
> > are categorized as valid. The recommendation sets constraints on syntax
> > and interpretation of those references which _are_ URI references, but
> > this reader could find no stipulation, that those system literals which
> > _are not_ valid URI references are thereby in error.
> 
> They are not in error.  Section 4.2.2 as amended by erratum E4 makes
> it clear that the XML processor is obliged to %-escape any characters
> in a system identifier that are not URI-legal.
> 
> --
> There is / one art             || John Cowan <jcowan@reutershealth.com>
> no more / no less              || http://www.reutershealth.com
> to do / all things             || http://www.ccil.org/~cowan
> with art- / lessness           \\ -- Piet Hein

an illustrative excerpt from the list of cases on which i am not clear:

; Warning: literal uri value will be used: "file:/dev/null" /
#<FILE-PATHNAME
file:///www/Dokumente/Standards/XML/XMLConf/xmlconf/sun/invalid/not-sa02.xml #xA58C736>:
;          Error parsing the URL, "file:/dev/null"..
; While executing: MAKE-URI
; Warning: literal uri value will be used: "file:/dev/null" /
#<FILE-PATHNAME
file:///www/Dokumente/Standards/XML/XMLConf/xmlconf/sun/invalid/not-sa02.xml #xA58C736>:
;          Error parsing the URL, "file:/dev/null"..
; While executing: MAKE-URI
; Warning: literal uri value will be used: "file:/dev/tty" /
#<FILE-PATHNAME
file:///www/Dokumente/Standards/XML/XMLConf/xmlconf/sun/invalid/not-sa02.xml #xA58C736>:
;          Error parsing the URL, "file:/dev/tty"..
; While executing: MAKE-URI
; Warning: literal uri value will be used: "file:/dev/console" /
#<FILE-PATHNAME
file:///www/Dokumente/Standards/XML/XMLConf/xmlconf/sun/invalid/not-sa02.xml #xA58C736>:
;          Error parsing the URL, "file:/dev/console"..
; While executing: MAKE-URI
; Warning: literal uri value will be used: "scheme://host/data" /
#<FILE-PATHNAME
file:///www/Dokumente/Standards/XML/XMLConf/xmlconf/sun/invalid/not-sa02.xml #xA58C736>:
;          No parser defined for protocol scheme in the URL, "scheme://host/data"..
; While executing: MAKE-URI
; Warning: literal uri value will be used:
"d:\\testspec\\images\\sunset.gif" / #<FILE-PATHNAME
file:///www/Dokumente/Standards/XML/XMLConf/xmlconf/ibm/valid/P56/ibm56v08.xml #x861A4BE>:
;          No parser defined for protocol scheme in the URL, "d:\\testspec\\images\\sunset.gif"..
; While executing: MAKE-URI

...