Protege4NamingAndRendering - Revision history

TaniaTudorache: /* Translating ontologies */

2016-05-24T04:03:05Z

‎Translating ontologies

TaniaTudorache at 04:01, May 24, 2016

2016-05-24T04:01:07Z

Tredmond: /* Annotations... */

2011-05-11T20:55:44Z

‎Annotations...

Tredmond: /* Annotations... */

2011-05-11T20:53:07Z

‎Annotations...

Tredmond: /* Rendering preferences */

2011-05-11T20:51:04Z

‎Rendering preferences

Tredmond: /* Prefixes... */

2011-05-11T20:46:42Z

‎Prefixes...

Absh1us at 20:20, August 18, 2010

2010-08-18T20:20:41Z

Nickdrummond at 12:23, November 27, 2008

2008-11-27T12:23:31Z

Nickdrummond: Added renderer preferences

2008-11-27T12:08:55Z

Added renderer preferences

Nickdrummond: /* New entity creation preferences */

2008-11-13T17:28:54Z

‎New entity creation preferences

@@ Line 171: / Line 171: @@
 Using a combination of the annotation renderer and label generation (both described above) it is possible to come up with and view an ontology in a given language.
-If you wish to provide multiple labels for internationalisation of your ontology, a quick way to do this is using the [http://code.google.com/p/co-ode-owl-plugins/wiki/MatrixViews matrix plugin].
+If you wish to provide multiple labels for internationalization of your ontology, a quick way to do this is using the [https://github.com/co-ode-owl-plugins/matrix matrix plugin].
 [http://code.google.com/p/co-ode-owl-plugins/wiki/MatrixViews#Translation Instructions for setting up the translation].

@@ Line 1: / Line 1: @@
 <div class="orangeBox">
-<span class="orangeBoxTitle">Naming and rendering of entities in Protege 4.x</span>
+<span class="orangeBoxTitle">Naming and rendering of entities in Protege</span>
-This page describes the various options for naming entities in an ontology.
+This page describes the various options for naming entities in an ontology for Protege 4, 5 and newer.
 </div>
-Back to [[Protege4UserDocs]]
+'''Back to [[Protege4UserDocs|Protege User Documentation]]'''
@@ Line 22: / Line 22: @@
 * '''base URI''' the (leftermost) part of the URI that will likely be common across multiple entities (eg '''http://www.co-ode.org/ontologies/pizza/pizza.owl#''').
-* '''URI fragment''' the part of a URI after the delimiter '''#''' (eg '''Pizza'''). In Protege 4.x, we sometimes broaden this to include the last path element if no fragment is available - particularly for rendering.
+* '''URI fragment''' the part of a URI after the delimiter '''#''' (eg '''Pizza'''). In Protege, we sometimes broaden this to include the last path element if no fragment is available - particularly for rendering.
 It is common for a base URI to be used across many entities with each having its own unique fragment.
-== Rendering of entities in Protege 4.x ==
+== Rendering of entities in Protege ==
-Because URIs will often be fairly long strings, Protege 4.x uses a '''renderer''' to show a shortened form of the name.
+Because URIs will often be fairly long strings, Protege uses a '''renderer''' to show a shortened form of the name.
 The renderer can be changed in the preferences (see below) and can show the fragment or ending part of the URI, or can show a name provided by an annotation on the entity.
@@ Line 71: / Line 71: @@
 Prefixes can be configured using the ''Ontology Prefixes'' view.  This view will appear in the default state of the Active Ontology tab and can be added to any tab by clicking Window->Views->Ontology Views->Ontology Prefixes.
-The table that is brought up allows the user to add new prefixes by hand or get P4 to generate them from the loaded ontologies.
+The table that is brought up allows the user to add new prefixes by hand or get Protege to generate them from the loaded ontologies.
 Several prefixes are available as default.
@@ Line 85: / Line 85: @@
 You can specify a list of which annotations are searched for a rendering in order of preference.
-eg the setup on the right will first try to find a '''label''' annotation in english, followed by one with no language set. If it fails, then it will look for any '''prefLabel''' it can find.
+eg the setup on the right will first try to find a '''label''' annotation in English, followed by one with no language set. If it fails, then it will look for any '''prefLabel''' it can find.
 If the annotations renderer fails to find an appropriate label then it will default to the fragment.
@@ Line 174: / Line 174: @@
 [http://code.google.com/p/co-ode-owl-plugins/wiki/MatrixViews#Translation Instructions for setting up the translation].

@@ Line 81: / Line 81: @@
 [[Image:Annotation-label-prefs.png|right|400px]]
-If you have set the renderer to be either of the annotations versions then the ''Configure'' button will allow you to set the annotation properties to be used.
+If you have set the renderer to be either of the annotations versions then the ''Configure'' button will allow you to set the annotation properties and languages to be used.
 You can specify a list of which annotations are searched for a rendering in order of preference.
-eg the setup on the right will first try to find a '''label''' annotation in english, followed by one with no language set, followed by any language. If it fails, then it will look for any '''prefLabel''' it can find.
+eg the setup on the right will first try to find a '''label''' annotation in english, followed by one with no language set. If it fails, then it will look for any '''prefLabel''' it can find.
 If the annotations renderer fails to find an appropriate label then it will default to the fragment.
 <br style="clear: both;" />

@@ Line 81: / Line 81: @@
 [[Image:Annotation-label-prefs.png|right|400px]]
-If you have set the renderer to be either of the annotations versions then this option will be available.
+If you have set the renderer to be either of the annotations versions then the ''Configure'' button will allow you to set the annotation properties to be used.
 You can specify a list of which annotations are searched for a rendering in order of preference.

← Older revision		Revision as of 20:51, May 11, 2011
Line 49:		Line 49:
	* '''annotation values with prefixes''' uses a combination of the [[#Annotations...\|annotation]] value and the qname [[#Prefixes...\|prefixes]]		* '''annotation values with prefixes''' uses a combination of the [[#Annotations...\|annotation]] value and the qname [[#Prefixes...\|prefixes]]

−	When using the 3rd and 4th option you probably wish to also set the [[#New_entity_creation_preferences\|New entities preferences]] to create labels when a new entity is created.~~[http://www.texas-liability-insurance.com/ Liability Insurance Texas]~~	+	When using the 3rd and 4th option you probably wish to also set the [[#New_entity_creation_preferences\|New entities preferences]] to create labels when a new entity is created.

@@ Line 69: / Line 69: @@
    pizza:CheeseTopping
-The prefixes... option is available for both the '''qname''' and the '''annotation values with prefixes'''  renderers.
+Prefixes can be configured using the ''Ontology Prefixes'' view.  This view will appear in the default state of the Active Ontology tab and can be added to any tab by clicking Window->Views->Ontology Views->Ontology Prefixes.
 The table that is brought up allows the user to add new prefixes by hand or get P4 to generate them from the loaded ontologies.

← Older revision		Revision as of 20:20, August 18, 2010
Line 49:		Line 49:
	* '''annotation values with prefixes''' uses a combination of the [[#Annotations...\|annotation]] value and the qname [[#Prefixes...\|prefixes]]		* '''annotation values with prefixes''' uses a combination of the [[#Annotations...\|annotation]] value and the qname [[#Prefixes...\|prefixes]]

−	When using the 3rd and 4th option you probably wish to also set the [[#New_entity_creation_preferences\|New entities preferences]] to create labels when a new entity is created.	+	When using the 3rd and 4th option you probably wish to also set the [[#New_entity_creation_preferences\|New entities preferences]] to create labels when a new entity is created.[http://www.texas-liability-insurance.com/ Liability Insurance Texas]

@@ Line 29: / Line 29: @@
 It is common for a base URI to be used across many entities with each having its own unique fragment.
-== Naming of entities in Protege 4.x ==
+== Rendering of entities in Protege 4.x ==
-Because URIs will often be fairly long strings, Protege 4.x uses a renderer to show a shortened form of the name.
+Because URIs will often be fairly long strings, Protege 4.x uses a '''renderer''' to show a shortened form of the name.
-The renderer can be changed in the preferences and can show the fragment or ending part of the URI, or can show a name provided by an annotation on the entity.
+The renderer can be changed in the preferences (see below) and can show the fragment or ending part of the URI, or can show a name provided by an annotation on the entity.
 So '''Pizza''' is actually just a rendering of the URI http://www.co-ode.org/ontologies/pizza/pizza.owl#Pizza.
@@ Line 39: / Line 39: @@
 The full URI can always be viewed by hovering over an entity in its tree (the tooltip shows the full name).<br>
 Also, the <span style="color:#B87A3D; font-weight:bold;">Refactor | Rename entity</span> menu item always works with the URI - in fact you can see the full URI by just clicking on the checkbox in the rename dialog.
 Until build 65, new entities were created with respect to the renderer settings, ie:
@@ Line 53: / Line 109: @@
 So the automatic naming has been revisited to make this more flexible.
-== New entity creation preferences ==
+=== New entity creation preferences ===
 [[Image:New-entities-preferences.png|right|400px]]
@@ Line 65: / Line 121: @@
+==== Entity URI ====
 New entities will be given a URI starting with the base:
 * '''Active ontology (default)''' the URI of the currently selected active ontology will always be used as the base URI.
@@ Line 78: / Line 133: @@
-=== Entity label ===
+==== Entity label ====
 Selecting one or both of the '''create label''' options generate an annotation on the new entities containing the supplied name (or ID).
@@ Line 87: / Line 142: @@
-=== Auto ID ===
+==== Auto ID ====
 Create a numerical identifier for new entities.