© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Thanks, that helps. Seeing it from dconf's perspective, that makes sense. Still, I can't stop myself thinking how frequent name collisions really are, and if there aren't alternative ways to avoid them, perhaps without throwing out all of the structure. Encouraging vendor sub-domains in apps, e.g. /apps/gnome/, /apps/ubuntu/, comes to mind. Projects without vendors would still be tolerated to stay in apps until a collision forced them to move.
The difficulty for Onboard is that there is neither vendor nor dedicated (internet) domain name (owned by us) and I can't tell if there will be either in the future. For now we're just a bunch of volunteers and we'd have to make both up out of thin air. Hence perhaps "/org/onboard". If someone registered that domain _and_ installed a colliding schema, we'd have to work it out or possibly move - like we have to right now...
Ryan, is this acceptable for you too? Francesco, Gerd for you?
Paths and schema names may be different entities, but aren't they both in danger of collisions? Would it really help to keep them not in sync?