Property talk:P11424

Documentation

• Start a query
• Current uses
• Statistics by class
• List of values
• List of qualifiers
• Count

service options
options for eating at a restaurant, café, etc

Represents	service option (Q115957529)
Data type	Item
Domain	restaurant (Q11707)
Allowed values	take-out (Q154383), drive-through (Q14253958), online booking system (Q57496985), dine-in (Q115734959), online ordering (Q115734960) or food delivery service (Q10932402)
Example	SOJO (Q28804296) → dine-in (Q115734959)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties By value of property Most statements Fewest statements Most sitelinks Most linked wikis Total of sitelinks on items Most identifiers Fewest identifiers Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Database reports/Constraint violations/P11424 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 4 Main statement 3 75% of uses Qualifier 1 25% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Scope is as main value (Q54828448): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P11424#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P11424#Entity types

Type “restaurant (Q11707)”: item must contain property “instance of (P31)” with classes “restaurant (Q11707)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P11424#Type Q11707, SPARQL

One of take-out (Q154383), drive-through (Q14253958), online booking system (Q57496985), dine-in (Q115734959), online ordering (Q115734960), food delivery service (Q10932402): value must be one of the specified items. Please expand list if needed. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P11424#One of, values statistics, search, SPARQL

online booking system (Q57496985) and online ordering (Q115734960) do not fit the description

I see 2 semantics or definitions being squashed together in the Allowed Values:

1. Ways (Systems) to place an order through a restaurant: drive-through (Q14253958) online booking system (Q57496985), dine-in (Q115734959) or online ordering (Q115734960)
2. Ways to eat food from a restaurant: take-out (Q154383), dine-in (Q115734959), and perhaps drive-through (Q14253958).

But the property's definition does say only "options for eating", which should be only the 2nd values?

How do others view this? Do we update the property definition slightly to include both definitions? -- Thadguidry (talk) 06:05, 4 January 2023 (UTC)

I think we should update the description. No need to limit this to restaurants. -wd-Ryan (Talk/Edits) 16:11, 4 January 2023 (UTC)