On Tue, Jul 28, 2015 at 06:01:29PM +0200, Tim Bruijnzeels wrote:
Option b: Clean up existing cases, "descr:" optional ===================================================== On the other hand if "descr:" could be optional, we would be able to do a bulk change to remove the existing organisation names from the "descr:" of objects, both for end-user resources as well as for allocations. And then leave it to the holders of these objects to modify as they please. This would be the cleanest in the sense that any remaining "descr:" would be fully maintained by the resource holders, and the one place to look for the organisation name is in the referenced organisation object.
Technically this would not be hard for RIPE NCC, but I fully appreciate that a schema change like this has potential big impact on users. That said, if there are many cases where there is no clear case for a "descr:" that is not the organisation name, then this may not be a bad option. Leaving this mandatory would then lead to descr content that is not very useful.
I've read the thread and it seems that the majority is in favor of "option B". I will yield my earlier preference for option A in favor what some in the group have argued to support option B. If you have objections against "option B", please raise them in the next few days, with arguments. I aim to discuss what has been said with the other chairs next week (or the week after if the discussion continues). Summary option B: - remove all mandatory populated 'descr:' attributes (the first descr: of an object) - change 'descr:' to be an optional attribute This change would essentially make 'descr:' and 'remarks:' the same. Kind regards, Job