The Zero one infinity (ZOI) rule is a rule of thumb in software design proposed by early computing pioneer Willem van der Poel. It argues that arbitrary limits on the number of instances of a particular type of data or structure should not be allowed. Instead, an entity should either be forbidden entirely, only one should be allowed, or any number of them should be allowed. Although various factors outside that particular software could limit this number in practice, it should not be the software itself that puts a hard limit on the number of instances of the entity.
| Attributes | Values |
|---|
| rdf:type
| |
| rdfs:label
| - Zero One Infinity (de)
- Zero one infinity rule (en)
|
| rdfs:comment
| - Zero One Infinity (ZOI) bezeichnet sprichwörtlich eine Regel beim Programmieren von Computerprogrammen, die Willem van der Poel zugeschrieben wird. “Allow none of foo, one of foo, or any number of foo.” „Ermögliche eine Sache nicht, ermögliche sie einmal oder ermögliche sie in unbegrenzter Anzahl.“ Zum Beispiel sollte ein Computeralgebrasystem entweder gar keine Graphen zeichnen können, einen Graph zeichnen können, oder beliebig viele Graphen zeichnen können. (de)
- The Zero one infinity (ZOI) rule is a rule of thumb in software design proposed by early computing pioneer Willem van der Poel. It argues that arbitrary limits on the number of instances of a particular type of data or structure should not be allowed. Instead, an entity should either be forbidden entirely, only one should be allowed, or any number of them should be allowed. Although various factors outside that particular software could limit this number in practice, it should not be the software itself that puts a hard limit on the number of instances of the entity. (en)
|
| dcterms:subject
| |
| Wikipage page ID
| |
| Wikipage revision ID
| |
| Link from a Wikipage to another Wikipage
| |
| sameAs
| |
| dbp:wikiPageUsesTemplate
| |
| has abstract
| - Zero One Infinity (ZOI) bezeichnet sprichwörtlich eine Regel beim Programmieren von Computerprogrammen, die Willem van der Poel zugeschrieben wird. “Allow none of foo, one of foo, or any number of foo.” „Ermögliche eine Sache nicht, ermögliche sie einmal oder ermögliche sie in unbegrenzter Anzahl.“ Zum Beispiel sollte ein Computeralgebrasystem entweder gar keine Graphen zeichnen können, einen Graph zeichnen können, oder beliebig viele Graphen zeichnen können. Eine Sache ein einziges Mal zu ermöglichen, kann sinnvoll sein und wird als Ausnahme angesehen. Sobald aber eine Sache zweifach ermöglicht wird, gibt es keinen Grund, sie nicht auch dreifach zu ermöglichen. Und wenn sie dreifach ermöglicht ist, wird es jemanden geben, der diese Sache vierfach ermöglicht sehen will. Jede willkürlich gewählte Begrenzung wird so von den Anwendern des Computerprogramms abgelehnt werden, weswegen solche Einschränkungen vermieden werden sollten. (de)
- The Zero one infinity (ZOI) rule is a rule of thumb in software design proposed by early computing pioneer Willem van der Poel. It argues that arbitrary limits on the number of instances of a particular type of data or structure should not be allowed. Instead, an entity should either be forbidden entirely, only one should be allowed, or any number of them should be allowed. Although various factors outside that particular software could limit this number in practice, it should not be the software itself that puts a hard limit on the number of instances of the entity. Examples of this rule may be found in the structure of many file systems' directories (also known as folders):
* 0 – The topmost directory has zero parent directories; that is, there is no directory that contains the topmost directory.
* 1 – Each subdirectory has exactly one parent directory (not including shortcuts to the directory's location; while such files may have similar icons to the icons of the destination directories, they are not directories at all).
* Infinity – Each directory, whether the topmost directory or any of its subdirectories, according to the file system's rules, may contain any number of files or subdirectories. Practical limits to this number are caused by other factors, such as space available on storage media and how well the computer's operating system is maintained. In real-world software design, violations of this rule of thumb are common. For example, the FAT16 file system imposes a limit of 65,536 files to a directory. (en)
|
| gold:hypernym
| |
| prov:wasDerivedFrom
| |
| page length (characters) of wiki page
| |
| foaf:isPrimaryTopicOf
| |
| is Link from a Wikipage to another Wikipage
of | |
| is Wikipage redirect
of | |
| is Wikipage disambiguates
of | |
| is foaf:primaryTopic
of | |
![[RDF Data]](/fct/images/sw-rdf-blue.png)
![[cxml]](/fct/images/cxml_doc.png)
![[csv]](/fct/images/csv_doc.png)
![[text]](/fct/images/ntriples_doc.png)
![[turtle]](/fct/images/n3turtle_doc.png)
![[ld+json]](/fct/images/jsonld_doc.png)
![[rdf+json]](/fct/images/json_doc.png)
![[rdf+xml]](/fct/images/xml_doc.png)
![[atom+xml]](/fct/images/atom_doc.png)
![[html]](/fct/images/html_doc.png)