Talk:Q235557
Jump to navigation
Jump to search
Autodescription — file format (Q235557)
description: formalized structure of information stored on a computer
- Useful links:
- View it! – Images depicting the item on Commons
- Report on constraint conformation of “file format” claims and statements. Constraints report for items data
For help about classification, see Wikidata:Classification.
- Parent classes (classes of items which contain this one item)
- file format (Q235557)
- data format (Q494823)
- technical specification (Q20819677)
- technical standard (Q317623)
- file format (Q235557)
- Subclasses (classes which contain special kinds of items of this class)
- ⟨
file format⟩ on wikidata tree visualisation (external tool)(depth=1) - Generic queries for classes
- See also
- This documentation is generated using
{{Item documentation}}.
Possible subclasses?
[edit]Should this have one or more subclass trees, such as:
- File format
- Binary file format
- Textual file format
- Markup file formats (children of this should perhaps be a separate attribute?)
- SGML-based file formats
- HTML-based file formats
- File format
- General file format
- Functional file format
- Image file format
- Document file format
(Context: as of July 2022, there are 105 direct subclasses, but the tree seems very ‘shallow’; i.e. with 282 total subclasses, many direct subclasses have zero children themselves)
As an example: Q1023647, Microsoft Complied HTML help, belongs to this class. Might it not be better for such topics to have a more precise subclass as a parent?
Thinking about the possible attributes of a particular file format, e.g.:
- proprietary vs. open-source
- (what about proprietary formats that are fully documented, either officially or through reverse-engineering?)
- human-readable vs. machine-readable
- (i.e. stripped of all special symbols / tags but with no further processing, would the resulting text be readable to a layperson and retain much/all semantic context?)
- (e.g. the result of passing various ‘.json’ files through the UNIX-style `strings` utility would be of limited use)
- type of contents: text, graphics, data (e.g. tabular), document hybrid, hybrid
- type of contents: compressed data, encrypted data, composite/hybrid data