OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: JB Clark 12/21/2004: Some references on HasLegalIntent


Jamie,
As requested today, here are some historical details:

    * Original summary:
      http://www.oasis-open.org/archives/ebxml-bp/200407/msg00065.html
      (July 2004)
    * Further clarifications:
      http://www.oasis-open.org/archives/ebxml-bp/200410/msg00128.html
      (Oct 2004)
    * Draft verbiage:

        a. Decision on draft verbiage:
        http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/9903/ebbp-mtgminutes-mm1-110104.txt
        (1 Nov 2004)
        b. Release of draft verbiage:
        http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200411/msg00004.html
        c. Update of draft verbiage:
        http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200411/msg00036.html

Current draft technical specification language:
=====================================================================================================
A business transaction activity MAY specify that this particular 
document interchange “has legal intent” via the hasLegalIntent attribute.
This attribute is optional and means that particular activity that could 
represents a statement or commitment between trading partners, and
their shared intent. Referencing the eCommerce Patterns v1.0 
[http://www.ebxml.org/specs/bpPATT.pdf], the digital signature cannot in 
and of
itself infer intent. This constraint could be used as a substantive and 
enforceable precondition on the BTA. The mechanisms in the BSI that
provide the capability to support this precondition are:

· reliability
· document security: confidential, tamper detectable and authenticated
· nonrepudiation
· authorization
· predictability

The hasLegalIntent attribute could have widely differing interpretations 
and enforceability depending on type of business, process, and
jurisdiction. No implication of interpretation or enforcability is made 
by the ebBP specification. The contractual framework, agreements
and their application to any artifact are outside the scope of this 
specification.
=====================================================================================================

Thanks.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]