Re: social-ISSUE-13 (ActivityTypes): Which activity types are built into AS2, and how are they defined/structured? [Activity Streams 2.0]

FWIW, The Vocabulary already covers this to a great deal.

- James Snell
   jasnell@us.ibm.com
   Technology & Partnerships
   IBM Open Technologies Architect - Node.js, Mobile Backend & Cloud
   (559) 707-6331 (mobile)



From:	"Social Web Working Group Issue Tracker" <sysbot
            +tracker@w3.org>
To:	public-socialweb@w3.org
Date:	02/19/2015 10:11 AM
Subject:	social-ISSUE-13 (ActivityTypes): Which activity types are built
            into AS2, and how are they defined/structured? [Activity
            Streams 2.0]



social-ISSUE-13 (ActivityTypes): Which activity types are built into AS2,
and how are they defined/structured? [Activity Streams 2.0]

http://www.w3.org/Social/track/issues/13

Raised by: Erik Wilde
On product: Activity Streams 2.0

http://dret.github.io/W3C/SocialWG/AS1-in-AS2.html was an initial attempt
to list all "well-known" AS1 activity types and see how they are
support/implemented/used in existing systems. Wouldn't there need to be a
list of "well-known" activity types for AS2 as well, so that consumers of
AS2 can have some expectation of what they might see?

AS1 had a mix of models where (i believe) the idea was a well-defined core
vocabulary, possible a registry for "registered extensions", and then the
ability for everybody to use URIs and those would be "unregistered
extensions". that's modeled after RFC 5988 and a variety of other specs
that use this combo of a "controlled vocabulary" and a syntactically
distinct "open extension space".

regardless of how exactly AS2 is doing this, it would be useful to maybe at
least continue collecting evidence/support for supported/well-known
activity types out there, which then at some point in time can be distilled
into an AS2 vocabulary, with yet to be determined registration/extension
mechanisms.