Matches in DBpedia 2016-04 for { <http://wikidata.dbpedia.org/resource/Q1936217> ?p ?o }
Showing triples 1 to 37 of
37
with 100 triples per page.
- Q1936217 subject Q7155980.
- Q1936217 subject Q7470461.
- Q1936217 subject Q8527502.
- Q1936217 abstract "Any change in a computing system, such as new feature or new component, is transparent if the system after change adheres to previous external interface as much as possible while changing its internal behaviour. The purpose is to shield from change all systems (or human users) on the other end of the interface. Confusingly, the term refers to overall invisibility of the component, it does not refer to visibility of component's internals (as in white box or open system). The term transparent is widely used in computing marketing in substitution of the term invisible, since the term invisible has a bad connotation (usually seen as something that the user can't see and has no control over) while the term transparent has a good connotation (usually associated with not hiding anything). The vast majority of the times, the term transparent is used in a misleading way to refer to the actual invisibility of a computing process.The term is used particularly often with regard to an abstraction layer that is invisible either from its upper or lower neighbouring layer.Also temporarily used later around 1969 in IBM and Honeywell programming manuals the term referred to a certain computer programming technique. An application code was transparent when it was clear of the low-level detail (such as device-specific management) and contained only the logic solving a main problem. It was achieved through encapsulation – putting the code into modules that hid internal details, making them invisible for the main application.".
- Q1936217 wikiPageWikiLink Q1094291.
- Q1936217 wikiPageWikiLink Q1200992.
- Q1936217 wikiPageWikiLink Q1305241.
- Q1936217 wikiPageWikiLink Q1332873.
- Q1936217 wikiPageWikiLink Q1400808.
- Q1936217 wikiPageWikiLink Q1414548.
- Q1936217 wikiPageWikiLink Q1488589.
- Q1936217 wikiPageWikiLink Q15912075.
- Q1936217 wikiPageWikiLink Q174989.
- Q1936217 wikiPageWikiLink Q179310.
- Q1936217 wikiPageWikiLink Q180634.
- Q1936217 wikiPageWikiLink Q2111.
- Q1936217 wikiPageWikiLink Q23808.
- Q1936217 wikiPageWikiLink Q2382874.
- Q1936217 wikiPageWikiLink Q2493.
- Q1936217 wikiPageWikiLink Q42283.
- Q1936217 wikiPageWikiLink Q4479242.
- Q1936217 wikiPageWikiLink Q5429725.
- Q1936217 wikiPageWikiLink Q623494.
- Q1936217 wikiPageWikiLink Q661062.
- Q1936217 wikiPageWikiLink Q6664826.
- Q1936217 wikiPageWikiLink Q7155980.
- Q1936217 wikiPageWikiLink Q7251920.
- Q1936217 wikiPageWikiLink Q741137.
- Q1936217 wikiPageWikiLink Q7470461.
- Q1936217 wikiPageWikiLink Q79872.
- Q1936217 wikiPageWikiLink Q80006.
- Q1936217 wikiPageWikiLink Q80993.
- Q1936217 wikiPageWikiLink Q8513.
- Q1936217 wikiPageWikiLink Q8527502.
- Q1936217 wikiPageWikiLink Q997233.
- Q1936217 comment "Any change in a computing system, such as new feature or new component, is transparent if the system after change adheres to previous external interface as much as possible while changing its internal behaviour. The purpose is to shield from change all systems (or human users) on the other end of the interface. Confusingly, the term refers to overall invisibility of the component, it does not refer to visibility of component's internals (as in white box or open system).".
- Q1936217 label "Transparency (human–computer interaction)".