[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 2.7 Language Extensibility
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings! I am uncertain about the purpose of 2.7 Language Extensibility. The list following "allows:" appears to repeat information that is reported in 4.2 (Extensions). And, it is followed by this paragraph: ***** The specification differentiates between mandatory and optional extensions (the section below explains the syntax used to declare extensions). If a mandatory extension is used, a compliant implementation MUST understand the extension. If an optional extension is used, a compliant implementation MAY ignore the extension. ***** The reference of: "...the section below..." is vague and should be replace by 4.2 (Extensions), if you keep this paragraph. However, as an illustration of the DRY (Don't repeat yourself), consider the next sentence: ***** If a mandatory extension is used, a compliant implementation MUST understand the extension. ***** That sounds rather hard to guarantee. That every implementation will "understand" some arbitrary extension. But, the precise rules of 4.2 (Extensions) say: ***** If a TOSCA implementation does not support one or more of the mandatory extensions, then the Definitions document MUST be rejected. ***** Now that is a rule can be successfully applied by an application. Don't understand, then reject. BTW, if you do make Section 2 normative, realize that Section 2.7 (if you retain it) will conflict (as presently written) with the language of 4.3 (Extensions). Hope everyone is having a great day! Patrick - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSJhd8AAoJEAudyeI2QFGoOAoQALeiJoP7HBCaYS3yWkE+yJE/ qlAz6qr8UCBNsWV9mjDR4HgcOByEQ6dZ9vxjHimyRRAtKDcGuSu2dhvFY84uWG9A Tecoq7Wr7RtUoat46r2C5m9AiMkH33rALfQm9xOrpiRrmmps4sMUIWdv4rDijNWC nEz1Q5sPNURsTgLKc06HkB459bm+mw6Lkx6EATKXcZREAWyBfJU4RKR/VqpPQMYD MPTCeGeZoH/AgOjfzYcpdTxWHsIBjHvkzrH102dr77EGSERiWHUlfgWkSfOy0Ue3 uTtUljmGztdi4bJUDQr1tWEKL7NPOseiiN9h5ScrjSJCqqeZxAHHVwv+E9D5MgeM LMKxQbBAKrOXv4wvsLbwZs44ygpdDsMoztE0u4BH+w6CDEh/V+rqX7FzPcnbrojy Qz8ZkZBIRO7OIjEpAFv/23ogKeOejEO4hslZhUtyH091lvAYXkuwaHUXQDJ8eG70 V9STF1j5hcrXE24nEBA1xMlQGhzFdO8KZMnuR9oX/iE51Z9idpOP6aI5oLMQ0eAh 2hAyRfG0wWaJl3u5nPfcyl8OKj8v/5Og3AwlhEBpWO2Zg8XaZvhNXRpFws3o70lv 5kvifNm12d6SDXhNv7CPV1H/DU1fv/pFt1/KUKt1hB3y8scRN4hcj2z/GgnhJVO7 xNn7lcNs4XlvRq8xJwYv =CX7T -----END PGP SIGNATURE-----
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]