lace_trim implications

BUR #3428 has been approved by @evazion.

Currently there is no umbrella tag to search for all lace-trimmed clothes and accesories in general, there is a lace trim tag, but it's extremely underused because so far only lace-trimmed choker implies it

EDIT: The bulk update request #3428 (forum #172521) has been approved by @evazion.

Fur trim and ribbon trim are already used as umbrella tags so I don't see why lace trim shouldn't do the same, +1.

Many of these tags currently imply lace instead. We need to decide whether they should imply lace or just lace trim, and whether lace trim should imply lace.

In topic #14098 it was suggested that lace should be reserved for clothing made entirely of lace. There's a difference between lace-trimmed bra and lace bra, which implies there should be a difference between lace trim and lace. This would mean removing all the lace-trimmed_* -> lace implications, renaming lace to lace clothing, then trying to remove all the lace-trimmed_* tags from lace clothing. Alternatively we could just have lace trim imply lace, but that raises the question of why have lace trim if we already have lace as the umbrella tag.

evazion said:

Many of these tags currently imply lace instead. We need to decide whether they should imply lace or just lace trim, and whether lace trim should imply lace.

In topic #14098 it was suggested that lace should be reserved for clothing made entirely of lace. There's a difference between lace-trimmed bra and lace bra, which implies there should be a difference between lace trim and lace. This would mean removing all the lace-trimmed_* -> lace implications, renaming lace to lace clothing, then trying to remove all the lace-trimmed_* tags from lace clothing. Alternatively we could just have lace trim imply lace, but that raises the question of why have lace trim if we already have lace as the umbrella tag.

I think the former option is best because as you said, there is a noticeable difference between a bra with a lace trim and one made out of lace.

+1 to keeping lace and lace_trim separate.

Yeah, there should be a distinction for things made entirely out of lace and things mde out of regular fabric which just so happen to have lace trims. Compare post #2857779 (lace_skirt with regular frills) and post #3731932 (solid skirt with lace trim)

topic #14104 was the follow up to the decision in topic #14098... but never got approved.

What about having a general lace_(material) tag and separate lace_clothing (for clothes made entirely out of lace) and lace_trim tags?

BUR #3549 has been approved by @evazion.

remove implication lace-trimmed_legwear -> lace
remove implication lace-trimmed_shirt -> lace
remove implication lace-trimmed_swimsuit -> lace
remove implication lace-trimmed_kimono -> lace
remove implication lace-trimmed_bikini -> lace
remove implication lace-trimmed_panties -> lace
remove implication lace-trimmed_gloves -> lace
remove implication lace-trimmed_ribbon -> lace
remove implication lace-trimmed_dress -> lace
remove implication lace-trimmed_skirt -> lace
remove implication lace-trimmed_bra -> lace

Removing lace trim to lace implications as per discussion.

EDIT: The bulk update request #3549 (forum #173552) has been approved by @evazion.

The bulk update request #3549 (forum #173552) has been approved by @evazion.

The bulk update request #3428 (forum #172521) has been approved by @evazion.

BUR #3550 has been rejected.

create alias lace -> lace_clothing

Rename lace to lace clothing to clarify that it should only be used for clothing made entirely of lace, not just for clothes that have lace trim. This will require a lot of cleanup of the lace tag.

EDIT: This bulk update request is pending automatic rejection in 5 days.

EDIT: This bulk update request has been rejected because it was not approved within 60 days.

EDIT: The bulk update request #3550 (forum #173555) has been rejected by @DanbooruBot.

Mexiguy said:

What about having a general lace_(material) tag and separate lace_clothing (for clothes made entirely out of lace) and lace_trim tags?

We could do this, but it adds an extra tag to every lace clothing and lace trim post basically just to save you the trouble of doing ~lace_clothing ~lace_trim to find all-things-lace. I don't think it's really worth the tag bloat.

evazion said:

Rename lace to lace clothing to clarify that it should only be used for clothing made entirely of lace, not just for clothes that have lace trim. This will require a lot of cleanup of the lace tag.

Just FYI, this will also leave us without a way to tag lace objects other than clothing. It'll be a lot harder to search for other lace fabrics like the lace tablecloth in post #1121020, the lace curtains in post #2664247, the cloth over the cabinet in post #2745386, etc. Or is this usage too trivial to justify the existence of one more tag?

iridescent_slime said:

Just FYI, this will also leave us without a way to tag lace objects other than clothing. It'll be a lot harder to search for other lace fabrics like the lace tablecloth in post #1121020, the lace curtains in post #2664247, the cloth over the cabinet in post #2745386, etc. Or is this usage too trivial to justify the existence of one more tag?

That would be another advantage of having a lace_(material) tag - in which case the above should be rejected and replaced with an alias from lace to lace_(material) - the lace_clothing would need to be created from scratch. In theory these should then be findable with lace_(material) -lace_clothing -lace_trim

On the other hand if the above alias goes ahead these items would then have to be manually removed from the lace_clothing tag, and then become unsearchable.

Yeah I think it would be a better idea to have al lace_* clothes tags imply lace_clothing instead of lace first and then rename lace to lace_(material) and have both lace_trim and lace_clothing imply it

This bulk update request is pending automatic rejection in 5 days.

This bulk update request has been rejected because it was not approved within 60 days.

The bulk update request #3550 (forum #173555) has been rejected by @DanbooruBot.