Skip to content

Latest commit

 

History

History
178 lines (116 loc) · 7.28 KB

FEATURES.md

File metadata and controls

178 lines (116 loc) · 7.28 KB

Features

The purpose of this file is to document the Features of and serve as a Roadmap for this Mindmapping tool.

Ideas for new Features are created as GitHub Issues.

Completed Features are documented here, for context.

Basic Features

  • Load a default file that renders a 3d map with many nodes
  • Edit node attributes like Name and Product
  • Save object data to a .json file

Nodes

  • Nodes are like people - they almost instantly identifiable
    • Nodes have shape and material that are editable and programmable
    • Shapes have position, scale, rotation, memory of different shapes
    • Materials have color, reflectivity, emissivity, textures and all the Three.js material qualities
    • Nodes may have children that are nodes
    • Nodes may have attributes. Attributes might include
      • Text, images, links and functions

Relations

  • Relations are a special kind of node
  • Relations have pointers to one or more nodes
  • Relations may indicate
    • Belonging: one node belongs to another node
    • Sharing: two nodes have something in common
    • Positioning and Timing: a node may be either here or there and even nowhere for a while
  • Relations can help one node pull and move other nodes
  • Relations can group nodes

Updating the Map

  • Load several nodes from .svg files

Graphing Knowledge

What's out there that we want to meet or exceed?

Mind Maps

A mind map is a diagram used to visually organize information. A mind map is hierarchical and shows relationships among pieces of the whole.[1] It is often created around a single concept, drawn as an image in the center of a blank page, to which associated representations of ideas such as images, words and parts of words are added. Major ideas are connected directly to the central concept, and other ideas branch out from those.

Note: Examples mostly always show a single central node. Can we have fun with multiple node groups?

GraphQL

Mind maps expressed in a different way

GraphQL provides a complete and understandable description of the data in your API,

GraphQL is a data query language developed internally by Facebook in 2012 before being publicly released in 2015. It provides an alternative to REST and ad-hoc web service architectures. It allows clients to define the structure of the data required, and exactly the same structure of the data is returned from the server. It is a strongly typed runtime which allows clients to dictate what data is needed, therefore preventing excessively large amounts of data being returned.

Have you ever noticed that you very rarely see a graph when you read about GraphQL. Can we change that?

Xanadu / Ted Nelson

Original 17 rules

  1. Every Xanadu server is uniquely and securely identified.
  2. Every Xanadu server can be operated independently or in a network.
  3. Every user is uniquely and securely identified.
  4. Every user can search, retrieve, create and store documents.
  5. Every document can consist of any number of parts each of which may be of any data type.
  6. Every document can contain links of any type including virtual copies ("transclusions") to any other document in the system accessible to its owner.
  7. Links are visible and can be followed from all endpoints.
  8. Permission to link to a document is explicitly granted by the act of publication.
  9. Every document can contain a royalty mechanism at any desired degree of granularity to ensure payment on any portion accessed, including virtual copies ("transclusions") of all or part of the document.
  10. Every document is uniquely and securely identified.
  11. Every document can have secure access controls.
  12. Every document can be rapidly searched, stored and retrieved without user knowledge of where it is physically stored.
  13. Every document is automatically moved to physical storage appropriate to its frequency of access from any given location.
  14. Every document is automatically stored redundantly to maintain availability even in case of a disaster.
  15. Every Xanadu service provider can charge their users at any rate they choose for the storage, retrieval and publishing of documents.
  16. Every transaction is secure and auditable only by the parties to that transaction.
  17. The Xanadu client–server communication protocol is an openly published standard. Third-party software development and integration is encouraged.

More

Test Applications

If our effort is to be useful then it should be able to display existing data sets in newly meaningful and informative ways.

The following are links to possible test case ideas

gbXML Product List

In the beginning we should probably be kicking this one around

Wardley Maps

Is there data for Wardley map in reproducible digital format

A Pattern Language

The book includes 253 patterns along with their links to each other, diagrams and more

Periodic Table

Might be a good place to start

Russell's version

Lego Projects

Ikea Product Assembly / Moving Manual Projects

Opentecture Projects

  • Coming soon