Re: [netmod] Module tags

[Christian Hopps <[e-mail]>]

Juergen Schoenwaelder <[e-mail]> writes:
>> The tag is there to help identify things about the module to the users
>> of that module, as the ultimate authority on the use of this module I
>> want to be able to override that default just like I can override other
>> default values.
>>
>> Your right I can add a new tag to be used by software that I can modify,
>> but what if other software I need to use is also using the designer's
>> tag? I can only control it by removing the tag in that case.
>
> Or you break software by removing that tag. If a module says an
> implementation must set a certain tag, how can it help to remove this
> tag? Are you not breaking a part of a contract between a module and
> implementations using the module?

I don't break your software, I break my network. I bought your software
I want control over it.

>> It doesn't cost anything really to allow for this, and it provides
>> future-proofing control to the user, conversely what do we gain from
>> disallowing it?
>
> I am simply challenging you in order to better understand how people
> expect tags to be used, what it means to have type (a), (b), and (c)
> tags and why it is necessary to be able to remove type (a) and (b)
> tags. I guess it all boils down to what it really means to say in a
> module that a certain set of tags must be set, i.e., whether an
> application can rely on these tags to be set or not.

Indeed, the application should rely on those tags being set. That's
what gives me control over what the application uses or doesn't.

I'd like to hear what is gained by *not* providing the user (customer!)
this option.

Thanks,
Chris.

> /js