Well, if we have to deal with possibly multiple concepts to be returned we, we have to use QList<Resource> or equivalent. We can't return either Resource or QList<Resource> and I think that splitting API to two functions isn't convenient for later use (unless we have *clear* definition when we want only one concept, when multiple).
-- You received this bug notification because you are a member of Wintermute Developers, which is a bug assignee. https://bugs.launchpad.net/bugs/846248 Title: Unable to load semantics from Ontology Status in Wintermute: Confirmed Status in Wintermute trunk series: Confirmed Bug description: Wintermute requires that information, more technically known as resources, a subset of a RDF statement, are required in order to form properly machine understandable statement. An ontology provides the logic of knowledge for natural language processing. We need Soprano to simply execute a SPARQL query. To manage notifications about this bug go to: https://bugs.launchpad.net/wintermute/+bug/846248/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~wintermute-devel Post to : wintermute-devel@lists.launchpad.net Unsubscribe : https://launchpad.net/~wintermute-devel More help : https://help.launchpad.net/ListHelp
