archive-org.com » ORG » J » JEFFSUTHERLAND.ORG

Total: 379

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Communication by Speech Act
    version Notes Speech act theory is a framework to account for communication between humans which has been adapted and extended as a general model of communication amongst agents of any kind Content expresses the action and object s to which the speech act refers and its context describes its situation including the speaker addressee time location and circumstances of the message These concepts form messages which typically have a communication

    Original URL path: http://jeffsutherland.org/oopsla98/marshall/tsld007.htm (2016-04-27)
    Open archived version from archive


  • Using Business Protocols
    Previous slide Next slide Back to first slide View graphic version Notes Understanding of terminology requires a shared vocabulary or common ontology to describe the concepts relationships and jargon of various domains Examples of message formats include EDIFACT and ANSI X12 for EDI Knowledge Query and Manipulation Language KQML for knowledge sharing and OAGIS messages for interaction of business applications Before a unit can communicate it must be able to

    Original URL path: http://jeffsutherland.org/oopsla98/marshall/tsld008.htm (2016-04-27)
    Open archived version from archive

  • Entity & Process
    process based systems and helps to partition the aspects of an entity amongst different areas of interest The concept of an organization role is used both to partition a process for workflow and security purposes and to partition an entity

    Original URL path: http://jeffsutherland.org/oopsla98/marshall/tsld009.htm (2016-04-27)
    Open archived version from archive

  • Situation & Policy
    occurs an obligation is incurred in terms of the policy and a process is scheduled to fulfill the obligation Note that an obligation is an objective that flows from a rule such as a law convention standard or contract It is typically incurred when a directive message in terms of a contract is sent from a customer to a supplier but may be created by a state of affairs that

    Original URL path: http://jeffsutherland.org/oopsla98/marshall/tsld010.htm (2016-04-27)
    Open archived version from archive

  • Contract Text
    ship it shall pay a penalty of 10 of total order value 4 The Shipper shall deliver the shipment within ten days 5 The Customer shall pay the Supplier within thirty days of receipt of the shipment 6 Finally should the Shipper fail to deliver the shipment it shall pay its full value to the Supplier Signed at on by Previous slide Next slide Back to first slide View graphic

    Original URL path: http://jeffsutherland.org/oopsla98/marshall/tsld011.htm (2016-04-27)
    Open archived version from archive

  • Contract Diagram
    that can be used by an information system These slides show how a contract can be designed using UML and implemented in XML one of many options Just as a contract has clauses that specify the courses of action in all situations a contract diagram represents it through its deontic states and the conditions which relate them This is a specialization of a state transition diagram in which each state

    Original URL path: http://jeffsutherland.org/oopsla98/marshall/tsld012.htm (2016-04-27)
    Open archived version from archive

  • Contract Class
    its fulfillment cancellation and violation Each results in another state of affairs coming into effect which is ultimately the terminating clause of the contract A set of clauses oblige permit or prohibit each party to perform processes in terms of the contract where permission and prohibition are types of authorization The appropriate process may be instantiated in terms of the contract and when completed results in a new state of

    Original URL path: http://jeffsutherland.org/oopsla98/marshall/tsld013.htm (2016-04-27)
    Open archived version from archive

  • XML Contract
    062 060PARTY 062 entity party Supplier 060OBLIGE 062 2 060DESCRIPTION 062The Supplier shall ship the Product via the Shipper 060 DESCRIPTION 062 060FULFILL 0624 process sale Ship 060 FULFILL 062 060VIOLATE 0623 process sale Reject 060 VIOLATE 062 060 OBLIGE 062 060OBLIGE 062 3 060DESCRIPTION 062Should the Supplier fail to ship it shall pay a 060 DESCRIPTION 062 060FULFILL 062END process sale PayPenalty 060 FULFILL 062 060 OBLIGE 062 060 PARTY 062 060PARTY 062 entity party Shipper 060OBLIGE 062 4 060DESCRIPTION 062 The Shipper shall deliver the shipment within ten 060 DESCRIPTION 062 060FULFILL 0625 process ship Deliver 060 FULFILL 062 060VIOLATE 0626 060 VIOLATE 062 060 OBLIGE 062 060 PARTY 062 060 CONTRACT 062 Previous slide Next slide Back to first slide View graphic version Notes The power of XML to structure a document and to tag its content with labels to give it meaning provides the opportunity to define policies and the processes by which they are enforced To illustrate this the supply contract is translated into an equivalent XML document The textual form of the document can be reconstructed from the 060DESCRIPTION 062 sections including its party and clause elements Each 060CONTRACT 062 has a name and

    Original URL path: http://jeffsutherland.org/oopsla98/marshall/tsld014.htm (2016-04-27)
    Open archived version from archive



  •