[rfc-i] [xml2rfc-dev] Preparing for allowing v3 submissions into the repository (was Re: Alternate artwork vocabulary and post preptool)

Julian Reschke julian.reschke at gmx.de
Sat Feb 9 02:30:56 PST 2019


On 09.02.2019 11:19, Julian Reschke wrote:
> On 07.02.2019 21:37, Henrik Levkowetz wrote:
>> Hi Robert,
>>
>> On 2019-02-07 21:07, Robert Sparks wrote:
>>> The change proposed in this thread (to allow the preptool to incorporate
>>> SVG from external files as artwork rather than a data URI) seems right,
>>> and important.
>>>
>>> The IESG is ready to allow v3 submissions into the repository as soon as
>>> the tooling is ready. The tooling is very close. As noted in the thread,
>>> our goal is to have the submission tool accept a standalone file (rather
>>> than solve how to allow submission of multiple components.)
>>>
>>> I'm asking that this change be made to the toolchain.
>>
>> Ok, I'll coordinate with Jim to make sure to support his original use
>> case, and make a tentative implementation, using the <artgroup> idea we
>> landed on in the original thread.  I'll provide the details of that in my
>> implementation notes draft, as part of the release notes of the release
>> where they appear, and in a separate message to the lists this message
>> goes to.  We can then adjust and iterate.
>>
>>
>>     Henrik
>> ...
> 
> Hm.
> 
> It's a bit unfortunate to complicate the grammar that much for this 
> case. I don't believe we need that.
> 
> Why don't we simply do something like
> 
> <artwork>
>    <text-equivalent>
> 
>    </text-equivalent>
>    <svg:svg>
>      ...
>    </svg:svg>
> <artwork>

Or even:

<artwork>
   <svg:svg>
     <svg:desc>
text equivalent
     </svg:desc>
     ...
   </svg:svg>
<artwork>

See 
<https://www.w3.org/TR/SVGTiny12/struct.html#TitleAndDescriptionElements>.

Best regards, Julian


More information about the rfc-interest mailing list