Category Archives: NM – Reference

Nodal maps – Core functionality

Nodal maps – Core functionality

A list of core features a user can expect on a nodal map: A user can…

A user can add arguments for and against any node
Create and apply logic nodes that detail requirements for 100% certainty, including the truth of a single node
Mark nodes as irrelevant (thus excluding the argument from their confidence score)
Define sets that may only be partial sections of a map (ie define sections of a map they are interested in)
Fork and merge maps (make a version of a map private for their own editing)
Score confidence in individual nodes
Identify inconsistent or different scoring ( that is, identify where scoring is not logical)
Modify definitions used within a map
Create connections and comments to and about nodes (ie specify a node is related to a different node and make comments about nodes)

Nodal maps content loading – response from copilot

Nodal maps content loading – response from copilot

I have seen SPA (single page applications) being promoted as they superior approach for most apps. Still, it seems wrong to require fetching data for content that is largely static, like menus and static pages. I gave copilot this query and here is the response:

Nodal maps content loading – response from ‘copilot’

Mainly, it suggests that static content should use a standard http connection while dynamic content benefits from libraries like react.

Nodal Maps book list

Nodal Maps book list