Amy Guy

• Person

Amy Guy liked on 2015-07-27 10:45:00

• Annotation
• Like

Amy Guy liked on 2015-08-11 09:01:36

• Annotation
• Like

Amy Guy mentioned on 2015-12-05 17:00:00

• Annotation
• Note

Amy Guy replied on 2015-08-11 08:57:08

<div typeof='oa:TextualBody' resource='#note-20150811085708' property='rdf:value' datatype='rdf:HTML'> <p>Threaded replies are what all the cool kids are doing.</p></div>

• Annotation
• Note

Corey Mwamba

• Person

Corey Mwamba replied on 2015-08-09 16:37:04

<div typeof='oa:TextualBody' resource='#note-20150809163704' property='rdf:value' datatype='rdf:HTML'> <p><a href='https://twitter.com/csarven'>@csarven</a> I will check that! Using sioc will make it easier to incorporate to my site too</p></div>

• Annotation
• Note

Corey Mwamba replied on 2015-08-15 04:47:01

<div typeof='oa:TextualBody' resource='#note-20150815044701' property='rdf:value' datatype='rdf:HTML'> <p><a href='https://twitter.com/csarven'>@csarven</a> I haven't implemented webmentions yet; still planning. Have you seen SORON? potentially useful? <a href='http://purl.org/net/soron'>purl.org/net/soron</a></p></div>

• Annotation
• Note

Melvin Carvalho

• Person

Melvin Carvalho

• Person

Melvin Carvalho mentioned on 2015-07-30 09:50:46

• Annotation
• Note

Melvin Carvalho replied on 2015-07-29 16:20:00

<div typeof='oa:TextualBody' resource='#note-20150729162000' property='rdf:value' datatype='rdf:HTML'> <p>This is an example reply to a webmention endpoint. It was originally created in RDF Turtle.</p></div>

• Annotation
• Note

note-20150729162000

• TextualBody

note-20150809150403

• TextualBody

note-20150809163704

• TextualBody

note-20150810110710

• TextualBody

note-20150811085708

• TextualBody

note-20150811094822

• TextualBody

note-20150815044701

• TextualBody

note-20150816130945

• TextualBody

Sarven Capadisli

• Person

Sarven Capadisli

• Person

Sarven Capadisli

• Person

Sarven Capadisli mentioned on 2015-08-09 15:04:03

<div typeof='oa:TextualBody' resource='#note-20150809150403' property='rdf:value' datatype='rdf:HTML'> <p><a href='http://twitter.com/coreymwamba'>@coreymwamba</a> Have a look at <a href='https://csarven.ca/webmention'>https://csarven.ca/webmention</a> #Webmention handling. #RDF #microformats are both welcome. Use the property param!</p></div>

• Annotation
• Note

Sarven Capadisli mentioned on 2015-11-28 06:46:52

• Annotation
• Note

Sarven Capadisli replied on 2015-08-10 11:07:10

<div typeof='oa:TextualBody' resource='#note-20150810110710' property='rdf:value' datatype='rdf:HTML'> <p>I use <a href='http://schema.org/'>schema.org</a>, <a href='http://xmlns.com/foaf/spec/'>FOAF</a> <a href='http://rdfs.org/sioc/'>SIOC</a>, <a href='http://www.openannotation.org/spec/core/'>Open Annotation</a>, and <a href='http://www.w3.org/TR/activitystreams-core/'>Activity Streams</a>, where applicable.</p></div>

• Annotation
• Note

Sarven Capadisli replied on 2015-08-11 09:48:22

<div typeof='oa:TextualBody' resource='#note-20150811094822' property='rdf:value' datatype='rdf:HTML'> <p>Electricity is the future.</p></div>

• Annotation
• Note

Sarven Capadisli replied on 2015-08-16 13:09:45

<div typeof='oa:TextualBody' resource='#note-20150816130945' property='rdf:value' datatype='rdf:HTML'> <p>@coreymwamba I don't recall seeing SORON. Relatively new. Thanks for the heads-up. It may be useful if you want "person interaction person"</p></div>

• Annotation
• Note

Webmention

