Graph model not explicitly mentioned in README
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- coffeescript, json
- Domain
- data
Research direction
Start at client/data.coffee#L58 and compare its graph assumptions with the linked graph_json_examples, Linkmap stream, and D3 conventions. Clarify whether the goal is to document the existing nodes/links model or design JSON-LD and semantic support; the issue currently provides no concrete completion test.
Written by the indexing model from the issue text.
Description
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
nodesandedges. - This plugin calls them
nodesandlinks.
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?
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fedwiki/wiki-plugin-data
-
NaN while scrubbing Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
fedwiki/wiki-plugin-data#7 · 3 comments ·
All issues in fedwiki/wiki-plugin-data
Similar issues
-
area/install-update comp/cli comp/desktop P3 sweeper:risk-compatibility type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#122386 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
docs web/
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100