Return-Path: X-Original-To: sml@mail2.ietf.org Delivered-To: sml@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id F2CD611B65438 for ; Tue, 21 Jul 2026 06:24:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784640242; bh=UcMsuarvf5CqJhmrHxiupIo2X1FSrCe9frsNetN/wnE=; h=Date:From:Subject:To; b=X+C4McBSc1Gh/W4/dQuWOmUpBSQcjREzgclOwwJ32DcHza7LLegvOP+o348sfyFYa FSP/jIII/8sFSeymr8ZSzRyL9pCnHOGJvgZ9FDaEM/0VfG23dNqryHQbLUXE9L2sgz Rx85cIj0e19NRzoKAQ1QFl5S4a7pPdkgiXLwKZRs= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hZ7apYQWsY9o for ; Tue, 21 Jul 2026 06:24:02 -0700 (PDT) Received: from waldorf.isode.com (waldorf.isode.com [195.21.82.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3CB2C11B65426 for ; Tue, 21 Jul 2026 06:24:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1784640233; d=isode.com; s=june2016; i=@isode.com; bh=QffJExy1ck0yvddWLCY2PScBsJ9YhOMcaG43/K3Srx4=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=RPt5k+rbUH/BLsdJaNou3vrNgeJ17N8VTOcYNfjPvTmGFU/nkDeITn4Nqcf2HdHiB10HtG vmkixa8Q6dIHolbXOPB5YvyOXYtOVu/PTJPhvMMjAFLfQP2wcGgnrueG0Zd3Nf+6N+eYGp TFM5XCVcfuICYImi+q0ZfK1xiLO0BoQ=; Received: from [192.168.0.116] (212-186-73-97.static.upcbusiness.at [212.186.73.97]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id ; Tue, 21 Jul 2026 14:23:52 +0100 Message-ID: <33fad54e-c138-4569-8618-66d84c872275@isode.com> Date: Tue, 21 Jul 2026 14:23:51 +0100 User-Agent: Mozilla Thunderbird From: Alexey Melnikov To: ptao@apple.com, sml@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------krQLZvW54pMpnLTinpPBfSbF" Content-Language: en-US Message-ID-Hash: ZR25QTPMQOZVMKGVZ2XSNHC56DHWC432 X-Message-ID-Hash: ZR25QTPMQOZVMKGVZ2XSNHC56DHWC432 X-MailFrom: alexey.melnikov@isode.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BSml=5D_Comments_on_draft-ietf-sml-structured-quoted-content-00?= List-Id: Structured Email Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --------------krQLZvW54pMpnLTinpPBfSbF Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi all, As I promised during the SML IETF meeting in Vienna, I am sending some small issues that I found while implementing: > 4. JSON-LD Objects General: please introduce each object type in prose (i.e. how it is used) before describing its properties. I am not always 100% certain what purpose is for different object types. Examples later in the text help, but I don't think the document has to rely on examples for explanation. > Structured Quoted Content uses the following object types. > > *EmailMessage* > > * vocabulary: schema.org and sml.draft.iana.org > * id format: "mid:" > * The following properties can be set: sender, toRecipient, dateSent, dateReceived, about (subject) ccRecipient and bccRecipient are not listed above, but shown in examples, so I think they need to be added to the above list. Are other properties allowed or is the above list supposed to be complete? What should happen if one of the EmailMessage properties not listed above is included in JSON-LD? In Section 8.1.2: "about": { "@type": "Thing", "@id":"mid:msg-ex1-001@example.com/subject", Does it matter that the URI ends in /subject instead of /about (EmailMessage property name)? Or it doesn't matter and the above is just an example? We should also check whether mid: URI syntax allows for the above. "name": "Lorem ipsum" }, { "@context":"https://sml.draft.iana.org", "@type": "QuotedContent", "@id": "quoted-content:A1000001-0000-0000-0000-000000000001", "message":"mid:msg-ex1-002@example.com", "preamble": "forward-preamble:A1000006-0000-0000-0000-000000000001", "headerBlock": "quoted-header-block:A1000002-0000-0000-0000-000000000001", "content": [ "text-content:A1000004-0000-0000-0000-000000000001", "quoted-content:A1000001-0000-0000-0000-000000000002" I was a bit confused about what is the meaning of multiple values here, so please clarify. Also, why would one choose to use a single QuotedContent object versa multiple? Thank you, Alexey --------------krQLZvW54pMpnLTinpPBfSbF Content-Type: text/html; charset=UTF-8 Content-transfer-encoding: quoted-printable

Hi all,

As I promised during the SML IETF meeting in Vienna, I am sending some small issues that I found while implementing:

4.  JSON-LD Objects

General: please introduce each object type in prose (i.e. how it is used) before describing its properties. I am not always 100% certain what purpose is for different object types. Examples later in the text help, but I don't think the document has to rely on examples for explanation.

   Structured Quoted Content uses the following obj=
ect types.

   *EmailMessage*

* vocabulary: schema.org and sml.draft.iana.org
* id format: "mid:<message-id header>"
* The following properties can be set: sender, toRecipient, dateSent, dateRe=
ceived, about (subject)

ccRecipient and bccRecipient are not listed above, but shown in examples, so I think they need to be added to the above list.

Are other properties allowed or is the above list supposed to be complete?

What should happen if one of the EmailMessage properties not listed above is included in JSON-LD?=C2=A0 =C2=A0 =C2=A0


In Section 8.1.2:

       "about": {
         "@type": "Thing",
         "@id": "mid:msg-ex1-001@example.com/subject",


Does it matter that the URI ends in /subject instead of /about (EmailMessage=
 property name)? Or it doesn't matter and the above is just an example?

We should also check whether mid: URI syntax allows for the above.=20

         "name": "Lorem ipsum"
       },


     {
       "@context": "https://sml.draft.iana.org",
       "@type": "QuotedContent",
       "@id": "quoted-content:A1000001-0000-0000-0000-000000000001",
       "message": "mid:msg-ex1-002@example.com",
       "preamble": "forward-preamble:A1000006-0000-0000-0000-000000000001",
       "headerBlock": "quoted-header-block:A1000002-0000-0000-0000-000000000=
001",
       "content": [
         "text-content:A1000004-0000-0000-0000-000000000001",
         "quoted-content:A1000001-0000-0000-0000-000000000002"

I was a bit confused about what is the meaning of multiple values here, so p=
lease clarify. Also, why would one choose to use a single QuotedContent obje=
ct versa multiple?

Thank you,
Alexey
--------------krQLZvW54pMpnLTinpPBfSbF--