Last update: 10/21/2011; 4:22:46 PM.
The occupy Namespace
;){kind=spacer}
OWS has inspired occupations in many other cities. They are connected via Facebook and Twitter, and through blogs hosted on a variety of platforms.
The community of blogs has defined a set of data they want to represent in their feeds that is not supported in the core of RSS 2.0. This data will allow them to connect in new ways specific to the needs of "occupy" blogs, as well as through the well-established mechanisms for RSS.
The data described in this document can be incorporated into RSS 2.0 feeds using XML namespaces. And while this namespace is designed for RSS 2.0, it can be used in any XML-based format that can be extended by namespaces.
Our hope is that the elements in this namespace will be supported in the user interfaces of the popular blogging tools, and that new aggregation tools will be created based on these elements.
As with RSS itself, we strive to be really simple in describing an occupation. Too much complexity creates an unnecessary barrier to entry, and formats that only technical people can understand make for fragile systems.
Dave Winer
New York, October 2011
New York, October 2011
;){kind=spacer}
Link to it as an attribute of an element containing sub-elements that are in this namespace.
For example, this is how you would link to it from the <rss> element:
<rss version="2.0" xmlns:occupy="http://namespace.occupyweb.org/">
Following is a list of elements in the occupy namespace.
;){kind=spacer}
The location of the occupation as a string of characters.
Example: <occupy:location>Anytown</occupy:location>
;){kind=spacer}
The home page of the occupation website. This may be different from the link in the RSS feed, which points to the HTML rendering of the items in the feed, usually the blog's home page. The homeUrl may point to page that contains more than the blog content, or merely points to the blog.
Example: <occupy:homeUrl>http://occupyanytown.org/</occupy:homeUrl>
;){kind=spacer}
One of three values: Occupation, GA or Incubating.
Example: <occupy:status>incubating</occupy:status>
;){kind=spacer}
Each occupation may have a kitchen, PR group, people who run the website.
Each is represented in the namespace by the group element. It has one attribute, which is optional, the email address of the contact for the group.
The possible values for group are: kitchen, info, pr, internet.
Example: <occupy:group contact="topchef@occupyanytown.org">kitchen</occupy:group>
;){kind=spacer}
This element lets you connect all the communication tools you use to your feed.
Its value is the name of a service. Examples: Twitter, Facebook, Flickr.
It has a single optional attribute which is the address of the occupation on that service. This must be a web address, in the form of a URL.
Example: <occupy:tool url="http://twitter.com/occupyAnytown">Twitter</occupy:tool>
;){kind=spacer}
Unless stated otherwise, the values for all elements and attributes in this namespace are case-insensitive. Of course names in XML are case-sensitive.
;){kind=spacer}
Create an example feed, link it into the Notes section.
For the group element, should we say these are the legal values, or you may make up your own values.
Is adminContact really different from the RSS 2.0 webMaster or managingEditor elements.