attachment
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
Hi Mike and Chris,
<div><br>
</div>
<div>Since this is a convention and not something that is normatively defined or validated, I suppose the vendor can do what it wants.</div>
<div><br>
</div>
<div>But what about the "xxx-supported" / "xxx-default" attributes that correspond to the member attributes in the collection?
<div><br>
</div>
<div>If at HP I define:</div>
<div><br>
</div>
<div>smi11-whatever-col (collection)</div>
<div> whatever-number (integer)</div>
<div> whatever-type (type2 keyword)</div>
<div><br>
</div>
<div>so that I can make:</div>
<div><br>
</div>
<div>smi11-whatever-col = {</div>
<div> whatever-number = 42</div>
<div> whatever-type = whale</div>
<div>}</div>
<div><br>
</div>
<div>there could likely be these accompanying attribute definitions:</div>
<div><br>
</div>
<div>whatever-number-supported (rangeOfInteger)</div>
<div>whatever-number-default (integer)</div>
<div>whatever-type-supported (1setOf type2 keyword)</div>
<div>whatever-type-default (type2 keyword)</div>
<div><br>
</div>
<div>Is that how we want this to be? Or would it be better like so:</div>
<div><br>
</div>
<div>
<div>smi11-whatever-col (collection)</div>
</div>
<div>
<div>
<div> smi11-whatever-number (integer)</div>
<div> smi11-whatever-type (type2 keyword)</div>
</div>
<div><br>
</div>
<div>and then</div>
<div><br>
</div>
<div>smi11-whatever-number-supported (rangeOfInteger)</div>
<div>smi11-whatever-number-default (integer)</div>
<div>smi11-whatever-type-supported (1setOf type2 keyword)</div>
<div>smi11-whatever-type-default (type2 keyword)</div>
</div>
<div><br>
</div>
<div><br id="lineBreakAtBeginningOfMessage">
<div>Smith<br>
<br>
/**<br>
Smith Kennedy<br>
HP Inc.<br>
*/ </div>
<div><br>
<blockquote type="cite">
<div>On Feb 9, 2024, at 5:39 PM, Michael Sweet via ipp <ipp@pwg.org> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div>CAUTION: External Email<br>
<br>
Chris,<br>
<br>
<blockquote type="cite">On Feb 9, 2024, at 6:34 PM, Rizzo, Christopher via ipp <ipp@pwg.org> wrote:<br>
<br>
If a vendor defined attribute ‘smiNNN-<attr-name>’ refers to a collection, should all member attributes of that collection also include the ‘smiNNN-‘ prefix?<br>
</blockquote>
<br>
No, just the top-level attribute needs the prefix.<br>
<br>
Similarly, if you add a vendor member attribute to a standard collection, just that member attribute needs the prefix, e.g., "smiNNN-media-flavor" for a "media-col" extension.<br>
<br>
________________________<br>
Michael Sweet<br>
<br>
_______________________________________________<br>
ipp mailing list<br>
ipp@pwg.org<br>
https://www.pwg.org/mailman/listinfo/ipp<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>