This is the point I was making, the system should be flexible enough to cater for the weird and abstract as of right - regardless of the priorities of the people that are doing the software engineering on the thing. This is almost like the pressure cylinder registration system aka the LAB/SP LAB number system. There are so many cases of SP LAB numbers issued where there was already a design approval/LAB number for that cylinder that meant the cylinders should just have been whacked with that number (ignoring the fact that it just invalidated the coating warranty on that cylinder but that's by the by). There are many cases in the LAB register of identical cylinders registered under different LAB numbers due to one or two minor differences in recordings, so the entire thing goes pear shaped as a register due to data crumples.
I can see the registry going bad to worse and ending up being useless in short time just due to the issues mentioned. As I keep saying, I'm not against the idea of a registry provided it is proven secure, is accurate, is cost effective and actually contributes to public safety and what we are seeing so far - doesn't appear to meet any of those tests just due to the way it's been done without subject matter experts involved in the design and development phases and the quality of the supporting infrastructure backing it up.
Bookmarks