W3C home > Mailing lists > Public > public-webid@w3.org > April 2013

Re: Archaic HTTP "From:" Header

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 03 Apr 2013 21:32:35 -0400
Message-ID: <515CD833.2080507@openlinksw.com>
To: public-webid@w3.org
On 4/3/13 7:01 PM, Mark Nottingham wrote:
> On 04/04/2013, at 4:18 AM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>> All,
>> I think the HTTP "From:" header [1] is now truly archaic circa. 2013. If the range of this particular predicate was a URI it would really aid our quest for a RWW.
> It's in active use by spiders and robots.
>> Suggestion:
>> As part of our RWW bootstrap effort, we could consider an "X-From:" header that basically takes a URI or Literal value.
>> I think we can flesh this out across WebID and RWW via implementations before moving up to TAG and IETF.
>> Mark: what do you think, anyway ? :-)
> If you want something that takes a link, we have a Link header.
> Whatever you do, don't prefix it with X-.
> Cheers,
> --
> Mark Nottingham   http://www.mnot.net/

Okay re. not taking the X- route.

With regards to "From:" I am saying it should accept literals or URIs 
instead of just literals. Net effect, I can then use: 
kidehen@openlinksw.com or <mailto:kidehen@openlinksw.com> or 
<http://kingsley.idehen.net/dataspace/person/kidehen#this> .

"Link:" is also a good idea, I'll maul this over as it could also work 
from the desired bootstrap perspective.



Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Thursday, 4 April 2013 01:32:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:05:50 UTC