Format built on a container#
This page is generated from the code and must not be edited by hand.
A file whose contents are a container, such as HDF5, is flagged as built on that container, and a ZIP under an archive’s extension is asked about, since only the lab can say what it holds.
format_built_on_a_container version 2+d1
Kind of rule: What is raised for attention (
flags). Raises something for a person’s attention without concluding anything.What it concludes: a finding
Reasoning:
defeasible. A conclusion is usually right, and is retracted when a rule it names concludes against it.What it reads: one file at a time
Is it available in this version?#
Yes. The engine runs it.
What would defeat it#
A finding is never withdrawn. When any of these rules also concludes about the same thing, the finding records it:
installed_software_in_folder: A folder is recognized as an installed program, such as a copy of Fiji or a Python environment, from the parts it holds, a name ending .app, its program-style subfolders or a majority of program files; its files are still indexed and read, and rules about experiments leave them alone.
It stands aside beneath every folder one of these rules raises:
Parameters#
Parameter |
Shipped value |
May be |
What it does |
|---|---|---|---|
|
|
text |
The type detector whose opinion stands behind the reading. |
|
|
one of |
Which half of a disagreement this rule reads. |
|
|
list of text |
The containers a format is written on. |
|
|
list of text |
The containers whose use only a laboratory can say. |
|
|
list of text |
The file types that are archives. An unclear container under an extension the Dictionary names as any other format is that program’s own, and is not asked about. |