add typescript classes created with script for review

[tgra]

Branch created with Typescript classes created from SHACL shapes in https://github.com/solid/shapes using https://github.com/theodi/shacl-shape-converter-typescript

[langsamu]

The string used as predicate looks like a blank node label. I'm sure this is unintentional. It would not work.

It probably highlights some fundamental parser/generator problem in the converter.

[tgra]

unresolved - the SHACL shape property from SolidOS uses [ sh:path [ sh:inversePath flow:message ]

[ sh:path [ sh:inversePath flow:message ] ;
          sh:minCount 1 ; 
          rdfs:label "Related Chat" ;
          rdfs:comment "The chat channel or conversation to which this message belongs." ;
          sh:codeIdentifier "relatedChatChannel";
        ] 

[tgra]

thanks for all your feedback @langsamu :-)

[langsamu]

the SHACL shape property from SolidOS uses [ sh:path [ sh:inversePath flow:message ]

I highly recommend that we don't try to support this pattern in the converter.

I can imagine some interpretations that would make sense in the context of generating classes/properties from these shapes.
But I still think that restricting these shapes to using only 'simple' sh:paths with IRI objects is the correct current approach.

[tgra]

https://github.com/solid/object/blob/main/src/solid/Container.ts

import { TermWrapper } from "rdfjs-wrapper"
import { Resource } from "./Resource.js"
import { LDP } from "../vocabulary/mod.js"

export class Container extends Resource {
    public get contains(): Set<Resource> {
        return this.objects(LDP.contains, TermWrapper.as(Resource), TermWrapper.as(Resource))
    }
}

compare with
https://github.com/solid/object/blob/feature/add-auto-objects/src/solid/Container.ts

import { Resource } from './Resource.js';
import { TermWrapper, ObjectMapping } from "rdfjs-wrapper";

export class Container extends TermWrapper {

  get contains(): Set<Resource> {
    return this.objects("http://www.w3.org/ns/ldp#contains", ObjectMapping.as(Resource), ObjectMapping.as(Resource));
  }
}

[tgra]

Hi @langsamu @matthieubosquet - there is a of blocker for the solid/shapes and shapes transform work, that @jeswr would like to have resolved today.

Wonder if you're able to take a look and advise on this please:

With the current version of Container.ts, why is Container extending Resource rather than TermWrapper?

https://github.com/solid/object/blob/main/src/solid/Container.ts

import { TermWrapper } from "rdfjs-wrapper"
import { Resource } from "./Resource.js"
import { LDP } from "../vocabulary/mod.js"

export class Container extends Resource {
    public get contains(): Set<Resource> {
        return this.objects(LDP.contains, TermWrapper.as(Resource), TermWrapper.as(Resource))
    }
}

[langsamu]

RE #13 (comment)

With the current version of Container.ts, why is Container extending Resource rather than TermWrapper?

Because a Container is a Resource (see LDP via Solid) and because inheritance is a fundamental tenet of object-oriented programming. As such it is a crucial feature of RDF/JS Wrapper library.

In my opinion, the SHACL translator should support this feature.

However there is nothing in my mind that requires modelling any particular mapping class as extending any other.