Query topic map - Revision history

Akivela: /* See also */

2009-10-30T10:26:44Z

‎See also

Olli: /* Examples */

2009-08-24T08:14:34Z

‎Examples

Akivela at 12:11, 26 July 2008

2008-07-26T12:11:38Z

Akivela at 13:38, 30 May 2008

2008-05-30T13:38:12Z

Olli at 07:54, 29 May 2008

2008-05-29T07:54:46Z

Olli: /* Queries in a query topic map */

2008-05-27T07:32:51Z

‎Queries in a query topic map

Olli: /* Examples */

2008-05-27T07:28:39Z

‎Examples

Olli: /* Examples */

2008-05-27T07:11:38Z

‎Examples

Olli at 07:05, 27 May 2008

2008-05-27T07:05:03Z

Olli at 12:55, 23 May 2008

2008-05-23T12:55:13Z

@@ Line 31: / Line 31: @@
 * [[Database topic map]]
 * [[Linked topic map]]
-* [[Remote topic map]]
+<!-- * [[Remote topic map]] -->

@@ Line 23: / Line 23: @@
 == Examples ==
-This section contains some example queries you can use in a query topic map.
+[[Query language]] documentation contains many examples which can be used directly with query topic maps.
-−
-=== Transitional closure ===
-−
- importPackage(org.wandora.query);
- importPackage(org.wandora.topicmap);
- new TransitiveDirective(XTMPSI.SUPERCLASS_SUBCLASS,
-                         XTMPSI.SUPERCLASS, XTMPSI.SUBCLASS);
-−
-Set http://www.topicmaps.org/xtm/1.0/core.xtm#superclass-subclass as association type.
-−
-This query will form a transitional closure of superclass-subclass associations. What this means is that if the context topic map has associations saying that A is a superclass of B and B is a superclass of C then this query will produce an association A is a superclass of C. Similarly for subclasses. The three parameters of TransitiveDirective are association type, and the two roles. By changing these you can create closures of other types of associations.
-−
-=== Instances and classes as associations ===
-−
- importPackage(org.wandora.query);
- importPackage(org.wandora.topicmap);
- new UnionDirective(
-   new JoinDirective(
-     new TypesOfDirective(),
-     new ContextTopicDirective("",XTMPSI.INSTANCE)),
-   new JoinDirective(
-     new InstancesDirective(),
-     new ContextTopicDirective("",XTMPSI.CLASS))
- );
-−
-Set http://www.topicmaps.org/xtm/1.0/core.xtm#class-instance as association type. Your topic map must also have topics with subject identifiers http://www.topicmaps.org/xtm/1.0/core.xtm#class-instance , http://www.topicmaps.org/xtm/1.0/core.xtm#class and http://www.topicmaps.org/xtm/1.0/core.xtm#instance . These are not in the default Wandora topic map.
-−
-This query will make associations out of all instance and class relations. Note how this is done as the union of types of a topic and instances of a topic. This is necessary to have each association visible regardless of what topic is used as the point of view. Suppose that A is the class of B which is of course same as B is an instance of A. If we're looking at topic A then the InstancesDirective will return this information. If we're looking at topic B then the same thing is returned by TypesOfDirective. The results of both these directives only have one column so we must join the context topic itself using JoinDirective and ContextTopicDirective.
 == See also ==

← Older revision		Revision as of 12:11, 26 July 2008
Line 52:		Line 52:

	This query will make associations out of all instance and class relations. Note how this is done as the union of types of a topic and instances of a topic. This is necessary to have each association visible regardless of what topic is used as the point of view. Suppose that A is the class of B which is of course same as B is an instance of A. If we're looking at topic A then the InstancesDirective will return this information. If we're looking at topic B then the same thing is returned by TypesOfDirective. The results of both these directives only have one column so we must join the context topic itself using JoinDirective and ContextTopicDirective.		This query will make associations out of all instance and class relations. Note how this is done as the union of types of a topic and instances of a topic. This is necessary to have each association visible regardless of what topic is used as the point of view. Suppose that A is the class of B which is of course same as B is an instance of A. If we're looking at topic A then the InstancesDirective will return this information. If we're looking at topic B then the same thing is returned by TypesOfDirective. The results of both these directives only have one column so we must join the context topic itself using JoinDirective and ContextTopicDirective.
		+
		+	== See also ==
		+
		+	* [[Layered topic map]]
		+	* [[Memory topic map]]
		+	* [[Database topic map]]
		+	* [[Linked topic map]]
		+	* [[Remote topic map]]

← Older revision		Revision as of 13:38, 30 May 2008
Line 1:		Line 1:
−	~~'''Note: This feature is not present in the current release version. Expect query topic maps in the version to be published on 31st of May.'''~~
−
	Query topic map is a special topic map implementation in Wandora. A query topic map is defined by a number of queries in the Wandora [[query language]]. Each query will return one type of associations and the topic map consists of all these associations and the topics needed by the associations. All queries are executed in the context of some other topic map.		Query topic map is a special topic map implementation in Wandora. A query topic map is defined by a number of queries in the Wandora [[query language]]. Each query will return one type of associations and the topic map consists of all these associations and the topics needed by the associations. All queries are executed in the context of some other topic map.

← Older revision		Revision as of 07:54, 29 May 2008
Line 6:		Line 6:

	Currently query topic maps can only be used to create associations. They may be expanded in the future to allow creation of new topics, occurrences, instances, subject identifiers and so on.		Currently query topic maps can only be used to create associations. They may be expanded in the future to allow creation of new topics, occurrences, instances, subject identifiers and so on.
		+
		+	The samples directory contains a QuerySample example project. This sample demonstrates the use of query topic maps including two example queries and a linked topic map as the query layer context. See also the readme.txt file in the sample directory.

	== Setting up a query topic map ==		== Setting up a query topic map ==

@@ Line 15: / Line 15: @@
 == Queries in a query topic map ==
-Queries in a query topic map are defined using the Wandora [[query language]]. Each query has a type which is the association type produced by the query. In the query editor, enter the subject identifier of the association type here. The queries themselves return a table of rows. Each column has a role, which will also be the role in the associations produced by the query. Rows of the returned table contain players for the associations.
+Queries in a query topic map are defined using the Wandora [[query language]]. Each query has a type which is the association type produced by the query. In the query editor, enter the subject identifier of the association type here. The queries themselves return a table of rows. Each column has a role, which will also be the role in the associations produced by the query. Rows of the returned table contain players for the associations. Note that association type and role topics must be in either the context topic map or some other topic map in the layer stack or the associations returned by query topic map will not be visible.
 As described in the [[query language]] page, all queries are executed using some topic as the query context. In query topic maps the currently opened topic acts as the query context. The query should return associations related to this topic. All rows that do not contain the context topic, i.e. context topic is not a player in the association, are ignored.

← Older revision		Revision as of 07:28, 27 May 2008
Line 36:		Line 36:
	This query will form a transitional closure of superclass-subclass associations. What this means is that if the context topic map has associations saying that A is a superclass of B and B is a superclass of C then this query will produce an association A is a superclass of C. Similarly for subclasses. The three parameters of TransitiveDirective are association type, and the two roles. By changing these you can create closures of other types of associations.		This query will form a transitional closure of superclass-subclass associations. What this means is that if the context topic map has associations saying that A is a superclass of B and B is a superclass of C then this query will produce an association A is a superclass of C. Similarly for subclasses. The three parameters of TransitiveDirective are association type, and the two roles. By changing these you can create closures of other types of associations.

−	=== ~~Convert instances to~~ associations ===	+	=== Instances and classes as associations ===
		+
		+	importPackage(org.wandora.query);
		+	importPackage(org.wandora.topicmap);
		+	new UnionDirective(
		+	new JoinDirective(
		+	new TypesOfDirective(),
		+	new ContextTopicDirective("",XTMPSI.INSTANCE)),
		+	new JoinDirective(
		+	new InstancesDirective(),
		+	new ContextTopicDirective("",XTMPSI.CLASS))
		+	);
		+
		+	Set http://www.topicmaps.org/xtm/1.0/core.xtm#class-instance as association type. Your topic map must also have topics with subject identifiers http://www.topicmaps.org/xtm/1.0/core.xtm#class-instance , http://www.topicmaps.org/xtm/1.0/core.xtm#class and http://www.topicmaps.org/xtm/1.0/core.xtm#instance . These are not in the default Wandora topic map.
		+
		+	This query will make associations out of all instance and class relations. Note how this is done as the union of types of a topic and instances of a topic. This is necessary to have each association visible regardless of what topic is used as the point of view. Suppose that A is the class of B which is of course same as B is an instance of A. If we're looking at topic A then the InstancesDirective will return this information. If we're looking at topic B then the same thing is returned by TypesOfDirective. The results of both these directives only have one column so we must join the context topic itself using JoinDirective and ContextTopicDirective.

← Older revision		Revision as of 07:11, 27 May 2008
Line 22:		Line 22:

	== Examples ==		== Examples ==
		+
		+	This section contains some example queries you can use in a query topic map.
		+
		+	=== Transitional closure ===
		+
		+	importPackage(org.wandora.query);
		+	importPackage(org.wandora.topicmap);
		+	new TransitiveDirective(XTMPSI.SUPERCLASS_SUBCLASS,
		+	XTMPSI.SUPERCLASS, XTMPSI.SUBCLASS);
		+
		+	Set http://www.topicmaps.org/xtm/1.0/core.xtm#superclass-subclass as association type.
		+
		+	This query will form a transitional closure of superclass-subclass associations. What this means is that if the context topic map has associations saying that A is a superclass of B and B is a superclass of C then this query will produce an association A is a superclass of C. Similarly for subclasses. The three parameters of TransitiveDirective are association type, and the two roles. By changing these you can create closures of other types of associations.
		+
		+	=== Convert instances to associations ===

← Older revision		Revision as of 07:05, 27 May 2008
Line 20:		Line 20:

	You should take care that same association is returned regardless of which player is used as the query context. For example, using topic A as context may produce an association saying that A is a superclass of B. Using B as context topic should then return an association saying that B is a subclass of A. Failure to do this will result in strange topic maps where some associations are visible only when looking at a certain topic.		You should take care that same association is returned regardless of which player is used as the query context. For example, using topic A as context may produce an association saying that A is a superclass of B. Using B as context topic should then return an association saying that B is a subclass of A. Failure to do this will result in strange topic maps where some associations are visible only when looking at a certain topic.
		+
		+	== Examples ==

← Older revision		Revision as of 12:55, 23 May 2008
Line 1:		Line 1:
−	'''Note: This feature is present in the current release version. Expect query topic maps in the version to be published on 31st of May.'''	+	'''Note: This feature is not present in the current release version. Expect query topic maps in the version to be published on 31st of May.'''

	Query topic map is a special topic map implementation in Wandora. A query topic map is defined by a number of queries in the Wandora [[query language]]. Each query will return one type of associations and the topic map consists of all these associations and the topics needed by the associations. All queries are executed in the context of some other topic map.		Query topic map is a special topic map implementation in Wandora. A query topic map is defined by a number of queries in the Wandora [[query language]]. Each query will return one type of associations and the topic map consists of all these associations and the topics needed by the associations. All queries are executed in the context of some other topic map.