David MacQuigg wrote:
You can apply for a "top-level" name 'spf', then the purl
will look like http://purl.net/spf
Yes, that's what I did with <http://purl.net/xyzzy/>, but
these are my resources. For other links I use 'net' as in
purl.net/net/rfc/nnnn => was faqs.org, now rfc-editor.org
purl.net/net/oeis/nnnn => Online Encylopedia of Integer Seq.
purl.net/net/scape/about/blank => misc. Netscape fun stuff
purl.net/net/de2en/uri => Google "translator" (de, en, fr)
purl.net/net/msgid/x(_at_)y => Google Usenet Message-ID <x(_at_)y>
For why.html a http://purl.net/net/spf would be okay, if the
Council wants it. But as long as they are unable to locate
their "executive director" to decide these web site and SPF
announce list issues, this is all pointless. It has been
posted here again and again and again and again since the day
when Meng destroyed his nice old working design (in May IIRC)
They correctly said that Julian obviously knows how to create
valid HTNL for a site visible with any browser, and IMNSHO
they MUST give <http://validator.w3.org> a veto right. I'd
contribute what I know about backwards compatibility, I have
test tools like Netscape 2.02, Lynx 2.8.5, and worse ;-) Bye