uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hai-Son Nguyen (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-6110) UIMA & GraphQL Tool
Date Wed, 07 Aug 2019 21:36:00 GMT

    [ https://issues.apache.org/jira/browse/UIMA-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902488#comment-16902488
] 

Hai-Son Nguyen commented on UIMA-6110:
--------------------------------------

An initial step in making an interface for GraphQL is a tool to digest a type system descriptor
and produce a schema for GraphQL.

1) An issue of complexity is that the GraphQL schema requires enumerating inherited methods. 

[https://graphql.org/learn/schema/]

2 ) Since all our type system types extend Annotation (extends AnnotationBase extends Top
extends FeaturesStructureImpl)

We may want to decide on how to specify how much of the inherited methods/properties we should
limit for the schema.

 

I think it can be straight-forward to read the type system and add the fields. The accounting
of fields that are "hiding" inherited fields need to be managed during the process as a special
case. The annotation viewer already specifies a type system for use so the UI can likely be
integrated with that existing tool.

 

> UIMA & GraphQL Tool
> -------------------
>
>                 Key: UIMA-6110
>                 URL: https://issues.apache.org/jira/browse/UIMA-6110
>             Project: UIMA
>          Issue Type: Brainstorming
>          Components: Tools
>            Reporter: Hai-Son Nguyen
>            Priority: Minor
>
> To gather ideas and discuss tasks related to creating a GraphQL tool to work with UIMA.
> Initiated by Marshall's email 7/8/2019
> "...
>  
> Some time ago, we added JSON serialization to UIMA, with some complexities
> around enabling accurate representation of the complete complexities of
> interlinked UIMA features.
>  
> It strikes me that users frequently are interested in much simpler kinds of
> things, and sometimes roll their own simple json serializers of some small part
> of the CAS.
>  
> I'm wondering if we could figure out and implement some general kind of graphQL
> support, to enable users to easily spec-out and retrieve what they wanted, and
> whether or not the user community would find that of interest?
>  
> -Marshall"



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message