Hello Osma,

we plan to release 4.4 in January. We have not yet decided whether we will make 
an official round of public betas but I am pretty sure we could send you a copy 
of TBC SE 4.4 ahead of the final release date. Sorry we have no plans for 
another 4.3 that would fix this particular issue.

If you haven't evaluated TBC-ME yet, you should be able to run TBC-ME 4.3 on 
those machines for 30 days until you can upgrade to 4.4 SE.

Regards,
Holger


On Dec 19, 2013, at 8:37 PM, Osma Suominen wrote:

> On 18/12/13 00:12, Holger Knublauch wrote:
>> This could be a bug in the sorted turtle writer (although I could not
>> reproduce this locally). All editions of 4.4 will use a different sorted
>> turtle writer (previously known as C14N) by default. Previous versions
>> of Standard Edition do not have this feature.
> 
> Hi Holger!
> 
> Thanks for your response.
> 
> I found out some more details. The problem happens only with literals which 
> have the same content but different language tag, e.g. "abc"@en and "abc"@de. 
> The order of these appears to change randomly on every save.
> 
> Attached is a fairly minimal test file with one rdfs:Class having multiple 
> rdfs:labels with same content but different language tags. I created it using 
> TBC SE 4.3.1, saved as Sorted Turtle, did a minor edit which I immediately 
> reverted (just to enable the Save button), and saved again. The rdfs:label 
> values are now in different order:
> 
> --- sorted-turtle-2-test.ttl  2013-12-19 12:34:27.304913732 +0200
> +++ sorted-turtle-test.ttl    2013-12-19 12:34:24.364851583 +0200
> @@ -12,5 +12,5 @@
> 
> :Class_1
>       rdf:type rdfs:Class ;
> -      rdfs:label "TestClass"@fi , "TestClass"@sv , "TestClass"@de , 
> "TestClass"@en ;
> +      rdfs:label "TestClass"@en , "TestClass"@de , "TestClass"@sv , 
> "TestClass"@fi ;
>       rdfs:subClassOf owl:Class .
> 
> 
> What is the timetable of 4.4? Is it possible to use the new C14N writer with 
> 4.3.1? Or would it be possible to fix just this one issue in 4.3.1? This is a 
> near-show-stopper for us, because it limits development to just one person at 
> a time, as SVN merges are in practice impossible to do. Having just purchased 
> 6 licenses this is a bit inconvenient...
> 
> Best regards,
> Osma Suominen
> 
> -- 
> Osma Suominen
> D.Sc. (Tech), Information Systems Specialist
> National Library of Finland
> P.O. Box 26 (Teollisuuskatu 23)
> 00014 HELSINGIN YLIOPISTO
> Tel. +358 50 3199529
> [email protected]
> http://www.nationallibrary.fi
> 
> -- 
> -- You received this message because you are subscribed to the Google
> Group "TopBraid Suite Users", the topics of which include Enterprise 
> Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, 
> SPARQLMotion, SPARQL Web Pages and SPIN.
> To post to this group, send email to
> [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/topbraid-users?hl=en
> --- 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/groups/opt_out.
> <sorted-turtle-test.ttl><sorted-turtle-2-test.ttl>

-- 
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary 
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, 
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--- 
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/groups/opt_out.

Reply via email to