Re: [ba-ohs-talk] New backlink metadata; mhpurple v0.2 released
I'm game. How do we start to assemble a common API for all the graph-based
editors? I was hoping that one of the graph editors would emerge as "the
best". Therefore such integration wouldn't have been necessary. (01)
Let's say we build an import/export standard. How do we make a tree (XML)
represent a graph?
How do we prune a graph for exporting subsets, branches or aggregates? (02)
What common baseline features are required in each graph editor for the API
to be useful: purple numbers, versioning, typed edges? (03)
Lucid Fried Eggs
PS. If I had to guess which graph editor was emerging as "the best", my
money's on Touchgraph. Let's hope Alex builds peer/peer or client/server
features into it so we can use it collaboratively. I still prefer typed
edges though. (05)
> * Integration and interoperability with all other applications using the
> same APIs. There's no reason I shouldn't be able to transclude a Wiki
> node in an e-mail, or for that matter, into Lucid Fried Eggs, which is
> really a Wiki with typed links.
> Incidentally, you can reframe a number of apps as essentially graph
> editors. XML editors? A tree editor, which of course is a type of graph.
> Threaded discussion forums and blogs are another examples of tree-based
> discussions. Lucid Fried Eggs, QuestMap/Mifflin, Topic Maps and RDF
> editors -- all graphs.
> If all of these tools shared a common API, and if there were tools that
> implemented these APIs, then all of these tools would be interoperable.
> The universe of those interoperable apps makes up the OHS, and the APIs
> are what enables all of this. (06)