Clothing attributes

Often the attribute of a clothing is called the type of clothing in contemporary speech. This is a common gotcha when it comes to tagging pictures. Let's examine the tag frills which is common on the boorus. The tag frills could be used when any form of frills appears inside the picture. This could be on a frill curtain, the neck frills of an animal or a frilled apron. Only one of these is clothing. Hence when we want to be explicit we assign clothing:frilled apron .

This is one of the benefits of the clothing: namespace for clothing enthusiasts. It lets them search and tag pictures with clothing specifically. If they did a general search on a big database only running frills they may end up with results of neck-frilled lizards and lord knows what kind of abominations instead of lovely clothes. It also lets them do a wildcard search on clothes insides the namespace containing the desired attribute e.g. clothing:frill*.

"Would it not be easier to search (and faster too) to parent all of those to clothing:frills which is then also parented to un-namespaced frills? I feel like the clothing:frilled apron tag is just a nested namespace in disguise. This could then be done for every attribute. Think clothing:seethrough, clothing:silk, clothing:red (though tagging clothes colours may be a bit out there I feel it diplays the point well)

It becomes especially problematic when you have say a frilled silk dress. Would you then tag clothing:frilled silk dress or clothing:silk frilled dress? (don't even get me started on a colour as well.) There are multiple options, either you limit to one sub-namespace: (there would be a lot of parents but with a somewhat managed list of attributes that could be automated) clothing:silk dress (parent of: clothing:silk, clothing:dress) clothing:frilled dress (parent of clothing:frills, clothing:dress)

Or you decide on an order (like how we did with X on Y tags for actions) I don't like this due to being harder to search (as seen above) and being harder to remember which is right. What could be neat with this is to have the large tower of attributes sorted by alphabet which you parent out into smaller towers, though that would be hell to maintain(even if it would please my autism brain) (and it would make for weird tag lists like):

clothing:frilled red dress

clothing:red dress

clothing:frilled dress

clothing:dress

clothing:frills

clothing:red (maybe too much to also do this lmao)

There may be more options for this as well, but I prefer the 'one sub-namespace' option the most."

-from matjojo