SM> document-creator-application-version ISSUE: For human or program consumption?

SM> document-creator-application-version ISSUE: For human or program consumption?

SM> document-creator-application-version ISSUE: For human or program consumption?

McCarthy, Ann L AMcCarthy at crt.xerox.com
Thu Apr 17 13:00:42 EDT 2003


Tom,

I agree with the change you are recommending.
Because semantics can change significantly from one version of an
application to another - I recommend upgrading this to a required
attribute.

Regards,
Ann

--------------------------------------------------------------------
Ann L. McCarthy
XIG/SSTC Imaging Systems Architect
Internal:8*221-8701     External: 585-231-8701
FAX: 585-265-8871      Mailcode: B128-30E


-----Original Message-----
From: Hastings, Tom N [mailto:hastings at cp10.es.xerox.com] 
Sent: Wednesday, April 16, 2003 9:20 PM
To: sm at pwg.org
Subject: SM> document-creator-application-version ISSUE: For human or
program consumption?

The CIP4 System Behaviour and Interoperability WG reviewed the corresponding
FileSpec attributes and pushed back on the equivalent of the
"document-creator-application-version" Operation/Document Description
attribute as being for human consumption.  They thought it would be needed
by consuming programs to know how to process the data for those formats
which different versions had different semantics.

The current spec is as follows: 

6.1.4.2 document-creator-application-version (text(127))

This OPTIONAL member Operation attribute identifies the version number of
the application that created the document.   The intent of this attribute is
for display to a human being, rather than being parsed by the Printer for
purpose of affecting the interpreting by the Printer and so may also include
the name of the application, as well as build or service pack numbers.
Examples:  
"Winzip* 8.1 (4331)", "Acrobat 5.0.5 10/26/2001", "Microsoft* Word 2000
(9.0.4119 SR-1)"
When populating the "document-creator-application-version-implemented"
member attribute of the "document-format-details-implemented" Printer
Description attribute, some of the trailing information MAY be omitted, so
that a substring match of the Printer's value with the value supplied by the
client is sufficient for a match.  For example, the Printer's value MAY be
"Winzip* 8.1", "Acrobat 5.0", and "Microsoft* Word 2000" as compared to the
corresponding example values above that MAY be supplied by the client.
If the client omits this member attribute or supplies a zero length string,
that matches with any version.  Similarly, the Printer's member attribute
MAY be omitted or be a zero length string to indicate any.


The following fix would keep the definitions alligned, if the PWG also
agrees that this attribute is for program consumption:

6.1.4.2 document-creator-application-version (text(127))

This OPTIONAL member Operation attribute identifies the version number of
the application that created the document.   The intent of this attribute is
for purpose of affecting the interpreting by the Printer for any formats for
which the creator application version might have different semantics.  They
value MAY include build or service pack numbers.  Examples:  
"8.1 (4331)" for Winzip* , "5.0.5 10/26/2001" for Acrobat*, "2000 (9.0.4119
SR-1)" for Microsoft* Word
When populating the "document-creator-application-version-implemented"
member attribute of the "document-format-details-implemented" Printer
Description attribute, some of the trailing information MAY be omitted, so
that a substring match of the Printer's value with the value supplied by the
client is sufficient for a match.  For example, the Printer's value MAY be
"8.1", "5.0", and "2000", respectively, as compared to the corresponding
example values above that MAY be supplied by the client.
If the client omits this member attribute or supplies a zero length string,
that matches with any version.  Similarly, the Printer's member attribute
MAY be omitted or be a zero length string to indicate any.

Comments?

Tom



More information about the Sm mailing list