Skip to content
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.

UseCase01: "Semantic Endpoint" #11

Open
Mec-iS opened this issue Mar 9, 2015 · 2 comments
Open

UseCase01: "Semantic Endpoint" #11

Mec-iS opened this issue Mar 9, 2015 · 2 comments

Comments

@Mec-iS
Copy link
Contributor

Mec-iS commented Mar 9, 2015

Define an "higher level API" to wrap the functionality of Concepts API, Space API and TagMe API to serve text analysis (semantic+syntactic).

@Mec-iS Mec-iS added this to the New Orleans milestone Mar 9, 2015
@jacoscaz
Copy link
Contributor

input: arbitrary text
output: json document w/ what?
flow: 
- client sends some text
- we use Tagme to obtain links to wiki/db-pedia docs
- we extrapolate the text's related concepts via our DB
- we hand the result back to the client 
result: 
{
  "text": "lorem ipsum blabber bla...",
  "relatedDocuments": [
    "http://somedbpediadocument",
    "http://someotherdbpediadocument"
  ],
  "relatedConcepts": [
    // Is this needed?
  ]
}

@jacoscaz jacoscaz self-assigned this Mar 15, 2015
@Mec-iS
Copy link
Contributor Author

Mec-iS commented Mar 15, 2015

result: 
{
  "text": "lorem ipsum blabber bla...",
  "relatedDocuments": [
    "http://somedbpediadocument",
    "http://someotherdbpediadocument"
  ],
  "relatedConcepts": [
    <concepts in the taxonomy> // not needed but more information we give the better
  ],
  "spotted": [ <words spotted in the text>],
  "annotations": [ <links to wikipedia>]
}

@Mec-iS Mec-iS modified the milestone: New Orleans Mar 30, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants