IETF Logo Mail Archive

Re: [media-types] Filling out templates in XML

Sean Leonard <dev+ietf@seantek.com> Wed, 06 July 2016 03:35 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C31A12D155 for <media-types@ietfa.amsl.com>; Tue, 5 Jul 2016 20:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uttrFOMBwhse for <media-types@ietfa.amsl.com>; Tue, 5 Jul 2016 20:35:46 -0700 (PDT)
Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DADC912D12E for <media-types@ietf.org>; Tue, 5 Jul 2016 20:35:45 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by pechora5.dc.icann.org (8.13.8/8.13.8) with ESMTP id u663ZONB023512 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <media-types@iana.org>; Wed, 6 Jul 2016 03:35:45 GMT
Received: from [192.168.123.110] (unknown [75.83.2.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2EB11509B6; Tue, 5 Jul 2016 23:35:22 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <5f7d616d-0904-2c63-222a-dbb3a0ebd118@gmx.de>
Date: Tue, 05 Jul 2016 20:35:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <36838BD3-74DA-4990-BE02-6088B5C3BCEE@seantek.com>
References: <be19f1f6-72ad-8a35-3104-f71799703d60@seantek.com> <5f7d616d-0904-2c63-222a-dbb3a0ebd118@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3124)
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Wed, 06 Jul 2016 03:35:45 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/o0EMr7HlaBT5AYEU5RVxtlEOvwg>
Cc: xml2rfc@ietf.org, "media-types@iana.org" <media-types@iana.org>
Subject: Re: [media-types] Filling out templates in XML
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2016 03:35:47 -0000

> On Jun 28, 2016, at 10:18 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 2016-06-29 05:24, Sean Leonard wrote:
>> Just curious if people have thought about using XML elements to fill out
>> templates, in xml2rfc, rather than sticking the template instance in an
>> artwork blob.
>> ...
> 
> 
> I have always put registrations either into tables or lists. I agree that using artwork is a very bad thing.
> 

Okay. How can we move forward on a proposal?

* figure out what features we want
  (suggested: kind of like <form> in HTML, in that it’s embedded in the source text. The idea is that the style of the <template-instance template="media-types"> or whatever could be put together by tools so that it looks appropriate for the data.)
* figure out what elements needed
* new sections in xml2rfc v3 about elements
* update Relax NG schema

Main thing at a high level is: is it preferable to embed elements from another namespace (like <svg> does) or make elements in xml2rfc? I think the latter because the text inside template instances should be treated like specification text (searchable, etc.).

Best regards,

Sean

v2.23.0 | Report a Bug | By Email