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

Refactor "target", "origin" and audience targeting properties

From: James M Snell <jasnell@gmail.com>
Date: Tue, 24 Mar 2015 13:23:51 -0700
Message-ID: <CABP7RbcuT3t4jB=qpOPvkfE4o3L0DOLhy0gZvy3sC+1ooPmZMw@mail.gmail.com>
To: "public-socialweb@w3.org" <public-socialweb@w3.org>
In the current vocabulary, we have the properties "origin" and
"target" that are used to indicate the entities from which and to
which an activity is directed. For instance, if I wanted to say that
"Sally moved the file from Folder A to Folder B" I would use:

  {
    "@type": "http://example.orgMove"
    "actor": "http://sally.example.org",
    "object": { "@type": "Document" },
    "target": { "@type": "Folder", "displayName": "B" },
    "origin": { "@type": "Folder", "displayName": "A" }
  }

We also have the audience targeting properties ("to", "bto", "cc" and
"bcc") which set up somewhat undefined concepts about "Primary" and
"Secondary" audiences for an Activity for the purposes of
notification.

For the sake of simplifying the Vocabulary, I would like to propose
two basic simplifications:

1. Rename "origin" and "target" to "from" and "to" to better reflect
their semantic purpose and
2. Drop the existing "to" and "bto" audience targeting concepts.

In other words, the following:

  {
    "@type": "http://example.orgMove"
    "actor": "http://sally.example.org",
    "object": { "@type": "Document" },
    "to": { "@type": "Folder", "displayName": "B" },
    "from": { "@type": "Folder", "displayName": "A" },
    "cc": "http://joe.example.org"
  }

Would say, "Sally moved the document from Folder A to Folder B. Let Joe know."

This is an overall simplification of the audience targeting that
better reflects how audience targeting typically works in most
existing social platforms and provides an overall model that is easier
to understand. There'd be no more of this "Primary" and "Secondary"
audience stuff.

The existing "target" would be moved to deprecated status and "origin"
would simply be dropped given that it was introduced in the previous
edit and has no backwards compatibility issues.

"cc" and "bcc" would be retained but "bto" would be dropped.
Received on Tuesday, 24 March 2015 20:24:38 UTC

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