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

Richard Eckart de Castilho commented on UIMA-3303:
--------------------------------------------------

Your suggestion implies that a type system is addressed by the import 
statement, while the initial suggestion appears to assume that type systems are 
imported by some other mechanism (e.g. uimaFIT type system detection) and then 
only certain types from these automatically imported type systems are made 
available in the script. How about this:

{noformat}
IMPORT * FROM <typesystemfile> AS <prefix> -- make all the types from 
typesystemfile available using prefix
IMPORT FROM <typesystemfile> AS <prefix> -- shorthand for command above
IMPORT <package>.* FROM <typesystemfile> AS <prefix> -- make package from 
typesystemfile available using prefix
IMPORT <package>.<type> FROM  <typesystemfile> AS <alias> -- make the specified 
type from typesystemfile available as the given alias
IMPORT <package>.* AS <prefix> -- make the specified automatically detected 
types in the specified package available as the given alias
IMPORT <package>.<type> AS <alias> -- make the specified automatically detected 
type available as the given alias
{noformat}


                
> Add a way to alias types in RUTA (e.g. "IMPORT type AS alias")
> --------------------------------------------------------------
>
>                 Key: UIMA-3303
>                 URL: https://issues.apache.org/jira/browse/UIMA-3303
>             Project: UIMA
>          Issue Type: Bug
>          Components: ruta
>            Reporter: Alexandre Patry
>
> It would be convenient to define type aliases in RUTA script.
> One scenario where it would help is when many types have the same short name:
> {{
> IMPORT com.example.a.T AS TA}
> IMPORT com.example.b.T AS TB}
> }}
> For a discussion about it, see UIMA-3292.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to