> On 14 Apr 2021, at 10:49, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > <[email protected]> wrote: > > Ok, thx, changed to: > > > > De gehanteerde prefixen & ‘name space URI’s’: <> > ¾ nen2660-vocab https://w3id.org/nen2660/vocab# > <https://w3id.org/nen2660/vocab> > ¾ nen2660 https://w3id.org/def/nen2660/def# > <https://w3id.org/def/nen2660/def> > Met ‘graaf URI’s’ (default voor vocab, 3 subgrafen voor def): > ¾ https://w3id.org/nen2660/vocab > <https://w3id.org/nen2660/vocab># (bestand: nen2660-skos.ttl) > ¾ https://w3id.org/nen2660-rdfs/def# > <https://w3id.org/nen2660-rdfs/def#> (bestand: nen2660-rdfs.ttl) > ¾ https://w3id.org/nen2660-owl/def# > <https://w3id.org/nen2660-owl/def#> (bestand: nen2660-owl.ttl) > ¾ https://w3id.org/nen2660-shacl/def# > <https://w3id.org/nen2660-shacl/def#> (bestand: nen2660-shacl.ttl) > IMO the Graph URI and the Namespace URI are best kept different so nobody gets confused. It is also the case that you may define constructs in any namespace in a graph and so there is really zero relation required between them.
So, I’d suggest this for your Graph URIs (no #): > Met ‘graaf URI’s’ (default voor vocab, 3 subgrafen voor def): > ¾ https://w3id.org/nen2660/vocab > <https://w3id.org/nen2660/vocab> (bestand: nen2660-skos.ttl) > ¾ https://w3id.org/nen2660-rdfs/def > <https://w3id.org/nen2660-rdfs/def> (bestand: nen2660-rdfs.ttl) > ¾ https://w3id.org/nen2660-owl/def > <https://w3id.org/nen2660-owl/def> (bestand: nen2660-owl.ttl) > ¾ https://w3id.org/nen2660-shacl/def > <https://w3id.org/nen2660-shacl/def> (bestand: nen2660-shacl.ttl) > As I explained earlier there are cases supporting versions of ontologies with the same classes defined - you may eventually need https://w3id.org/nen2660/v1/vocab <https://w3id.org/nen2660/v1/vocab> and https://w3id.org/nen2660/v2/vocab <https://w3id.org/nen2660/v2/vocab> to both contain https://w3id.org/nen2660/vocab/PhysicalObject <https://w3id.org/nen2660/vocab/PhysicalObject> concept. In the engineering world where apps are audited (e.g. Aircraft design and manufacture), there are situations where there is a hard requirement for very strictly managed change to all apps, so versions are needed in the ontologies Graph URIs. The ontology provider can offer both a versioned release with v1, v2, etc. in the Graph URI and an un-versioned release with no v1, etc. in the Graph URI that is always the latest-and-greatest. That way implementors can choose “always the latest” or “a specific version”. The main point is to separate the Graph URI from Namespace URI in your thinking, and maintain that separation in the artefacts themselves. Cheers, David > > > > Dr. ir. H.M. (Michel) Bohms > Scientist Specialist > Structural Reliability > T +31 (0)88 866 31 07 > M +31 (0)63 038 12 20 > E [email protected] <mailto:[email protected]> > Location <http://www.tno.nl/locations/DTS> > > > <image001.gif> <http://www.tno.nl/> > This message may contain information that is not intended for you. If you are > not the addressee or if this message was sent to you by mistake, you are > requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use it > and for damage of any kind resulting from the risks inherent to the > electronic transmission of messages. > > Van: [email protected] <mailto:[email protected]> > <[email protected] <mailto:[email protected]>> > Namens David Price > Verzonden: woensdag 14 april 2021 11:41 > Aan: [email protected] <mailto:[email protected]> > CC: Opgenoort, Rik <[email protected] <mailto:[email protected]>>; > Kronemeijer, Redmer <[email protected] > <mailto:[email protected]>>; Bart Bink <[email protected] > <mailto:[email protected]>> > Onderwerp: Re: [topbraid-users] best practise name space in multiple > languages? > > > > > On 14 Apr 2021, at 10:28, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > <[email protected] <mailto:[email protected]>> > wrote: > > I thought the / or # only came in with the porefix independent of the uri > itself….. > > No, the # or / is part of the Namespace URI. > > From the Turtle Primer: > > The full triples notation requires that URI references be written out > completely, in angle brackets, which, as the example above illustrates, can > result in very long lines on a page. For convenience, the Primer uses a > shorthand way of writing triples (the same shorthand is also used in other > RDF specifications). This shorthand substitutes aqualified name (or QName) > without angle brackets as an abbreviation for a full URI reference . A QName > contains a prefix that has been assigned to a namespace URI, followed by a > colon, and then a local name. The full URIref is formed from the QName by > appending the local name to the namespace URI assigned to the prefix. So, for > example, if the QName prefix foo is assigned to the namespace URI > http://example.org/somewhere/ <http://example.org/somewhere/>, then the QName > foo:bar is shorthand for the URIrefhttp://example.org/somewhere/bar > <http://example.org/somewhere/bar>. Primer examples will also use several > "well-known" QName prefixes (without explicitly specifying them each time), > defined as follows: > > prefix rdf:, namespace URI: http://www.w3.org/1999/02/22-rdf-syntax-ns# > <http://www.w3.org/1999/02/22-rdf-syntax-ns> > prefix rdfs:, namespace URI: http://www.w3.org/2000/01/rdf-schema# > <http://www.w3.org/2000/01/rdf-schema> > prefix dc:, namespace URI: http://purl.org/dc/elements/1.1/ > <http://purl.org/dc/elements/1.1/> > prefix owl:, namespace URI: http://www.w3.org/2002/07/owl# > <http://www.w3.org/2002/07/owl> > prefix ex:, namespace URI: http://www.example.org/ <http://www.example.org/> > (or http://www.example.com/ <http://www.example.com/>) > prefix xsd:, namespace URI: http://www.w3.org/2001/XMLSchema# > <http://www.w3.org/2001/XMLSchema> > > Cheers, > David > > > UK +44 (0) 7788 561308 > US +1 (336) 283-0808 > > -- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/71D1477B-766D-4035-8730-90B7E5FF27CB%40topquadrant.com > > <https://groups.google.com/d/msgid/topbraid-users/71D1477B-766D-4035-8730-90B7E5FF27CB%40topquadrant.com?utm_medium=email&utm_source=footer>. > > -- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/be42ca7c28bb4be3aeb984164725ebcd%40tno.nl > > <https://groups.google.com/d/msgid/topbraid-users/be42ca7c28bb4be3aeb984164725ebcd%40tno.nl?utm_medium=email&utm_source=footer>. UK +44 (0) 7788 561308 US +1 (336) 283-0808 -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/63EB21FE-8C4B-4834-82DF-0098F8A73888%40topquadrant.com.
