Thanks for the feedback!
Can you roll out the ::types usage, I’m not following the shorthand at 11PM my time 
My 50p on inheritance and linking:
- I’d not include all textual content from A in A’. That would heavily duplicate data and not serve any purpose to me. So I guess that’s where I’m breaking with OOP, somewhat. Then again, if I want to gain access to the method (in programming parlance), I can essentially do
self.parent.METHOD_A
in Obsidian, this would be to me
CTRL+ALT+Left-Arrow to get to the previous note. And then I can just go to the heading I’m looking for.
- So in my Parent-Child Meeting Workflow, I am doing two things:
a) a child has an up-link to its parent, following self.parent basically
b) a parent, such as a Project, that has meeting-children, (which was my then-usecase), has a Dataview list, collecting all notes with type (ah there I’m already using types, here in this UML I’m intending to change this to class to stick with the OOP paradigm). So I’m asking for:
ALL notes WITH type = ‘meeting’ AND project = self.project
(not actual dataview, you can look it up in the code on my github if you’re keen.
With the new structure I’m designing around “Domains”, I haven’t yet decided, I’m thinking there should be as many useful links TO a Domain as necessary, so that I can follow all tracks pertaining to a domain if I need to think wide. So, say, a Project can link to a domain, and a Meeting too, also a tech note. Also an idea. Anything that is in an actual inheritance structure, like meetings, sources, etc. the links can be auto-generated.
Hope this makes sense. Please keep the feedback coming, my mind is going at 100 Miles thinking about this stuff 