It would be great to work documents as if they were source code. With modularity, persistent objects, versioning, forking, merging. I've been working on a list-based data model that does that. I am a lawyer, and the direct goal is codified legal documents, improving quality and making them quick and universally available. The same approach of course also applies to other kinds of documents, like reports and even school work.
I've been using a number of different platforms, including Mediawiki. A smart person pointed me towards Neo4j and I've been talking with the team and playing with gists. Chris Leishman suggested posting here. This is the gist - http://gist.neo4j.org/?github-HazardJ%2Fgists%2F%2FDoc_Graph_As_Lists I'd be really interested in your thoughts. Jim -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
