Design node/tree package manager

[deSagaz]

Once users have finished designing learning journeys, they should be able to publish them in the Blosm Network.

These packages should be searchable, may need to be curated to some extend, and should be easily remixable and versionable. They should contain which plugins are required to open them, so clients can ensure the right libraries are available (e.g., a VR js library) - this should also enable backward compatibility if versions of plugins and content are different.

Packages should have a unique id/hash according to their content (see #1, #2). That means that if you see the same nodes/trees in someone else's garden, they show YOUR interactions with them (completion/comments...).

Sources of inspiration:

• NPM
• PiPy
• Git

[deSagaz]

Requirements for Trees:

• Users work locally on trees, privately, and are able to save revisions locally.
  • Proposed revision id (to allow automatic generation): [user_id]_[current_date+time]
• Users can publish trees online, publicly.
• Users can edit published trees locally, privately.
• Users can suggest edits of the original published tree to the author.
• Users can fork original published trees, and become part of the public network, without author involvement.
• Users should be able to compare trees and their history, and merge selected trees (showing two at once).

[deSagaz]

Requirements for Nodes:

• Are added by specifying link
• If link (= id) added first time in the history of blosm:
  • Take title based on meta-data or page title (in that order)
  • Take description from meta-data or kept out
  • Take language from meta-data or kept out
  • Take instructor from meta-data or kept out
    • If found, tie to registered (verified) author account on blosm
  • Take revision from meta-data, hash of (certified static) content or current date (in that order)
  • Take type from meta-data, website (if known), or kept generic
• Else, find existing data in global repository, and copy the data from there.
• Content cannot be edited directly inside Blosm, but only at external sources (in principle).
• Server should allow users to report duplicates and to allow merging of nodes by authors