I don't currently have a plan for this on the V3 branch, but I remember it.
Extending the type system after commit would require changing the way feature structures store data, to be more "flexible". This is always a tradeoff vs space/performance. There's room to innovate here, I think, to acheive a good balance (e.g. no penalty if this flexibility is not used). Adding types may take some thinking, especially in the general case where types might be inserted into the hierarchy (and therefore change the hierarchy). Extensions to arbitrary java objects is partially built into V3. An issue is how to serialize/deserialize (in our various formats) these kinds of objects. -M On 8/12/2016 5:15 AM, Richard Eckart de Castilho wrote: > Hi Marshall, > > some time back, there were discussions and ideas floating around about > > - allowing (almost) arbitrary Java objects to be used as feature values; > > - allowing additions of types and features despite the TS already being > locked. > > Are these ideas somehow on the horizon of UIMAv3? > > Do you already plan for such changes in the modifications that are presently > being > made on the v3 branch? > > Cheers, > > -- Richard
