Re: [topbraid-users] render issue in case of uuid code as name

Wed, 02 Jun 2021 15:52:19 -0700

Apologies, you are right. I even found a ticket in our Jira system from 2017 where we wanted to update this but it fell through the cracks. The problem is that the Sorted Turtle writer uses an outdated base library that we cloned from an earlier Jena version. We'll try to fix that for 7.1. 

Holger
On 2021-06-02 6:03 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote: 

Hi Holger,

Are you sure? latest Turtle says:

[168s]

        

|PN_LOCAL|

        

::=
(PN_CHARS_U <https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS_U>|| |'|:|' || |[|0-9|] || |PLX <https://www.w3.org/TR/turtle/#grammar-production-PLX>) ((PN_CHARS <https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS>|| |'|.|' || |'|:|' || |PLX <https://www.w3.org/TR/turtle/#grammar-production-PLX>)|*| (PN_CHARS <https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS> || |'|:|' || |PLX <https://www.w3.org/TR/turtle/#grammar-production-PLX>))? 

It was not allowed in the 2008 variant hence (see red):


      D.4 Changes from January 2008 Team Submission
      <http://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114/> to
      First Public Working Draft
      <http://www.w3.org/TR/2011/WD-turtle-20110809/>

  * Adopted three additional string syntaxes from SPARQL:
    STRING_LITERAL2
    <http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL2>,
    STRING_LITERAL_LONG1
    
<http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL_LONG1>,
    STRING_LITERAL_LONG2
    
<http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL_LONG2>
  * Adopted SPARQL's syntax for prefixed names (see editor's draft
    <http://www.w3.org/TR/sparql11-query/#rPrefixedName>):
      o '.'s in names in all positions of a local name apart from the
        first or last, e.g. |ex:first.name|.
      o digits in the first character of the PN_LOCAL
        <http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL> lexical
        token, e.g. |ex:7tm|.
  * adopted SPARQL's IRI resolution and prefix substitution text.
  * explicitly allowed re-use of the same prefix.
  * Added parsing rules <https://www.w3.org/TR/turtle/#sec-parsing>.

GR MICHEL

        

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 michel.bo...@tno.nl <mailto:michel.bo...@tno.nl>

        

Location <http://www.tno.nl/locations/DTS>

<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:*topbraid-users@googlegroups.com <topbraid-users@googlegroups.com> *Namens *Holger Knublauch 
*Verzonden:* woensdag 2 juni 2021 03:40
*Aan:* topbraid-users@googlegroups.com
*Onderwerp:* Re: [topbraid-users] render issue in case of uuid code as name
We use slightly different serialization algorithms across tools but local names cannot start with digits so writing the full URI is correct.
If you just export "Turtle" from EDG or save to Turtle from TBC you'll get test_uuid:675d0ae5-d8eb-49b7-867f-80ba8c0b09e9 while Sorted Turtle will produce <http://example.org/ontologies/test_uuid#675d0ae5-d8eb-49b7-867f-80ba8c0b09e9> <http://example.org/ontologies/test_uuid#675d0ae5-d8eb-49b7-867f-80ba8c0b09e9> which is more correct AFAIK. Both can be parsed though, so it shouldn't matter too much. 

Holger
On 2021-06-01 10:14 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote: 

    Dear tq

    I have asked earlier but I could not refind….

    I have:

    https://w3id.org/cbnl/skos/term#048B3010-0BD1-4A89-9F49-FE6D825DA799
    <https://w3id.org/cbnl/skos/term#048B3010-0BD1-4A89-9F49-FE6D825DA799>

      rdf:type skos:Concept ;

      dct:source "IMBOR2021beta"@NL-nl ;

    skos:broader nen2660-term:InformationObject ;

    skos:definition "Informatieobject voor het registreren en koppelen
    van documenten aan objecttypes."@NL-nl
    
<mailto:%22Informatieobject%20voor%20het%20registreren%20en%20koppelen%20van%20documenten%20aan%20objecttypes.%22@NL-nl>;

    skos:prefLabel "Document"@NL-nl ;

    .

    So name is UUID code.

    Despite prefixes are fine TBC does not use prefix in interface now.

    Think I reported earlier.

    (when I change uuid number into “Document” things render fine again)

    Gr michel

        

    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 michel.bo...@tno.nl <mailto:michel.bo...@tno.nl>

        

    Location <http://www.tno.nl/locations/DTS>

    <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.
-- 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 topbraid-users+unsubscr...@googlegroups.com
    <mailto:topbraid-users+unsubscr...@googlegroups.com>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/topbraid-users/2329b36a509f49ee83b4571bf7b18330%40tno.nl
    
<https://groups.google.com/d/msgid/topbraid-users/2329b36a509f49ee83b4571bf7b18330%40tno.nl?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 topbraid-users+unsubscr...@googlegroups.com <mailto:topbraid-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/ed7bed42-9beb-9459-761b-e2e662ab4122%40topquadrant.com <https://groups.google.com/d/msgid/topbraid-users/ed7bed42-9beb-9459-761b-e2e662ab4122%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 topbraid-users+unsubscr...@googlegroups.com <mailto:topbraid-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/3adda84e743e444a86ceb17518850eec%40tno.nl <https://groups.google.com/d/msgid/topbraid-users/3adda84e743e444a86ceb17518850eec%40tno.nl?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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/c2289e8b-d7cc-3980-3686-63289d0c05f1%40topquadrant.com.

Reply via email to