On Fri, Sep 9, 2016 at 4:29 PM, Peter Klügl <[email protected]> wrote:
> > Am 09.09.2016 um 15:59 schrieb Joern Kottmann: > > If you merge the type systems of the components you want to use you end > up > > with > > a huge mess of a merged type system and you have to do type system > > conversions > > between the AEs. > > Why do you end up with a huge mess? All is fine if everyone uses their > own namespaces, as it is with java classes. If you combine many java > libraries you also get a lot of classes. > I know that it works, but this doesn't change the fact that I end up with a type system which is the result of merging multiple type systems. And that means that more or less very similar things are duplicated, e.g. different annotations to represent tokens, sentences, etc. Why do I need to have more or less the same type multiple times? In my opinion, if you get beyond simple type systems, you cannot convert > the types on the fly. You need some knowledge about the conversion, > e.g., implemented in a converter. This can be a performance problem... > Yes, and that is the worst thing, I am burdened to understand the merged together type system to then write components which can translate between the types. Jörn
