Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proving usability of ActivityStreams2.0 and Microformats together by example #1

Closed
elf-pavlik opened this issue May 1, 2015 · 2 comments

Comments

@elf-pavlik
Copy link
Member

I see need for showcasing how to use ActivityStreams2.0 together with Microformats. I have impression that while AS2.0 focuses on Activities (~Events), Microformats already does Objects and as:Objects duplicates it in incompatible way instead of aligning with it.
Post recently written by @rhiaro has interesting insights very relevant to this issue http://rhiaro.co.uk/2015/04/post-and-activity-types
I would like to propose very pragmatic approach to find resolution for this issue:

  1. @tantek - one of Social WG chairs uses Microformats in his deployment
  2. @evanp - one of Social WG chairs uses ActivityStreams in his deployment

Reaching basic interoperability between two of our dear chairs will prove that we stay on tracks and don't wonder off in incompatible directions. Argument that we need federation component for that I would consider invalid. The Web will not break apart if to get started their deployments simply pull each other feed(s) and/or stream(s) even every second.

I would suggest starting demoing user stories which both of them +1
https://www.w3.org/wiki/Socialwg/Social_API/Sorting_user_stories

Also Micropub and ActivityPump look very close to each other and use two simple endpoints: Micropub/Outbox & Webmention/Inbox more early comparisons available at https://www.w3.org/wiki/Socialwg/Social_API/Comparison#Endpoint

@elf-pavlik
Copy link
Member Author

@akuckartz
Copy link

I have not seen anything "rude" or "condescending" and think that this characterisation and reaction is not justified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants