W3C home > Mailing lists > Public > public-rdfa@w3.org > May 2012

Re: Problem with pyrdfa3 CLI distiller

From: Ivan Herman <ivan@w3.org>
Date: Sun, 20 May 2012 19:48:07 +0200
Message-Id: <8A310CC0-4CF5-4853-BCC1-F3D172199F0D@w3.org>
Cc: public-rdfa <public-rdfa@w3.org>
To: Tom Baker <tom@tombaker.org>
Hey Tom,

as I said in a separate mail, I decided to add .shtml to the set of accepted prefixes for local files, and it would yield HTML5. For non-local files what counts is the return header anyway...

Cheers

I.

---
Ivan Herman
Tel:+31 641044153
http://www.ivan-herman.net

(Written on mobile, sorry for brevity and misspellings...)



On 20 May 2012, at 19:31, Tom Baker <tom@tombaker.org> wrote:

> Thank you, Ivan!
> 
> I see you and Gregg are resolving this, but FWIW:
> 
> On Sat, May 19, 2012 at 04:14:25PM +0200, Ivan Herman wrote:
>> - with a suffix of .shtml, the (local) file is not considered to be
>> HTML5. (Maybe this is a bug, actually, I am not sure what .shtml is
>> usually used for. 
> 
> In the case of .shtml files on the dublincore.org server, the
> explanation at [1] matches what I vaguely recall hearing many years ago,
> i.e., 
> 
>    On some websites, the webmaster sets up the server to parse, or read
>    through every .html or .htm file to see if it contains server
>    instructions.  However, this WILL slow things down when people link
>    to the pages.
> 
>    So, many webmasters have instituted the .shtml files. This is simply
>    a naming convention that says "This html file includes Server
>    commands - please parse it before delivering to the browser site"
>    (hence the "s"). That way parsing can be skipped for all "plain"
>    .html [or .htm] files.
> 
> Tom
> 
> [1] http://www.hwg.org/resources/faqs/shtmlFYIFAQ.html#shtml
> 
> -- 
> Tom Baker <tom@tombaker.org>
Received on Sunday, 20 May 2012 17:48:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 May 2012 17:48:29 GMT