Main.HowToTuneVisualizationOptions History

Hide minor edits - Show changes to markup

January 28, 2008, at 11:19 AM by 129.20.167.23 -
Added lines 1-2:

How to tune visualization options

Added line 5:

Instructions

Changed lines 16-18 from:

4,5,6 This function allows to specify under which condition some element shoule be visualized as a distinct node each time it is added to the network (the corresponding URI is unique). This is usefule for instance when visualizing currency metabolites, that would be displayed as hubs is the correspondence URI to nodes was always 1 to 1. When 4 is selected, the are in 5' becomes active. Here it is possible to specify conditions that ientify elements that should always be visualized as unique nodes. This specification is in the form of a list of RDQL queries, separated by a string "OR CONDITION" (note that this is merely syntactic sugar, there is not an AND CONDITION, or anythig else than "CONDITION"). An example of specification is given below. When selected 6 the specifications shown are registered in the system (not yet in the filesystem, this happens when "save context" is selected, see How to work with analysis contexts). Note that this specification may be complex to input interectively, it should be almost always provided in the analysis context

to:

4,5,6 This function allows to specify under which condition some elements shoule be visualized as a distinct node each time they are added to the network (the corresponding URI is unique). This is useful for instance when visualizing currency metabolites, that would be displayed as hubs is the correspondence URI to nodes was always 1 to 1. When 4 is selected, the are in 5' becomes active. Here it is possible to specify conditions that ientify elements that should always be visualized as unique nodes. This specification is in the form of a list of RDQL queries, separated by a string "OR CONDITION" (note that this is merely syntactic sugar, there is not an AND CONDITION, or anythig else than "CONDITION"). An example of specification is given below. When selected 6 the specifications shown are registered in the system (not yet in the filesystem, this happens when "save context" is selected, see How to work with analysis contexts). Note that this specification may be complex to input interectively, it should be almost always provided in the analysis context

Added lines 45-46:

FAQ

June 11, 2006, at 06:32 PM by 157.99.164.30 -
Added line 17:
Added line 19:
Added line 22:
Added line 25:
Added line 27:
Added line 29:
Added line 32:
Added line 36:
Added line 38:
Added line 40:
June 11, 2006, at 06:31 PM by 157.99.164.30 -
Added lines 1-35:

RDFScape presents several options to tune visualization of information. Some are discussed are presented in Selecting namespaces, also relevant is How to use inference.

http://www.sgtp.net/AndreaSplendiani/ext/rdfscape/VisualizationOptions.jpg

0 Visualization options are under Options-> Browser. However, only the option described in 1 is specific to the browsing functionality. They other apply in al visualizations of ontologies in RDFScape.

1 Namespace selection in and. For each item in the menu, each statement in the relative context menu (see How to browse ontologies) present up to two namespaces. These can be selected namespace or not. If this options is not selected all statements that have at least one element in a selected namespace are shown. If this option is selected, only the statement with both namespaces selected are shown. Note that namespace of the node the menu is relevant is not relevant to this option. Blank nodes are always considered as not selected.

2 Treat datatype as attributes. If this option is selected, when adding a node, all its datatype properties are also added as attributes of the node (the datatype property becomess the attribute name, the corresponding object its value).

3 Use labels instead of URIs. Use rdfs:label as node or edges label instead of URIs.

4,5,6 This function allows to specify under which condition some element shoule be visualized as a distinct node each time it is added to the network (the corresponding URI is unique). This is usefule for instance when visualizing currency metabolites, that would be displayed as hubs is the correspondence URI to nodes was always 1 to 1. When 4 is selected, the are in 5' becomes active. Here it is possible to specify conditions that ientify elements that should always be visualized as unique nodes. This specification is in the form of a list of RDQL queries, separated by a string "OR CONDITION" (note that this is merely syntactic sugar, there is not an AND CONDITION, or anythig else than "CONDITION"). An example of specification is given below. When selected 6 the specifications shown are registered in the system (not yet in the filesystem, this happens when "save context" is selected, see How to work with analysis contexts). Note that this specification may be complex to input interectively, it should be almost always provided in the analysis context

SELECT ?z WHERE (?z <http://www.biopax.org/release/biopax-level1.owl#NAME> ?h) AND ?h eq "H2O"

OR CONDITION

SELECT ?z WHERE (?z <http://www.biopax.org/release/biopax-level1.owl#NAME> ?h) AND ?h eq "ATP"

OR CONDITION

SELECT ?z WHERE (?z <http://www.biopax.org/release/biopax-level1.owl#NAME> ?h) AND ?h eq "CO2"