- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Wed, 15 Jul 2015 14:10:25 +0200
- To: Amy G <amy@rhiaro.co.uk>
- Cc: "public-socialweb@w3.org" <public-socialweb@w3.org>
- Message-ID: <CAKaEYhJ-tyxK8+JPJFdozWObP8Cf+n4FNnqdqMcxCtivKkcxqg@mail.gmail.com>
On 15 July 2015 at 12:49, Amy G <amy@rhiaro.co.uk> wrote:
> So... if a webmention endpoint accepted
>
> {"source":"http://example.com/post","target":"http://elpmaxe.org/post"}
>
> instead of source=http://example.com/post&target=http://elpmaxe.org/post
>
> is that what you'd want to see?
>
Potentially, yes. As long as it passes the test suite for the common JSON
syntax this group ends up agreeing on.
>
> I don't think I understand your PHP reference.
>
> On 15 July 2015 at 11:30, Melvin Carvalho <melvincarvalho@gmail.com>
> wrote:
>
>>
>>
>> On 15 July 2015 at 12:20, Amy G <amy@rhiaro.co.uk> wrote:
>>
>>> Webmention itself doesn't care about the data structure of the source.
>>> If you can retrieve JSON from the source URL (whether by parsing
>>> microformats, content negotiation, or following a link rel or whatever)
>>> then this works just fine according to the charter.
>>>
>>
>> I get what you are saying. Replace "webmention" in the sentence above
>> with "PHP". It would be an equally true sentence.
>>
>> In general the point, was not about what webmention can reference or
>> process. It was about what it accepts. What I think would be nice is if
>> all the technologies we have on the REC track could support the common JSON
>> social syntax.
>>
>>
>>>
>>> On 15 July 2015 at 09:42, Melvin Carvalho <melvincarvalho@gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On 15 July 2015 at 08:19, Amy G <amy@rhiaro.co.uk> wrote:
>>>>
>>>>> > For example sending a direct message via a JSON activity stream, is
>>>>> one of the user stories.
>>>>>
>>>>> Which user story mentions json or activity streams?
>>>>>
>>>>
>>>> The charter does.
>>>>
>>>>
>>>
>>
>
Received on Wednesday, 15 July 2015 12:10:53 UTC