| | 1 | = The Use of RDF = |
| | 2 | |
| | 3 | We should discuss where and how RDF is used in this framework. In previous email discussions we already thought about using RDF as a way to let an Extractor output its extracted information, because of the flexibility it provides: |
| | 4 | |
| | 5 | - no assumption on what the metadata looks like, can be very simple or very complex - easy to store in RDF stores, no transformation necessary (provided that you have named graphs support) |
| | 6 | |
| | 7 | The same technique could also be used in the DataObjects?, which now use a Map with dedicated keys, defined per DataObject? type. I would be in favour of changing this to "something RDF", as it considerably eases development. |
| | 8 | |
| | 9 | Leo came up with an idea that allows delivering RDF while at the same time providing a simpler interface to programmers not knowledgeable in RDF. The idea is to create a class that implements both the org.openrdf.model.Graph interface as well as the java.util.Map interface. The effect of |
| | 10 | |
| | 11 | result.put(authorURI, "chris"); with the authorURI being equal to the URI of the author predicate, would then be equal to |
| | 12 | |
| | 13 | result.add(documentURI, authorURI, "chris"); |
| | 14 | |
| | 15 | I.e., you can use the Map methods to insert simple resource-predicate-literal statements (the majority), which is simple to document and understand, whereas people who know what they are doing can also add arbitrary RDF statements. |
