typeIndex shapes

[timea-solid]

For SHACL and ShEX

[woutermont]

Good start! Overal structure looks good to me. I've added some corrections and suggestions on the ShaCL/ShEx syntax.

[timea-solid]

@woutermont thank you so much for the feedback thus far!
Let me know about the open question above and then I will go in and fix the rest to streamline the file.
Afterward, I will check in the meeting if the constraints are enough and correct.

[megoth]

Very good ^_^ Added some notes that I think should be resolved

[woutermont]

EDIT: As discussed in the meeting, I've moved this to a separate issue #8

---

One general comment I have about TypeIndexes, and how they are used, is that we currently rely on the unspecified anti-LinkedData convention that Type Registrations will be served in the same file as the Type Index itself.

I.m.o. it would be better to specify this in a Linked Data manner, by adding an extra predicate to the Type Index shapes:

:TypeIndexShape a sh:NodeShape ;
    # ...
    sh:property [
        sh:path solid:hasTypeRegistration ;
        sh:nodeKind sh:IRI
    ] .

typeIndex:TypeIndex EXTRA a {
    # ...
    solid:hasTypeRegistration IRI .
}

This way, all Type Registrations are linked to from their Type Index.

[timbl]

Maybe have separate alternative paths for instance and instanceContainer and set the target class (range) of instanceContainer to be ldp:Container