Hi Mike and Chris,
Since this is a convention and not something that is normatively defined or validated, I suppose the vendor can do what it wants.
But what about the "xxx-supported" / "xxx-default" attributes that correspond to the member attributes in the collection?
If at HP I define:
smi11-whatever-col (collection)
whatever-number (integer)
whatever-type (type2 keyword)
so that I can make:
smi11-whatever-col = {
whatever-number = 42
whatever-type = whale
}
there could likely be these accompanying attribute definitions:
whatever-number-supported (rangeOfInteger)
whatever-number-default (integer)
whatever-type-supported (1setOf type2 keyword)
whatever-type-default (type2 keyword)
Is that how we want this to be? Or would it be better like so:
smi11-whatever-col (collection)
smi11-whatever-number (integer)
smi11-whatever-type (type2 keyword)
and then
smi11-whatever-number-supported (rangeOfInteger)
smi11-whatever-number-default (integer)
smi11-whatever-type-supported (1setOf type2 keyword)
smi11-whatever-type-default (type2 keyword)
Smith
/**
Smith Kennedy
HP Inc.
*/
On Feb 9, 2024, at 5:39 PM, Michael Sweet via ipp <ipp at pwg.org> wrote:
CAUTION: External Email
Chris,
On Feb 9, 2024, at 6:34 PM, Rizzo, Christopher via ipp <ipp at pwg.org> wrote:
If a vendor defined attribute ‘smiNNN-<attr-name>’ refers to a collection, should all member attributes of that collection also include the ‘smiNNN-‘ prefix?
No, just the top-level attribute needs the prefix.
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.
________________________
Michael Sweet
_______________________________________________
ipp mailing list
ipp at pwg.orghttps://www.pwg.org/mailman/listinfo/ipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20240210/f08c5268/attachment.html>