Mailing-List: contact dev-help@streams.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@streams.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of steve@blackmon.org designates
 209.85.128.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAENpzYXj_h1wt3d4U8zX_OY8noExPsE=VKuUCs+08X_3nXWTvA@mail.gmail.com>
References: <CF853637.4BB7%rdouglas@w2odigital.com>
	<CABP7Rbdk94sK5--2cwLhaX3cxX+MaRM_MQBm3ng--ANKpZSi+g@mail.gmail.com>
	<CF853ADD.4BBB%rdouglas@w2odigital.com>
	<CA+jwTarZJ-5A683G1L-jbXLAxmRm4GyJzb1AS4G1QVAg+_3iVQ@mail.gmail.com>
	<CAENpzYXj_h1wt3d4U8zX_OY8noExPsE=VKuUCs+08X_3nXWTvA@mail.gmail.com>
Date: Mon, 5 May 2014 11:54:14 -0500
Message-ID: 
 <CAJ7ACC_ZofTb9PMHkMxjuPF_KYhVQBZNVJdZg1eAt5ibKibzmA@mail.gmail.com>
Subject: Re: New Generalized Extensions for ActivityStreams Schema
From: Steve Blackmon <steve@blackmon.org>
To: dev@streams.incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think it's a worthwhile exercise to attempt to standardize
well-defined custom attributes across streams implementations.  I
think gender and authoritative metrics sourced from upstream (total
shares, likes as of some point in time) fall into that category.

I do think we should keep a barrier between a core activity (defined
by published spec) and usage of activity with additional designated
fields.  I'd like to see a pattern where individual contributed
modules can extend the core activity model and use bind-able jackson
objects generated from schemas so other contributed modules with an
asserted dependency can interact with the extended activity through a
more specific typed interface.

Since some of the specific concepts referred to in this thread are
global in nature i.e. not aligned directly to any specific module, i
suggest that we put the associated schema and supporting classes in a
streams-pojo-extensions module, which implementers can use if they
want to gain access to these fields, and not use if they prefer to
work with objects directly from the spec.

Steve

On Thu, May 1, 2014 at 7:36 PM, Matt Franklin <m.ben.franklin@gmail.com> wr=
ote:
> On Tue, Apr 29, 2014 at 8:17 PM, Bill Christian <bill.christian@gmail.com=
>wrote:
>
>> Not a fan of a generic 'extensions' collection. I have, though, found
>> use in defining entities collection for items referenced in the
>> content section. The style mimics the approach from App.net messaging
>> schema. From your examples, this would only address hashtags,
>> mentions, and urls. The gender of the author should be a custom
>> attribute on the actor or object. However, an example might clarify.
>> Aren't rebroadcasts consider downstreamDuplicates?
>>
>
> I think rebroadcasts in this case are shares, retweets, etc.
>
>
>>
>> On Tue, Apr 29, 2014 at 12:20 PM, Robert Douglas [W2O Digital]
>> <rdouglas@w2odigital.com> wrote:
>> > I=C2=B9m working on mocking up the new schema at the moment, but =C5=
=92extensions=C2=B9
>> > would become a new top-level element in the json structure. Each of th=
e
>> > proposed extensions would then be a sub-element in that =C5=92extensio=
ns=C2=B9
>> > element.
>> >
>> > On 4/29/14, 11:12 AM, "James M Snell" <jasnell@gmail.com> wrote:
>> >
>> >>In this proposal, how would these manifest in the json structure?
>> >>
>> >>On Tue, Apr 29, 2014 at 8:57 AM, Robert Douglas [W2O Digital]
>> >><rdouglas@w2odigital.com> wrote:
>> >>> Hi all,
>> >>>
>> >>> Given that there are certain attributes that are similar across
>> >>>multiple social media feeds (ie. A =C5=92like=C2=B9 on Facebook, =C5=
=92favorite=C2=B9 on
>> >>>twitter, and =C5=92+1=C2=B9 on Google+ are all equivalent) I think it=
 makes sense
>> >>>to break these out into generalized extensions. I=C2=B9d like to prop=
ose the
>> >>>following extensions:
>> >>>
>> >>>
>> >>>  *   extensions.hashtags
>> >>>     *   An array that holds an entry for each unique hashtag mention=
ed
>> >>>in a post
>> >>>  *   extensions.likes.perspectival
>> >>>     *   A boolean field that denotes whether or not this post was
>> >>>favorited by another user
>> >>>  *   extensions.likes.count
>> >>>     *   The total number of likes a post received
>> >>>  *   extensions.rebroadcasts.perspectival
>> >>>     *   Whether or not this post was rebroadcasted
>> >>>  *   extensions.rebroadcasts.count
>> >>>     *   The total number of rebroadcasts this post received
>> >>>  *   extensions.rebroadcasts.users
>> >>>     *   An array that holds an entry for each user that rebroadcaste=
d
>> >>>this post
>> >>>  *   extensions.user_mentions
>> >>>     *   An array that holds an entry for each user that is mentioned=
 in
>> >>>this post
>> >>>  *   extensions.urls
>> >>>     *   An array that holds an entry for each URL that is mentioned =
in
>> >>>this post. Each entry would have both the raw URL in addition to just
>> >>>its domain
>> >>>  *   extensions.gender
>> >>>     *   The gender of the author
>> >>>
>> >>> What are everyone=C2=B9s thoughts?
>> >>>
>> >>> Thanks,
>> >>> Robert Douglas
>> >
>>