Property talk:P4102
Jump to navigation
Jump to search
Documentation
Atlas of Hillforts ID
identifier in the Atlas of Hillforts database
identifier in the Atlas of Hillforts database
[create Create a translatable help page (preferably in English) for this property to be included here]
Item “instance of (P31): hillfort (Q744099), promontory fort (Q92086), partial contour fort (Q31028314), contour fort (Q28045079), marsh fort (Q31028965), multiple enclosure hillfort (Q31029044), level terrain fort (Q31028835), hillslope fort (Q31028695)”: Items with this property should also have “instance of (P31): hillfort (Q744099), promontory fort (Q92086), partial contour fort (Q31028314), contour fort (Q28045079), marsh fort (Q31028965), multiple enclosure hillfort (Q31029044), level terrain fort (Q31028835), hillslope fort (Q31028695)”. (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/P4102#Item P31, search
List of violations of this constraint: Database reports/Constraint violations/P4102#Format, hourly updated report, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4102#Item P17, hourly updated report, search, SPARQL
Item “located in the administrative territorial entity (P131)”: Items with this property should also have “located in the administrative territorial entity (P131)”. (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/P4102#Item P131, search, SPARQL
Type “hillfort (Q744099)”: item must contain property “instance of (P31)” with classes “hillfort (Q744099)” 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/P4102#Type Q744099, 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/P4102#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): 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/P4102#Scope, SPARQL
Expand "instance of" constraint
[edit]@Fralambert: Thanks for putting in place the constraints on this property. How do we change it so that each item has to be an instance of hillfort or a subclass of hillfort? Most hillforts in Wikidata have instance of (P31) promontory fort (Q92086) or a similar subclass. Is it possible to express the constraint so that these do not register as a constraint violation? Thanks in advance for any help, MartinPoulter (talk) 11:23, 17 January 2018 (UTC)
- I added a corresponding type constraint. If you want to monitor P31 values, you could keep the item constraint. If you don't, it could be deleted.
--- Jura 11:47, 17 January 2018 (UTC)
Categories:
- United Kingdom-related properties
- Ireland-related properties
- Isle of Man-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with constraints on items using them
- Properties with format constraints
- Properties with constraints on type
- Properties with entity type constraints
- Properties with scope constraints