Property talk:P1163

From Wikidata
Jump to navigation Jump to search

Documentation

media type
IANA-registered identifier for a file type
DescriptionInternet media type (aka MIME type, media type (Q1667978))
Representsmedia type (Q1667978)
Associated itemInternet Assigned Numbers Authority (Q242540)
Data typeString
Template parameter"Internet media type" in en:template:infobox file format
Domain
According to this template: creative work
According to statements in the property:
file format (Q235557), file format family (Q26085352), media type (Q1667978), file system (Q174989), computer network protocol (Q15836568) or programming language (Q9143)
When possible, data should only be stored as statements
Allowed values(application|audio|example|font|image|message|model|multipart|text|video)/[a-zA-Z0-9\-+_.]+
ExampleJPEG File Interchange Format (JFIF) (Q26329975)image/jpeg
Portable Network Graphics (Q178051)image/png
Portable Executable (Q1076355)application/vnd.microsoft.portable-executable
HTML (Q8811)text/html
Sourcehttps://www.iana.org/assignments/media-types/media-types.xhtml
Formatter URLhttps://www.iana.org/assignments/media-types/$1
Tracking: usageCategory:Pages using Wikidata property P1163 (Q38536868)
See alsoMac OS type code (P7126)
Lists
Proposal discussionProposal discussion
Current uses
Total8,658
Main statement8,53698.6% of uses
Qualifier1201.4% of uses
Reference2<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “(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)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Virtual Reality Modeling Language (Q176061), ActivityPub (Q40463886)
List of violations of this constraint: Database reports/Constraint violations/P1163#Format, SPARQL
Format “(application|audio|chemical|example|font|image|message|model|multipart|text|video)/[^\n]+[^ ]: 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/P1163#Format, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033), Wikibase property (Q29934218): 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/P1163#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P1163#Scope, 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/P1163#Unique value, SPARQL (every item), SPARQL (by value)

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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]

 Support --Wdpp (talk) 12:17, 4 May 2021 (UTC)[reply]
Mario Santiago Valdés 152.207.167.150 17:55, 3 August 2023 (UTC)[reply]

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)[reply]

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)[reply]