Reduced Topic Maps - Revision history

Akivela at 20:00, 12 July 2012

2012-07-12T20:00:29Z

2012-07-12T19:59:52Z

2012-07-12T19:57:01Z

2010-04-06T18:57:24Z

‎Additional notes

2010-04-06T18:55:37Z

‎Additional notes

2008-07-30T07:41:00Z

‎Additional notes

2008-07-14T15:54:23Z

‎Additional notes

2007-11-09T14:36:35Z

‎Additional notes

2007-06-02T11:53:58Z

‎Additional notes

2007-06-02T11:53:18Z

‎Additional notes

@@ Line 11: / Line 11: @@
 # Associations cannot have scopes.
 # Associations can only have one player per member and cannot have two members with same role.
-# No reifiers. Thus, a reifier can not be added to a topic, an association nor any other topic map structure. When a topic or an association needs a reifier, it can be implemented using an association or an association player.
+# No reifiers. Thus, an explicit reifier can not be added to a topic, an association nor any other topic map structure. When a topic or an association needs a reifier, it can be implemented using an association or an association player.
 It should be noted that many of the features that were left out are somewhat vaguely defined in the topic map standard. For example, the interpretation of scopes is almost entirely left to the application, as is the decision when to resolve subject identifier URIs.

@@ Line 11: / Line 11: @@
 # Associations cannot have scopes.
 # Associations can only have one player per member and cannot have two members with same role.
-# No reifiers. Thus, a reifier can not be added to a topic, an association nor any other topic map structure.
+# No reifiers. Thus, a reifier can not be added to a topic, an association nor any other topic map structure. When a topic or an association needs a reifier, it can be implemented using an association or an association player.
 It should be noted that many of the features that were left out are somewhat vaguely defined in the topic map standard. For example, the interpretation of scopes is almost entirely left to the application, as is the decision when to resolve subject identifier URIs.

@@ Line 11: / Line 11: @@
 # Associations cannot have scopes.
 # Associations can only have one player per member and cannot have two members with same role.
 It should be noted that many of the features that were left out are somewhat vaguely defined in the topic map standard. For example, the interpretation of scopes is almost entirely left to the application, as is the decision when to resolve subject identifier URIs.

@@ Line 19: / Line 19: @@
 * Although topic map implementation does not resolve subject locators, Wandora application views an icon or a thumbnail for the subject locator and the icon is created using the subject locator resource. To create the icon or a thumbnail, Wandora must resolve the subject locator and download the image.
-** As Wandora doesn't resolve identifiers, you may use invalid URIs as subject locator and as subject identifier. If you try to export your topic map containing invalid URIs in RDF format, for example, the resulting RDF serialization is invalid due to invalid subjects in Wandora.
+** As Wandora doesn't resolve identifiers, you may use invalid URI as a subject locator and a subject identifier. Exporting a topic map containing invalid URIs in RDF format, for example, results an invalid RDF serialization.
 * Base and variant names in Wandora should not contain new line characters as the GUI element holding a name supports only single line strings.

← Older revision		Revision as of 18:55, 6 April 2010
Line 19:		Line 19:

	* Although topic map implementation does not resolve subject locators, Wandora application views an icon or a thumbnail for the subject locator and the icon is created using the subject locator resource. To create the icon or a thumbnail, Wandora must resolve the subject locator and download the image.		* Although topic map implementation does not resolve subject locators, Wandora application views an icon or a thumbnail for the subject locator and the icon is created using the subject locator resource. To create the icon or a thumbnail, Wandora must resolve the subject locator and download the image.
−	* Base and variant names in Wandora should not contain new line characters as GUI element holding ~~the~~ name supports only single line strings.	+	** As Wandora doesn't resolve identifiers, you may use invalid URIs as subject locator and as subject identifier. If you try to export your topic map containing invalid URIs in RDF format, for example, the resulting RDF serialization is invalid due to invalid subjects in Wandora.
		+	* Base and variant names in Wandora should not contain new line characters as the GUI element holding a name supports only single line strings.

@@ Line 18: / Line 18: @@
 == Additional notes ==
-* Although topic map implementation does not resolve subject locators, Wandora application views an icon or a thumbnail for the subject locator and the icon is created using the subject locator resource if it refers an image for example. To create the icon or a thumbnail, Wandora must resolve the subject locator and download the image.
+* Although topic map implementation does not resolve subject locators, Wandora application views an icon or a thumbnail for the subject locator and the icon is created using the subject locator resource. To create the icon or a thumbnail, Wandora must resolve the subject locator and download the image.
 * Base and variant names in Wandora should not contain new line characters as GUI element holding the name supports only single line strings.