
Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[tlug] Re: [tlug-admin] TLUG Articles: "Windows Is Free: The impact of pirated software on free software", by Dave Gutteridge
- Date: Mon, 13 Aug 2007 21:12:05 +0900
- From: Edward Middleton <emiddleton@example.com>
- Subject: [tlug] Re: [tlug-admin] TLUG Articles: "Windows Is Free: The impact of pirated software on free software", by Dave Gutteridge
- References: <d8fcc0800708092237w7b8af83bld6ab1b5d18c806ed@mail.gmail.com> <87hcn76h54.fsf@uwakimon.sk.tsukuba.ac.jp> <d8fcc0800708100051p558495canad28b11c025c074d@mail.gmail.com> <46C03A26.9050802@samsara.bebear.net> <d8fcc0800708121933s57fef82ds65986d2bfeb63e68@mail.gmail.com>
- User-agent: Thunderbird 2.0.0.4 (X11/20070713)
Josh Glover wrote:
On 13/08/07, Edward Middleton <emiddleton@example.com> wrote:
I think we really need to use articles for the canonical URI. The
canonical URI should be meaningful. articles/xxx tells us that xxx is
an article identified by xxx. pub doesn't really tell us anything we
about the xxx resource.
Well, I was thinking about "pub" as being short for "publications",
but if you think article is better, that is cool.
OK, my first thought was pub as in the public folder on an ftp site.
Publications to me, tends to suggests that the article has been
published in a technical journal.
So should the keitai URI be http://tlug.jp/pub/winfree.html or
http://tlug.jp/a/winfree.html? articles is just too long.
Is the issue inputing the URI or size limits for URI length?
My first preference would be to have the URI's the same and have them
redirected to the appropriate file by a parameter, something like.
# keitai version
http://tlug.jp/a/winfree/
permanent redirect -> [1]http://tlug.jp/articles/Windows-Is-Free?mobile
server side rewrite ->
http://tlug.jp/articles/Windows-Is-Free.kaitai.html
# full size html version
http://tlug.jp/articles/Windows-Is-Free
server side rewrite ->
http://tlug.jp/articles/Windows-Is-Free.full.html
This would give us a simple approach for adding new serializations or
even translations. i.e.
Japanese translation
http://tlug.jp/articles/Windows-Is-Free?lang=ja
> a) you serve mobile and PC content from separate URIs, and
Curt, when you talked about having separate URI for mobile and content
was this because content negotiation doesn't work or are there other
issues. Would the above approach work?
Edward
1. There should be a parameter for specifying a specific display device.
I couldn't find it with a quick google.
Home |
Main Index |
Thread Index