Hi Regina, On Mon, Feb 07, 2022 at 08:55:10PM +0100, Regina Henschel <rb.henschel@xxxxxxxxxxx> wrote: > I have discussed the problem with the OASIS TC today. Their advise is, to > not use Boolean as data type but a string and have namespaced values. That > way it is more flexible in allowing further different ways to implement a > 'metal' rendering. > So I will change that. > > The attribute itself will be with prefix 'loext' till it is integrated in > ODF. But what namespace prefix (and associated namespace) should I use for > the value? I think, a meaningful prefix would be "loext" or "drawooo". My understanding is that we try to standardize on "loext" for all new ODF extensions, so that looks like a better option. > And a second question is the data type of the internal (and API) property. > In the current state of the patch it is "MetalColored" with data type > Boolean. If you have an ODF attribute with a number of possible values, then that could be an enum internally and a set of constants at the UNO API level, I guess. (enum at the UNO API level would be nice, but then you'll have trouble extending that.) 'git grep constants offapi' can give you examples. Regards, Miklos