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

Re: social-ISSUE-20 (Collection Serialization): Represent Collections using JSON Text Sequences (RFC 7464)

From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
Date: Sun, 15 Mar 2015 14:03:09 +0100
Message-ID: <5505830D.6010907@wwelves.org>
To: Social Web Working Group <public-socialweb@w3.org>
On 03/11/2015 01:56 PM, Social Web Working Group Issue Tracker wrote:
> social-ISSUE-20 (Collection Serialization): Represent Collections using JSON Text Sequences (RFC 7464)
> 
> http://www.w3.org/Social/track/issues/20
> 
> Raised by: Erik Wilde
> On product: 
> 
> it is not quite clear to me how github issues relate to w3c tracker issues, but it seems that the latter gets more visibility in IRC and other meetings. because of this, i am duplicating an issue from github to the w3c tracker. the original github issue URI is https://github.com/jasnell/w3c-socialwg-activitystreams/issues/69
> 
> "Currently, AS collections must use a JSON array (http://www.w3.org/TR/2015/WD-activitystreams-core-20150129/#collections). This can be cumbersome and problematic for scenarios with streaming activity data, and/or very large collections. One possibility would be to also allow JSON text sequences https://tools.ietf.org/html/rfc7464. Since they have their own media type, standard HTTP mechanisms could be used between a client and a server to negotiate the supported/preferred format for collections."
Hi Erik,

I included your raised issue in proposed face 2 face agenda point about
Collections
https://www.w3.org/wiki/Socialwg/2015-03-17#Day_1_-_Tuesday_17_March_2015

I also linked to that ISSUE from "Streaming & Push" wiki page
https://www.w3.org/wiki/Socialwg/Streaming_%26_Push

To my understanding currently we don't focus on coming up with clear
recommendation. At the same time we want to capture various requirements
for that and make sure that we don't make any design choices which will
make it problematic to add it in near future.

Cheers!


Received on Sunday, 15 March 2015 13:03:41 UTC

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