Design unknown

[almereyda]

The architectural design of the transformap-editor is still unknown, yet we already anticipate some components. These could be aligned around the persistence, engine and presentation layers involved.

persistence:

• data.transformap.co
• base.transformap.co
• wikidata.org
• (openstreetmap.org)

engine

• search + queries
• authentication + authorization
• semantics + transformation

presentation

• map design < cartography, interactivity
• interface design < query builder from facets, responsivity, social features
• familiarity with other transformap services

Further ideas can be found at https://tree.taiga.io/project/transformap/epic/386

Any feedback is welcome.

[josefkreitmayer]

@almereyda could you go more into detail, especially with the definitions of "persistence", "engine" and "presentation" and the relating items. Which parts of the thread are still relevant given the current state of development?

About authentication via base.transformap.co: #3

@species are you familiar with the issue presented by @almereyda?

[species]

The current design is a very very basic one tailored to fulfil the SSEDAS requirements with minimal effort.
Any advanced features we were discussing (Linked Open Data, e.g. with OpenStreetMap or Wikidata) are not considered yet.