We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
About available languages of when defining Entity/Relation in Knowledge Studio.
I would like to request Japanese added to characters that can be used for Entities/Relations in Knowledge Studio.
(This request is strongly seek by our clients of a major cosmetics manufacturer that has expanded worldwide through our Project.)
the problem statement/pain points
When annotating in Knowledge Studio, it is required to define Entities/Relations in advance, however currently only alphanumeric characters can be used for the name. (Japanese cannot be used).
Due to this limitation, when the members who does the annotation task tries to select Entities/Relations for the document on the annotation display in Knowledge Studio, it is difficult for them to choose Entities/Relations intuitively, therefore they have to translate the name of the Entity/Relation from English to Japanese once and have to remember what each of them means before annotating.
Although the annotation process is a very demanding task, the inability to use languages other than alphanumeric characters in the names of Entities/Relations further divides the interpretation among the members, creates unnecessary tasks (a correction of incorrect Relation/Entity settings etc).
If non-alphanumeric characters (especially Japanese) can be used for Entity/Relation names, it will be possible to select Entity/ Relation in one's native language, which is expected to foster more awareness of same understanding among the members and moreover is expected to reduce the number of wrong annotations, thus reduce the annotation task load.
Do not place IBM confidential, company confidential, or personal information into any field.