RDF 1.1 made "strings" have a datatype of xsd:string.
Writing "abc" or "abc"^^xsd:string is the same RDF term - a literal with 
lexical form "abc" and datatype xsd:string.
Writing without ^^xsd:string is the preferred way but it makes no 
difference to RDF meaning.
Same for 2.40 - it is just special syntax for "2.40"^^xsd:decimal.

The Turtle writer outputs short forms from the internal java objects. The 
Turtle parser does the work of turning these short forms into the internal 
java objects. No other code sees the short forms.

There are decimals that can not be abbreviated: "1"^^xsd:decimal for 
example. 1 is the short form for an xsd:integer.  So if the decimal has no 
decimal point, it can't be abbreviated.

xsd:doubles can be abbreviated if they have an exponent in the lexical 
form. 1.5e0 but "1.5"^^xsd:double.

N-Triples does not have such abbreviations.

Your data also has:
 ex:clearOpeningHeight "2.40 m"^^cdt:length ;
(the only occurrence of "^^" I found)

That is not an xsd:decimal and there is no short form for cdt:length.

    Andy

On Tuesday, 4 June 2019 22:49:53 UTC+1, Bohms, H.M. (Michel) wrote:
>
> In the ocde I have:
>
>  
>
> ex:ClearOpeningHeight_1
>
>   rdf:type bs:Property ;
>
>   bs:hasPropertyType ex:ClearOpeningHeight ;
>
>   bs:hasUnit "m" ;
>
>   bs:hasValue 2.40 ;
>
> .
>
>  
>
> I expected:
>
> ex:ClearOpeningHeight_1
>
>   rdf:type bs:Property ;
>
>   bs:hasPropertyType ex:ClearOpeningHeight ;
>
>   bs:hasUnit "m"^^xsd:string ;
>
>   bs:hasValue “2.40”^^xsd:decimal ;
>
> .
>
>  
>
> Guess wrong expectation?
>
>  
>
> Thx again
>
>  
>
>  
>
>  
>
>  
>
>
>
>
>
>
>
>
>
>

-- 
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/db099c88-410c-4d3d-b079-7ed144267bf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to