#aaronpkwhy can an h-card have street-address, locality, region, etc on it when it might also have an embedded h-adr that could have the same properties?
#DanC_it's better for the author, who gets priority. it's harder for the parser, who now has 2 places to look
#tantekit's choosing to allow a more limited but simpler model for the *common* case, rather than making the common case complex for the sake of "consistency" with the complex case.
#aaronpkluckily in my case I am both the publisher and consumer since i'm using this as an internal storage mechanism :)
#tantekusually devs/programmers make the opposite decision, that is, they argue all about all the complex/edge cases, and expand/distort/generalize their solution until it covers both common cases and all those edge cases, typically resulting in something incredibly unnecessarily complex for the common case
#tantekand when asked why, the answer is always, because you might want to x (edge case / complex case)
#aaronpkinterestingly, this means that if I know the "location" property is either an h-card or an h-adr, I know I can always find a property called "locality" there
#tantekthe interesting side effect is that for common consuming code cases, things get simplified too
#aaronpkwhich actually then results in simpler consuming code
#DanC_if I had a nickel for every piece of open source software that said "you can configure it to do anything you want!" before explaining how to do the 3 most typical things...
#aaronpkDanC_: lol yeah. at this point when i hear "it can do everything" I interpret that as "it doesn't actually do anything without a lot of extra work"
#DanC_look at this pile of silicon! you can fabricate it into chips that can compute anything you want!