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/db-wg@ripe.net/
[db-wg] IM contact
- Previous message (by thread): [db-wg] IM contact
- Next message (by thread): [db-wg] IM contact
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
s.steffann at computel.nl
Mon Aug 13 10:59:54 CEST 2007
Hi, > So why not go completely abstract and support an URI field, like > > URI: <role> <URI> [optional] > > Where <role> is a set of peviously defined words. This would > also allow easy extension later. > > e.g. > > URI: abuse im:icq:1234567890 > URI: sales sip:sales at isp.net > URI: info http://www.myisp.net/info/ That would indeed make putting contact info in the db very flexible. I don't think we should put the role in the URI field, because there already is a role object in the db, and two ways to specify a role will probably cause a bit of a mess. I think adding the URI field to the irt, role and person objects would be enough to structure the information. Otherwise I think this a good idea to consider. - Sander
- Previous message (by thread): [db-wg] IM contact
- Next message (by thread): [db-wg] IM contact
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]