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]/
[ncc-services-wg] Re: [db-wg] The New "organisation object" Proposal
- Previous message (by thread): [ncc-services-wg] The New "organisation object" Proposal
- Next message (by thread): [ncc-services-wg] Re: [db-wg] The New "organisation object" Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joao Damas
joao at psg.com
Mon Aug 25 14:34:18 CEST 2003
I think this proposal is very good. On Monday, Aug 25, 2003, at 12:27 Europe/Amsterdam, DB-News wrote: > > Dear Colleagues, > > [apologies for duplicate messages] > > Following discussions at the RIPE NCC about a new Whois Database > object, > the organisation object, we have modified the previous proposal that > you > can find at: > > http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00013.html > > The main changes from the previous proposal are: > > - a "country:" attribute is added. > - "org-type:" and "org-name:" attributes are added, and > "organisation:" > attribute is now a NIC handle, which will be automatically assigned > during the creation of the object. The motivation for this is > explained > in Section 3 of the proposal. A very welcome modification. The last thing the RIPE DB needs to get dragged into are trade mark disputes about object names. Could it be made a bit stricter and allow only for auto-generation of organisation NIC handles? > - Hierarchical names can be removed, mainly for simplicity. I got lost on this one. Do you mean "can be removed" or "have been removed"? > - Differing query results on the whois server introduced in section 5. > According to this, the relevant organisation objects are appended > to the > query results (because the organisation that holds the resource is > at > least as important as the person/role objects mentioned in the > resource object). This is good. Also being able to disable it with '-r'. Will the database enforce any restrictions on the assignment of org-types, so that new IANAs and new RIRs can't be created, with potential for introducing confusion? I think this is a good proposal for an organisation object in the RIPE Database, Joao
- Previous message (by thread): [ncc-services-wg] The New "organisation object" Proposal
- Next message (by thread): [ncc-services-wg] Re: [db-wg] The New "organisation object" Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]