Subject: Fwd: Network functional capability requirements |
From: Scott Mintz <scott.w.mintz@gmail.com> |
Date: 8/11/10, 16:53 |
To: Clark Robinson <robinsonchicago@gmail.com>, Barrett Brown <barriticus@gmail.com>, tessig@me.com, Mano Singham <mano.singham@case.edu> |
Primary Push After a Project PM member blogger/columnist/journalist (hereafter called Blogger) publishes a piece of writing to the web, he/she may relatively effortlessly choose to submit (hereafter called Push) a link using the Project PM widget (or similar tool) specific to the published item (hereafter called a Post) to other Bloggers who agreed to receive such links (hereafter called Connections).
Connection Bloggers can submit requests to other Bloggers to add them as a Connection. By agreeing to be Connected, Bloggers are affirming that they will review links and read Posts Pushed to them by the Connected Blogger and considers whether or not those Posts warrant further Pushing. Another means of making a Connection, is for an existing Blogger to invite someone to join Project PM. Connections can be terminated at any time by either Connected Blogger. Proper notification is necessary for Connection establishment and termination.
![]() |
I've shared Network functional capability requirements |
Following comments from Scott, Todd, Mano and Barrett, I have re-written the description of the network functions with the following goals: 1. eliminate the assumption that the network will be peer-to-peer and depend on widgets for all functions 2. reduce specification of technical solutions that should be in the domain of the programmer 3. the earlier version of these specifications was written with a goal of reducing the amount of data transmitted and simplifying network transactions--an assessment of the need for such limitations should be made by the programmer, not in this document Feel free to make comments and revisions in the spreadsheet itself. You can't hurt these Google docs; all prior versions are recoverable.Click to open: