… SHOULD, and SHOULD NOT are used in this document in accordance with RFC 2119 [ RFC2119 ]. Please send comments on this finding to the publicly archived TAG mailing list www-tag@w3.org ( archive ). Registration of Media Types by W3C Working Groups Consistency of Media Types and R…
… SHOULD, and SHOULD NOT are used in this document in accordance with RFC 2119 [ RFC2119 ]. Please send comments on this finding to the publicly archived TAG mailing list www-tag@w3.org ( archive ). Relevant Principles of Web Architecture Use GET for addressability Dereferencing U…
… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. This document is not intended to change the algorithm implementation requirements of any IETF or W3C document. Use of [ RFC2119 ] terminology is intended to be only such as is already state…
…ng terms are used in this specification. These terms extend the definitions in [RFC2119] in ways based upon similar definitions in ISO/ IEC 9945-1:1990 [POSIX.1] : Implementation-defined A value or behavior is implementation-defined when it is left to the implementation to define…
…HOULD", "MUST", and "MUST NOT" are to be interpreted as described in RFC 2119 [ RFC2119 ]. However, for readability, these words do not appear in all uppercase letters in this specification. [6.1] RDF ::= ['< rdf :RDF>'] obj * ['</ rdf :RDF>'] [6.2] obj ::= description | containe…
…and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119] 1.3.2 RDF graph notation The underlying structure of RDF is a directed labeled graph. For communication between computer systems, RDF uses a serialization in XML to represent these graphs. Th…
…", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119. [RFC2119] Requirements phrased in the imperative as part of algorithms (such as "strip any leading space characters" or "return false and abort these steps") are to be interpreted with the me…
…, "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. This document is not intended to change the algorithm implementation requirements of any IETF or W3C document. Use of [RFC2119] terminology is intended to be only such as is already stated o…
…" in the normative parts of this document are to be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification. [RFC2119] Requirements phrased in the imperative as part of algorithms (such as "strip any leading s…
…erms MUST, SHOULD, and SHOULD NOT are used in this document in accordance with [RFC2119] Please send comments on this finding to the publicly archived TAG mailing list www-tag@w3.org ( archive ). Table of Contents Introduction 1.1 Scenarios 1.2 Relevant Principles of Web Architec…
…g terms are used in this specification. These terms extend the definitions in [ RFC2119 ] in ways based upon similar definitions in ISO/ IEC 9945-1:1990 [ POSIX.1 ]: May With respect to implementations, the word "may" is to be interpreted as an optional feature that is not requir…
…the normative parts of this specification are to be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification. [RFC2119] 2.1 Security Notifications should only be presented when the user has indicated they are d…
…2017 . Clarifying Capitalization of Key Words The following change is made to [ RFC2119 ]: === OLD === In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words a…
… 以下の用語はこの仕様書の中で使われているものである。これらの用語は、ISO/ IEC 9945-1:1990 [POSIX.1] での類似の定義に基づいて [RFC2119] での定義を拡張している。 実装定義の (implementation-defined) 正しい文書構造についての対応する必要条件を定義[し文書化]することが実装にゆだねられているとき、値または挙動は実装定義である。 してもよい (may) 実装に関しては、「してもよい」という言葉は、この仕様書では要求されないが提供することができる任意的機能として解釈されるべきものである。 文書の…
…NOT RECOMMENDED SHOULD , and SHOULD NOT are to be interpreted as described in [ RFC2119 ]. This document describes best practices for the authors of other specifications, as well as recommendations for implementations and content authors. These best practices can also be found in…