Skip to content

Roadmap can be read as saying we don't support text #382

Closed

Description

@justinormont

In a recent StackOverflow answer, our Roadmap was seemingly interpreted it to say that text/NLP is a purely future work item.

The roadmap currently says:

Featurization Improvements

  • Text (*)
    • Natural language text preprocessing such as tokenization, part-of-speech tagging, and sentence > breaking
    • Pre-trained text models that can be used for extracting of semantic or sentiment features from text
  • Image (*)
    • Image preprocessing such as loading, resizing, and normalization if images
    • Image featurization, including industry-standard pre-trained ImageNet neural models, such as ResNet and AlexNet

We should change the roadmap to indicate that further text/NLP techniques like pre-trained WordEmbedding models, improvements to tokenization, etc. are on the roadmap, whereas text handling, in the form of n-grams, already exists.

Activity

  1. jwood803 commented on Jun 20, 2018

    @jwood803
    Contributor

    Apologies, I believe that's my fault for mentioning that in the StackOverflow answer. Thanks for clarifying, though!

    I can play around with it and see if I can come up with a sample to add to the samples repository to help guide folks that those things exist.

  2. added this to the 0918 milestone on Sep 4, 2018
  3. added a commit that references this issue on Aug 22, 2019
  4. ghost locked as resolved and limited conversation to collaborators on Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions