On Mon, 8 Oct 2012, david@lang.hm wrote:
exactly. If we support hierarchical structures, we can use a single tag, if we make everything flat, we can reserve a prefix (ideally, a prefix that translates to a subtree name so that people who want it flat can treat it as if it's flat, people who want hierarchical can treat it as a subtree)
I would actually reserve two prefixes/subtree names
The first for the tags that are generated by the logging infrastructure
The second for a place to relocate any tags that are passed to us in a reserved space.
for the sake of argument, call these 'trusted.' and 'forged.' If someone submits something with trusted.uid, move it to forged.trusted.uid. If someone submits something with forged.uid move it to forged.forged.uid.
If the prefix is unique there is a very low chance that the resolved fields would be overwritten unintentionally.
exactly.
Now, from the discussion a couple of weeks ago, people have a real hard time with 'trusted' (arguments crop up about how much you can really trust it), so we need to pick something else.
we could do lumberjack. for trusted and beaver. for forged :-) This is a bit long, someone with more creativity can pick a couple of names.
using the terminology from the wiki page listed in the subject, these would be 'objects' instead of 'subtrees' and the character at the end would be a '!' instead of a '.'
David Lang