On 24/06/15 13:51, Osma Suominen wrote:
On 24/06/15 15:39, Chris Dollin wrote:
In practice, the literal value would be stored using the Lucene
facility to
store the original field value alongside the indexed value
(TextField.TYPE_STORED). This would be similar to how LARQ worked. If the
langField setting was in use, the language field would hold the
language tag as
well. If not, the returned literals would not have a language tag (in
the above
example, the value would be "My resource").
Typed literals should work as well.
Okay, but where should the type be stored in that case? In another field,
analoguous to langField?
Could use the same field with a flag for language vs type.
Do you have a specific use case in mind for storing and retrieving typed
literals in the jena-text index?
Not at present. But if we're going to handle languaged literals,
I don't see why we shouldn't handle typed literals as well.
I remember some gotchas where bits of the code believed that what came
out of the index could only be a non-blank resource, but it was fixable
and presumably you've already spotted that.
Hmm, not sure I follow. The literal value would be returned in addition to the
resource, not instead of it.
Ah, I see I didn't read your proposal properly. Apologies.
The experiment I did returned just the literal, not the subject as well.
If I'm remembering the context correctly, converting the subject URI
to a Node took a good deal of the query time -- more than usign the
literal to do an indexed lookup in the triplestore.
[Hmm, where /did/ I put that code?]
Now would be a good time to find it :)
It looks like I put it in a repository. Somewhere.
(fx:gnashing-of-teeth)
Chris
--
"You work with mad scientists and you're surprised at a talking /cat/?"
/Girl Genius/
Epimorphics Ltd, http://www.epimorphics.com
Registered address: Court Lodge, 105 High Street, Portishead, Bristol BS20 6PT
Epimorphics Ltd. is a limited company registered in England (number 7016688)