<p><mark>The documentation of this experimental work is kept here for historical reasons, however the service is placed out of commission. If you want independently built decentralised applications that can send, receive, or consume data that is decoupled from the user-interface with reusable notifications as well as being interoperable with the rest of the W3C stack, I recommend using the W3C Recommendation <cite><a href='https://www.w3.org/TR/ldn/'>Linked Data Notifications</a></cite>.</mark></p> <p>This is my site’s webmention endpoint. Send <code>POST</code> requests to this URL (<code>https://csarven.ca/webmention</code>) with <strong><code>source</code></strong>, <strong><code>property</code></strong> (optional) and <strong><code>target</code></strong> (optional) parameters, or use the form below, to let me know that you’ve linked to a URL on my site. This endpoint can handle claims using RDF and microformats 2 data patterns found at the source.</p> <form class='form-settings' id='webmention-write' method='post' action='/webmention'> <fieldset> <legend>Webmention</legend> <p class='note'><span class='required'>*</span> marked fields are required.</p> <ul class='form-data'> <li> <label for='source'>Source <span class='required'>*</span></label> <input disabled='disabled' placeholder='http://example.org/note' value='' id='source' name='source' type='text'></input> </li> <li> <label for='property'>Property</label> <input disabled='disabled' placeholder='as:inReplyTo' value='' id='property' name='property' type='text'></input> </li> <li> <label for='target'>Target</label> <input disabled='disabled' placeholder='https://csarven.ca/webmention' value='' id='target' name='target' type='text'></input> </li> </ul> <input disabled='disabled' class='submit' id='submit' value='Submit' name='submit' type='submit'></input> </fieldset> </form> <p>As of <time datatype='xsd:dateTime' content='2015-07-27T00:00:00Z' property='schema:dateModified' datetime='2015-07-27'>2015-07-27</time>, this webmention endpoint offers a way to be more flexibile and precise about the claims than the current webmention design. The approach taken at this endpoint is intended to be a superset on how to deal with mentions i.e., making the receiver aware of a hyperlink with a relation which may be of interest.</p> <p id='source-parameter'>Webmention works essentially in two steps: 1) a claim is made 2) the said claim is verified, and possibly displayed. Thus, the source URL is the most essential component, regardless of whether the information for the <code>property</code> or <code>target</code> is provided. At the end of the day, the receiver makes all of the decisions on if and how to deal with the claim - in which, there is no formal specification that is globally accepted nor forced. Naturally this is a good thing. The information that is provided in the <code>POST</code> is just that, a claim. It may or may not be of interest to the receiver, and the receiver makes no promise to do anything with it. Making decisions e.g., optimization, trust, driven from the claim would be premature. Hence, decision making around optimization and trust, for instance, are best left outside of the original claim. The ability to receive only the source URL is the simplest design.</p> <p>We are now free to build rest of the blocks by optionally accepting the <code>property</code> and <code>target</code> parameters:</p> <p id='property-parameter'>The <code>property</code> parameter indicates the type of relation between the source and the target (which is found at the source URL). Its value may be a <em>term</em> e.g., <code>u-in-reply-to</code>, a <em>IRI</em> e.g., <code>http://rdfs.org/sioc/ns#reply_of</code>, or a <em>prefixed name</em> e.g., <code>as:inReplyTo</code>. The <code>property</code> information allows us to make precise claims, i.e., mentions, and consequently 1) it gives an opportunity for the receiver to decide whether to even make a single <code>GET</code> on the source URL, 2) better narrowing down or filtering of the claim.</p> <p id='target-parameter'>In a similar way to the <code>property</code> information, having the <code>target</code> allows us to further narrow down on the claim i.e., we can check if we want to deal with a claim made to that particular target URL, regardless of the <code>property</code> information being present or not.</p> <p>Table of possible <code>POST</code>s with interpretations:</p> <table id='webmention-posts'> <caption>Webmention <code>POST</code>s using <code>source</code>, <code>property</code>, and <code>target</code></caption> <thead> <tr><th><code>source</code></th><th><code>property</code></th><th><code>target</code></th><th>Possible process</th></tr> </thead> <tbody> <tr><td></td><td></td><td></td><td>Show error</td></tr> <tr><td></td><td>✔</td><td></td><td>Show error</td></tr> <tr><td></td><td></td><td>✔</td><td>Show error</td></tr> <tr><td></td><td>✔</td><td>✔</td><td>Show error</td></tr> <tr><td>✔</td><td></td><td></td><td>Verify interest with that <code>source</code></td></tr> <tr><td>✔</td><td>✔</td><td></td><td>Verify interest with that <code>source</code> and <code>property</code></td></tr> <tr><td>✔</td><td></td><td>✔</td><td>Verify interest with that <code>source</code> and <code>target</code></td></tr> <tr><td>✔</td><td>✔</td><td>✔</td><td>Verify <code>source</code>, <code>property</code>, <code>target</code></td></tr> </tbody> <tfoot> <tr><td colspan='4'>✔ indicates that the parameter is submitted.</td></tr> </tfoot> </table> <p id='what-to-practice'>What might be a good practice here? In my opinion, the sender should aim to be precise about the claim by providing all three components: source, property, and target, to the receiver. What do you think?</p>

• Article
• CreativeWork
• Document
• Entity
• Post