Compact shapes classes DiagramKind

[amivanoff]

• No separate top-level PropertyShape nodes, only NodeShape nodes are top-level
• All simple-type PropertyShapes (string, int,.. all except IRI) are like UML class properties (in compartments in Class nodes)
• Arrow types
  • Class inheritance relation (class-to-superclass) -- arrow between NodeShapes based on relation between their targetClass classes
  • Class reference relation (classA-to-classB-by-propertyC) -- arrow between shapes if there is a PropertyShape in class A with sh:nodeKind = sh:IRI and sh:class = iri of class B. Arrow label = propertyC IRI

[Mvwivs]

Actually change from #13

now user is not forced to pass parentId explicitly during node view implementation: parentId is passed to children with useContext (context uses nearest provided value and thus nearest parent)

doesn't allow to create separate [IRI] PropertyShape nodes from some "current" node (parent id is passed implicitly with context, so created shapes always become children of the "current" one). Reverting back to previous approach with passing parent id explicitly as prop should resolve this problem.