I agree - let's not introduce quoting/escaping issues.
All lowercase keywords (what RFC 5013 calls the 'Elment Name'
in section 6) followed by a single literal equal sign '=', followed
by zero or more UTF-8 characters (which can be multi-octet).
Allow for the zero characters for the explict empty string value
being passed through from another document metadata interface.
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
mailto:blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
On Mon, Nov 28, 2011 at 5:48 PM, Michael Sweet <msweet at apple.com> wrote:
> On Nov 28, 2011, at 1:59 PM, Ira McDonald wrote:
>> Hi Mike,
>> You got it.
>> Yes - I like this clean and simple approach. It really hardly needs
> ABNF (though I could write a closed one for the 15 keywords in
> about 20 minutes).
>>> I did an ABNF anyways, and allow the fixed set of 15 keyword in 5013 or
> any "x-foo" keyword for vendor/client-defined values that need to be
>> One LAST question - do we want to stack these critters
> (keyword=value;keyword=value), so that each
> document-dc-metadata value is one *set* of related metadata
> (creator, date, etc.)?
>>> That would open up quoting issues for the values - we could certainly do
> this, but given that we have a list of key/value pairs applying to the
> current document I don't see any advantage...
> Michael Sweet, Senior Printing System Engineer, PWG Chair
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...