Using js, nodejs and json for the project?

[ankotsios]

Hi James,
Have you ever thought the possibility to develop the whole project js-based (js, nodejs and json)?

[HazardJ]

Andreas,

Short answer is yes! In connection with thinking about IPFS as distributed publishing for prose objects - I did this "view" of the source. It's fake, but gives the idea:
commonaccord.org/index.php?action=ipld&file=G/IACCM-Cooperate-CmA/Demo/Acme-Ang-NDA.md

@jbenet responded briefly to a discussion of integration.
CommonAccord/Cmacc-Org#16
(I think that the semantics of their links contains an error. It certainly contains a difference. The rest of their solution is so powerful and appropriate that it would be great to find the connection point. And if they are right, to incorporate that learning.)

#4

More broadly, Prose Objects, and especially the high-volume data from specific transactions, will need to be in a variety of formats:

1. The "source code" - lawyer-collaboration part probably is best in the current format which strongly resembles source code. It does not contain a bunch of quotes and unquotes, colons and commas to write a line. Much easier to read. This is not a religious statement, just a guess as to convenience. Interface can hide the complexity, but interface also intermediates - reduces touch and control.

2. Transmitting individual transactions will often be in JSON - from Interledger (greatly underestimated) to Hyperledger.

3. Management of large collections (e.g. internal operations at a bank or web-merchant) will be in databases. Many of those databases will be conventional. But Prose Objects are fundamentally a graph - I did a rough demo using Neo4j (more Scandinavians!), but I'm told that the graph community has moved on to other centers of gravity.

This is great. Jim