Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
1. What type of tags will we allow? (Should specific tags like UrlRewrite be allowed?) I would argue that urlrewrite (or perhaps more appropriately since Microsoft renders it as URL Rewrite, url-...
Answer
#1: Initial revision
> 1\. What type of tags will we allow? (Should specific tags like UrlRewrite be allowed?) I would argue that *urlrewrite* (or perhaps more appropriately since Microsoft renders it as *URL Rewrite*, url-rewrite) is actually a specific case of the more general concept of *url-rewriting*. So is, say, *mod-rewrite* (the corresponding functionality in the Apache web server). It might be beneficial to call that out in the tag name; for example, *iis-url-rewrite* and *apache-mod-rewrite* might both be subtags of a more generic *url-rewriting* tag. Someone who is looking for information relating to Microsoft IIS' URL rewriting functionality might not be interested in the corresponding feature in Apache or nginx, but someone who is interested in questions about URL rewriting *in general* might well want to see all three (and then others). The more generic *url-rewriting* tag could perhaps be used for questions which apply equally regardless of software implementation; for example, how to decide between HTTP status codes 301, 302, 303, 307 and 308. The specific example notwithstanding, then, **this type of situation in general seems like it lends itself very well to a tag hierarchy.** Specifically, it's a generic type of functionality, which is implemented differently by different software packages; and it's a type of functionality that a software developer can reasonably be expected to need to deal with.