[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 ]
denis
ripedenis at yahoo.co.uk
Wed Aug 12 20:26:09 CEST 2015
HI Job 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. 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. cheers denis > > 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 ]