- From: Heidi Vanparys via GitHub <sysbot+gh@w3.org>
- Date: Thu, 31 Jan 2019 08:09:52 +0000
- To: public-dxwg-wg@w3.org
heidivanparys has just created a new issue for https://github.com/w3c/dxwg: == Harmonization with ISO/IEC concepts == The concepts in the set of documents regarding profiles should be harmonized with the ISO/IEC concepts, as the concept of profiling is also described in ISO/IEC standards. Or as a minimum, it should be described how they relate to each other. What is the relation between [dct:Standard](http://dublincore.org/documents/dcmi-terms/#terms-Standard) (_A basis for comparison; a reference point against which other things can be evaluated._) on the one side and the following concepts on the other side: **normative document** document that provides rules, guidelines or characteristics for activities or their results Note 1 to entry: The term "normative document" is a generic term that covers such documents as standards, technical specifications, codes of practice and regulations. Note 2 to entry: A "document" is to be understood as any medium with information recorded on or in it. Note 3 to entry: The terms for different kinds of normative documents are defined considering the document and its content as a single entity. [[ISO/IEC Guide 2:2004](https://isotc.iso.org/livelink/livelink?func=ll&objId=8387841&objAction=Open&nexturl=%2Flivelink%2Flivelink%3Ffunc%3Dll%26objId%3D8389141%26objAction%3Dbrowse%26sort%3Dname)] **standard** document, established by consensus and approved by a recognized body, that provides, for common and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the achievement of the optimum degree of order in a given context Note 1 to entry: Standards should be based on the consolidated results of science, technology and experience, and aimed at the promotion of optimum community benefits. [[ISO/IEC Guide 2:2004](https://isotc.iso.org/livelink/livelink?func=ll&objId=8387841&objAction=Open&nexturl=%2Flivelink%2Flivelink%3Ffunc%3Dll%26objId%3D8389141%26objAction%3Dbrowse%26sort%3Dname)] **technical specification** document that prescribes technical requirements to be fulfilled by a product, process or service Note 1 to entry: A technical specification should indicate, whenever appropriate, the procedure(s) by means of which it may be determined whether the requirements given are fulfilled. Note 2 to entry: A technical specification may be a standard, a part of a standard or independent of a standard. [[ISO/IEC Guide 2:2004](https://isotc.iso.org/livelink/livelink?func=ll&objId=8387841&objAction=Open&nexturl=%2Flivelink%2Flivelink%3Ffunc%3Dll%26objId%3D8389141%26objAction%3Dbrowse%26sort%3Dname)] And OGC defines specification and standard as follows: **specification** A document written by a consortium, vendor, or user that specifies a technological area with a well-defined scope, primarily for use by developers as a guide to implementation. A specification is not necessarily a formal standard. [[OGC glossary](http://www.opengeospatial.org/ogc/glossary/s)] **standard** A document that specifies a technological area with a well-defined scope, usually by a formal standardization body and process. [[OGC glossary](http://www.opengeospatial.org/ogc/glossary/s)] This issue may be related to #367 . Please view or discuss this issue at https://github.com/w3c/dxwg/issues/722 using your GitHub account
Received on Thursday, 31 January 2019 08:09:55 UTC