Projects/Nepomuk/GraphConcepts - Revision history

AnneW: Marked this version for translation

2012-12-13T16:29:35Z

Marked this version for translation

AnneW: Prepare for translation

2012-12-13T16:29:24Z

Prepare for translation

Vishesh at 10:29, 24 August 2012

2012-08-24T10:29:59Z

Vishesh: /* Agents */ Remove data by application link

2012-08-24T08:04:19Z

‎Agents: Remove data by application link

Vishesh at 08:02, 24 August 2012

2012-08-24T08:02:36Z

Vishesh: /* Graph Creation */ Added links

2012-08-24T08:00:45Z

‎Graph Creation: Added links

Vishesh: Graph Creation

2012-08-24T07:57:30Z

Graph Creation

Vishesh: /* Agents */

2012-08-22T10:27:44Z

‎Agents

Vishesh: /* Agents */

2012-08-22T10:27:32Z

‎Agents

Vishesh: Initial Commit

2012-08-22T10:27:05Z

Initial Commit

@@ Line 2: / Line 2: @@
 <translate>
-== The Semantic Web - with quadruples ==
+== The Semantic Web - with quadruples == <!--T:1-->
 '''Nepomuk''' is based on the Semantic Web, and even though the Semantic Web is largely advertised as a triple store, Nepomuk is NOT a triple store. We in fact store quadruples -> <tt>Subject - Predicate - Object - Graph</tt>. The <tt>Graph</tt> part of these quadruples is always automatically managed by Nepomuk. Clients rarely (if ever) need to care about the graph.
 However, if you still want to know why they are present. Read on.
 The <tt>graph</tt> is also called the context of the statement. It is used to store some information about each triple
-== Graph Naming ==
+== Graph Naming == <!--T:5-->
 Every graph in '''Nepomuk''' is given a unique uri which is of the form <tt>nepomuk:/ctx/uuid</tt>. The <tt>ctx</tt> over here is an abbreviation for context.
