- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Sun, 16 Aug 2015 19:15:03 +0200
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- CC: "public-socialweb@w3.org" <public-socialweb@w3.org>
Received on Sunday, 16 August 2015 17:15:19 UTC
On 08/16/2015 03:27 PM, Melvin Carvalho wrote: > On 14 August 2015 at 13:24, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> > wrote: > >> On 08/14/2015 01:01 PM, Melvin Carvalho wrote: >>> 2. a new URI scheme (acct:) is used whereas for email mailto: is typical >> >> webfinger spec allows querying for URIs using *any* scheme >> https://tools.ietf.org/html/rfc7033#section-8.1 >> >> > I have now implemented this: > > http://gitpay.org/.well-known/webfinger Nice! implementing++ > > Example: > > http://gitpay.org/.well-known/webfinger?object=melvincarvalho%40gmail.com 1. I see you don't use URI, no mailto: scheme 2. It doesn't seem to support content negotiation for "Accept: application/ld+json", in context of this group text/turtle stays out of scope. 3. Response doesn't even include melvincarvalho@gmail.com 4. IMO "resource" parameter recommended by RFC7033 makes sense since it doesn't decide if requested URI/Literal needs to appear as subject or object in statements. Do you really need to violate that spec? https://tools.ietf.org/html/rfc7033#section-4.2 > > As linked data: > > http://graphite.ecs.soton.ac.uk/browser/?uri=http://gitpay.org/.well-known/webfinger?object=melvincarvalho%40gmail.com >
Received on Sunday, 16 August 2015 17:15:19 UTC