fedwiki/wiki-plugin-data

Federated Wiki - Data Plugin

wiki-plugin-data's Issues

NaN while scrubbing

It would be nice if NaN, Not a Number, was suppressed while scrubbing over the data.

Migrating to fedwiki org.

Part of the refactor, see WardCunningham/Smallest-Federated-Wiki#403

• Update package.json to include new repository and issues url
• Update ReadMe.md
• check pages for any GitHub references, and update as required.
• increment patch version
• move to fedwiki org.
• remove github wiki, if not already done.
• add ward as an owner of the package
• republish to npm

Graph model not explicitly mentioned in README

The README states we can also fearlessly drop a JSON representation of a graph.

data.coffee#L58 makes some assumptions about how such a graph should be modeled.

By looking into some almereyda/graph_json_examples I've found that wiki goes different directions here:

• The Websocket stream of the Linkmap Plugin submits a graph similiar to the Directed Acyclic Graph (DAG) as proposed on stackoverflow as a node list with containing edges lists.
• Yet the D3 DAG generator I've come across stores nodes and edges.
• This plugin calls them nodes and links.

Would it make sense here to upgrade the graph support of this component to JSON-LD, to follow a spec, and start implementing stronger Semantics?

Support the DAT ecosystem

The dat-data.com project abstracts streaming data interfaces and data version control. wiki tries to wrap data with visualization, which implies data mangling.

Dat is supported by @maxogden and seems to develop into a modular ETL engine for distributed (micro)service-oriented architectures. Now the federation comes into play. The following just came to my mind:

---

Wiki's drag-and-drop workflow could offer easy instantiation of new dats for a karissa/dathub (pinging @Karissa) for example, by offering a compatible ReadWrite API.

Experiments in this regard could mean to

• offer Newline Delimited JSON support for import and export in wiki-plugin-data. (pinging @finnp)
• streamline ReadWriteWeb APIs both offer
  • in terms of
    • authorization or
    • the semantics and vocabulary of shared endpoints and,
      • where this plugin may offer additional ones,
  • maybe later even esp. in regards of the Linked Data Platform and wiki and generalized Hydras. (pinging @bblfish)
• share thoughts on
  • backend-agnostic storage workflows.
  • distributed versioning and maybe patch-based versioning infrastructures. (pinging @rynomad)
  • federated Publish-Subscribe (Merge/Fork) scenarios.