Property talk:P1163
Documentation
IANA-registered identifier for a file type
(application|audio|chemical|example|font|image|message|model|multipart|text|video)/[a-zA-Z0-9+.-]+
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P1163#Format, SPARQL
(application|audio|chemical|example|font|image|message|model|multipart|text|video)/[^\n]+[^ ]
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P1163#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1163#Entity types
List of violations of this constraint: Database reports/Constraint violations/P1163#Type Q235557, Q26085352, Q1667978, Q174989, Q15836568, Q9143, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1163#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1163#Unique value, SPARQL (every item), SPARQL (by value)
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Formatter URL and values
[edit]I tried to set a formatter URL. It seems to work for some, but not for others. Is just the IANA site is more complicated or incomplete, or do we include types that are not registered? --- Jura 08:38, 20 October 2015 (UTC)
Unofficial MIME types
[edit]chemical MIMEs are not official MIME types [1] but [2] claims they are widely used. Should we accepet them? --Pasleim (talk) 12:45, 28 January 2017 (UTC)
- Pasleim As far as I see, general practice mentions unofficial MIME types in file format items. They should be easy to distinguish from official ones thanks to the "x|X" subtype prefix and because they lack a stated in (P248) qualifier specifying an RFC. --Dipsode87 (talk) 11:08, 18 December 2019 (UTC)
Distinct values constraint
[edit]I removed the distinct values constraint since many file formats and file format versions can share the same MIME type. --Dipsode87 (talk) 09:12, 5 October 2018 (UTC)
removed required statement of filename extension (Q186157)
[edit]I had a look at /usr and at my Dockerfiles. I noticed that this constraint made little sense. -- Dr.üsenfieber (talk) 08:15, 11 April 2020 (UTC)
- Support --Wdpp (talk) 12:17, 4 May 2021 (UTC)
- Mario Santiago Valdés 152.207.167.150 17:55, 3 August 2023 (UTC)
Subject type constraint: not to be used on data formats
[edit]media type (P1163) should not be used on content format (Q5165081) (generally referred to as "codecs"), only on containers. That's why I replaced the authorized subject data format (Q494823), too broad (one of its subclasses is content format (Q5165081)) by file format (Q235557). --Dipsode87 (talk) 12:25, 7 August 2023 (UTC)
- I think content format (Q5165081) is acceptable for media type (P1163). It seems that the RFC 4855 and RFC 4856 uses media types for audio coding format (Q758871) and video compression format (Q7927899) (both are subclass of content format (Q5165081)). --Wdpp (talk) 15:44, 8 October 2023 (UTC)