[Mulgara-general] Mulgara size limits

Seaborne, Andy andy.seaborne at hp.com
Tue Jul 1 12:25:42 PDT 2008


> I didn't realize that the ARP code was keeping blank node mappings in
> memory. Whoever implemented the content handler with ARP must not have
> known this, as the content handler maintains it's own mappings. These
> mappings are file-based, so they shouldn't have memory restrictions,
> though I can't comment on their speed, as I don't know how well they
> cache in memory.
>
Paul,

We're talking at cross-purposes.  ARP isn’t managing the blank node mappings - it only handles document scope and so the content handler has to manage the document scope to database scope relationship.  What ARP is checking is the RDF syntax rule that rdf:nodeID be used only once per file (I don't know why RDF/XML has this restriction except to guess it is so it has similar rules to to rdf:ID and xml:ID).  Without checking, there is no state needed because the rdf:nodeID attribute value forms the output label to document scope.

        Andy



More information about the Mulgara-general mailing list