C) Allow system entities to use standard XML tools and the PWG (and
potentially other) schemas to determine that a request is well formed
D) Facilitate development around the PWG semantic model by creating
schema structures that expose both objects and values through commonly used
As for B), I'd say the semantic model certainly needs to enable capabilities
to be ascertained, but I'm not honestly sure whether it's in scope for the
SM project to "completely" solve this. It may be sufficient here just to
declare the objects & values in such a way that they can be readily used by
capabilities schemes, and that the "full" capabilities problem will be
solved in forums like PSI & UPDF.
> -----Original Message-----
> From: Zehler, Peter [mailto:PZehler at crt.xerox.com]
> Sent: Thursday, September 26, 2002 5:50 AM
> To: PWG Semantic Model WG (E-mail)
> Subject: SM> Keyword Extension ISSUE 1
>> As stated in the previous mail note "CORRECTED Keyword
> Extension Mechanism
> for schema" sent earlier, I would like to resolve ISSUE 1.
>> ISSUE 1: What requirements do we have to help us close on a solution?
>> It seems to me that the primary objectives are to
> A) Insure that the schema for the print model is easily
> extended. For both vendors and sites. The extensions should
> be allowed at
> both the object and semantic element value levels.
> B) Enable print client developers to ascertain the
> of a print device at runtime.
>> I think I heard a requirement that a client be able to
> determine that a
> request is well formed, in the PWG schema sense, using XML
> tools and the PWG
> schema. Am I hearing that requirement correctly?
>> What do you think the requirements are for selecting a
> solution for schema
>>> Peter Zehler
> Xerox Architecture Center
> Email: PZehler at crt.xerox.com> Voice: (585) 265-8755
> FAX: (585) 265-8871
> US Mail: Peter Zehler
> Xerox Corp.
> 800 Phillips Rd.
> M/S 128-30E
> Webster NY, 14580-9701