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] AS-NULL
- Previous message (by thread): [db-wg] AS-NULL
- Next message (by thread): [db-wg] AS-NULL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Tue Dec 16 09:51:49 CET 2014
Nigel Titley wrote: > > On 15/12/14 16:26, Nick Hilliard wrote: > >> On 15/12/2014 16:13, Job Snijders wrote: >> >>> Can you elaborate on the use of AS-NULL? Isn't it common place to use >>> something like "NOT ANY"? >> >> "NOT ANY" is not the same as AS-NULL - they're not interchangeable. >> >> AS-NULL is a convenience placeholder token for where might be a need to >> have an empty as-set. My particular itch today involved needing to >> use an >> AS-SET of some form, but where the contents didn't particularly >> matter. It >> was more convenient to use an empty set rather than a set with some >> members >> in it because that gave an element of semantic consistency. >> >> There are other similar sets in the various irrdbs, e.g. AS-EMPTY >> occurs in >> RADB. This suggests that there is at least one other person in the world >> who needs this sort of construct. >> > I don't see any particular problem with the NCC creating and owning such > an empty set Same here, in principle, but... After having a look at some RFCs I'd suggest to rather go for an AS-EMPTY, as the use of AS0 (AS zero or null) seems to have some semantics attached. I may easily be wrong. :-) Wilfried > Nigel
- Previous message (by thread): [db-wg] AS-NULL
- Next message (by thread): [db-wg] AS-NULL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]