Ira,
That works for me, and if you like I can add this to JPS3 before the F2F.
I assume we also want to add "document-dc-metadata" as Document Description, Job Description, and Operation attributes - we already do this for the document-xxx attributes defined in RFC 2911 and PWG 5100.7...
On Nov 28, 2011, at 11:40 AM, Ira McDonald wrote:
> Hi Pete and Mike,
>> I suggest that, since the IETF seems to heavily rely on this one, we just take
> the plain keyword names for the 15 DC v1.1 elements defined in RFC 5013
> and say they're what goes into values of a new single IPP attribute:
>> document-dc-metadata (1setOf (octetString (MAX))
>> where each value is:
>> keyword=value (utf-8 string)
>> Note that no paths or qualifiers are needed - the elements are free-standing.
> RFC 5013 is technically equivalent to DCMI v1.1 and the XML schema.
>> WDYT?
>> Cheers,
> - Ira
>>>> 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
>http://sites.google.com/site/blueroofmusic>http://sites.google.com/site/highnorthinc> 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
>
________________________________________________________________________
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...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20111128/37aa6c4e/attachment-0001.html>