danny.ayers at gmail.com
Fri Apr 16 18:26:32 CEST 2010
pings are great, and recording pings is a great idea (you don't think
google don't do this already?). Bit over engineered - all you need is
maybe A -> B (hopefully URIs) and a timestamp.
On 14 April 2010 11:00, Story Henry <henry.story at bblfish.net> wrote:
> I would like to propose a ping relation. It is extremely common for people
> to ask how does one make friends in foaf. For a long time, I thought looking
> at the referrer in the logs would be enough. But that is perhaps just a bit
> too minimalistic. Here we can do better.
> This is a sketch of what the relation should look like. It should be really
> simple, something that would allow a simple html form to do the job for
> human readers too.
> The access to the resource can be protected using foaf+ssl, so that one can reduce spam
> opportunities, or at least filter them.
> It would be defined like this
> @prefix fp: <http://foaf-protocols.com/ont/> . # made up name-space
> @prefix owl: <http://www.w3.org/2002/07/owl#> .
> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
> fp:ping a rdf:Property;
> rdfs:domain foaf:Agent;
> rdfs:range xxx:POSTResource;
> rdfs:comment """
> This relation gives a way for other services to ping
> this webid when a new document is found that mentions this WebID.
> The relation relates a WebId to a collection. A new resource of
> type PingEvent can be created in that collection by POST ing a
> URL that mentions the given WebId.
> The POSTing would be the post created by the following html form where
> ?coll is the name of the object of the relation, and ?rederer is the URL of
> the referring resource
> <form action="POST" action="?coll">
> referer: <input type="text" name="referer"/><br/>
> comment: <input type="text" name="comment"/>
> The resource returned by a GET on the POSTResource can even return the above html
> The resource created should be a named ping request, which itself
> can be described using this ontology.
> This end point could long term accept more flexible contents to be
> posted. One could post an atom Entry for example.
> """ .
> Social Web Architect
> foaf-protocols mailing list
> foaf-protocols at lists.foaf-project.org
More information about the foaf-protocols