W3C home > Mailing lists > Public > public-socialweb@w3.org > July 2015

Re: A webmention endpoint implementation

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Thu, 30 Jul 2015 11:50:17 +0200
Message-ID: <CAKaEYh+s+q1EtiVJB+3OFigbK6eaf0x54CzeP89r8qYnEWQzRQ@mail.gmail.com>
To: Sarven Capadisli <info@csarven.ca>
Cc: "public-socialweb@w3.org" <public-socialweb@w3.org>
On 29 July 2015 at 22:46, Sarven Capadisli <info@csarven.ca> wrote:

> Hi, just some implementation feedback and a look at extending the current
> Webmention:
> I've created a http://csarven.ca/webmention endpoint on my site which is
> also an article describing its own implementation/approach.
> The endpoint accepts source, property (optional) and target (optional)
> parameters. It accepts claims via standalone POSTs, or by submitting
> through the form on the page. The page is also an article giving further
> details about its approach/extension to the current webmention design. The
> endpoint can handle claims using RDF (i.e., in different serializations:
> RDFa, Turtle, N-Triples, JSON-LD, RDF/XML, [and probably SPARQL results but
> have not tested that yet]), and microformats 2 data patterns found at the
> source (although at the time of this writing IWC interactions are not
> microformats, but rather just IWC terms).
> I've tried to find equivalents of some of the terms using IWC
> interactions, SIOC, schema.org, Open Annotations, Activity Streams. So,
> if the property parameter is given in a webmention or the property/relation
> is picked up as part of the verifications process, it will apply whatever
> it can in the output/display. Read the article for some other details, and
> see also the few interactions it received.
> IMO, the key addition to the current webmention design is for receivers to
> accept the property parameter. It is an explicit claim given to the
> receiver, in which the receiver can even decide whether to handle the claim
> or not without doing a single GET.
> If we look at this from another angle, not providing the property (as
> term, prefixed name, or URI) means that something most likely hyperlinked
> (aka "webmention"ed) something else. This is currently what we have in
> webmention, a super-property.
> Questions/feedback welcome. Happy to test further if anyone wants to play
> along.


Best of all worlds.  Should be compatible with SoLiD, Activity Pump and
IndieWeb.  Well done!

> -Sarven
> http://csarven.ca/#i
Received on Thursday, 30 July 2015 09:50:46 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 December 2016 15:48:22 UTC