Property talk:P3903

Documentation

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

column
column in the page of a document, column number of source referenced for statement

Represents	column number (Q96167300)
Data type	String
Domain	According to this template: sources According to statements in the property: publication (Q732577) or text (Q234460) When possible, data should only be stored as statements
Allowed values	.{1,10}
See also	section, verse, paragraph, or clause (P958), page(s) (P304), folio(s) (P7416)
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 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) Chart by item creation date Database reports/Constraint violations/P3903 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 72,923 Main statement 66,224 90.8% of uses Qualifier 4,706 6.5% of uses Reference 1,993 2.7% of uses

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

Type “publication (Q732577), text (Q234460)”: item must contain property “instance of (P31)” with classes “publication (Q732577), text (Q234460)” 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/P3903#Type Q732577, Q234460, SPARQL

Format “.{1,10}”: value must be formatted using this pattern (PCRE syntax). (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/P3903#Format, SPARQL

This property is being used by: eu:Txantiloi:Aldizkari infotaula Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Discussion

Loosening the constraint

Is there any reason this property should only apply to typographical document? As per this discussion, some people discussed how it would be possible to model column number for other kind of documents, such as inscription (Q1640824). This property would be a good fit in my opinion. Do you have any thoughts?

Alexmar983 Jahl de Vautban DerMaxdorfer Mentxu Zorita Epìdosis Liber008 Accurimbono Ahc84 (talk) 18:39, 2 August 2024 (UTC) sarcanon User:Anna Clara Maniero Azzolini JBradyK

Notified participants of WikiProject Epigraphy. Liber008 (talk) 21:10, 12 August 2024 (UTC)

As already written in the mentioned discussion, I don't see any good reason for this restriction on documents produced via printing press. As this recent volume has shown, the invention of the printing press fostered some changes in layout and design of text documents (of course), but no fundamental deviation of earlier practices known from clay tablets, papyri, inscriptions, scrolls or hand-written books. The "statements" and "constraints" of this item don't imply or impose any restriction on typographical documents as well. The "typographical" is only part of the description text in some, but not even all languages (German and Norwegian being exceptions) - they were probably all translated from one initial description. --DerMaxdorfer (talk) 21:44, 12 August 2024 (UTC)

 Support adding to publication (Q732577) also text (Q234460), which would include also inscription (Q1640824) under itself, for the reasons expressed above. --Epìdosis 09:32, 13 August 2024 (UTC)

If there is no objection, then I would go with @Epìdosis' suggestion. As mentionned by @DerMaxdorfer, we would need to change the description in several language to reflect that change, but it would be as simple as deleting the "typographic" concept in these. Liber008 (talk) 12:08, 14 August 2024 (UTC)

@Epìdosis Would you care to do the clean up regarding the constraint and the descriptions? --Liber008 (talk) 13:18, 23 August 2024 (UTC)

Constraint edited (easy); for the descriptions, I removed "typographic"/"printed" in all languages I was somehow able to understand; "page" anyway still gives some impression of print (or at least of a support like paper/parchment, e.g. a manuscript) and seems somehow strange for writing on stone or other supports, so suggestions are welcome to improve further. Epìdosis 14:03, 23 August 2024 (UTC)