SM> Adding 4 more member attributes to "document-format-detai l" (coll ection) attribute

SM> Adding 4 more member attributes to "document-format-detai l" (coll ection) attribute

SM> Adding 4 more member attributes to "document-format-detai l" (coll ection) attribute

Hastings, Tom N hastings at cp10.es.xerox.com
Wed Jan 22 21:20:34 EST 2003


For the Semantic Model face to face on Thursday:

Ira and I talked today and we propose the following tweaks to the IPP and
JDF proposals:

1. Don't use the term "platform" in the attribute name, use "os" or
"operating-system (OS or OperatingSystem in JDF).  The term "platform" often
means the middleware.  What we want here is the operating system.  Also the
IANA Registry is called Operating System Names.
See: http://www.iana.org/assignments/operating-system-names

2. The IANA Registry has token strings without spaces that include the base
operating system name and the version.  Examples are: 'linux', 'linux-2.2',
'os/2', 'mac', 'mac-x', 'sun-os-4.0', 'unix', 'unix-bsd', 'win32',
'windows-95', 'windows-98', 'windows-ce', 'windows-nt', 'windows-nt-4',
'windows-nt-5', 'windows-2000', and 'unknown'.  However, it is useful for
software to determine the base operating system independent of the version
and to also determine the version.  To get both, it is simpler to have two
attributes.   We also propose that the second attribute (the one that
includes the version), be the complete IANA registry entry, rather than just
the version and be named: "os-name-and-version".  Applications can then
choose which attribute to match on and no parsing is needed.

I've downloaded an updated proposal for IPP and JDF which in summary is at:
ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/Comparison of JDF and IPP
document-format-attrs.pdf (213K)
ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/Comparison of JDF and IPP
document-format-attrs.doc (264K)
ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/Comparison of JDF and IPP
document-format-attrs.zip (33K)

This downloaded document proposes adding 3 more attributes to JDF FileSpec
resource: 
MimeTypeVersion, IEEE1284DeviceId, and DocumentPart. 

and clarify that 

and 4 more member attributes to the proposed IPP "document-format-details
(collection):: 
"application-name", "application-name-and-version", "os-name-and-version",
and
"user-file-name" 

in order to align both of them and to take the features of one and make them
available in the other.

Comments?

Tom


-----Original Message-----
From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
Sent: Wednesday, January 22, 2003 13:44
To: 'Hastings, Tom N'; sm at pwg.org
Cc: ipp at ipp.org
Subject: RE: SM> Adding 4 more member attributes to
"document-format-detai l" (coll ection) attribute


Hi Tom,

There's some confusion in your proposal below.

The current "document-format-detail" member attribute "platform"
and the proposed additional member attribute "platform-version"
(or "os-version") are likely to be redundant.

The only standardized source of values for all these attributes
is the IANA registry of operating system names - it contains BOTH
OS and version as a single string (e.g., "WINDOWS-95") and
generally does NOT contain the simple name (e.g., there is no
registered "WINDOWS" operating system).  See:

ftp://ftp.iana.org/assignments/operating-system-names

In the IPP Driver Installation spec we have a single attribute
"os-type" (with the values normalized to lowercase for IPP).  See:

ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipp-install-04.txt

Cheers,
- Ira McDonald
  High North Inc

-----Original Message-----
From: Hastings, Tom N [mailto:hastings at cp10.es.xerox.com]
Sent: Tuesday, January 21, 2003 8:06 PM
To: sm at pwg.org
Cc: ipp at ipp.org
Subject: SM> Adding 4 more member attributes to "document-format-detail"
(coll ection) attribute


PWG Semantic Model folks (and IPP WG folks),

This is a similar mail message that I've send to the CIP4 JDF Capabilities
WG.

The IPP Document object spec has a "document-format-detail" (collection)
attribute which contains member attributes that give more information about
a document, such as "document-format-version",
"document-format-natural-language", "platform", "device-id", and a recursive
"document-format-details" (collection) to describe the unique Parts of an
application/zip or multipart/related file.   See:
ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/pwg-ipp-document-object-latest.pdf

The IPP "document-format-details" (collection) attribute is much like the
FileSpec resource in JDF.  So I've downloaded a comparison of the IPP
document format attributes including the proposed "document-format-detail"
(collection) attribute and the JDF/1.1 FileSpec resource.  See:
ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/Comparison of JDF and IPP
document-format-attrs.pdf (213K)
ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/Comparison of JDF and IPP
document-format-attrs.doc (264K)
ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/Comparison of JDF and IPP
document-format-attrs.zip (33K)

This downloaded document proposes adding 3 more attributes to JDF FileSpec
resource: 
MimeTypeVersion, IEEE1284DeviceId, and DocumentParts. 

and 4 more member attributes to the proposed IPP "document-format-details
(collection):: 
"application", "application-version", "platform-version" (or "os-version"),
"user-file-name" 

in order to align both of them and to take the features of one and make them
available in the other.

I'll be glad to write up the new JDF FileSpec attributes (if the CIP4
Capabilities WG likes the proposed semantics) and update the IPP Document
object spec (if the PWG Semantic Model WG likes the proposed semantics). 

Comments?

Thanks,
Tom 



More information about the Sm mailing list