The current "document-id-uri" in the IPP Document Object spec
clearly that states that it is an opaque identifier, and cannot
be used as the target of an operation (unlike the "job-uri" in
RFC 2911). And it gives an example of an 'ipp:' schemed URI.
I think I should write an Appendix to the Document Object that:
(1) extends the IPP URL Scheme (adopted last month by the IETF
for RFC publication as an IETF Proposed Standard) to apply
to Document objects as well,
(2) specifies the opaque identifier limitation,
(3) is normatively referenced by the "document-id-uri" attribute
definition in the main spec.
As we discussed on the PSI telecon this morning, PSI doesn't
care what the URL scheme is in the DocumentURI, just that it
be unique within a print server.
- Ira McDonald, co-editor of IPP URL Scheme
High North Inc