Here are the meeting notes from the 9/19 teleconference. There will not be
a teleconference on 9/26. The next teleconference will be on 10/3. The
Semantic Model & schema extensibility will surely be discussed again. I will
send out the teleconference information on 9/30. Let me know what you would
like on the agenda.
Xerox Architecture Center
Email: PZehler at crt.xerox.com
Voice: (585) 265-8755
FAX: (585) 265-8871
US Mail: Peter Zehler
800 Phillips Rd.
Webster NY, 14580-9701
Pete Zehler Xerox
Ira McDonald High North
Bob Taylor HP
Dave Hall HP
Alan Berkema HP
Ted Tronsen Novell
Lee Farrel Canon
Jerry Thasher Lexmark
Harry Lewis IBM
Tom Hasting Xerox
Norbert Schade Oak
1) PWG Semantic Model Issues
1a) Addition of Document Object attributes: (ISSUES 5 and 7 and general
Attributes will be added. Semantics of attributes will be
discussed on the IPP list and described in the Document Object document. We
will reference that document from the Semantic Model document.
1b) Addition of JobCopies, JobFinishings and JobFinishingsCol to the Job
Processing Attributes to separate job vs. document semantic of Copies,
Finishings and FinishingsCol.
1c) Resolve collision of MediaSize attribute (PWG vs. UPnP semantics)
Will rename UPnP's MediaSize to MediaSizeName and keep semantic
1d) Check FSG definition of Page Override
Semantic currently aligned. Will remove issue and keep
1e) Is DocumentStateMessage needed (ISSUE6)
1f) Should globalization be covered in the Semantic Model (ISSUE 9)
Consensus is yes but level of detail was not agreed upon. I will take
a stab at some globalization statements.
2) Element syntax for strings
The syntax for keyword, user settable strings and automata
The keywords (e.g. JobStateReasons, Finishings) will be NMTOKEN.
(NOTE: Further investigation indicates NMTOKEN and NMTOKENS should be used
only for attributes. The token type is used for elements) I will
investigate the appropriate types do discriminate the localized(invariant)
strings set by users and strings that are set by automata that can be
3) Mechanism for extending values for PWG keywords (i.e. type 2 and type 3
Separate mailnote(Keyword Extension Mechanism for schema) will be sent
out with the detail (further discussion required)
Four proposals are under consideration 1)appinfo, 2)union, 3)link
4)Derived Schemas. Current consensus is for solution 3.