On Sat, 13 Nov 2004 14:09:25 +0000, Graham <[EMAIL PROTECTED]> wrote: > On 13 Nov 2004, at 11:07 am, Danny Ayers wrote: > > > > with the user agent probably defaulting the label value to the term > > value > > > term mandatory: > > 0. false > > 1. true (current) > > > > scheme mandatory: > > 0. false (current) > > 1. true > > > > label mandatory: > > 0. false (current) > > 1. true > > Maybe I'm biased because of the kind of product I work on, but I'd > think the most import part is the label to show the user, and being > able to relate back to a vocabulary is a secondary concern. I wouldn't > want to default to showing term, since it may well be a number or a > URI.
Yep, sure - forget "probably defaulting", that would be implementation-specific. But do you think the optional/mandatory setup needs rearranging? The reason for giving term super-extra-powers was that it should, in principle at least, be possible to get hold of a useful label given the (scheme+)term, but not necessarily the other way around. What does your product suggest? Cheers, Danny. -- http://dannyayers.com
