…eader internationalization. 11.1 . Impact on URIs and IRIs The mailto: schema [ RFC6068 ], and the discussion of it in the Internationalized Resource Identifier (IRI) specification [ RFC3987 ], may need to be modified when this work is completed and standardized. 11.2 . Use of Em…

…port Provides information about the TD maintainer as URI scheme (e.g., mailto [ RFC6068 ], tel [ RFC3966 ], https [ RFC9112 ]). optional anyURI base Define the base URI that is used for all relative URI references throughout a TD document. In TD instances, all relative URIs are r…

… For example, an email distribution list could employ the "mailto" URI scheme [ RFC6068 ] for efficiency. Cardinality: * Special notes: This property MUST NOT be present unless the value of the KIND property is "group". ABNF: MEMBER-param = "VALUE=uri" / pid-param / pref-param / …

…MUST NOT provide a "mailto" URL in the "contact" field that contains "hfields" [RFC6068] or more than one "addr-spec" in the "to" component. If a server encounters a "mailto" contact URL that does not meet these criteria, then it SHOULD reject it as invalid. Barnes, et al. Standa…

… For example, an email distribution list could employ the "mailto" URI scheme [ RFC6068 ] for efficiency. Cardinality: * Special notes: This property MUST NOT be present unless the value of the KIND property is "group". ABNF: MEMBER-param = "VALUE=uri" / pid-param / pref-param / …

…eader internationalization. 11.1 . Impact on URIs and IRIs The mailto: schema [ RFC6068 ], and the discussion of it in the Internationalized Resource Identifier (IRI) specification [ RFC3987 ], may need to be modified when this work is completed and standardized. 11.2 . Use of Em…

… generating an email [ RFC5322 ] message can instead use the mailto: URI scheme RFC6068 ]. Implementors interested in referencing a message or a set of messages available from a mailstore over IMAP [ RFC3501 ], POP RFC1939 ], or web [ RFC2616 ] can instead use the imap: [ RFC5092…

… to be an email address conforming to the addr-spec definition in Section 2 of [RFC6068] (so does not include the prefix "mailto:"). This element appears as a child element of <address> ( Section 2.2 ). Content model: only text content. 2.15 . <eref> Represents an "external" link…

… For example, an email distribution list could employ the "mailto" URI scheme [ RFC6068 ] for efficiency. Cardinality: * Special notes: This property MUST NOT be present unless the value of the KIND property is "group". ABNF: MEMBER-param = "VALUE=uri" / pid-param / pref-param / …

… generating an email [ RFC5322 ] message can instead use the mailto: URI scheme RFC6068 ]. Implementors interested in referencing a message or a set of messages available from a mailstore over IMAP [ RFC3501 ], POP RFC1939 ], or web [ RFC2616 ] can instead use the imap: [ RFC5092…

… For example, an email distribution list could employ the "mailto" URI scheme [ RFC6068 ] for efficiency. Cardinality: * Special notes: This property MUST NOT be present unless the value of the KIND property is "group". ABNF: MEMBER-param = "VALUE=uri" / pid-param / pref-param / …

…For example, an e-mail distribution list could employ the "mailto" URI scheme [ RFC6068 ] for efficiency. Cardinality: * Special notes: This property MUST NOT be present unless the value of the KIND property is "group". ABNF: MEMBER-param = "VALUE=uri" / pid-param / pref-param / …

…. For example, an email distribution list could employ the "mailto" URI scheme [RFC6068] for efficiency. Cardinality: * Special notes: This property MUST NOT be present unless the value of the KIND property is "group". ABNF: MEMBER-param = "VALUE=uri" / pid-param / pref-param / a…

… For example, an email distribution list could employ the "mailto" URI scheme [ RFC6068 ] for efficiency. Cardinality: * Special notes: This property MUST NOT be present unless the value of the KIND property is "group". ABNF: MEMBER-param = "VALUE=uri" / pid-param / pref-param / …

… MUST NOT provide a "mailto" URL in the "contact" field that contains "hfields" RFC6068 ] or more than one "addr-spec" in the "to" component. If a server encounters a "mailto" contact URL that does not meet these criteria, then it SHOULD reject it as invalid. Barnes, et al. Stand…