Property talk:P6833
Jump to navigation
Jump to search
Documentation
title in HTML
(qualifier) for title property (P1476), to write title with HTML markup, if the string can't render it normally. Allowed tags are: sup, sub, i
(qualifier) for title property (P1476), to write title with HTML markup, if the string can't render it normally. Allowed tags are: sup, sub, i
Represents | title in HTML (Q114769209) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type | Monolingual text | ||||||||||||
Domain | title statements (note: this should be moved to the property statements) | ||||||||||||
Allowed values | According to this template:
plain text and the following HTML tags:
According to statements in the property:
When possible, data should only be stored as statements.*<(sup|sub|i|SUP|SUB|I)>.+</(sup|sub|i|SUP|SUB|I)>.*(?i)((?!\b(<br>|<br />|<br/>|</br>)).)*(?i)((?!\b(<p>|</p>)).)*(?i)((?!\b(<em>|</em>|<strong>|</strong>|<b>|</b>)).)* | ||||||||||||
Example | Chinese species of Pediobius Walker (Hymenoptera: Eulophidae) (Q28937634) → Chinese species of Pediobius Walker (Hymenoptera: Eulophidae). Alien 3 (Q108543) → Alien3 | ||||||||||||
See also | title in LaTeX (P6835), title (P1476) | ||||||||||||
Lists | |||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
|
[create Create a translatable help page (preferably in English) for this property to be included here]
Scope is as qualifier (Q54828449), 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/P6833#Scope, SPARQL
Format “
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). .*<(sup|sub|i|SUP|SUB|I)>.+</(sup|sub|i|SUP|SUB|I)>.*
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P6833#Format, SPARQL
Format “
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). (?i)((?!\b(<br>|<br />|<br/>|</br>)).)*
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P6833#Format, SPARQL
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/P6833#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P6833#Format, SPARQL
Format “
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). (?i)((?!\b(<em>|</em>|<strong>|</strong>|<b>|</b>)).)*
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P6833#Format, SPARQL
Qualifier of P1476 only
Is defined as a qualifier of title (P1476), not other properties (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P6833#Qualifier of P1476 only
Is defined as a qualifier of title (P1476), not other properties (Help)
Violations query:
SELECT ?item ?p WHERE { ?st pq:P6833 [] . MINUS { ?item p:P1476 ?st } MINUS { ?item p:P1855 ?st } ?item ?p ?st }
List of this constraint violations: Database reports/Complex constraint violations/P6833#Qualifier of P1476 only
References
[edit]This property is currently only accepted in qualifiers. It would be useful in references as well: if the reference uses title (P1476), adding this property would work like a qualifier of that. Thoughts? —Tacsipacsi (talk) 11:37, 12 June 2019 (UTC)
- How about making an item for the reference and adding it there? title in LaTeX (P6835) would probably be too much a challenge for the GUI for references anyways. --- Jura 11:43, 12 June 2019 (UTC)
- That’s a solution for often-used references, but for a web site used only in one item, to support only one statement, it seems a bit overkill. Some asymmetry between the two properties is acceptable IMO, although (LA)TEX also works well in links: (the only issue is that the link is black when using PNG output, but the external links’ icon shows that it’s a link). —Tacsipacsi (talk) 15:34, 12 June 2019 (UTC)