This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] NCC still enforcing descr: content
- Previous message (by thread): [db-wg] NCC still enforcing descr: content
- Next message (by thread): [db-wg] NCC still enforcing descr: content
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Wed Aug 12 20:31:53 CEST 2015
On Wed, Aug 12, 2015 at 08:26:09PM +0200, denis wrote: > On 12/08/2015 16:13, Job Snijders wrote: > > >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. > > I think some clarification is also needed on the future use of the "descr:" > attribute. When you say it is the same as "remarks:" you can also argue that > "address:" is the same as "remarks:". They are all attributes containing > free text values. yeah, this was just my observation. > The slight difference is that both "address:" and "descr:" are only > allowed in certain object types. Most people know what is expected to > be in an "address:" attribute and would not use it for additional > comments, even though you could. Maybe some guide lines are now needed > about what is expected in a "descr:" attribute if it is optionally > included. Any guidelines agreed could be included in documentation and > help output, for example with a '-v' query. What do you think should be in "descr:"? Do you have suggestions for new guidelines for descr:? Kind regards, Job
- Previous message (by thread): [db-wg] NCC still enforcing descr: content
- Next message (by thread): [db-wg] NCC still enforcing descr: content
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]