W3C home > Mailing lists > Public > www-svg@w3.org > July 2008

RE: Question about getURL() (SVGT 1.2)

From: Julien Reichel <Julien.Reichel@spinetix.com>
Date: Tue, 29 Jul 2008 13:47:11 +0200
Message-ID: <364D31930BDB974AB40E22C5C2E584ED10D141@asterix.SPINETIX.local>
To: <www-svg@w3.org>

Hi all,

I know my question might not be very sexy :-) but can anybody offers
some help/answers/suggestions to my question ? 

I'm worried that if the behaviour of getURL() is not clear enough people
will simply use the XMLHttpRequest() function and the specification of
getURL() will just add noise to the SVG specification ...

Does any UA implement the getURL() function ? 

Julien



> -----Original Message-----
> From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] 
> On Behalf Of Julien Reichel
> Sent: 22 July 2008 11:47
> To: www-svg@w3.org
> Subject: Question about getURL() (SVGT 1.2)
> 
> 
> Hi al,
> 
> The getURL is described is section A.8.18 & A.8.20 of SVG Tiny 1.2.
> 
> 1) The charset decoding rules are simplistic:
> 	"if the media type of the response body was in the 
> text/* hierarchy and specified a charset parameter, then the 
> text must be converted into the host programming language's 
> native form" 
> 	But that will not work in most cases since the server 
> typically does not know the correct encoding and sends a 
> default from its configuration file, usually utf-8. It seems 
> that rules from the W3C XMLHttpRequest spec
> (http://www.w3.org/TR/XMLHttpRequest/#text-response-entity-bod
> y) are more appropriate to accommodate plain text (using the 
> byte order marks), XML and HTML strings. The problem is that 
> they are not compatible with the wording in SVGT in the case 
> of xml and html documents. Do you have any suggestion 
> concerning this case ?
> 
> 2) Converting first to a DOMString then parsing the XML means 
> that the XML may have to be modified in case it had a <?xml?> 
> mark with charset.
> Is this the intent ? 
> 
> 3) If the content is binary, how is it supposed to be 
> converted into a DOMString ? A mapping that could make sense 
> is that each byte of the binary string be mapped to the 
> character with the corresponding number (from 0 to 255) in 
> UNICODE. This would allow decoding with the string access functions. 
> 
> 
> Best regards
> 
> Julien
> 
> --------------------------------------------------------------
> ----------
> --
> 
> Julien Reichel, PhD
> Technology Architect, SpinetiX S.A.
> PSE-C, CH-1015, Lausanne, Switzerland
> 
> Tel:     +41 (0) 21 693 89 81
> Mail:   julien.reichel@spinetix.com
> Get Information : http://www.spinetix.com
> 
> --------------------------------------------------------------
> ----------
> --
> 
> 
Received on Tuesday, 29 July 2008 11:47:50 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:39 GMT