📝Ben Reiniger wrote on Tue, Jul 3, 2018 03:06 PM UTC:
chess+compounds was working before; taginfo.php was already decoding urls.
Suggest that semantic URLs use underscores for spaces instead? They seem easy to understand as replacing a space, less likely to be actually used in a tag name, and easy to replace in taginfo after decoding.
I think we need to come to a decision on tag relationships. I think three things have been floated:
using TagParent in the database to build a treelike hierarchy
allowing tags to have tags via their taginfo page (this gets away from the idea that only games will have tags)
no formal relationship, just using the tag names (as I've done so far, with the colon-separated tag names)
no relationships
I agree with Fergus that 3 isn't great. Is 1 flexible enough for what we'd want to do? Any other ideas?
Originally 1 was my intent (hence the database column TagParent). If we go that way (or something similar), how should the list of games with a parent tag be displayed? Just those with the parent tag, not any of the descendents? Or all games with the parent or descendent tags in one list? Or several lists, one for each descendent tag? (I think a list of games with the parent tag but none of the descendents could be useful, e.g. to find "unique" applications of the tag's description. Having all the lists on the one page is redundant, but perhaps useful?)
chess+compounds was working before; taginfo.php was already decoding urls.
Suggest that semantic URLs use underscores for spaces instead? They seem easy to understand as replacing a space, less likely to be actually used in a tag name, and easy to replace in taginfo after decoding.
I think we need to come to a decision on tag relationships. I think three things have been floated:
I agree with Fergus that 3 isn't great. Is 1 flexible enough for what we'd want to do? Any other ideas?
Originally 1 was my intent (hence the database column TagParent). If we go that way (or something similar), how should the list of games with a parent tag be displayed? Just those with the parent tag, not any of the descendents? Or all games with the parent or descendent tags in one list? Or several lists, one for each descendent tag? (I think a list of games with the parent tag but none of the descendents could be useful, e.g. to find "unique" applications of the tag's description. Having all the lists on the one page is redundant, but perhaps useful?)