Goals

Use cases, scenarios which explain how SolrDrWatson can be used; this drives architectural considerations: use cases should be cross-linked to architectural ideas

In defining use cases, heuristically thinking, it is probably wise to avoid blue sky concepts like Understand Natural Language,  instead (perhaps) thinking in terms of specific kinds of goals which drive specific kinds of use cases.  In many instances, it's reasonable to expect that some use cases will satisfy more than one goal.

Many of the use cases are highly related, as if there might be some taxonomic structure that could be imposed upon them, or sets of relations which wire them together. An overall activity is that of understanding natural language, our blue sky notion. Thus, we introduce Use Case 0, Machine Reading to serve as an umbrella for parsing, understanding, and related activities.
RELATED ARTICLESExplain
OpenSherlock Project
Goals
What about facilitating / empowering collective understanding?
What about learning?
What about prediction?
Use Case 0: Machine Reading
Use Case 1: Question Answering
Use Case 2: Topic Map Merging
Use Case 3: Locating Entailments
Use Case 4: Knowledge-based Discovery
Use Case 5: Support SolrKnowledgeFederationServer
How To ?
What Quests are entailed in this project?
Architecture Ideas
Curation Notes
Github
Project funding
References
Resources
Software License
SolrSherlock Project Summary
Tags
Tasks
Terms and Definitions
The project's name
Graph of this discussion
Enter the title of your article


Enter a short (max 500 characters) summation of your article
Enter the main body of your article
Lock
+Comments (0)
+Citations (0)
+About
Enter comment

Select article text to quote
welcome text

First name   Last name 

Email

Skip