Property talk:P7534
(Redirected from Wikidata talk:Database reports/Constraint violations/P7534)
Documentation
MIC market code
ISO 10383 market identifier code
ISO 10383 market identifier code
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “stock market (Q475000), stock exchange (Q11691), systematic internaliser (Q91437908), Approved Publication Arrangement (Q85742512), futures exchange (Q2298435), commodities exchange (Q695817)”: item must contain property “instance of (P31)” with classes “stock market (Q475000), stock exchange (Q11691), systematic internaliser (Q91437908), Approved Publication Arrangement (Q85742512), futures exchange (Q2298435), commodities exchange (Q695817)” 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/P7534#Type Q475000, Q11691, Q91437908, Q85742512, Q2298435, Q695817, SPARQL
Single value: this property generally contains a single value. (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/P7534#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (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/P7534#Unique value, SPARQL (every item), SPARQL (by value)
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/P7534#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P7534#Format, 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/P7534#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/P7534#Scope, SPARQL
Qualifiers “applies to jurisdiction (P1001), reason for deprecated rank (P2241), start time (P580), end time (P582)”: this property should be used only with the listed qualifiers. (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/P7534#allowed qualifiers, SPARQL
FIX ALLCAPS LABELS
see Help:Label (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P7534#FIX ALLCAPS LABELS
see Help:Label (Help)
Violations query:
SELECT ?item ?l WHERE { ?item wdt:P7534 []; rdfs:label ?l. FILTER( lang(?l) ="en" && REGEX(?l,"[A-Z]{4,}") ) } LIMIT 10
List of this constraint violations: Database reports/Complex constraint violations/P7534#FIX ALLCAPS LABELS
FIX ALLCAPS DESCRIPTIONS
see Help:Descriptions (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P7534#FIX ALLCAPS DESCRIPTIONS
see Help:Descriptions (Help)
Violations query:
SELECT ?item ?l WHERE { ?item wdt:P7534 []; schema:description ?l. FILTER( lang(?l) ="en" && REGEX(?l,"[A-Z]{4,}") ) } LIMIT 10
List of this constraint violations: Database reports/Complex constraint violations/P7534#FIX ALLCAPS DESCRIPTIONS
MIC Market Categories
[edit]The new MIC format has a controlled field for kind of exchange/market/facility. We need to match them to existing WD items, creating subclasses if needed.
Then record the codes as "catalog code" with qualifier "catalog=MIC". See examples:
- Approved Publication Arrangement (Q85742512)
- organised trading facility (Q87120569)
- systematic internaliser (Q91437908)
- Swap Execution Facility (Q7653780)
Here's a count in the latest MIC data:
csvtk cut -f "MARKET_CAT_CODE" ISO10383_MIC-202208.csv|sort|uniq -c count CAT Name 24 APPA Approved Publication Arrangement ARMS Approved Reporting Mechanism 83 ATSS Alternative Trading System 3 CASP Crypto Asset Services Provider CTPS Consolidated Tape Provider 3 DCMS Designated Contract Market 1 IDQS Inter-Dealer Quotation System 154 MLTF Multilateral Trading Facility 103 OTFS Organised Trading Facility 199 RMKT Regulated Market 4 RMOS Recognised Market Operator 10 SEFS Swap Execution Facility 298 SINT Systematic Internaliser 4 TRFS Trade Reporting Facility 3 (missing) 1640 NSPD Not Specified 7 OTHR Other
I added this to Wikipedia: https://en.wikipedia.org/wiki/Market_Identifier_Code#Market_Categories
Categories:
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with constraints on type
- Properties with single value constraints
- Properties with unique value constraints
- Properties with format constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties with qualifiers constraints
- Properties with complex constraints