create implication open_bikini -> bikini
create implication open_blazer -> blazer
create implication open_blouse -> blouse
create implication open_cardigan -> cardigan (EDIT - exists)
create implication open_coat -> coat (EDIT - exists)
create implication open_dress -> dress (EDIT - exists)
create implication open_hoodie -> hoodie
create implication open_jacket -> jacket
create implication open_kimono -> kimono (EDIT - exists)
create implication open_robe -> robe
create implication open_shirt -> shirt (EDIT - nontrivial and not sure if wanted - see discussion below)
create implication open_shorts -> shorts
create implication open_skirt -> skirt
create implication open_vest -> vest

create implication open_bikini -> open_clothes
create implication open_blazer -> open_clothes
create implication open_blouse -> open_clothes
create implication open_cardigan -> open_clothes
create implication open_coat -> open_clothes (EDIT - exists)
create implication open_dress -> open_clothes
create implication open_hoodie -> open_clothes
create implication open_jacket -> open_clothes (EDIT - exists)
create implication open_kimono -> open_clothes
create implication open_robe -> open_clothes (EDIT - exists)
create implication open_shirt -> open_clothes (EDIT - exists)
create implication open_shorts -> open_clothes
create implication open_skirt -> open_clothes
create implication open_vest -> open_clothes

Link to request

Please note that I've autogenerated this list (by taking list of open_* tags and comparing it with data from tag group:attire).

