W3C home > Mailing lists > Public > public-xg-webid@w3.org > December 2011

RE: broken turtle

From: Peter Williams <home_pw@msn.com>
Date: Thu, 22 Dec 2011 16:57:14 -0800
Message-ID: <SNT143-W461309F514DF69868A41B492AB0@phx.gbl>
To: <j.jakobitsch@semantic-web.at>
CC: "public-xg-webid@w3.org" <public-xg-webid@w3.org>

ok you gave me the right cue. thanks. At least one site (my data mapper, into xml/rdf stream format) can now read the file, and treat them as a triple collection.

 

I was too pedantic (where would I get that trait from?). I saved my windows text file as UTF-8 (rather than ANSI), since the turtle spec went overboard to note how UTF-8 was to be assumed, and normal mime tpe conventions were totally forbidden, when stating char encodings. This (unwanted) act added the 3 byte UTF header to the response stream (which Im guessing throw the morph.talis.com consuming site). If I removed them by treating the char stream as ASNI encoding (with 8 bit octets), and at least one site can consume the stream, now.

 

http://yorkporc.wordpress.com/2011/12/22/turtle-web/ is the current state.

 

i didnt document the failure modes (or the fix). No scientific value. 

 

I wonder the foafssl.org testing site is doing a GET on the tagged resource? (since that is what is in the SAN)?

 

that didnt seem totally unsuitable to a consumer, since one just uses a opretty classical, desktop file copy tool, similar to a 2-pane windows explorer tool. Once one teaches the tool that .ttl file extension is bound application/turtle, the file is copied with that web-centric attribute, each time. 		 	   		  
Received on Friday, 23 December 2011 00:57:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 December 2011 00:57:51 GMT