Sorry, can't run the test case right now.
No I'm thinking RDF/XML :) But the prefixes are only used for
properties, not subject (@rdf:about) or object (@rdf:resource) values.
What would you gain by adding an xml:base? You could shorten
prfx:lcl-name to just lcl-name by setting xml:base to prfx:
No.
If you run the test case you see that RDF/XML writes out xmlns defns of
prefixes and uses the prefixes in the serialization. Perhaps you are thinking
of n-triples.
Thanks,
Chris
> On Feb 22, 2019, at 16:52, Martynas Jusevičius wrote:
>
> Isn't it so that RDF/XML writer always writes
Isn't it so that RDF/XML writer always writes absolute URIs, so
xml:base is unnecessary because it would have no effect anyway?
On Fri, Feb 22, 2019 at 11:20 PM Chris Tomlinson
wrote:
>
> Hello,
>
> We are trying to serve various ontology files in a variety of serializations,
> principally
Hello,
We are trying to serve various ontology files in a variety of serializations,
principally RDF/XML and Turtle.
The specs indicate that if the baseURI for an ontology is the URL by which the
ontology is retrieved then it is not required that the producer include an
explicit xml:base or
I finally update the jena text query documentation with the helpful table
supplied by Sorin Gheorghiu.
Thank you for the contribution,
Chris
> On Feb 5, 2019, at 6:07 AM, Sorin Gheorghiu
> wrote:
>
> Hi,
>
> it is a great that Jena supports further the Full Text Search extension.
>
It's here - http://jena.apache.org/documentation/tdb/architecture.html
Rob
On 22/02/2019, 04:03, "Ekaterina Danilova" wrote:
Thank you, it was exactly what I needed. It is still nice to hear what
others think about my idea of data storage as resources and I think I will
stick to
In addition:
* if there are 3 fields in /text:map/, then during indexing one
contains data (let's name it 'text1'), the others are empty (let's
name them 'text2' and 'text3'),
* if on the next attempt the field 'text1' is commented out, then
'text2' contains data and 'text3' is empty
TDB's design is given in official documentation here:
https://jena.apache.org/documentation/tdb/architecture.html
ajs6f
> On Feb 22, 2019, at 5:02 AM, Ekaterina Danilova
> wrote:
>
> Thank you, it was exactly what I needed. It is still nice to hear what
> others think about my idea of data
Hi,
When building the text index with the /jena.textindexer/ tool in Jena
3.10 for an external full-text search engine (Elasticsearch of course)
and having multiple fields with different names in /text:map/, just *one
field is indexed* (more precisely one field contains data, the others
are
Thank you, it was exactly what I needed. It is still nice to hear what
others think about my idea of data storage as resources and I think I will
stick to that option, but TDB storage logic was quite unclear to me. Would
be great if it was mentioned in official documentation since I couldn't
find
10 matches
Mail list logo
