I would suggest this is the perfect example of a project which should extend SCIM [1], a recently release RFS for this functionality. SCIM is Simple Cross-domain Identity Management and allows sharing of user and group information via RESTful JSON APIs. It's easily sufficient for vCard information and is also easily extensible. I think calendar and to-do information is the next step.<p>[1] <a href="http://www.simplecloud.info/" rel="nofollow">http://www.simplecloud.info/</a>
An ambitious idea. Some questions immediately spring to mind.<p>> Task is owned by a Project. Project belongs to a User. User is a member of Domain.<p>Can Tasks have subtasks? Recursively? To an arbitrary depth?<p>Can Projects have subprojects? (see above)<p>I assume since a "User" is just an email address, a group email address would implement a "Group" at the "User" level?<p>In a company setting, Users (Contractors, Employees) come and go during the life of a Project. What happens to Tasks assigned to a User who leaves the (company|Domain|Project)?
I'd follow along with what the IndieWeb folks are doing. They've got a pretty good principle of reusing existing infrastructure in new ways to build interesting things without needing coordinated upgrades.<p>As an example, getting widespread adoption of a new TX DNS record type is unlikely, though you can fake it with TXT records.<p><a href="https://indiewebcamp.com/Category:building-blocks" rel="nofollow">https://indiewebcamp.com/Category:building-blocks</a>
The idea is great. Perhaps, however, it is too ambitious.<p>Maybe this could start as a thinner protocol, with adaptors to turn Todoist, Asana, Trello and Basecamp into clients.
As someone who uses Todoist for personal tasks, Asana at work, and Basecamp for those clients who haven't migrate to Asana yet ... yes.<p>From a pragmatic perspective, I'm not sure this can gain traction. The mail exchange protocol was built in a very different environment, and you'd have to get some serious weight behind this to gain much traction.
Had the same idea couple of times, whet I needed to distribute tasks between couple of servers. Now I can imagine it, as some sort of TCP service (like EMAIL) powered by DNS records and TCP server/client. Maybe SMTP can be also used. This desires and requires more time and energy, maybe a team of people, maybe open standard and SW implementation of TCP services. This could be used, not only for humas, but also for automation.
What is the use case? (Ideally, use cases -- plural.) I can sort of extrapolate from what is written but it would be great to have that clearly stated.
I'm not getting what this is for. It seems to be something about automation around arbitrary people on the Internet giving you work to do. It seems like this is a flaw to get rid of? Email and bug trackers make it all too easy.