h-feed

2013-06-29T23:11:36Z

Sandeepshetty: /* Examples in the wild */ Added sandeep.io

{{stub}}

'''<dfn>h-feed</dfn>''' is a [[microformats2]] experiment with a top level feed object to contain [[h-entry]] posts.

From experience with [[hAtom]], it's not clear that there's actually a need (use-case) for a top level feed, but for those that wish to experiment with it, here it is.

root class name: h-feed

properties:
* p-name - name of the feed
* p-author - author of the feed, optionally embed an [[h-card]] {{main|h-card}}
* u-url - URL of the feed
* u-photo - representative photo / icon for the feed

children:
* nested [[h-entry]] objects representing the items of the feed

== Use Cases ==
* Generate an Atom feed
** This seems like a legacy use-case, not sufficient to actually justify h-feed.

* Feed per channel of content - needs a name
** "I will have a feed per tag (channel) so I want to name them." - Sandeep Shetty in #indiewebcamp
** It appears there is some desire to create separate feeds for an indieweb site for separate subsets of content, and name them <em>explicitly</em> accordingly. This presents a need for a container object for the h-entry elements, where the container itself can have a name. This is a potential interesting use-case for an explicit 'h-feed'.

== Examples in the wild ==
* http://tantek.com/ uses h-feed with p-name and p-author properties and child h-entry posts.
* http://sandeep.io/ uses h-feed with p-name and p-author properties and child h-entry posts.

== Parsing ==
When parsing a page for an h-feed, do so per [[microformats2]].

Fallback:

If there is no explicit "h-feed" element, implementations may:
* Treat the <code><title></code> of the page as the p-name
* Use http://indiewebcamp.com/authorship to discover authorship of posts.
* Treat top level h-entry elements as items in the feed.

== See Also ==
* [[h-entry]]
* [[microformats2]]
* [[hAtom]]

activity-streams

2013-06-13T10:46:08Z

Sandeepshetty: /* see also */ added link to "RSSB microformats to Activity Streams"

<entry-title>activity streams</entry-title>
== introduction ==
As people use various different web sites to [[blogging-tools|blog]], update their [[picoformats|status]], post their [[geo|location]], or [[photo-info|photos]], sites and tools have emerged to aggregate these various actions into a continuous eclectic stream of activities.

Such activities typically involve a '''subject''' (the person doing the activity), a '''verb''' (what the "doing" is of the activity), and often a '''direct object''' (what the activity is being done to or with). Activity stream aggregators typically republish activities in reverse chronological order, independent of type of activity.

[http://friendfeed.com Friendfeed] is perhaps the most well known web site that does cross site activity aggregation/publication, and [[movable-type|Movable Type]] has built-in support for aggregation/publication of activity streams as of v4.1.

For more examples, see the [http://diso-project.org/wiki/activity-streams DiSo wiki activity streams page] (see also [http://wiki.diso-project.org/ the other DiSo wiki], not sure [http://twitter.com/t/status/972796117 which to use]).

== problem statement ==
The type and variety of activities that services support and publish is growing every month. Services like Friendfeed and tools like Movable Type must either be continuously updated with one-off per service implementation support, or provide nothing more than lowest common denominator feed aggregation and publication.

If activity streams were published in an open standard format then activity stream aggregators that supported such an open format would automatically support any new standards supporting activity stream services without having to play the continuous one-off proprietary API implementation catch-up game. In addition, new activity publishers would be less beholden to trying to reimplement others' proprietary APIs (and all the giving up control to a likely competitor problems that arise from that practice).

== existing standards ==
Feeds (and related formats, RSS, [[Atom]], [[hAtom]]) solve most of the problems of activity streams. [[movable-type|Movable Type]] 4.1's activity stream publishing support already supports [[hAtom]] today for example.

The '''subject''' of an activity is nearly always the author of a feed.

The '''direct object''' of an activity is typically an item or entry in a feed.

Sites that publish different kinds of objects/items in their interfaces often present those items/posts differently depending on the kind of object. Activity Streams thus has a set of object-types that represent these kinds of objects, based on their research on existing object type publishing examples in the wild.

== apparent need and focus ==
Thus key pieces that seem worthy of standardization are:
* the '''verb''' aspect of an activity
* the '''object-type''' of an item or post

Per the [[microformats]] [[principles]], by focusing on these smaller parts of the problem (verbs and object-types), we may be able to more quickly solve the larger problem of representing activities and activity streams.

Thus, per the microformats [[process]]:

* [[activity-verb-examples]]
* [[activity-verb-formats]]
* [[activity-verb-brainstorming]]

And:

* [[activity-object-examples]]
* [[activity-object-formats]]
* [[activity-object-brainstorming]]

=== activity object brainstorm ===
Strawman brainstorm (to be incorporated into [[activity-object-brainstorming]]) : for now, try simply re-using the Activity Streams set of object-types as class names, preceded with "h-as-", as a [[microformats2]] poshformat for representing different Activity Stream object-types in [[hAtom]]. Use these object-type class names to "subclass" the "h-entry" class in hAtom, e.g. where you might publish
<source lang=html4strict>
<div class="h-entry hentry">
</source>
With this strawman proposal, for blog posts you might publish:
<source lang=html4strict>
<div class="h-entry hentry h-as-article">
</source>
Or for little tweet/text notes:
<source lang=html4strict>
<div class="h-entry hentry h-as-note">
</source>
And [[rsvp|RSVPs]] (as [[rsvp-brainstorming|brainstormed]]) :
<source lang=html4strict>
<div class="h-entry hentry h-as-rsvp">
</source>

==== sites implementing activity object brainstorm ====
See: http://indiewebcamp.com/ActivityStreams#Use_with_microformats2

== see also ==
* [[h-entry]]
* [[hAtom]]
* [[events/2008-10-21-sf-weekly-meetup-dinner]]
* [http://wiki.activitystrea.ms/Microformats-for-Activities ActivityStrea.ms Wiki Page for Microformats]
* http://indiewebcamp.com/activitystreams
* [http://www.sandeep.io/50 RSSB microformats to Activity Streams]

Microformats Wiki - User contributions [en]

h-feed

activity-streams