Printer Services Mail Archive: PS> RE: [PSI]: minutes 6/11/

PS> RE: [PSI]: minutes 6/11/02

From: BERKEMA,ALAN C (HP-Roseville,ex1) (alan_berkema@hp.com)
Date: Tue Jun 18 2002 - 18:08:57 EDT

  • Next message: BERKEMA,ALAN C (HP-Roseville,ex1): "PS> PSI Minutes from -- Apr '02"

     
    PSI Working Group:
    *Alan Berkema Gail Songer *Dave Hall
    *Jerry Thasher Harry Lewis Ted Tronson
     Peter Mierau *Peter Zehler Paul Tykodi
    *Bob Taylor Don Levinstone *Lee Farrell
    *Don Wright *Kirk Ocke *Ira Mcdonald

    * = attendance

    06/18/02 Agenda
    1) Review Target Device Identifier and Reference schema
    2) Review PWG Semantic model with consideration for PSI

    Minutes:
    1) Review Target Device Identifier and Reference schema
    Postponed to F2F

    2) Review PWG Semantic model with consideration for PSI

    Spent most of the meeting talking about the PWG Semantic model
    using rev 06-020617.
    Started with Figure 5. Is this just an example of how Attributes
    could be used or is this the actual model?
    PSI is very close to this except that PSI has separated out Job
    and Content Objects.

    Talked about 3 levels of the Semantic Model
    1) Base Attribute Definitions
    2) Structure Definitions
    3) Base Operational Model

    For PSI JobAttributes, ContentAttributes, RenderingAttributes,
    FinishingAttributes and ImpositionAttributes are all Base Level
    Attribute groupings.
    The Base Attributes are defined within each of these.

    Job and Processing are structures which import the Base Level
    Attribute groupings.

    General discussion on grouping indicated a desire for the appropriate
    level of granularity.
    One extreme would be no grouping at all, just attribute defs like
    words in a dictionary, while this has some value since we would all
    have the same definitions, it does not move the model forward for
    interoperability and reuse. It looses the semantic meaning.

    Another extreme is to group them all together. This would be too much for
    some
    applications and might still not be enough for others.

    Need a compromise that could allow profiles to structure the Base level
    groupings in a way that suits the application.

    Also decided that Fidelity should be part of Job as well as Content.

    See ya next week,
    Alan

    ----
    

    0) Job Control Interface starting to stabilize

    Work Remaining Overview: 1) Finalize reference and Target Device Schemas 2) Attributes: PSI has Job, Document, and Processing (template) Need to help with and leverage the PWG semantic model attributes 3) Discovery, PS and the target Devices a PS knows about? 4) Revisit Target Device Interface 5) Status code, hoping that this will also be part of the PWG semantic model for leverage 6) Event Notification 7) Security

    Finish all that and PSI is done :)

    New 6/11/02 Actions: 1) Referenc schema work user name, passwd, certifiacte and e-mail elements. Owner: Kirk: 2) Investigate original thouts on time attribute with Bluetooth folks Owner: Alan 3) Examine Use Models for Job Control interface implemenation owner: Dave

    Thanks, Alan



    This archive was generated by hypermail 2b29 : Tue Jun 18 2002 - 18:09:09 EDT