Wikidata:Property proposal/has visual representation

has visual representation

Originally proposed at Wikidata:Property proposal/Generic

Withdrawn

Description	what the markup element is typically visually represented as
Data type	Item
Example 1	em (Q94100297) → italic (Q344098)
Example 2	strong (Q94100299) → boldface (Q19360705)
Example 3	i (Q94100343) → italic (Q344098)
Example 4	b (Q94100344) → boldface (Q19360705)
Example 5	s (Q94100302) → strikethrough (Q3500439)
Example 6	hr (Q94100267) → horizontal line (Q13144729)
Example 7	ul (Q94100277) → bulleted list (Q115204371)
Example 8	ol (Q94100275) → numbered list (Q115204416)
Example 9	progress (Q94100423) → progress bar (Q762308)

Motivation

There does not appear to be an existing property suited for these relationships.

Note that using has use (P366) for this would be very much wrong since you should use elements for their semantic meaning and explicitly not their common representation.

E.g. hr (Q94100267)has use (P366)thematic break (Q115204565) and hr (Q94100267)has visual representationhorizontal line (Q13144729)

--Push-f (talk) 09:50, 14 November 2022 (UTC)[reply]

Discussion

WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.. --Push-f (talk) 09:52, 14 November 2022 (UTC)[reply]
Comment I find numerous examples problematic in this proposal. For example, hourglass (Q179904) is an object/device that I would argue is better modeled as hourglass (Q179904)symbolizes (P4878)waiting (Q16944487) (I think this is the closest item existing for "short term expectation (Q1362683)"). throbber (Q1447854) is subclass of (P279) wait cursor (Q115203937). i (Q94100343) and b (Q94100344) are manifestation of (P1557) (or another property to denote symbolism of?) emphasis (Q65044042). ol (Q94100275) is a manifestation of (P1557) sequence (Q133250) etc. I'm not seeing the need for a computer UI-specific property and think it'd be best to consider physical UI items such as slider (Q47450667) and control knob (Q16061674) which also have meanings. For example, a vertical (up/down) slider (Q47450667) usually has a meaning of maximum as the top position, minimum as the bottom position and counter-clockwise for control knob (Q16061674) means less/lower and clockwise means more/higher. For text, there are a wide range of options for conveying emphasis including size, colour, letter spacing and physical-world-only options such as choice of material (reflectivity). --Dhx1 (talk) 13:05, 14 November 2022 (UTC)[reply]
I think an hourglass (Q179904) rather symbolizes "passage of time" in general than waiting (Q16944487) in specific, but I agree that this would be better modeled with a "symbolized by" property (which would be the inverse property of symbolizes (P4878)), so I have dropped my last example from this proposal, reducing the scope of this proposed property to the typical visual representations of markup elements.

throbber (Q1447854) is certainly not a subclass of wait cursor (Q115203937) because they are commonly just placed on the page (as opposed to replacing the cursor icon).

I also strongly disagree with HTML elements being manifestations of their visual representation: they are used for such manifestations but the concept of an HTML element is not such a manifestation by itself.

So I am still seeing the need for a computer GUI-specific property, since the properties you mentioned don't seem adequate. In regards to markup elements I think their typical visual representation is very much of interest since markup elements are often misused for their visual representation as opposed to using them for their intended semantics. Denoting these relationships in Wikidata would allow the querying of such problem zones (e.g. b (Q94100344) and strong (Q94100299) both being typically visually represented as boldface (Q19360705)). --Push-f (talk) 16:20, 14 November 2022 (UTC)[reply]
Withdrawn in favor of using Xdepicted by (P1299)Ynature of statement (P5102)often (Q28962312) .--Push-f (talk) 12:28, 27 November 2022 (UTC)[reply]