Some (maybe majority) of these implications already exist, but some doesn't!
I was too lazy to eliminate existing ones from the request, as I think that Danbooru will automatically noop redundant ones anyway (sorry if I'm wrong - I can script this too if there is a need).
EDIT: So I was wrong here. Deleted redundant ones.

So now rationale:
For the first part it's obvious by definition - open_<foo> implicates <foo>.

For the second part (open_<foo> -> open_clothes) I'm not actually sure - wiki for open_clothes says:

This implies that nothing is being worn underneath aside from underwear.

The question is whether open_* tags implies the same.
- Some of them (like open shirt, open_coat) seem to imply that.
- Some other ones (like open_jacket) - not so much (but there already is implication for this one).
- Some like open_vest or open_blazer doesn't also seem to imply that and there are no existing implications for them.

open_shirt wiki says "shirt" or "blouse" and may be used with a variety of other unnamed upper body clothes.

S1eth said:

open_shirt wiki says "shirt" or "blouse" and may be used with a variety of other unnamed upper body clothes.

If we don't want to change that, we can excludecreate implication open_shirt -> shirt
If we want to [partially] change that, then we can try to do something like that:
mass update open_shirt -shirt bolero -> bolero open_bolero mass update open_shirt -shirt blouse -> blouse open_blouse mass update open_shirt -shirt bustier -> bustier open_bustier mass update open_shirt -shirt crop_top -> crop_top open_crop_top mass update open_shirt -shirt camisole -> camisole open_camisole mass update open_shirt -shirt corset -> corset open_corset mass update open_shirt -shirt dress -> dress open_dress mass update open_shirt -shirt tag_group:dress -> tag_group:dress open_tag_group:dress mass update open_shirt -shirt habit -> habit open_habit mass update open_shirt -shirt halterneck -> halterneck open_halterneck mass update open_shirt -shirt criss-cross_halter -> criss-cross_halter open_criss-cross_halter mass update open_shirt -shirt halter_top -> halter_top open_halter_top mass update open_shirt -shirt hoodie -> hoodie open_hoodie mass update open_shirt -shirt jumper -> jumper open_jumper mass update open_shirt -shirt poncho -> poncho open_poncho mass update open_shirt -shirt raglan_sleeves -> raglan_sleeves open_raglan_sleeves mass update open_shirt -shirt dress_shirt -> dress_shirt open_dress_shirt mass update open_shirt -shirt sleeveless_shirt -> sleeveless_shirt open_sleeveless_shirt mass update open_shirt -shirt striped_shirt -> striped_shirt open_striped_shirt mass update open_shirt -shirt t-shirt -> t-shirt open_t-shirt mass update open_shirt -shirt surcoat -> surcoat open_surcoat mass update open_shirt -shirt sweater -> sweater open_sweater mass update open_shirt -shirt cardigan -> cardigan open_cardigan mass update open_shirt -shirt pullover -> pullover open_pullover mass update open_shirt -shirt turtleneck -> turtleneck open_turtleneck mass update open_shirt -shirt sleeveless_turtleneck -> sleeveless_turtleneck open_sleeveless_turtleneck mass update open_shirt -shirt sweater_dress -> sweater_dress open_sweater_dress mass update open_shirt -shirt ribbed_sweater -> ribbed_sweater open_ribbed_sweater mass update open_shirt -shirt tabard -> tabard open_tabard mass update open_shirt -shirt tank_top -> tank_top open_tank_top mass update open_shirt -shirt tubetop -> tubetop open_tubetop mass update open_shirt -shirt bandeau -> bandeau open_bandeau mass update open_shirt -shirt jacket -> jacket open_jacket mass update open_shirt -shirt cropped_jacket -> cropped_jacket open_cropped_jacket mass update open_shirt -shirt blazer -> blazer open_blazer mass update open_shirt -shirt coat -> coat open_coat mass update open_shirt -shirt raincoat -> raincoat open_raincoat mass update open_shirt -shirt trench_coat -> trench_coat open_trench_coat mass update open_shirt -shirt vest -> vest open_vest mass update open_shirt -shirt sweater_vest -> sweater_vest open_sweater_vest mass update open_shirt -shirt waistcoat -> waistcoat open_waistcoat
Which is again autogenerated and would require some sanity checks.

Your edit lists assume every image on danbooru contains one person and nothing in the background which is far from the truth.

Most of those are far too specific to warrant their own tag, or even plain impossible (open t-shirt o_0). I think we don't need all this. What's the point, really? If someone really wants this specific combination of tags, he can just search open_clothes+whatever.

Log said:

Your edit lists assume every image on danbooru contains one person and nothing in the background which is far from the truth.

Well, the very first and biggest assumption of this mass update list is that we don't want to have open_shirt as a catch-all tag as it is now.
Of course a community decision would have to be made.
I just wrote it to illustrate what I mean, not to propose actually applying it.

Fair point. I tried to write those mass update queries to avoid false positives.
Unfortunately with basic account (searching only 2 [meta]tags in one query) I can't even properly sanity check them.
I'd be thankful if you could give some examples which could help improve them.

So for now - would leaving open_shirt as a catch-all tag (not implicating shirt from it) and proceeding with other implications from OP (NOT mass updates from second list) make sense?

Dariush said:

Most of those are far too specific to warrant their own tag, or even plain impossible (open t-shirt o_0). I think we don't need all this. What's the point, really? If someone really wants this specific combination of tags, he can just search open_clothes+whatever.

About "open T-shirt" - that's exactly what I meant by "sanity check". Thank you for pointing that out.
As for second list - it would require some to not create new, quite possible unneeded tags.
I'll try to split it in two by that criterion.

The problem why not just have "open_clothes + sth" is that now there are many non-shirts tagged as open_shirt..

The rest look fine on the surface, I didn't check any of them to make sure because I'm putting pixiv tags in wiki pages at the moment. The wikis should reveal if any of them are used in a different way, though.

A number of the proposed implications already exist:

• open_dress -> dress
• open_coat -> coat
• open_kimono -> kimono
• open_cardigan -> cardigan

• open_coat -> open_clothes
• open_shirt -> open_clothes
• open_robe -> open_clothes
• open_jacket -> open_clothes

Attempting to create an implication that already exists will result in an error which will stop all the other ones from going through as well. Meaning the above would need to be removed from the request to prevent duplicates if the others were going to be approved.

Toks said:

Attempting to create an implication that already exists will result in an error which will stop all the other ones from going through as well. Meaning the above would need to be removed from the request to prevent duplicates if the others were going to be approved.

Ok, corrected that.
Getting existing ones from API was easier than I was thinking (and good text editor is a half of success ;) ).

Are we looking at the final list being the OP minus strikethrough?

create implication open_bikini -> bikini
create implication open_blazer -> blazer
create implication open_blouse -> blouse
create implication open_hoodie -> hoodie
create implication open_jacket -> jacket
create implication open_robe -> robe
create implication open_shorts -> shorts
create implication open_skirt -> skirt
create implication open_vest -> vest
create implication open_bikini -> open_clothes
create implication open_blazer -> open_clothes
create implication open_blouse -> open_clothes
create implication open_cardigan -> open_clothes
create implication open_dress -> open_clothes
create implication open_hoodie -> open_clothes
create implication open_kimono -> open_clothes
create implication open_shorts -> open_clothes
create implication open_skirt -> open_clothes
create implication open_vest -> open_clothes

?

jxh2154 said:

Are we looking at the final list being the OP minus strikethrough?

Ok, so looks like all of these are done now, thanks. ;)

I may want to revisit open_shirt case sometime later, but... Maybe later.