You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Adam Lally (JIRA)" <ui...@incubator.apache.org> on 2006/11/21 17:19:03 UTC
[jira] Created: (UIMA-51) Add version number to XCAS (or maybe to
CAS built-in typesystem?)
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
[jira] Closed: (UIMA-51) Add version number to XCAS (or maybe to
CAS built-in typesystem?)
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Lally closed UIMA-51.
--------------------------
No review necessary.
> Add version number to XCAS (or maybe to CAS built-in typesystem?)
> -----------------------------------------------------------------
>
> Key: UIMA-51
> URL: https://issues.apache.org/jira/browse/UIMA-51
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Adam Lally
> Assigned To: Eddie Epstein
> Priority: Minor
> Fix For: 2.1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-51) Add version number to XCAS (or maybe to
CAS built-in typesystem?)
Posted by "Tong Fin (JIRA)" <ui...@incubator.apache.org>.
[ 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
[jira] Resolved: (UIMA-51) Add version number to XCAS (or maybe to
CAS built-in typesystem?)
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Lally resolved UIMA-51.
----------------------------
Resolution: Fixed
Assignee: Eddie Epstein (was: Adam Lally)
XCASes now will have root tag <CAS version="2">
> Add version number to XCAS (or maybe to CAS built-in typesystem?)
> -----------------------------------------------------------------
>
> Key: UIMA-51
> URL: https://issues.apache.org/jira/browse/UIMA-51
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Adam Lally
> Assigned To: Eddie Epstein
> Priority: Minor
> Fix For: 2.1
>
>
> 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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (UIMA-51) Add version number to XCAS (or maybe to
CAS built-in typesystem?)
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Lally updated UIMA-51:
---------------------------
Fix Version/s: 2.1
Assignee: Adam Lally
Doing this now, since we realized we needed to add a getSupportedXCasVersions to our Vinci services anyway (UIMA-216). The version number will be "2".
In response to Tong's comment, I think tools will need a mapping in any case. If we write the current framework version number into the XCAS, that will not solve anything. Say you are running on v2.1 and you get an XCAS that says version="3.0". Does that mean it's compatible? We may or may not change the XCAS format when we relese UIMA 3.0, there's no way to know now.
I think it's better to have a different version number. That way if UIMA 3.0 still generates the same XCAS format, it will still write verison="2" at the top of it.
> Add version number to XCAS (or maybe to CAS built-in typesystem?)
> -----------------------------------------------------------------
>
> Key: UIMA-51
> URL: https://issues.apache.org/jira/browse/UIMA-51
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Adam Lally
> Assigned To: Adam Lally
> Priority: Minor
> Fix For: 2.1
>
>
> 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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira