Schema - Revision history

Akivela: /* Using the example schema */

2008-08-19T09:06:44Z

‎Using the example schema

2008-08-19T09:06:11Z

‎Specifying roles of schema

2008-08-19T09:04:43Z

‎Specifying roles of schema

2008-08-19T09:00:25Z

‎Specifying content type of schema

2008-08-19T08:58:39Z

2008-08-19T08:57:59Z

2008-08-18T19:17:21Z

‎Using the example schema

2008-08-18T19:16:25Z

‎Specifying roles of schema

2008-08-18T19:15:18Z

‎Using the example schema

2008-08-18T19:06:37Z

‎Using the example schema

@@ Line 110: / Line 110: @@
-Now we are are to try how the schema works in real life. Lets create yet another album. Select '''album''' topic in tree. Right click the topic and select '''New topic > New instance topic...'''.
+Now we are ready to try how the schema works in real life. Lets create yet another album. Select '''album''' topic in tree. Right click the topic and select '''New topic > New instance topic...'''.
@@ Line 159: / Line 159: @@
 Created schema is not automatically symmetric. Our schema says nothing about creating '''hasAlbum''' association in point of view of the album. If you want to add artist-album associations in albums, you need to create symmetric schema specification to '''album''' topic. As role definitions remain the same you just have to define '''Content type''' and '''Association type'''.
 === Summary of schema creation steps===

@@ Line 104: / Line 104: @@
 [[Image:schema_example_08.gif|center]]
-We have just specified that '''hasAlbum''' association consists of players of type '''album''' and '''artist''', that is, instances of '''album''' and instances of '''artist'''.
 === Using the example schema ===

← Older revision		Revision as of 09:04, 19 August 2008
Line 103:		Line 103:

	[[Image:schema_example_08.gif\|center]]		[[Image:schema_example_08.gif\|center]]
		+
		+	We have just specified that '''hasAlbum''' association consists of players of type '''album''' and '''artist''', that is, instances of '''album''' and instances of '''artist'''.

	=== Using the example schema ===		=== Using the example schema ===

@@ Line 63: / Line 63: @@
 === Specifying content type of schema ===
-Now you should have '''artist''' open in Wandora as shown above. Note that topic has only one class '''myMusic''' and one instance '''The Art of Noise (artist)'''. Next step is to add class '''Content type''' to the topic. Right click '''Classes''' header title and select '''Add class...'''. Wandora opens a dialog used to select the topic. Open '''Schema type''' subtree and select '''Content type'''. Finally confirm class addition clicking '''OK'''. You have just specified the topic '''artist''' is a content type.
+Now you should have '''artist''' open in Wandora as shown above. Note that topic has only one class '''myMusic''' and one instance '''The Art of Noise (artist)'''. Next step is to add class '''Content type''' to the topic. Right click '''Classes''' header title and select '''Add class...'''. Wandora opens a dialog used to select topics. Open '''Schema type''' subtree and select '''Content type'''. Finally confirm class addition clicking '''OK'''. You have just specified the topic '''artist''' is a content type.
 [[Image:schema_example_02.gif|center]]
 === Specifying association type of schema ===

@@ Line 9: / Line 9: @@
 * Superclass-subclass hierarchy with inheritance of schema definitions
-Schema does '''not''' restrict the associations, roles or players you can view or import to Wandora, that is, schema is not used to validate the topic map. You can always create whatever associations or occurrences you want. Schema just offers you a framework and constructions to do things more comfortably. Schema is a collection of topics and associations found usually under '''Schema type''' topic.
+Schema does '''not''' restrict the associations, roles or players you can view or import to Wandora, that is, schema is not used to validate the topic map. You can always create whatever associations or occurrences you want. Schema just offers you a framework to do things more comfortably. Schema is a collection of topics and associations found usually under '''Schema type''' topic.
 [[Image:Schema_tree.gif|center]]

@@ Line 6: / Line 6: @@
 * What roles are allowed and required within associations.
 * What players are allowed to play a specific role.
-* What kinds of text data (occurrences) are allowed for the topic.
+* What kinds of occurrences are allowed for the topic.
 * Superclass-subclass hierarchy with inheritance of schema definitions

@@ Line 162: / Line 162: @@
-Summary of schema creation steps:
+=== Summary of schema creation steps===
 * Open class topic of topic's you want to edit.
 * Make topic instance of '''Content type'''.

@@ Line 87: / Line 87: @@
 [[Image:schema_example_05.gif|center]]
 === Specifying roles of schema ===
@@ Line 102: / Line 104: @@
 [[Image:schema_example_08.gif|center]]
 === Using the example schema ===

← Older revision		Revision as of 19:06, 18 August 2008
Line 146:		Line 146:

	[[Image:schema_example_16.gif\|center]]		[[Image:schema_example_16.gif\|center]]
		+
		+
		+	New '''hasAlbum''' association is created when you click OK.
		+
		+
		+	[[Image:schema_example_17.gif\|center]]