Slashdot Mirror

Hi. I created Coworking for exactly the reasons in that article. Coworking is community office space for programmers, writers, and anyone who works from home. From our Wiki (http://coworking.pbwiki.com):

"Coworking is cafe-like community/collaboration space for developers, writers and independents.
Or, it's like this: start with a shared office and add cafe culture. Which is the opposite of most modern cafes. ;)"

We already have two spaces in San Francisco, one in the Dog Patch area called The Hat Factory (http://hatfactory.net), and another called Teh Space that is downtown and will be comming up to speed soon. There are groups planning spaces in New York City, Paris, Boston, Chicago -- all over the world. If you go to our wiki, at coworking.pbwiki.com, you can coordinate a space in your own city. Some areas that can't support full time spaces are having Coworking Days, like the one that was just put on in Sausalito, California.

Best,
    Brad Neuberg
    bkn3@columbia.edu
    http://codinginparadise.org/

Hi there; I'm the software architect and implementor of HyperScope, and thought I'd provide some more info on the OPML capabilities of what you can do with it.

HyperScope is like OPML and HTML hyperlinks on steroids. There are so many different kinds of addressing your nodes that its not even funny. You can do direct addressing using hiearchical placement, even if there are no anchors:

mydoc.opml#2A

Where 2A is the second node (2), followed by it's first child (A). Node numbering always alternates between letters and numbers for readability; so you might have 2A3B. These are generated automatically and will work across all OPML documents, not just ones that have been marked up with the optional HyperScope namespaced attributes.

You can target node IDs, which are unique values that never change for a node even if it is moved around; these always start with a 0:

mydoc.opml#0626

Node IDs are optional, and placed on an OPML outline node using the hs: namespace:

<outline text="foobar" hs:nid="0626"/>

Node IDs are optional, and are created on document creation or editing, while the node hierachical numbers above work for any OPML file.

You can target based on label, using the optional hs:label attribute:

<outline text="foobar" hs:label="mylabel">

This would be the following address:

mydoc.opml#mylabel

Now, here's some cool stuff; once you've hit your target address using direct addressing, you can start to use relative addresses to move relative to the one you just targeted. For example, once I've gone to 'mylabel', I could jump down in the node hierarchy then to the next 2 nodes using the following:

mydoc.opml#mylabel.d2n

Which is .d for down and .2n for next two. You can jump through the hierarchy using many of these, including successor (.s) for going to the next sibling of the current node, independent of children; predecessor (.p) for the same, but for the previous sibling; back (.b), which will take you to the previous node that is right before you, independent of hierarchy; next (.n) for the same but forward; up (.u) to move up an ancestor; down (.d) to move down; tail (.t) to move to the last child sibling on my level; head (.h) to move to the first child sibling on my level; and more.

Once you've done these, you can start doing some other fun stuff. I can now do an indirect link, which is .l (that's a lower case L):

mydoc.opml#mylabel.d2nl

The 'l' is magical; it says: "once you've found the final node after dereferencing the other addresses, look inside the contents of this node, and take the first address you find then follow it."

For example, if the node that lies at mylabel.d2n has the following contents (that's an encoded HTML hyperlink in there):

<outline text='Make sure to see the document: &lt;a href=&quot;http://foobar.com/important.opml#2&quot ;Important&lt;/&lt;/&gt;

then adding that .l will cause HyperScope to extract
http://foobar.com/important.opml#2, and follow it and dereference it, which will cause the browser to jump to important.opml, then jump to node #2.

So indirect links let you create a layer of indirection between you and a set of links. You could imagine combining this with the node labels to create a kind of link database; just create a file that you always use that has named nodes for important links that you want to go to, then use indirect links against these. This is exactly what Engelbart does; I've sat and watched him and studied how he uses the system. You can see modern screencasts of that system and his work practices at these blog posts of mine: http://codinginparadise.org/weblog/2006/03/new-scr eencast-of-douglas-engelbarts.html and

I'm one of the software engineers who worked on the Open Library's Flipbook viewer. I just put up a blog post with further technical details on what we have done here:

http://codinginparadise.org/weblog/2005/10/introdu cing-open-library-and-ajax.html

Check it out.

Brad Neuberg

Most people don't realize that t/space and Burt Rutan are one and the same. T/space has prototyped and is creating an alt.space orbital craft, and has Rutan's design style and fingerprints all over it. I'll bet strong money that the design mapped out by t/space will be what SpaceShipThree basicly is. I've blogged more about this in the past at:

"Alternatives to NASA: Transformational Space":
http://codinginparadise.org/weblog/2005/08/alterna tives-to-nasa-transformational.html

That blog post points to videos, design documents, and opinions on what might be a preview of a SpaceShipThree-style craft, mapped out by t/space today.

Cheers, Joel