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] 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 ]
Sander Steffann
sander at steffann.nl
Mon Jan 4 07:11:55 CET 2021
One more question after coffee: > > On deployment update any objects in the RIPE Database containing a > > "remarks: Geofeed" with a correctly formatted url into a "geofeed:" > > attribute. > > Sounds simple enough 🙂 What happens when someone (or someone's automated system) pushes an object with a "remarks: Geofeed" again? Do an automatic conversion on update? How many scripts will that break (or worse: how many scripts will get stuck in a loop because the object in the database isn't what they believe it should be, so they update it again and again and …) So maybe not do an automatic update after all, and maybe update the web based editor with a helpful "This looks like a Geofeed remark, click here to change it to a geofeed attribute" button 🙂 Cheers! Sander -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: </ripe/mail/archives/db-wg/attachments/20210104/4b61d80c/attachment.sig>
- 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 ]