On 02.04.2015, at 01:37, Nick Hill <[email protected]> wrote: >> In one context, we also rely heavily on CAS addresses serving as unique >> identifiers of feature structures in the CAS. Does your implementation >> provide any stable feature structure IDs, preferably ones that are part of >> the system and not actually declared as features? > > Yes, there are various cases where an 'equivalent' of an FS address is > required (for example if the LL API is being used). In this case the id gets > allocated on the fly and will subsequently be unique to that FS within the > CAS. In many cases an FS might never have such an ID allocated (it's not > really part of the non-LL "public" APIs), but you can always 'request' one.
We are using the CAS address as IDs in the WebAnno annotation editor. When we render an annotation in the UI, this ID creates the logical connection between the visual representation and the CAS. So in this context, we basically need these IDs for all FSes and we need them to be available and stable across serialization. Is it already possible to request such an ID in your current implementation? Cheers, -- Richard
