SM> Semantic Model Teleconference info (10/02)

SM> Semantic Model Teleconference info (10/02)

McDonald, Ira imcdonald at
Tue Sep 30 13:28:54 EDT 2003

Hi Pete,

Your SM agenda doesn't agree with the agenda posted by Harry Lewis (Amy's
note this morning was out-of-date).  The agenda for next week (according
to Harry's note last Friday, 26 Sept):
PWG - NYC Meeting - 2003 Details
October 6 - 10, 2003
Grand Hyatt
New York, NY 


WBMM      Monday     9:30 - 5:00 pm  
PSI       Tuesday    8:30 - 5:00 pm  
Plenary   Wednesday  8:30 - Noon and 1:00 pm - 2:30 pm 
CR        Wednesday  2:30 - 5:30 pm  
IPP Exts  Thursday   8:30 am - Noon
Semantic  Thursday   1:00 - 5:00 pm  
Notify /  Friday     8:30 - 1:00 pm  

Park Avenue at Grand Central Station
New York, New York
10017 USA
1 212 883 1234


- Ira McDonald
  High North Inc

PS - I'll probably have to miss the SM telecon this Thursday, due
to a time conflict.  Good luck.

-----Original Message-----
From: Zehler, Peter [mailto:PZehler at]
Sent: Tuesday, September 30, 2003 1:10 PM
To: PWG Semantic Model WG (sm at; IPP Discussion List (IPP at
Subject: SM> Semantic Model Teleconference info (10/02)


We will have a Semantic Model Teleconference this week.  The teleconference
details are below.  The agenda is below.  Please send out any
comments/issues you wish to discuss during the teleconference by cob
Wednesday.   Current list of comments is appended below.


1)      Adjust agenda 
2)      Quick status of SM, Schema, JobX, Overrides and Document Object 
3)      Discuss upcoming face to face 
a.      Tuesday SM (1/2 day pm) 
b.      Thursday IPP extensions (1/2 day am) 
c.      Thursday JobX (1/2 day pm) 
4)      Review any comments/issues 
a.      Handle editorial first 
b.      Discuss more involved comments and issues 
5)      Next steps 

Peter Zehler
Xerox Innovation Group
Email: PZehler at
Voice:    (585) 265-8755
FAX:      (585) 422-7961
US Mail: Peter Zehler
        Xerox Corp.
        800 Phillips Rd.
        M/S 128-25E
        Webster NY, 14580-9701
Meeting Date: 10/02/2003
Meeting Time: 11:50 AM CENTRAL TIME
Instant Meeting Details:
USA Toll Free Number: 877-707-6056
VNET Number(Xerox): 8*594-0077
Participant Passcode: 437874
Meeting Date: 09/30/2003 
Meeting Time: 1:00 PM Eastern (11:00 AM Pacific)
Instant Net Conference Details:
Meeting Number:          747275324
Meeting Passcode:        PwgSm
Meeting Host:            Pete Zehler
Join Instructions for Instant Net Conference:

1. Join the meeting now: 
2. Enter your name
3. Agree to the Terms & Conditions and click Proceed.
1. Go to 
2. Type in the Meeting Number
3. Type in the Meeting Passcode (if one was provided)
4. Choose "Conference" and click Proceed
5. If you are a new user, click on "New Users" to check your system 
and download the software and go back to Join Net Conference page
6. Enter your name
7. Agree to the Terms & Conditions and click Proceed.
Current list of comments.issues (9/30/03):
Document Object
Editorial Comments:
1) Cover Page Line 26:
The sentence about listing "all" of the attributes defined in other IPP
specifications is probably not going to be accurate for very long.....if
2) Page 9, line 311:
The sentence should read.... "The semantics of the
"document-state..."...(missing "the").
3) Page 9, line 317-320:
This paragraph needs to be reworded to state what the spec. is, not what
it's proposed to be.
4) Page 13, line 403:
The Job operatations that MUST NOT have any ..... (remove the word "that" )
5) Page 14, line 413:
The semantic of Fidelity on a Job are intended..... (The "semantics" of
6) Page 15, line 446,447,451
The sentence "For example, such Job Template attributes as
"job-priority"...." sounds odd.. (should read "For example, Job Template
attributes such as .....) Same comment for line 447 and 451 "Printer MUST
NOT copy down any..." (should be "Printer MUST NOT copy any Job Level
attributes ...")
7) Page 21, line 653: is only an empty job which is.... (recommend: "it is an empty job that
is scheduled and...)
8) Page 24, line 777:
..Document object was submitted...(should be: ...Document object is
9) Page 24, line 781:
..The only differences are that the Set-Job-Attibutes operation is...
(should be: ..The only difference is that the ...operation is...)
10) Page 26, line 831,832:
Formatting problem (unnecessary indentation....)
11) Page 26, line 833:
First sentence worded funny. (suggest: Most Document Description attributes
(see...)are NOT settable, i.e., they are defined to be READ-ONLY.)
12) Page 45, line 1258:
First character space on that line is inadvertently highlighted...
13) Page 48, line 1305, 1309; Page 51, line 1389;
Remove the names of the attribute at the beginning of the description.  It's
both unnecessary and inconsistent with the other attribute descriptions.
(There are other descriptive paragraphs with the same problem..Page 58,59
14) Page 57, line 1571:
First printed character (') is highlighted for no reason.
15) Page 65,66,67
Remove highlighted areas...
lines 1776-1778, 1785-1787, 1795-1797, 1830, 1844-1846, 1847-1849. Page 66,
line1828 (PrintBasic: 1.0) is in red....
15) Page 75, line 2221,2224
Broken reference links.....
16) Page 14, line 430-431:
After a strong conformance statement on the client, the printer is required
to accept a non-conformant client operation..... (should be an error if the
client supplies this attribute in a Doc Creation operation.. and the Printer
should be allowed to flag it..)
17) Page 26, line 837-839:
The note that provides guidance for future extensions doesn't belong in a
specification, it belongs in the requirements doc of the future'll get lost in this spec.... (suggest removing the note)
18) Page 28 Cancel-Document operation (and line 922)
Question/Comment: What happens to the document DATA when a document is
cancelled (assuming it's already been sent to the Printer)?
Line 922 should read ....which only cancels the processing of the document,
and doesn't delete the document object itself.....
But it still says nothing about the document DATA. If the DATA is kept after
a Cancel Document then there may be a security issue for the overly security
conscious since this is the only way a client can request a document NOT be
processed (then the data hangs around in the print spool for some unknown
time). (Cancel Doc is mandatory for Printer, Delete Doc is optional)
If the Data is not kept, what is the mechanism for the reprocess job
operation if the data is expected to be there?
JobX ( 
Editorial Comments:
19) Page 13, footnote 5
Operation is partially italicized....(shouldn't be)
20) Page 34, line 1051
Need a little more informative test explaining what these are in addition
21) Page 37, line 1162
the word "PrintBasic:1.0" is in red....
22) See page 16 Lines 497 - 500 of the Sept. 8 Draft....
Action Item: (Tom and Ira): Propose a format for the file......
Did this get resolved and/or just missed in the final edits?
No comments

More information about the Sm mailing list