20230712 OpenSCD NEXT Architecture

Today we will check the alignment on the product vision first:
https://lf-energy.atlassian.net/wiki/display/SHP/OpenSCD+next+architecture (product vision / motivation and principles)

https://github.com/openscd/.github/pull/11/files history.md

Add history.md to the project. Daniel will proofread. 

Agreement on modular structure.
Product vision 

-----

Daniel suggested: I'd quite like to see the product vision to have a goal which is end-user focussed, e.g. “To enable fully digital substations—from design and commissioning through to maintenance and replacement” or something like that.

https://github.com/openscd/.github/pull/12/files

-----

Tamás added: https://github.com/openscd/open-scd-core/pull/127
and a general discussion about the progress of the wizarding API and Core

-----

Tamás: What means easy to write plug-in? We clearly state trade-offs. Integration. 
Daniel: Wanna do: provide interface, undo/redo, SCL abstracting out the complexities. 

Daniel: CORE is like Operating System (Sander: base layer)

Tamás: (1) Interaction with SCD should be easy. (2) easy to integrate, easy to deploy plug-in

Daniel: Centralised functionality

Jakob: modular and loosely coupled

No use-case for multiple instances of OpenSCD.

OpenSCD integrable. It is a PWA already.

Use the 'window'! Discuss it later. [ACTION]

Sander mentions the work for the coming 4 weeks: Components to CORE etc.

Technical and functional: we need a product owner. Separation between plugins and core. Concept of add-ons, event bus. 

We don't have a clear maintainer. Merge POC ideas into one POC. [ACTION]. Pascal and Tamas. Compete!

[PASCAL] Develop a POC plugin. 

[Daniel] localisation does not support web components. Open issue … suited replacement? 

What is a wizard? Is it a popup? Purpose of wizard. 
A wizard is context aware.
Wizard is for editing or trigger SCL action; A wizard is limited 

Content of a wizard

A wizard should support multiple name-spaces

'Select IED' as component?