The bulk update request #7424 is pending approval.

Reason: https://en.wikipedia.org/wiki/Low-rise_(fashion)#
https://en.wikipedia.org/wiki/Low-rise_pants

Low-rise is a distinct type of bottomwear that are essentially the opposite of high waisted bottomwear (a tag that could also use a standardization BUR, and the fashion standard name for which seems to be high-rise, which would be nicely consistent with this BUR, but that's for after this gets approved).

Although, unlike its high waist rival, low-rise is basically nonexistent in tags. Not without some attempts to tag it here and there however, as reflected in my BUR with some stray low-usage tags. Hell, low-cut_jeans is a tag with multiple aliases and an implication, yet only has 4 uses.

Basically, it should/could be populated, I would like to populate it, but the biggest problem is that the name is both not very well known and not standardized, leading to those scattered tags and poor usage like I mentioned.
I mean, I like the look, Marina from Splatoon iconically wears low-rise bottomwear in all of her outfits and she has 2k posts here on e6. That's what led to this BUR. Danbooru's lowleg tag has over 16k uses too, so there's definitely room for usage.

As for how this would be defined: "A type of bottomwear that sit low on, or below, the hips" from Wikipedia, with an additional "enough for the shape of the pelvic bones to be visible" should be specific enough.

The bulk update request #7425 is pending approval.

Reason: Part 2

You'll need to unalias and unimply the low-cut_jeans first, otherwise that'll block the BUR

Hell, low-cut_jeans is a tag with multiple aliases and an implication, yet only has 4 uses.

The aliases and implications were from the usual suspect topic #27327

"Low-rise" honestly doesn't sound very obvious what it's meant for. I'm aware of "high-rise" as a term for skyscrapers and other tall buildings, which causes me confusion over what "low-rise" is intended to mean if not smaller buildings.

snpthecat said:
You'll need to unalias and unimply the low-cut_jeans first, otherwise that'll block the BUR
The aliases and implications were from the usual suspect topic #27327

I initially wrote that but thought update would've done it automatically, thanks for telling me. Hopefully I untangled it properly.

watsit said:
"Low-rise" honestly doesn't sound very obvious what it's meant for. I'm aware of "high-rise" as a term for skyscrapers and other tall buildings, which causes me confusion over what "low-rise" is intended to mean if not smaller buildings.

Yeah that's the thing, there just isn't a term for it that's well known and recognizable by people. The only other candidate, unless I'm missing something obvious, would be "low-cut" and it isn't better. That's why I'm going with what Wikipedia and a bunch of fashion websites use (I've looked around and it's the most common term I've seen).
"Lowleg" is a Japanese term and "low-waist" as an opposite of "high-waist" just makes no sense as it is placed low on the hips if anything. So unless someone can think of something better, this is the best word for it.

yand said:
I initially wrote that but thought update would've done it automatically, thanks for telling me. Hopefully I untangled it properly.

mass update just shifts posts, and if you want to port aliases and implications directly you'll have to make an alias request instead of a BUR

Edit: Did the unalias and unimplication get added after i made my earlier message? In that case the mass update can be changed to an alias in the second BUR since the BTR would be handled after the first is approved

Edit 2: If we're porting over aliases from the low-cut_jeans and low-leg_panties, then we'll need the following followup BUR (after the first has passed)
alias low_cut_jeans -> low-rise_jeans alias lo-cut_jeans -> low-rise_jeans alias lo_cut_jeans -> low-rise_jeans alias lowleg_panties -> low-rise_panties

snpthecat said:
mass update just shifts posts, and if you want to port aliases and implications directly you'll have to make an alias request instead of a BUR

Edit: Did the unalias and unimplication get added after i made my earlier message? In that case the mass update can be changed to an alias in the second BUR since the BTR would be handled after the first is approved

Added after. Changed the update to an alias as you suggested.

Edit for Edit 2: I can't do that because I get Error: Antecedent name has already been taken for each of them (before you ask, yes I'm doing it in the Part 2 BUR), it's what stopped me from adding them before and I assumed this is what you were talking about when you said to "make an alias request instead of a BUR".

Isn't this just sagging?