Topic: [APPROVED] Valve Hardware BUR

The bulk update request #12598 is active.

mass update steam_controller -> steam_controller_(2015)
change category steam_controller_(2015) (20) -> copy
create implication steam_controller (28) -> valve_hardware (179)
create implication steam_controller_(2015) (20) -> steam_controller (28)
create implication steam_controller_(2026) (8) -> steam_controller (28)
create implication steam_machine_(2026) (6) -> valve_hardware (179)
change category valve_hardware (179) -> copy
change category steam_machine_(2026) (6) -> copy
create implication steam_frame (2) -> valve_hardware (179)
change category steam_frame (2) -> copy
create implication valve_index (12) -> valve_hardware (179)
create implication steam_deck (143) -> valve_hardware (179)
create alias steam_hardware (0) -> valve_hardware (179)
mass update valve -> valve_corporation
create implication valve_hardware (179) -> valve_corporation (9593)
change category valve_corporation (9593) -> copy

Reason: Fixup for new and old Valve hardware. Items excluded:

• Knuckles controller (reason: confusing naming, might add later)
• New VR controller (reason: unnamed)
• Lighthouse (reason: usage)
• Steam Link (reason: usage)
• Original Steam Machine (reason: usage)

Possible nicknames to add for funsies:

• alias deckard -> steam_frame
• alias gabecube -> steam_machine_(2026)

What might be nice is a valve_hardware tag as an intermediate, thoughts?

EDIT:

• updated to make steam_controller as a middle
• added valve hardware. This also serves as a generic for items that dont have a specific tag
• valve -> valve corp

TODOs:

• Should these be copy tags? xbox_controller isn't.

EDIT: The bulk update request #12598 (forum #472271) has been approved by @spe.

A tag for Steam Hardware (not Valve Hardware, apparently) to group the subject matter together sounds like a good idea to me. For the deckard and gabecube aliases I'd say see if they see any significant usage first.

If a steam_hardware tag is created to contain all of the above tags for systems and peripherals, it should imply electronics.

I was going to suggest that the Steam Deck and Steam Machine tags should imply computer. However, it looks like steam_deck is a copyright tag, and many gaming formats have one tag for copyright, plus a general tag for the actual physical devices that appear in images. (For example, playstation_2 is a copyright tag and ps2_console is a general tag, and only the latter implicates game_console.)

So to be consistent with that, does that mean that steam_machine_(2026) should be a copyright tag, and there should be another general tag for the physical device, and only the latter should imply computer?

chemistrynoisy said:
If a steam_hardware tag is created to contain all of the above tags for systems and peripherals, it should imply electronics.

I was going to suggest that the Steam Deck and Steam Machine tags should imply computer. However, it looks like steam_deck is a copyright tag, and many gaming formats have one tag for copyright, plus a general tag for the actual physical devices that appear in images. (For example, playstation_2 is a copyright tag and ps2_console is a general tag, and only the latter implicates game_console.)

So to be consistent with that, does that mean that steam_machine_(2026) should be a copyright tag, and there should be another general tag for the physical device, and only the latter should imply computer?

If we want to be consistent then steam_deck should have a subsidiary steam_deck_(device) tag created. Following this logic there should be steam_controller_(2026)_(device) tags and steam_frame_(device) tags too.

I can't really tell why there would be one tag for a console as a concept and another for the physical appearance of that console. What's the intended use case of these tags?

eightoflakes said:
A tag for Steam Hardware (not Valve Hardware, apparently)

This is kind of true. There is still a valve hardware category with them inside of it. Additionally, the Valve Index isn't technically 'Steam Hardware' (except on the support page).

create implication steam_controller_(2026) (2) -> valve (9390)
mass update steam_controller -> steam_controller_(2015)
change category steam_controller_(2015) (0) -> copy # missing

Is there any follow-up intended for this? Right now it'll just leave an empty steam_controller tag.

If we want to follow existing precedent, steam_controller should probably be used as an umbrella tag like xbox_controller (xbox_original_controller, xbox_360_controller, etc.) and playstation_controller (dualshock_1, dualshock_2, etc.)

faucet said:
Is there any follow-up intended for this? Right now it'll just leave an empty steam_controller tag.

If we want to follow existing precedent, steam_controller should probably be used as an umbrella tag like xbox_controller (xbox_original_controller, xbox_360_controller, etc.) and playstation_controller (dualshock_1, dualshock_2, etc.)

Thought crossed my mind, I will update it later when we decide on other changes

chemistrynoisy said:
If a steam_hardware tag is created to contain all of the above tags for systems and peripherals, it should imply electronics.

What if it's only a mock depiction of the system and peripherals, which clearly look like it but are clearly non-functional cardboard or paper?

eightoflakes said:
If we want to be consistent then steam_deck should have a subsidiary steam_deck_(device) tag created. Following this logic there should be steam_controller_(2026)_(device) tags and steam_frame_(device) tags too.

I can't really tell why there would be one tag for a console as a concept and another for the physical appearance of that console. What's the intended use case of these tags?

I assume it's for things like this image, which shows the console's logo (and therefore needs the brand's copyright tag), but doesn't show the device itself:

post #5968220

watsit said:
What if it's only a mock depiction of the system and peripherals, which clearly look like it but are clearly non-functional cardboard or paper?

Good point!

The bulk update request #12598 (forum #472271) has been approved by @spe.