-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Niels Hoffmann
committed
Jan 20, 2025
1 parent
4483df3
commit 34f0642
Showing
3 changed files
with
149 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,118 @@ | ||
# Main findings | ||
|
||
## Lab questions | ||
|
||
-- guardrails/principes | ||
-- theoretische experimenteer omgeving. moeten kunnen doorzien dat | ||
|
||
interoperabiliteit is een requirement | ||
open standaarden is een uitgangspunt | ||
|
||
'security by design' | ||
|
||
--- | ||
Use Open International Standards and avoid lock-ins | ||
People & Organization understand => interface voor mens en machine. | ||
Datacentric, not software centric – FAIR | ||
Ethics central | ||
The web is the operating system | ||
Comprehensive architecture, driven by and from use-case | ||
Components (Products) are loosely bound and talk to each other over API’s | ||
Work with the best that is available today (affordable, reliable, scalable & resilient) | ||
Components are containerable, developer friendly | ||
Avoidpre-optimalisation | ||
--- | ||
|
||
|
||
## Studio questions | ||
|
||
-- capabilities | ||
|
||
we hebben deze specifieke open standaarden nodig om in de use case operabiliteit te realiseren | ||
testbed/mvp (nog bewust beperkt) | ||
|
||
'we weten dat security belangrijk is, maar nemen nu nog even 'shortcuts' ' | ||
|
||
--- | ||
tijdreizen | ||
|
||
integreren | ||
|
||
zoeken/vinden | ||
|
||
rekenen | ||
|
||
ontsluiten | ||
|
||
vertrouwen | ||
|
||
identificeren | ||
|
||
Beleven | ||
|
||
Simuleren | ||
|
||
Orkestratie | ||
|
||
Voorsteppen | ||
|
||
Analyseren | ||
|
||
reproduceren | ||
|
||
Meten/Aansturen | ||
|
||
bewerken | ||
|
||
---- | ||
experimenteer omgeving opzetten, met juiste 'hardware'/infrastructuur | ||
|
||
|
||
--- | ||
|
||
## Arena questions | ||
|
||
-- realization (service, components) | ||
|
||
we beproeven de standaarden/ interoperabiliteit in testbeds (open uitnodiging aan partijen om mee te experimenteren) | ||
|
||
'we willen security oplossingen testen op bruikbaarheid, robuustheid e.d.' | ||
|
||
--- | ||
kies de juiste visualisatie tools | ||
|
||
maak een keuze uit etl tools | ||
|
||
maak een keuze uit catalogi oplossingen | ||
|
||
beproeven 'interoperabiliteit' (wat werkt samen en wat bijt elkaar) | ||
|
||
Hoe stromen nieuwe functionaliteiten in, in een bestaande omgeving (installed base) | ||
|
||
internal technische marketing, lessons learned delen | ||
|
||
organisatie technisch klaar maken om data te delen (technnische en organisatie randvoorwaarden regelen) | ||
|
||
file share vs block storage | ||
|
||
--- | ||
|
||
## Agora questions | ||
|
||
-- dpeloyment/implementaion | ||
|
||
'hoe borgen we dat de security componenten afdoende werken' / 'we zorgen ervoor dat security goed werkt' | ||
IDSA/Dataspace connectoren. | ||
|
||
--- | ||
|
||
SLA's | ||
|
||
gebruikers opleiden | ||
|
||
audit en control ingeregeld hebben | ||
|
||
it systemen moet je governance ondersteunen, (je governance moet niet een 'handmatig' proces zijn) | ||
CI/CD ingericht 'business as usual' | ||
|
||
--- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,33 @@ | ||
# Main findings | ||
|
||
## Lab questions | ||
|
||
-- guardrails/principes | ||
-- theoretische experimenteer omgeving. moeten kunnen doorzien dat | ||
|
||
|
||
|
||
|
||
## Studio questions | ||
|
||
-- capabilities | ||
|
||
we hebben deze specifieke open standaarden nodig om in de use case operabiliteit te realiseren | ||
testbed/mvp (nog bewust beperkt) | ||
|
||
|
||
|
||
|
||
## Arena questions | ||
|
||
-- realization (service, components) | ||
|
||
we beproeven de standaarden/ interoperabiliteit in testbeds (open uitnodiging aan partijen om mee te experimenteren) | ||
|
||
|
||
## Agora questions | ||
|
||
-- dpeloyment/implementaion | ||
|
||
|
||
--- |