[TBC] human readable rdfs:label

[edoras]

Hello,

I'm on TopBraid Standard Edition, and I'm interesting by the function
"Toggle between qnames and human-readable rdfs:labels". I have
differents users who speak english, or spanish or german (and in my
ontology, I have rdfs;labels in these three languages).

So, I would like to know if it is possible to customize this button to
specify which type of rdfs:labels I want to have in my tree of
classes, like with Protégé.

Thanks in advance,

Xavier

[Scott Henninger]

Xavier; The way to create multilingual labels in RDF is to use
language tags. For example, if you want to define a resource with
labels in English, German, and Spanish, enter the label with the
{@lang} syntax in the rdfs:label text box. So a label for the number
1 would have three entries,
one{@en}
uno{@es}
eins{@de}

In RDF, this would look like
{ :one rdfs:label "one"@en, "uno"@es, "eins"@de .}

Then you can set the UI agent to view the data using that tag. In
Composer, choose Preferences > TopBraid Composer, and enter the
"Preferred language(s) of rdfs:label". Note 1) that you can define
the order of which language should appear, and 2) that this setting
applies for a subproperties of rdfs:label.

For Ensemble, it is the same concept. Set the preferred language in
the browser and Ensemble will choose the compatible language label to
display.

-- Scott

[edoras]

Nice!!! Thank you very much!!!

I have an other question. On an other ontology, I don't use
"rdfs:label" but "skos:prefLabel" and "skos:altPrefLabel". With
Protégé, we can choose any type of annotation as human-readable in the
tree of class (e.g. prefLabel). Is it possible to do the same thing
with TBC SE ?

Thanks in advance,

Xavier

[Scott Henninger]

Xavier; The label algorithm for TopBraid Live and TopBraid Composer
computes the labels for all subproperties of rdfs:labels, with more
specific subproperties having precedence for display. Since
skos:prefLabel and skos:altLabel are both subproperties of rdfs:label,
these will automatically be chosen over rdfs:label.

The full algorithm for computing labels for Ensemble (browser-based UI
for TopBraid Live) and Composer, including precedence and label
conflict resolution, can be found in Section 1.6 of the TopBraid
Ensemble Application Development Guide. See the More Information
sidebar of http://www.topquadrant.com/products/TB_Ensemble.html.

-- Scott

[bradleys]

Scott,

As a follow on, I am importing foreign language terms into skos:label for Skos:Concept population via TB Import Tab deliminated spreadsheet.

A german term like 

Technischer Überwachungsverein  Causes TB to eliminate the Ü in the instance name and replace it with ? icon in the label. I have ten's of thousands of terms to import so I would like to figure out a mechanism to "turn on" multilingual character recognition.  At this point, I do not need to worry about designating the term as belonging to one language group or another Bradley Shoebottom

[Holger Knublauch]

Hi Bradley,

you may need to specify the file encoding manually. The following works for me:

1) Create an empty .txt file in TBC
2) Right click on the file and on Properties change its encoding to UTF-8
3) Paste the content into that file and save
4) Open the import wizard
5) In the encoding section, enter "UTF-8"

We will look into streamlining this process.

HTH
Holger

--
-- 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 Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
topbrai...@googlegroups.com
To unsubscribe from this group, send email to
topbraid-user...@googlegroups.com
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 topbraid-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[ceyockey]

With respect to assigning the preferred language, the default for my installation of Maestro 4.1 was "en en-US", but the language tag I'd brought in from an external source was "EN".  I had to revise from "en" to "EN" to get the proper rendering.  Thanks very much for the instruction provided here ... I'm just providing a qualification that case seems to matter in the interpretation of the parameter value.  Would be useful to make this case-insensitive. (unless there are negative consequences of that) --Courtland

[ceyockey]

It appears that the presence of an English language tag is (in our 4.0 installation) preventing EVN from showing labels in the Concept Hierarchy (tried but could not attach a screenshot).  Is there a way to adjust EVN settings so that "EN" could be recognized as default and allow labels to appear in the concept hierarchy ... or perhaps this is an enhancement emerging in 4.1 or 4.2?  Thanks. --Courtland

 

 

 

[Bob Ducharme]

Courtland,

Because EVN is built around SKOS, it looks for skos:prefLabel values to display on the concept hierarchy. Do your concepts have rdfs:label values instead of skos:prefLabel values? 

Bob

On Mon, Apr 1, 2013 at 5:10 PM, ceyockey <courtlan...@astrazeneca.com> wrote:

It appears that the presence of an English language tag is (in our 4.0 installation) preventing EVN from showing labels in the Concept Hierarchy (tried but could not attach a screenshot).  Is there a way to adjust EVN settings so that "EN" could be recognized as default and allow labels to appear in the concept hierarchy ... or perhaps this is an enhancement emerging in 4.1 or 4.2?  Thanks. --Courtland

 

 

 

--

[Holger Knublauch]

Yes the algorithm is indeed case-sensitive, but I believe this is the desired behavior as it is generally not a good idea to have multiple ways of stating the same thing.

If you have data that uses "EN" then you may want to massage the data before it gets uploaded into EVN, e.g. through a global search and replace of that string in a text editor. I have not come across examples that use uppercase language tags, and I wonder how frequently this happens and whether our importer/data cleansing algorithm should take care of such cases.

EVN uses the language from the http request, i.e. if you access your model from a browser where "EN" is the default language then it should work. You can change the default language in Firefox as shown in the screenshot:



And BTW EVN is using skos:prefLabel first, but if no prefLabel exists then it will fall back to rdfs:label.

HTH
Holger

On 4/2/2013 7:10, ceyockey wrote:

It appears that the presence of an English language tag is (in our 4.0 installation) preventing EVN from showing labels in the Concept Hierarchy (tried but could not attach a screenshot).  Is there a way to adjust EVN settings so that "EN" could be recognized as default and allow labels to appear in the concept hierarchy ... or perhaps this is an enhancement emerging in 4.1 or 4.2?  Thanks. --Courtland