Magnus Manske <magnusmanske(a)googlemail.com> wrote:
[...]
At the risk of over-designing, would it be worth to gather
language-independent requirements for a module/library, on the
toolserver wiki or on meta, and then keep implementations of that
standard (yes, I know, "one more standard") available on the
toolserver? At the very least, a language-neutral brainstorming might
prevent design flaws, especially with database-with-API-fallback in
mind.
It depends on what you mean by "requirement". Something
like "a library *must* provide a function normalizeLink()
with these semantics" would probably deter developers from
trying to implement it. If on the other hand there was an
algorithm "if you want to normalize links, do A, B, C, D and
E" and corresponding test cases to check compliance, I think
it would be much more inviting.
Tim