Re: [topbraid-users] best practise name space in multiple languages?

To summarize, without knowing all the details of your plans and requirements, we recommend something along the following lines: Do not have separate graph URIs for serializations. It is the same graph, irrespective of the serialization. Your server should generate/provide different

Re: [topbraid-users] best practise name space in multiple languages?

> On 6 Apr 2021, at 15:22, Irene Polikoff wrote: > > There is definitely no problems for a resource to be both a class and a > shape. In fact, this is very convenient and used by TopBraid by default. In > SHACL specification it is discussed as implicit targeting. > > As far as a resource

Re: [topbraid-users] best practise name space in multiple languages?

There is definitely no problems for a resource to be both a class and a shape. In fact, this is very convenient and used by TopBraid by default. In SHACL specification it is discussed as implicit targeting. As far as a resource being both a skos:Concept and a class and/or, potentially even a

RE: [topbraid-users] best practise name space in multiple languages?

In bold om what Holger said and adding a question: On 6 Apr 2021, at 12:22, Holger Knublauch mailto:hol...@topquadrant.com>> wrote: Hi Michel, First we should make sure that the users of your models understand the distinction between namespaces and graph URIs. You can of course use the

Re: [topbraid-users] best practise name space in multiple languages?

A few comments following on from what Holger said and adding a question: > On 6 Apr 2021, at 12:22, Holger Knublauch wrote: > > Hi Michel, > > First we should make sure that the users of your models understand the > distinction between namespaces and graph URIs. You can of course use the same

Re: [topbraid-users] best practise name space in multiple languages?

Hi Michel, First we should make sure that the users of your models understand the distinction between namespaces and graph URIs. You can of course use the same namespace (e.g., https://w3id.org/def/nen2660# ) in multiple graphs. What you are probably referring to

[topbraid-users] best practise name space in multiple languages?

In case I have the same specification on different modelling levels: * Skos * Rdfs * Rdfs+owl * Rdfs+shacl Is there some best practice for the name space? (compare same name space for different serializations but now for different languages used...). I now have ie: #

Re: [topbraid-users] Validating sh:xone

Thanks, I will report That library is a port of SHACL.js, and it also has the same issue, in case you'd want to support the original library too :) poniedziałek, 5 kwietnia 2021 o 01:13:58 UTC+2 Holger Knublauch napisał(a): > Hi Tom, > > you may want to contact the developers of that API