-== Graph Creation ==
+== Graph Creation == <!--T:7-->
 The first obvious question is - When are graphs created? Is everything just added into one big graph?
 '''Nepomuk''' works by creating new graphs for each atomic operation. These operations are the ones defined by the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/datamanagement_8h.html DataManagement functions] -
 * [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#gafb8a64e1fb9e8339ff87be1b7a370a57 addProperty]
 * [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#gaa86c603d624d55703b0e41bbec77d2ec setProperty]
@@ Line 26: / Line 33: @@
 Each time any of these operations is called and new data is being pushed, a new graph with the current date time is created.
-== Graph contents ==
+== Graph contents == <!--T:12-->
 Graphs in '''Nepomuk''' store the following information -
 * Graph Type
 * Creation Date
@@ Line 38: / Line 48: @@
 Example -
 <syntaxhighlight lang="text">
@@ Line 48: / Line 59: @@
 The <tt>nao:created</tt> and <tt>nao:lastModified</tt> properties are identical to those used in resources. Except for the fact that graphs are generally never modified. They are only created or destroyed.
-=== Graph Type ===
+=== Graph Type === <!--T:17-->
 Each graph has a type which depends on the type of data it holds. The 3 most commonly used types are -
 * <tt>nrl:Ontology</tt> - Used to hold ontology data.
@@ Line 57: / Line 70: @@
 * <tt>nrl:DiscardableInstanceBase</tt> - Used for data which can be reproduced and should not be backed up. This type is generally reserved for data created during indexing of files.
-=== Agents ===
+=== Agents === <!--T:19-->
 Each graph contains a property called <tt>nao:maintainedBy</tt> which specifies which application created that data -
 <syntaxhighlight lang="text">
 <nepomuk:/ctx/c4d93812-7d8c-4c8f-b8a7-e1d4dbc5fed5>
@@ Line 68: / Line 83: @@
          nao:maintainedBy        nepomuk:/res/e2eb2efb-14ee-4038-ac24-698f916289b0
 <nepomuk:/res/e2eb2efb-14ee-4038-ac24-698f916289b0>
          rdf:type                nao:Agent
@@ Line 75: / Line 91: @@
 Each application is represented as a <tt>nao:Agent</tt> with the application name specified as the nao:identifier. This name is automatically determined via <tt>KComponentData</tt> and can be spoofed. Security was not one of our concerns.
 Each triple may be maintained by a number of different applications. This information is valuable for the advanced DataManagement functions such as [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#ga0fbf22be4b581afd0b5bcd1f203e934f <tt>removeDataByApplication</tt>].
 [[Category:Documentation]]
 [[Category:Development]]
 [[Category:Tutorials]]
 </translate>

@@ Line 1: / Line 1: @@
-Nepomuk is based on the Semantic Web, and even though the Semantic Web is largely advertised as a triple store, Nepomuk is NOT a triple store. We in fact store quadruples -> <code>Subject</code> - <code>Predicate</code> - <code>Object</code> - <code>Graph</code>. The <code>Graph</code> part of these quadruples is always automatically managed by Nepomuk. Clients rarely (if ever) need to care about the graph.
+<languages />
 However, if you still want to know why they are present. Read on.
-The <code>graph</code> is also called the context of the statement. It is used to store some information about each triple
+The <tt>graph</tt> is also called the context of the statement. It is used to store some information about each triple
-= Graph Naming =
+== Graph Creation ==
-Every graph in Nepomuk is given a unique uri which is of the form <code>nepomuk:/ctx/uuid</code>. The <tt>ctx</tt> over here is an abbreviation for context.
 The first obvious question is - When are graphs created? Is everything just added into one big graph?
-Nepomuk works by creating new graphs for each atomic operation. These operations are the ones defined by the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/datamanagement_8h.html DataManagement functions] -
+'''Nepomuk''' works by creating new graphs for each atomic operation. These operations are the ones defined by the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/datamanagement_8h.html DataManagement functions] -
 * [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#gafb8a64e1fb9e8339ff87be1b7a370a57 addProperty]
@@ Line 21: / Line 28: @@
 Each time any of these operations is called and new data is being pushed, a new graph with the current date time is created.
-= Graph contents =
+== Graph contents ==
 Graphs in Nepomuk store the following information -
 * Graph Type
@@ Line 40: / Line 48: @@
-The <code>nao:created</code> and <code>nao:lastModified</code> properties are identical to those used in resources. Except for the fact that graphs are generally never modified. They are only created or destroyed.
+The <tt>nao:created</tt> and <tt>nao:lastModified</tt> properties are identical to those used in resources. Except for the fact that graphs are generally never modified. They are only created or destroyed.
 Each graph has a type which depends on the type of data it holds. The 3 most commonly used types are -
-* <code>nrl:Ontology</code> - Used to hold ontology data.
+* <tt>nrl:Ontology</tt> - Used to hold ontology data.
-* <code>nrl:InstanceBase</code> - Used for normal data
+* <tt>nrl:InstanceBase</tt> - Used for normal data
-* <code>nrl:DiscardableInstanceBase</code> - Used for data which can be reproduced and should not be backed up. This type is generally reserved for data created during indexing of files.
+* <tt>nrl:DiscardableInstanceBase</tt> - Used for data which can be reproduced and should not be backed up. This type is generally reserved for data created during indexing of files.
-== Agents ==
+=== Agents ===
-Each graph contains a property called <code>nao:maintainedBy</code> which specifies which application created that data -
+Each graph contains a property called <tt>nao:maintainedBy</tt> which specifies which application created that data -
 <syntaxhighlight lang="text">
@@ Line 66: / Line 75: @@
-Each application is represented as a <code>nao:Agent</code> with the application name specified as the nao:identifier. This name is automatically determined via <code>KComponentData</code> and can be spoofed. Security was not one of our concerns.
+Each application is represented as a <tt>nao:Agent</tt> with the application name specified as the nao:identifier. This name is automatically determined via <tt>KComponentData</tt> and can be spoofed. Security was not one of our concerns.
-Each triple may be maintained by a number of different applications. This information is valuable for the advanced DataManagement functions such as [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#ga0fbf22be4b581afd0b5bcd1f203e934f <code>removeDataByApplication</code>].
+[[Category:Documentation]]

← Older revision		Revision as of 10:29, 24 August 2012
Line 4:		Line 4:

	The <code>graph</code> is also called the context of the statement. It is used to store some information about each triple		The <code>graph</code> is also called the context of the statement. It is used to store some information about each triple
		+
		+	= Graph Naming =
		+	Every graph in Nepomuk is given a unique uri which is of the form <code>nepomuk:/ctx/uuid</code>. The <tt>ctx</tt> over here is an abbreviation for context.

	= Graph Creation =		= Graph Creation =

← Older revision		Revision as of 08:04, 24 August 2012
Line 65:		Line 65:
	Each application is represented as a <code>nao:Agent</code> with the application name specified as the nao:identifier. This name is automatically determined via <code>KComponentData</code> and can be spoofed. Security was not one of our concerns.		Each application is represented as a <code>nao:Agent</code> with the application name specified as the nao:identifier. This name is automatically determined via <code>KComponentData</code> and can be spoofed. Security was not one of our concerns.

−	Each triple may be maintained by a number of different applications. This information is valuable for the advanced DataManagement functions such as <code>removeDataByApplication</code>.	+	Each triple may be maintained by a number of different applications. This information is valuable for the advanced DataManagement functions such as [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#ga0fbf22be4b581afd0b5bcd1f203e934f <code>removeDataByApplication</code>].

@@ Line 2: / Line 2: @@
 However, if you still want to know why they are present. Read on.
 = Graph Creation =
@@ Line 17: / Line 19: @@
 = Graph contents =
-The <code>graph</code> is always called the context of the statement. It is used to store some metadata about each triple. In our case we currently store the following information
+Graphs in Nepomuk store the following information -
 * Graph Type

@@ Line 6: / Line 6: @@
 The first obvious question is - When are graphs created? Is everything just added into one big graph?
-Nepomuk works by creating new graphs for each atomic operation. These operations are the ones defined by the DataManagement functions -
+Nepomuk works by creating new graphs for each atomic operation. These operations are the ones defined by the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/datamanagement_8h.html DataManagement functions] -
 * addProperty
-* setProperty
+* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#gafb8a64e1fb9e8339ff87be1b7a370a57 addProperty]
-* createResource
+* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#gaa86c603d624d55703b0e41bbec77d2ec setProperty]
-* storeResources
+* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html#gad731308a74b75a1a2bb20b1676eda2ed createResource]

@@ Line 46: / Line 46: @@
          nao:identifier          nepomukindexer
 </syntaxhighlight>
 Each application is represented as a <code>nao:Agent</code> with the application name specified as the nao:identifier. This name is automatically determined via <code>KComponentData</code> and can be spoofed. Security was not one of our concerns.
 Each triple may be maintained by a number of different applications. This information is valuable for the advanced DataManagement functions such as <code>removeDataByApplication</code>.