Bernhard B.

> Being able to parse properties from a label string (“small toy red car”) would be perfect, but might be difficult because of natural language issues (eg ‘glass’ being both...

totally agreed. We definitely need to find a way to solve that. I think in general the system is expressive enough to deal with that type of problem. The question...

that would indeed be awesome. I think the most important thing is to get the foundation right. If we find a format that is expressive enough we can build simplifications...

like that! Although I think the problem stays the same: In order to parse the semantics we probably need static lists. Otherwise it will probably be too complicated to reliably...

Thanks a lot for all the examples! I was thinking a lot about the problem scope lately and those examples really help to get a better understanding :) After playing...

> ... so what I imagined without free labelling was a “pipeline” concept.. we’d gradually unlock domains, and prioritise serving images from the domains whose labels were more comprehensive .....

you raised some vaild points here. The pickup truck is indeed an example where my labels/properties approach would fail (or at least needs some adaption) What I personally like most...

that's a nice one - like that! There are probably a few changes needed in the sourcecode to support such a mode, but I think it should be doable. :)...

After thinking about it again (yeah, sometimes sleep helps a bit), your arguments make more sense to me. You are right, there are some (long term) changes needed in order...

> The problem with the current 'goto' is at the moment you click, the labels you just added aren't yet registered as tasks (as far as i can tell) .....