On Wed, May 9, 2012 at 1:45 PM, Laurent-Walter Goix
<
laurentwa...@gmail.com> wrote:
[snip]
>
> thanks for this. as i can see most of the changes are going either
> into the entreprise SN direction, or media consumption/experience and
> gaming. here are some more specific comments:
Generally yes. Several are being driven by SCM-style systems; others
are derived from efforts such as Tin Can.
> - i am not sure about the difference between "retract" and "delete"
> but i admit this may be because of my limited english. anyway maybe a
> clearer description could help. is this more related to auctions-type
> of actions (i have noticed the new sell & purchase)?
The two are very closely related, yes, but differ one important way:
deletion implies destruction; retraction only implies that the object
was "pulled back" or "disavowed".
> - maybe the "answer" verb could well suit the "Question" object: i
> could not figure out so far how to represent this type of activity
> otherwise
We have an existing mechanism for indicating that any given object is
a "reply to" any other object in the form of the "inReplyTo" (see the
Replies extension for Activity Streams).... We also use a Question
object as the target of an activity... for instance:
{
"actor": {"displayName":"Joe"},
"verb": "post",
"object": {"objectType":"note","content":"my answer"},
"target": {"objectType":"question", ...}
}
That said, I'm not opposed to an "answer" verb, but I don't think it's
strictly necessary.
> - regarding Binary & File, could these eventually be merged (e.g. the
> File could benefit the md5 property as well) which type of use case do
> you envision for this? i assume that for small binaries a File object
> with data: URI could work as well, so is this intended for larger
> binaries (e.g. uploading a picture)?
Entirely possible but the two are intended to serve very difficult
purposes. I had intended binary to be used more in relation to the
"attachments" property on another object rather than as a standalone
object.
> - reporting abuses (aka flag as inappropriate) are also quite common
> activities in SN. what about defining an "Abuse" object type (more
> flexible than a "report-abuse" or "flag-inappropriate")? a "summary"
> property may be interesting here
>
Hmm... good point. Going to have to think about it.
>
>> > last, the wording "at a minimum" is quite unclear to me, also
>> > considering that some properties already exist in the "basic" object
>> > and others are described as optional. could you clarify what is the
>> > normative implication of such statement?
>>
>> I'm actually considering rewording this in an update. Essentially, the
>> meaning is not to convey that the existing properties are required or
>> changed in any way, but that they are minimally meaningful to the
>> object. I need to come up with another way of conveying that
>> information... likely through the use of clear, concrete examples.
>> Watch for another iteration of the draft to be posted this week with
>> editorial updates.
>
> ok, i'll wait for you to propose a new wording for the properties
> (which ones MAY meaningfully be provided) as you seem to have some
> ideas already.
>
> walter
>