Wikidata:Property proposal/format string

format strings

format string placeholder

Originally proposed at Wikidata:Property proposal/Generic

   Not done

Description	describes which placeholder is used by values of this format string property (usually $1, which indicates that $1 has to be replaced)
Data type	String
Domain	property
Example 1	formatter URL (P1630)format string placeholder$1
Example 2	DOI formatter (P8404)format string placeholder$1
Example 3	URN formatter (P7470)format string placeholder$1

format string produces

Originally proposed at Wikidata:Property proposal/Generic

   Not done

Description	describes what a format string of this property produces when interpolated with values
Data type	Item
Domain	property
Example 1	formatter URL (P1630)format string producesURL (Q42253)
Example 2	DOI formatter (P8404)format string producesdigital object identifier (Q25670)
Example 3	URN formatter (P7470)format string producesURN (Q76497)
Example 4	ARK formatter (P8054)format string producesArchival Resource Key (Q2860403)
Example 5	road number formatter (P8498)format string producesroad number (Q3241753)
Example 6	road name formatter (P8898)format string producesstreet name (Q1640962)
Example 7	shortened URL formatter (P11136)format string producesshort URL (Q99513765)

Motivation

We currently have 12 format string properties and that number will go up as time goes on. There are however two problems with our format string properties:

1. Data consumers cannot reliably detect that a given property is a $1-placeholder-based format string property.
2. Data consumers cannot reliably infer what the string formatting produces because Wikidata item of this property (P1629) is ambiguous (e.g. road number formatter (P8498) has both road number (Q3241753) and road number prefix (Q1881659) as road number formatter (P8498) values).

So I propose the introduction of a #format string placeholder property to address #1 and the introduction of a #format string produces property to address #2.

Note that #format string produces is very similar to the existing class of non-item property value (P10726) ... however there is an important semantical difference:

• Pclass of non-item property value (P10726)C ∧ APB ⇒ Binstance of (P31)C

whereas

• Pformat string producesC ∧ APB ⇒ format_P(B, V)instance of (P31)C

In fact for all of these format string properties, class of non-item property value (P10726)format string (Q3748135) can be stated ... the class produced by the format string can however differ between the properties as shown in the above examples.

--Push-f (talk) 09:30, 16 December 2022 (UTC)

Discussion

• julle (talk) wd-Ryan (talk/edits) Arlo Barnes (talk) WT20 (talk) Zblace (talk) applsdev RampantSpirit (talk)
  Notified participants of WikiProject Websites WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. --Push-f (talk) 09:32, 16 December 2022 (UTC)
•  Support This makes sense. See also, Property talk:formatter URL#Name change -wd-Ryan (Talk/Edits) 15:25, 16 December 2022 (UTC)
• @User:Push-f, could you provide a single example where "format string placeholder" != "$1"? --Lockal (talk) 08:57, 16 March 2023 (UTC)

  general property-based URL formatter (P8183) Midleading (talk) 04:21, 23 March 2023 (UTC)

•  Oppose "format string produces". A property that will only be used 12 times is far too specialised. I'm not sure why product, material, or service produced or provided (P1056) couldn't be expanded to include properties. - Nikki (talk) 23:17, 19 March 2023 (UTC)
• @Wd-Ryan, Nikki, Push-f:  Not done, no consensus of proposed property at this time based on the above discussion. Regards, ZI Jony ^(Talk) 05:03, 25 January 2024 (UTC)