Conversation
It is in the default case. There was actually a debate if they should be different or not. But for the widget, becuase it's only using defaults, then yes it's the same input/output. |
|
Oh I see @Narsil Does it mean that the widget has to support PDF upload? |
|
Should be transparent for the widget, no ? In any case neither the API nor the actual pipeline deal with it right now, but it's something that we could/should do. |
|
I see, in this case, I will just reuse "VisualQA widget for DocumentQA pipeline" until more features are needed |
|
@Narsil does api-inference support |
* Reuse VisualQA for DocQA (for now) * fix
|
It looks like this has already been merged, but one thing I didn't do before pushing the initial PR is fix the examples to be more relevant to document question/answering. Is it possible still to change those? Happy to send a PR. |
should probably be https://miro.medium.com/max/787/1*iECQRIiOGTmEFLdWkVIH2g.jpeg |
DocumentQuestionAnswering by @ankrgyl
**first of all, amazing work @ankrgyl !
I'm opening a PR here from @ankrgyl branch.
Demo
https://63243249748e56079f18d750--huggingface-widgets.netlify.app/impira/layoutlm-document-qa
API shape
input (identical to VisualQuestionAnsweringWidget ):
output (similar to VisualQuestionAnsweringWidget):
todos:
cc: @NielsRogge @osanseviero
Questions:
@ankrgyl @Narsil Is the API shape for pipelines
visual-questions-answering&document-questions-answeringare identical? If so, we can just reuse VisualQA widget for DocumentQA pipeline as well. Please let me know