| | 46 | = Problem BlankNodes = |
| | 47 | |
| | 48 | For many datasources it is nescessary to create some blank nodes to express more complicated meta-data. |
| | 49 | |
| | 50 | For instance, in the ImapCrawler we create the following: |
| | 51 | |
| | 52 | {{{ |
| | 53 | |
| | 54 | myimapsource:Blah-1 a :Message ; to [ a :Person ; :email "bob@bob.com@ ]. |
| | 55 | |
| | 56 | }}} |
| | 57 | |
| | 58 | (hope everyone reads N3 :) |
| | 59 | |
| | 60 | Here we need an ID for the node representing bob. Currently each crawler makes up this node id, but this is tricky, because blanknode IDs must conform to XML names, which are not trivial to define... (the specs are pretty much unreadable). |
| | 61 | To get around this Chris and Gunnar have discussing adding a createBNode() method to the RDFContainer, which returns a bnode guaranteed unique within this store/repository/whatever. Good plan? |
