[Proposed Work Item]: Domain Driven Design and Solid

[elf-pavlik]

https://en.wikipedia.org/wiki/Domain-driven_design

Domain-driven design (DDD) is a software design approach that focuses on modeling software to match a domain according to input from that domain's experts.) DDD is against the idea of having a single unified model; instead it divides a large system into bounded contexts, each of which have their own model.

This work item will possibly only produce Primer/Note.

I see an unaddressed challenge of bridging the gap between generic data schemas and terminology and domain specific schemas and terminology. In some cases generic schema may work across domains but terminology will differ. In other cases generic data will need additional more domain specific data.

I would imagine this work being coordinated with ODI Use Cases program introduced by @Roberto-Breitman

Another challenge is related to representation. I believe most CG participants are tech oriented and we may lack domain experts. Collaborating with Practitioners, ODI, and other pathways to potential domain experts will be required for this work to advance. OS Tools group should be also involved.

Related efforts that should be informed by this work item

• https://github.com/solid/shapes
• https://github.com/solid/object

Possibly related

• Achieve interoperability through social consensus rather than technical complexity, such as inference or mappings solid/shapes#25
• Allow passing custom JSON-LD context mappings to @ldo/cli o-development/ldo#47
• https://soukai.js.org/guide/solid-protocol/solid-models.html#rdf-definitions