Using @vocab keyword from JSON-LD serialization

Hi everyone, I am playing with Jena and using JSON-LD syntax for reading and outputting the data. I could not find much documentation and examples on supported keywords from JSON-LD in Jena. So I wanted to ask is there a way to use @vocab keyword from JSON-LD in Jena? Also, I would appreciate

Re: Fuseki 2 text: how to factor out entMap in configuration

On 20/12/15 12:58, Jonathan Camilleri wrote: Are there examples of such macros and scripts? I was thinking of processing with perl (sed, m4, cpp, choice here>) to build text files. A shell script will do. What Joachim needs is to concatenate the same http://zbw.eu/namespaces/fuseki/entMap

Re: Fuseki 2 text: how to factor out entMap in configuration

Another way is to have one configuration file : they don't have to be separated out into individual files on configuration. Multiple definitions can go in the top-level config.ttl or passed in on the start up line. Andy On 20/12/15 12:02, Andy Seaborne wrote: In assemblers, URIs

Re: Query with spatial *and* text searches.

Hi Marco. Yes, that's it. The indexes work well in isolation, but don't combine well. Smooshing them into a single index would be a great idea, especially if the query could resolve both text and spatial predicates with one matching scan of the index. Perhaps Stephen could be persuaded to

Re: Fuseki 2 text: how to factor out entMap in configuration

Are there examples of such macros and scripts? Jon https://delicious.com/jon80 On 20 December 2015 at 13:02, Andy Seaborne wrote: > In assemblers, URIs are just names. They are not dereferenced, nor is > there an include mechanism. > > One way around this, for some

Re: Fuseki 2 text: how to factor out entMap in configuration

In assemblers, URIs are just names. They are not dereferenced, nor is there an include mechanism. One way around this, for some situations, is to build the configurations files as the service starts with a macro processor/templating solution of your choice. Andy On 20/12/15

RE: Fuseki 2 text: how to factor out entMap in configuration

Thanks for looking into this! The URI was supposed to be just a name, not to be dereferenced. Your question triggered the idea of a more simple solution (omitting an additional namespace and referencing the according definition in config.ttl directly): <#swdskosIndex> a text:TextIndexLucene ;

Re: Query with spatial *and* text searches.

Hi Mark! I'm not sure that the jena-external-index approach would help. It might or might not, depending on how it's implemented. AFAIK it's just an idea right now, I haven't seen any code. In any case I think the problem with jena-text and probably jena-spatial too (not very familiar with