You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Tong Fin (JIRA)" <ui...@incubator.apache.org> on 2006/11/25 01:33:03 UTC
[jira] Commented: (UIMA-51) Add version number to XCAS (or maybe to
CAS built-in typesystem?)
[ http://issues.apache.org/jira/browse/UIMA-51?page=comments#action_12452541 ]
Tong Fin commented on UIMA-51:
------------------------------
Tools do not care how we define the version.
But, tools need some way to know if this XCAS/XMI file can be processed by this UIMA version.
If we use yet-another-version from built-in CAS type system, we need to "publish" how it is related to the Framework being used/targetting.
> Add version number to XCAS (or maybe to CAS built-in typesystem?)
> -----------------------------------------------------------------
>
> Key: UIMA-51
> URL: http://issues.apache.org/jira/browse/UIMA-51
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Adam Lally
> Priority: Minor
>
> From version 1.x to 2.x we broke XCAS compatibility. (v2.x can read v1.x XCASes but not vice-versa.) We've been thinking we might want to have a version number on the XCAS so that we can detect an incompatibility and report a good error message.
> It occurs to me that what changed here is not the XCAS syntax, but the built-in CAS type system. In v2.x the annotation type changed (the "sofa" feature became a reference instead of an int). Also new primitive types and new array types were added.
> So perhaps the right thing to do is to have a version number on the CAS built-in type system, and dump that version number in our XCAS (and XMI) serializations.
> I'm not sure if it's right to just use the framework version number (which might lock us into a versioning scheme such as agreeing not to add new built-in types without incrementing the major version number), or having a completely separate version number just for the built-in type system?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira