GLOSSARY ENTRY (DERIVED FROM QUESTION BELOW) | ||||||
---|---|---|---|---|---|---|
|
20:24 Dec 14, 2018 |
English to Polish translations [PRO] Tech/Engineering - IT (Information Technology) / Specyfikacja oprogrogramowania | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Mariusz Jagodziński Poland Local time: 15:13 | ||||||
Grading comment
|
Summary of answers provided | ||||
---|---|---|---|---|
3 | specyfikacje zbiorcze |
|
umbrella spec specyfikacje zbiorcze Explanation: Proponuję specyfikacje zbiorcze na podstawie poniższej definicji: Appendix A: Umbrella specifications It is not always practical, desirable, or possible to have a monolithic specification - that is, one that presents the requirements for a technology in a single document. The Working Group may produce several documents that act collectively to specify the technology (e.g., Web Ontology Language OWL). There are all sorts of reasons for having or needing a collection or series of specifications to describe a technology. These reasons include: the technology is too big to present in one document, the technology evolves over time the technology is easier to understand or organize as multiple documents the technology consists of several modules or subdivisions that revolve around a single information model or framework. In these cases, there should be a single document, called an umbrella specification that ties all the documents together. The umbrella specification serves as foundation or "Read me First" document for the entire collection or series. https://www.w3.org/TR/spec-variability/#umbrella |
| |
Login to enter a peer comment (or grade) |
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.