SPS (Simple Project Syndication) is a dialect of XML for project syndication over the Internet. It proposes an open schema for the organization of information flow between people, documents, and tasks in a distributed ecosystem rather than a hierarchical one.

SPS Sample (XML)
SPS Schema (XSD)

Open-tasking (2004-2005) was an experimental web application that utilized the SPS schema. It enabled people to create and manage tasks that can be altered by other people to include more detail. In Open-tasking, people collectively designed vertically deep or horizontally wide projects based on other people’s skills. The distributed and open architecture of the Open-tasking system enabled people to manage their own complexity, so as the project develops, a worker becomes a manager and vice versa.

Element Structure

The top element is <project> that describes the main container for tasks. The element structure for projects is below:

Element Description Example
title The name of the project The Ultimate Potluck
link The URL to the website corresponding to the task. http://plw.media.mit.edu/
treehouse/projects/ultimatePutlock
description Description of the project. We are going to cook food for everyone here. Join us.
language The language the channel is written in. en-us
creator Name and email address for person who created the project. Burak Arikan arikan *at* mit.edu
A project contains any number of <task>s. The sub-elements of a task represents the essential information about the task. These are important for easy syndication of the project.
Element Description Example
title The title of the task. Spicy BBQ Hot dogs
link The URL to the website corresponding to the task. http://plw.media.mit.edu/ treehouse/projects/task/?= bbqhotdogs
description Description of the task. Cooking BBQ hot dogs for fifteen people.
creator Name and email address for person responsible for the project. Burak Arikan arikan *at* mit.edu
implementors List of people who are going to execute the task. It containts sub-elements that are in the <implementor>.
dateStart Date and time of the task. 2004-05-28T12:00:10
duration Duration of the task. P2H
.
dateCreated The task is created on this date and time. 2004-05-17T08:30:00
dateModified The task is created on this date and time. 2004-05-17T08:32:11
milestones List of milestones on the task timeline. It contains sub-elements that are in the <milestone>
budget Budget of the task, that is going to be paid to the implementor by the creator. $15
parentTask Link to the task that is on top of this task. This may not exist. http://plw.media.mit.edu/ treehouse/projects/task/?=bbqparty
nextTask Link to the task after this task. http://plw.media.mit.edu/ treehouse/projects/task/?= mixsauce
prevTask Link to the task before this task. http://plw.media.mit.edu/ treehouse/projects/task/?= doshopping
pubDate Indicates when the task was published. 2004-05-30T09:30:10
Each implementor is a list of people who are exeucting tasks, and they are contained in the <implementor>. Implementor has two elements:
Element Description Example
contact Information about the responsible person. Noah Fields noah **at** noah.cx
role Description of the responsibility. Chef
<milestones> is a list of milestones that points important dates on the task timeline. Milestones are contained in <milestone>. Implementor has two elements:
Element Description Example
title Description of the milestone. Heat hot dogs as directed on package, or grill until heated through.
date DAte and time for the milestone. 2004-04-28T12:30:00