Git Product home page Git Product logo

vocidex's People

Contributors

cygri avatar pyvandenbussche avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

vocidex's Issues

Create a document in the index for the owl:Ontology in add-vocabulary

Currently, the add-vocabulary tool only indexes a document for each class and for each property (and for each datatype, in a slightly broken way).

It should also add a document to the index for the vocabulary itself, of type vocabulary.

Unlike add-vocabulary, the index-lov tool already does this, by using the nicely curated LOV metadata.

In the case of add-vocabulary, we have to be more careful because any number of owl:Ontology instances could be floating around in the input graph (other imported ontologies, a directory of versions of this ontology, and so on), and we need to be careful to pick only the β€œreal” one. Perhaps its URI can be provided as a command-line option, to override the default choice.

Indexing terms other than rdfs:label

Is there a way to configure vocidex to index on other terms (annotation property values) attached to the classes? I've got the basic set-up running, and it works very well. But I can't figure out how to get it to index values other than rdfs:label. Sorry, I know that this isn't an "issue" per se. But I didn't find any other contact method.

Add prefixes in add-vocabulary

The add-vocabulary tool is currently unaware of prefixes. It doesn't know the prefix of the current vocabulary.

If the same vocabulary were indexed via index-lov, then the prefix and prefixed name would be set on all terms, as provided by LOV metadata.

We should make an effort to discover the prefix also in add-vocabulary. A number of sources are possible:

  • Prefix declaration in the input graph
  • vann:preferredNamespacePrefix on the owl:Ontology node
  • Specified by user on the command line

problems with vocidex

Hello:

Nowdays I am using vocidex to insert in elasticsearch different ontologies, but I am founding the next fail:

015-06-05 15:37:00,668][WARN ][transport.netty ] [Contemplator] Message not fully read (request) for [0] and action [], resetting

WARN [Orbit] Message not fully read (response) for [0] handler future(org.elasticsearch.client.transport.TransportClientNodesService$SimpleNodeSampler$1@4adf9095), error [true], resetting

Could you comment something about this?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.