On 12.08.2015 21:19, Job Snijders wrote:
So are you OK with a final situation where "descr:" is optional in some objects and still mandatory in others?
If we make 'descr:' optional, i'd prefer it to be optional across the entire board.
+1
For me as operator, I think I'd like "descr:" to be a one-line description what the object is about. If an organisation has many aut-nums, it would be beneficial if there is one line which describes the differences between all those aut-nums by providing a one-line summary. Because of "org:" I can programmatically follow which organisation it belongs to, but some more meta-data might be useful.
Yes, that's why I like the "descr:", too.
As a neutral observer from operational point of view, that makes sense to me. But does that mean you would like to make the attribute 'single' instead of 'multiple' as it is now? If you make it single what would you do with objects that already have multiple lines (besides the org name)? You could convert any existing additional lines into "remarks:".
I have no particular preference whether single or multiple is better. If anything, it would be a matter of clearly documentating.
Given that "remarks:" already is multiple, it might make sense to declare "descr:" as 'single' and thus offer a clear differentiator between the two.
"descr:" - one-line optional summary what the object is about "remarks:" - the story of your life
That would work for me. Cheers, Tim