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

AS2 Issues List

From: James M Snell <jasnell@gmail.com>
Date: Tue, 31 Mar 2015 09:44:12 -0700
Message-ID: <CABP7Rbc3Dzo-tBP6FerrHr+C721MDCLGghLfKHiu1yQi1=Dwyw@mail.gmail.com>
To: "public-socialweb@w3.org" <public-socialweb@w3.org>
For the call today...

I'm recommending closing the following issues:

ISSUE-4 - Explicit typing or support implicit typing - Already
addressed in current draft
ISSUE-7 - Are AS consumers required to understand the pre-JSON-LD
syntax -  Already addressed in current draft
ISSUE-12 - Action Types Structure and Processing Model - it was
decided already that RDF style reasoning should be supported but not
required.
ISSUE-14 - as:Link complexity - the spec already includes language
that deals with the relationship between as:Link and as:Object and how
they relate to one another. If there are specific suggestions to
improve the language, then ok. If the proposal is to remove as:Link,
then it ought to be a specific proposal to remove as:Link
ISSUE-15 - AS2.0 vocab duplicating microformats.org and schema.org
efforts - microformats and schema.org are not normative dependencies
for AS2.0. Some duplication is ok and ought to be expected.
ISSUE-20 - Support JSON Text Sequences? - out of scope, recommend
first seeing if there are ways of having JSON-LD generically support
JSON Text Sequences
ISSUE-23 - Backwards compatibility in AS 2.0 - already dealt with in the draft

The following existing open issue still need discussion:

ISSUE-13, Which activity types should be in the core? (Erik)
ISSUE-16, Improve spec structure (Erik) Specific suggested edits would
be helpful (PR anyone?)
ISSUE-17, Identity, Agent, Person, Persona, Account etc. need
clarifications (Elf)

Raised Issues that need to be opened and resolved:

ISSUE-26, Representing Profiles (James)
ISSUE-27, Representing Changs to Profiles, (James)
ISSUE-28, Remodel "Connect" and "FriendRequest" or remove them, (James)
ISSUE-29, Removing Activity Types not used by User Stories, (James)
ISSUE-30, Deprecate "actor" in favor of "attributedTo", (James)
ISSUE-31, Refactor "target", "origin" and audience targeting, (James)
ISSUE-32, Deprecate "generator" and "provider" (James)
ISSUE-33, Deprecate or remove the "rating" property (James)
ISSUE-34, Context vs Motivation (James)
ISSUE-35, Simplify the Actor Types (see Issue-17 also) (James)
ISSUE-36, Leveraging JSON-LD context vs. RDF vocabulary (elf).
Specifically, do we want to leverage JSON-LD mechanisms for reverse
properties. There are inherent complexities
with this approach when working strictly with the JSON-LD expanded form.


Actions:

ACTION-14 Setup json-ld context for namespace... Open ... still need this
ACTION-26 Review microformats examples... Open... ongoing
ACTION-29 Reach out to open social foundation members... recommend
closing, rather pointless at this time.
Received on Tuesday, 31 March 2015 16:45:03 UTC

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