attachment-0001
Hi Pete and Mike,<br><br>I suggest that, since the IETF seems to heavily rely on this one, we just take<br>the plain keyword names for the 15 DC v1.1 elements defined in RFC 5013<br>and say they're what goes into values of a new single IPP attribute:<br>
<br> document-dc-metadata (1setOf (octetString (MAX))<br><br>where each value is:<br><br> keyword=value (utf-8 string)<br><br>Note that no paths or qualifiers are needed - the elements are free-standing.<br>RFC 5013 is technically equivalent to DCMI v1.1 and the XML schema.<br>
<br>WDYT?<br><br>Cheers,<br>- Ira<br><br><br><br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>
Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a style="color:rgb(51, 51, 255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102, 0, 204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div>
</div><div></div><div></div><div></div><br>
<div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup"></div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.