broidHQ/integrations

inconsistency in broid-schemas object keys

gregory opened this issue · 1 comments

Overview

  • What project is this issue for?: broid-schemas
  • Is this a bug, security, feature request, or feedback: Feedback

Details

broid-schemas use the field "to" to refer to the target of an outbound message, whereas both the activitystream spec & inbound messages schemas refer to is as the "target"

If there is no technical reason behind this choice, it would be nice to see some consistency.

Considering the spec, the both can be work

While there are means (based on the action type, actor, object and target of the activity) to infer the primary audience for many types of activities, heuristics do not work in every case and do not provide a means of identifying the secondary audience. The to, cc, bto and bcc properties may be used within an Object to explicitly identify the Primary and Secondary audiences.

reference, dfn-to and dfn-target

We choose to to try to keep the same thinking than peoples/developers can be found in the mail world.

But it's a good point about the consistency...
I am not close to updating the schemas if for the community it makes sense (cc @dustinblackman )