Changes between Version 8 and Version 9 of ApertureRDF

Timestamp:

10/26/05 12:07:31 (19 years ago)

Author:

anonymous

Comment:

--

ApertureRDF

@@ -30 +30 @@
 Arjohn explained this decision to me as follows. Have a look at the architecture graphic on http://www.openrdf.org/doc/sesame2/system/ch02.html. The RDF Model at the bottom is the foundation for the rest of the system to manipulate RDF information. It is very awkward and may potentially result in problems when you are able to manipulate the RDF at the model level, as it bypasses the Sail stack and any inferencing, security restrictions, etc. that takes place in it. Therefore these interfaces from now on provide read-only information only. This way it is for example not possible to add properties to Resources obtained from a query result, which may result in indefined behaviour.
 
-If you want to manipulate statements, the Repository class is the way to go. It contains methods for adding triples as well as functionality for posing queries, extracting RDF, etc. Only drawback is that this resulted in quite a large class. Also, just creating a repository is not enough, it always operates on top of a Sail. This architecture provides great flexibility at the cost of more code complexity.
+If you want to manipulate statements, the Repository class is the way to go. It contains methods for adding triples as well as functionality for posing queries, extracting RDF, etc. Furthermore, a number of utility classes (URIVertex, LiteralVertex, ...) are provided that take a Repository as argument and that let you treat the RDF statements as a graph datastructure.
+
+The only drawback of the Repository class is that this resulted in quite a large class. Also, just creating a repository is not enough, it always operates on top of a Sail. This architecture provides great flexibility at the cost of more code complexity.
 
 Example: you want to create an in-memory RDF "container" that you can pass to an Extractor:
 
+{{{
+#!java
 Repository repository = new Repository(new MemoryStore());
 repository.initialize();
 extractor.doYourWork(repository);
-
+}}}