We did previously discuss on this DL the idea of using 1setOf text, instead
of inventing a new longer octetString32k data type.
However, we had not read the CONNEG standards carefully enough.
At the last IPP FAX telecon on May 30, this issue was re-raised. From
reading the CONNEG RFCs, the same *white space* rules are used between
tokens as for email. Thus, we could represent CONNEG strings as 1setOf
text, where each text value contains one or more CONNEG tokens. When
combining a 1setOf text into a CONNEG string, the parser would insert some
*white space" between each value.
Note: each token doesn't have to be a separate text value (though it can
be).
The advantage of using existing IPP data types, instead of inventing a new
data type, is that existing gateways can be used. Remember that a number of
initial IPP implementations were just gateways to existing printing systems.
A similar issue relates to the vCard data types. We need to read what vCard
standard intends to be between what appears to be separate lines in the
vCard. Could we put each separate line into a separate 1setOf text and
thereby avoid the line ending problem between systems, where Windows uses
CRLF and Unix uses just LF to separate lines.
Comments?
Tom
This archive was generated by hypermail 2b29 : Mon Jun 18 2001 - 18:07:51 EDT