courtfiling-reqts message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [courtfiling-reqts] Groups - Profile Requirements Strawman (P rofileRequirementsStrawman.doc) uploaded
- From: "Scott Came" <scott@justiceintegration.com>
- To: courtfiling-reqts@lists.oasis-open.org
- Date: Tue, 9 Aug 2005 14:39:12 -0700 (PDT)
Shane:
While Query and Transaction interaction models may exist, at a conceptual level, I'm failing to see
why it's important to force profiles to distinguish between them. They are both implemented as operations on MDEs.
The requirement that a profile support message transmissions (as defined in the strawman) seems to support them, does
it not?
With respect to Event interaction models, which MDE operations and/or messages identified in the
existing domain model constitutes an Event interaction? Do we actually have any of these defined in the current draft
spec? I don't disagree that these could exist in theory...I just don't believe we've identified any in practice, as
things currently stand.
Perhaps we just need an explicit requirement: A profile must support the
transmission of messages from a sender to an MDE.
Thanks.
--Scott
> Scott, Jim,
>
> I agree with most of Jim's questions and comments.
>
> In addition, I have these
comments:
>
> I think we should stress our interaction models as part of the definition of
>
the MDE, and part of the profile requirements.
>
> The interaction models (aka operation types) that
we have discussed:
>
> Query (Data Access)
> Transaction (Data Update)
> Event
(Notification)
>
> We might say: An MDE is a logical grouping of one or more of these operation
> types.
> We might go onto conclude: A requirement of a profile is to support these
>
interaction models.
>
> One profile property that might then be concluded, is that the profile
must
> support a 'synchronous' call-response mechanism.
> Here's why:
>
> Our three
operation types all involve synchronous call-response:
>
> Query:
> GetCase ( myCaseId ) :
Case
>
> Event:
> NotificationOfX ( myNotice ) : messageReceipt
>
>
Transaction:
> ReviewFiling ( myFiling ) : messageReceipt
> ReviewFiling_Callback ( myFilingReceipt
) : messageReceipt
>
> All of the interactions we have discussed have a 'synchronous' aspect to
> them.
> A profile must be able to support, or sufficiently emulate, this type of
> behavior.
>
> - Shane Durham
> LexisNexis
>
>
>
>
>
-----Original Message-----
> From: scott@justiceintegration.com [mailto:scott@justiceintegration.com
>
]
> Sent: Wednesday, July 27, 2005 10:02 AM
> To:
courtfiling-reqts@lists.oasis-open.org
> Subject: [courtfiling-reqts] Groups - Profile Requirements
Strawman
> (ProfileRequirementsStrawman.doc) uploaded
>
> Here is a listing of requirements
to get us started on the profile
> requirements.
>
> Can we get a discussion going soon on
this? I will be on vacation next
> week and unable to participate in any discussions...
>
>
Thanks.
> --Scott
>
> -- Mr Scott Came
>
> The document named Profile
Requirements Strawman
> (ProfileRequirementsStrawman.doc) has been submitted by Mr Scott Came to
> the
LegalXML Court Filing Requirements SC document repository.
>
> Document Description:
> A
listing of requirements to get us started on the profile requirements.
>
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/courtfiling-reqts/document.php?
> document_id=13788
>
> ?document_id=13788>
>
> Download Document:
>
http://www.oasis-open.org/apps/org/workgroup/courtfiling-reqts/download.php/
>
13788/ProfileRequirementsStrawman.doc
>
> /13788/ProfileRequirementsStrawman.doc>
>
>
> PLEASE NOTE: If the above links do not work for you, your email application
> may be
breaking the link into two pieces. You may be able to copy and paste
> the entire link address into the
address field of your web browser.
>
> -OASIS Open Administration
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]