Hi Michel,

Conforming Turtle implementations are required to read all valid forms of 
Turtle but are not required to maintain any manual formatting (or syntactic 
sugar) done in a text editor or by other Turtle writers. It’s a lot of 
not-very-usefule-coding to worry about trying to maintain that foreign 
formatting when RDF files have read from Turtle, been edited in Composer and 
are saved as Turtle. Composer users are not typically down in the weeds editing 
Turtle manually to try and make them prettier.

FWIW in your example, the way Composer wrote the file is actually more 
efficient if editing/diff’ing files as line deletes/comparisons are quicker to 
perform - i.e. “efficient” is in the eye of the beholder.

Cheers,
David

UK +44 7788 561308
US +1 336 283 0606




> On 12 Jul 2017, at 15:42, Bohms, H.M. (Michel) <[email protected]> wrote:
> 
> Hi Richard,
> I understand (that they are equivalent) but you would expect full support of 
> Turtle meaning support for all available ttl abbreviations types for the most 
> efficient representation.
> Otherwise you could also forget all other ttl abbreviations types and be back 
> at sets of triples only… 😊.
>  
> Hope you agree….Greetings Michel
>  
>  
>  
> Dr. ir. H.M. (Michel) Böhms
> Senior Data Scientist
> 
> T +31888663107
> M +31630381220
> E [email protected] <mailto:[email protected]>    
> Location 
> <https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=!3m1!4b1!4m5!3m4!1s0x47c5b58c52869997:0x56681566be3b8c88!8m2!3d52.000788!4d4.376707>
> 
>  
>  <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.
>  
>  
>  
>  
> From: [email protected] 
> <mailto:[email protected]> 
> [mailto:[email protected] 
> <mailto:[email protected]>] On Behalf Of Richard Cyganiak
> Sent: woensdag 12 juli 2017 16:33
> To: [email protected] <mailto:[email protected]>
> Subject: Re: [topbraid-users] turtle support
>  
> Michel,
>  
> On 12 Jul 2017, at 14:44, Bohms, H.M. (Michel) <[email protected] 
> <mailto:[email protected]>> wrote:
>  
> somple:Deck_1
>   rdf:type somple:Deck ;
>   cmo:hasDirectPart somple:Slab_1, somple:Slab_2, somple:Slab_3 ;
> .
>  
> Seems always rewritten after save by tbc into:
>  
> somple:Deck_1
>   rdf:type somple:Deck ;
>   cmo:hasDirectPart somple:Slab_1 ;
>   cmo:hasDirectPart somple:Slab_2 ;
>   cmo:hasDirectPart somple:Slab_3 ;
> .
>  
> Is there a special reason, or is the turtle-abbreviation (“,”) type just not 
> supported?
>  
> The two snippets are equivalent. They encode the same RDF triples. The 
> difference is simply that one uses more “syntactic sugar” than the other.
>  
> When a Turtle file is opened in Composer and saved again, the file will 
> contain the same data, but with different “cosmetics”. Composer generally 
> doesn’t provide user control over these cosmetics like whitespace handling, 
> order, use of abbreviations, etc.
>  
> Best,
> Richard
>  
>  
> 
> 
>  
> Thx Michel
>  
>  
>  
>  
> Dr. ir. H.M. (Michel) Böhms
> Senior Data Scientist
> 
> 
> T +31888663107
> M +31630381220
> E [email protected] <mailto:[email protected]>    
> Location 
> <https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=!3m1!4b1!4m5!3m4!1s0x47c5b58c52869997:0x56681566be3b8c88!8m2!3d52.000788!4d4.376707>
> 
>  
> <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.
>  
>  
>  
>  
>  
> -- 
> 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]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
>  
> -- 
> 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]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> -- 
> 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]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to