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] proposal: new attribute 'geofeed:'
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] proposal: new attribute 'geofeed:'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Wed Oct 7 16:19:59 CEST 2020
On Wed, Oct 07, 2020 at 03:43:33PM +0200, Horváth Ágoston János wrote: > An interesting proposal, but merging an external data set with RIPE > Database arises some questions: > > - RIPE Database is set up to contain hierarchical data already. With this > proposal, we would take some of this data outside the database in a manner > that does not guarantee consistency with the database itself. I don't think that is what is happening, this is more analogous to "abuse-mailbox:". The value contains an email address (which is an entrypoint outside the database, and interacting with the entrypoint is outside the scope of this working group). The "geofeed:" attribute is a pointer to elsewhere, and what a data consumer wants to do with that information is up to them. Kind regards, Job
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] proposal: new attribute 'geofeed:'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]