[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [legalxml-courtfiling] Policy MDE vs. MDE Policies
One of my 'ToDos' from the last face-to-face (at CTC9)...
...was to compose an email to restate my position on our approach to
'policy'.
The debate is really about this:
Should there exist a single, consolidated policy set, describing the
behavior of all implemented MDEs participating in a system? Or, should each
implemented MDE express its own policy set, describing the behavior and
code-sets of that specific MDE?
I think John poetically described the issue this way: "Is there a
PolicyMDE... or are there MDE Policies?"
To understand my position, you first need to understand how I perceive
'policies'.
I see 'Policy' as the MDEs' "rules of engagement" - a set of rules to
describe the interactive behavior of our implemented MDEs
'Policy' can describe things such as:
- The valid codes you may use or expect when performing an interaction with
the MDEs.
- The argument extensions or restrictions to the 'normalized' set of MDE
interactions.
- The set of (link to) business rules regarding MDE interactions (court
hours, font size).
Furthermore, I see policies as describing the interactions of any our
implemented MDE.
Others see 'Policies' as describing (or controlling) only interactions with
the court, whether it be an interaction we have categorized as FilingReview,
or whether it is an interaction we have assigned to CourtRecord. Their
point of view is often reflected in their nomenclature: 'Court Policies',
rather than simply 'Policies'.
To be fair, all of the Policies we have discussed so far, happen to only be
concerned with how we interact with the court. For example, we have not yet
discussed policies for FilingAssembly, because, coincidentally, our scope
has not officially recognized any queries or transactions into the
FilingAssembly MDE (aside from a Callback function), though, we all agree
that FilingAssemblyMDE could define transactions and queries, and,
presumably, those interactions would then have the potential to have
associated policies.
Perhaps, the lingering 'Court Policy' concept reflects that some of us are
not entirely on-board with the 'MDE' approach to the system. That's fair
enough - MDE is merely an architectural concept which might or might not be
successful for us in the long run - but, nevertheless, at this point, for
this version of LegalXML, we have decided to pursue the MDE approach, and, I
feel, we need to be thoroughly consistent with it.
If we have agreed to organize our court interactions into 'FilingReview' and
'CourtRecord', then, we should also agree to categorize the MDE's 'rules of
engagement' along those same lines:
These are the 'FilingReview' rules...
And Those are the 'CourtRecord' rules...
At the face-to-face, I seemed to get some decent buy-in on that concept. It
was noted that some of our rules (such as query extensions/restrictions) are
distinctly MDE-specific, and those policies should therefore be organized by
MDE.
But, just because we might agree that policies should be organized by MDE,
does not mean that they could not continue to be consolidated into a single
file. The question remained: Should there exist a single file to express
all policies of all implemented MDEs?.. or should the system consist of
multiple policy files, one per implemented MDE?
So, do we want to see something like this?:
SystemPolicy
CourtRecord (MDE 1)
CodeSet1, QueryExtension2, QueryRestriction3, etc.
FilingReview (MDE 2)
CodeSet1, QueryExtension2, QueryRestriction3, etc.
Or, something like this?:
Policy-1 for CourtRecord ( MDE 1 )
CodeSet1, QueryExtension2, QueryRestriction3, etc.
Policy-2 for FilingReview ( MDE 2 )
CodeSet1, QueryExtension2, QueryRestriction3, etc.
Now, I look around me for another real-world example of the proposed
singleton approach.
I can think of none.
- Some may refer to Windows registry as an example of a consolidated set of
rules
First of all, this is a bad example: WindowsRegistry isn't really intended
to be a way for system components to describe themselves to one another.
The registry might persist component settings but it is not intended to be a
publisher of settings. For example: MicrosoftWord has a documented API by
which you can learn of its settings - you are not supposed to go poking
through WindowsRegistry to learn about word's settings.
Nevertheless, we'll run with this example....
....if you were to look at distributed systems that rely on WindowsRegistry
to persist settings, you would find that a single windows registry is not
used to capture all settings of the entire system. If you were running in a
Windows environment, each of your distributed components (on separate
machines) would use their local windows registry to manage their settings.
And, in a distributed environment, there would not exist a single registry
from which all components exchange their configurations. Component-A
doesn't learn about Component-B by means of a shared WindowsRegistry. In
windows (COM or DCOM), Component-A typically learns about Component-B's
settings... by directly interacting with Component-B's API.
(Note: Component-A learns about the existence of Component-B through
another mechanism, which we have referred to as a 'directory'. 'Directory'
describes the location of a component - it is not related to 'policy'. )
- Some might think of DNS as an example of a consolidated set of rules.
DNS is, in fact, an example of a directory of other systems. It provides a
consolidated means to find other systems. It does not represent a
consolidated set of rules for interacting with those systems. It is little
more than a list of addresses.
- Some may refer to UDDI, for WebServices, as an example of consolidated
rules.
UDDI is an excellent example of how components might publish their 'rules of
engagement. However, UDDI does not represent the singleton approach.
UDDI represents a singular access point for finding or obtaining individual
rules (i.e. WSDLs - the syntactical rules of a WebService). A consumer
still asks the UDDI host for WSDLs, one by one. The WebService rules are
*still* organized, and segregated, by the individual WebServices.
(Truth be told, I feel that UDDI is a much better example of the position I
am advocating than as an example of the singleton approach.)
I have further basis for my position on this issue. I drafted a larger
email illustrating how the singleton approach gets to be very difficult to
implement once the system begins to incorporate multiple CourtRecordMDEs
(court-1 and court-2 policy), or if the system begins to incorporate
FilingAssembly queries...
....but, for now, I'm going to pause here for feedback on this much:
Consider:
1) Do we agree that Policies are MDE-specific ( Such as MDE-query
extensions/restrictions? )
2) If so, then, can we agree that Policies should then be organized by MDE
(MDE-1's policies vs. MDE-2's policies)?
3) Can we agree that the proposed 'singleton' approach is inconsistent with
other types of distributed multi-component systems?
If we can agree on that much, then why would we want to adopt the proposed
'singleton' approach?
If I left my position at this much:
'MDE policies' is an approach that is most consistent with other
distributed system designs (UDDI)....
or , conversely,
'PolicyMDE' is an approach that is inconsistent with other distributed
system designs....
....then, is anyone able to disagree with that assessment?
...and/or, is anyone willing to provide an explanation of how the
'singleton' approach is still better and worthy of pursuit?
Will my dissenters please stand?
- Shane
LexisNexis
------_=_NextPart_001_01C5C3A0.FA5A77C6
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40"; xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2800.1515" name=3DGENERATOR>
<META content=3D"Microsoft Word 11" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C58C5A.845F98D0"; =
rel=3DFile-List><o:SmartTagType=20
name=3D"PostalCode"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"State"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"City"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"Street"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"address"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
</w:LatentStyles>
</xml><![endif]--><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; =
}
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: =
personal-compose; mso-style-noshow: yes; mso-ansi-font-size: 10.0pt; =
mso-bidi-font-size: 10.0pt; mso-ascii-font-family: Arial; =
mso-hansi-font-family: Arial; mso-bidi-font-family: Arial
}
SPAN.GramE {
mso-style-name: ""; mso-gram-e: yes
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
</style>
<![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue=20
bgColor=3D#ffffff>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2>>> <FONT=20
face=3DArial color=3D#000000>non-programming specific=20
policies</FONT></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>I believe you mean business rules, such as =
font-size,=20
page-colors, document format (word, pdf,=20
wordperfect)...</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>I'll call these 'business=20
practices'.</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN> </DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>I think we said that the 'Policies' =
would contain=20
a link to some URL/document which expresses business practices in =
plain=20
english.</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN> </DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>So, to your =
suggestion...</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>>> <FONT face=3DArial =
color=3D#000000> the=20
single court policy can maintain non-programming specific policies, and =
it can=20
also point to the MDEs specific programming=20
policy</FONT></SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DArial color=3D#000000 =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN> </DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>Try this instead: =
</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>The individual MDE policies can point =
to the=20
same central 'business practices' URL.</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>(And, if necessary, they still have the =
flexibility=20
to refer to MDE-specific business practices as=20
well.)</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN> </DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>I think this approach would be more =
consistent with=20
the current spec and MDE concept.</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN> </DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005>- Shane</SPAN></FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN> </DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D615455119-27092005></SPAN></FONT></SPAN> </DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><SPAN=20
class=3D615455119-27092005> </SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT face=3DTahoma=20
size=3D2><B>From:</B> Dallas Powell [mailto:dpowell@tybera.com] =
<BR><B>Sent:</B>=20
Tuesday, September 27, 2005 12:50 PM<BR><B>To:</B> Durham, Shane =
(LNG-SEA);=20
legalxml-courtfiling@lists.oasis-open.org<BR><B>Subject:</B> Re:=20
[legalxml-courtfiling] Policy MDE vs. MDE Policies<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=3DArial size=3D2>From my recollection during the =
Friday f2f the=20
group agreed that because query was code specific it would be =
reasonable to=20
allow the MDEs to each control their own query interface and not =
have a=20
centralized definition. But because 'Policy' dealt with issues =
that were=20
not just code specific, the group seemed to be of the opinion that =
policy should=20
be centraized. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Shane your arguments seem to =
address the=20
programming view. The options you have presented are a single =
policy or=20
MDE specific policies and no other option. It seems to me that =
there can=20
be a middle ground where the single court policy can maintain =
non-programming=20
specific policies, and it can also point to the MDEs specific =
programming=20
policy. Perhaps we should allow for a division of =
non-program=20
specific policies in the central policy and MDE specific policy which =
could be=20
aggregated together in a central location or point to the MDE specific=20
portion.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It is fair to say that someone is =
going to have to=20
manually create a policy that contains non-programming items =
while the MDEs=20
may have programatic methods of exposing their policies.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Dallas</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3DShane.Durham@lexisnexis.com=20
=
href=3D"mailto:Shane.Durham@lexisnexis.com";>Shane.Durham@lexisnexis.com<=
/A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
title=3Dlegalxml-courtfiling@lists.oasis-open.org=20
=
href=3D"mailto:legalxml-courtfiling@lists.oasis-open.org";>legalxml-court=
filing@lists.oasis-open.org</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, September 26, =
2005 11:45=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> =
[legalxml-courtfiling] Policy=20
MDE vs. MDE Policies</DIV>
<DIV><BR></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>One of my 'ToDos' from the last =
face-to-face (at=20
CTC9)...</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>...was to compose an email to restate my =
position on=20
our approach to 'policy'.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN =
class=3D163282615-25092005></SPAN></FONT><FONT=20
face=3DGeorgia color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>The debate is really about this: =
</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005>Should there exist a =
single,=20
consolidated policy set, describing the behavior of all implemented =
MDEs=20
participating in a system? Or, should each implemented MDE =
express its=20
own policy set, describing the behavior and code-sets of that =
specific=20
MDE?</SPAN></FONT></DIV></BLOCKQUOTE>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>I think John poetically described the =
issue this way:=20
"</SPAN></FONT><FONT face=3DGeorgia color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005><STRONG>Is there a PolicyMDE... =
or are there MDE=20
Policies?</STRONG>"</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN =
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>To understand my position, you first need =
to=20
understand how I perceive 'policies'.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><STRONG>I see 'Policy' as the MDEs' =
"rules of=20
engagement"</STRONG> - a set of rules to describe the =
interactive=20
behavior of our implemented MDEs </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN =
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D163282615-25092005><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>'Policy' can describe things such=20
as:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>- The valid codes you may use or=20
expect when performing an interaction with the=20
MDEs.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>- The argument extensions or =
restrictions to the=20
'normalized' set of MDE interactions.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>- The set of (link to) business rules =
regarding=20
MDE interactions (court hours, font size).</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D163282615-25092005>Furthermore, <STRONG>I see =
policies as=20
describing the interactions of <EM>any</EM> our implemented=20
MDE.</STRONG></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN =
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT=20
face=3DGeorgia><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT =
face=3DGeorgia><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT =
face=3DGeorgia><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT =
face=3DGeorgia><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT =
face=3DGeorgia><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT =
face=3DGeorgia><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D163282615-25092005>Others see 'Policies' as =
describing (or=20
controlling)<EM> only</EM> interactions with the court, whether =
it be an=20
interaction we have categorized as FilingReview, or whether it is an=20
interaction we have assigned to CourtRecord. Their =
point of=20
view is often reflected in their nomenclature: '<STRONG>Court=20
Policies</STRONG>', rather than simply=20
=
<STRONG>'Policies'</STRONG>. </SPAN></FONT></FONT></FONT></DI=
V>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN =
class=3D163282615-25092005></SPAN></FONT></FONT></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D163282615-25092005>To be fair, all of the =
Policies we have=20
discussed so far, happen to only be concerned with how we interact =
with the=20
court. For example, we have not yet discussed policies for =
FilingAssembly, because, coincidentally, our scope has not=20
officially recognized any queries or transactions into the=20
FilingAssembly MDE (aside from a Callback function), though, we all =
agree that=20
FilingAssemblyMDE <EM>could</EM> define transactions and =
queries,=20
and, presumably, those interactions would then have the =
potential to have=20
associated policies.</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN =
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT=20
face=3DGeorgia><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D163282615-25092005>Perhaps, the lingering =
'Court Policy'=20
concept reflects that some of us are not entirely on-board with =
the 'MDE'=20
approach to the system. </SPAN></FONT></FONT></FONT><FONT=20
face=3DGeorgia><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005>That's fair enough - MDE is merely an =
architectural=20
concept which might or might not be successful for us in the long run =
- but,=20
nevertheless, at this point, for <EM>this</EM> version of =
LegalXML,=20
we have decided to pursue the MDE approach, and, I feel, we =
need to=20
be thoroughly consistent with it.</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN =
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT=20
face=3DGeorgia><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT =
face=3DGeorgia><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT =
face=3DGeorgia><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></FONT></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D163282615-25092005>If we have agreed =
to organize=20
our court interactions into 'FilingReview' and 'CourtRecord', then, =
we should=20
also agree to categorize the MDE's 'rules of engagement' along those =
same=20
lines:</SPAN></FONT></FONT></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D163282615-25092005><U>These</U><EM> are the=20
'FilingReview' rules...</EM></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN =
class=3D163282615-25092005></SPAN></FONT></FONT></FONT><FONT=20
face=3DGeorgia><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005><EM>And </EM><U>Those</U><EM> are the =
'CourtRecord'=20
=
rules...</EM></SPAN></FONT></FONT></FONT></SPAN></SPAN></DIV></BLOCKQUOT=
E>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005>At the =
face-to-face, I=20
seemed to get some decent buy-in on that concept. It was =
noted that=20
some of our rules (such as query extensions/restrictions) are =
distinctly=20
MDE-specific, and those policies should therefore be organized =
by=20
MDE. </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>But, just because we might agree that =
policies should=20
be organized by MDE, does not mean that they could not continue to be =
consolidated into a single file. </SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005>The =
question=20
remained: Should there exist a single file to express all =
policies of all=20
implemented MDEs?.. or should the system consist of =
multiple=20
policy files, one per implemented MDE?</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>So, do we want to see something like=20
this?:</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>SystemPolicy</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005> CourtRecord (MDE=20
1)</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005> =20
CodeSet1,</SPAN></FONT><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005> QueryExtension2,</SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005> =20
QueryRestriction3, =
etc.</SPAN></FONT></SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005> FilingReview (MDE=20
2)</SPAN></FONT></SPAN></FONT></DIV><SPAN =
class=3D163282615-25092005><SPAN=20
class=3D163282615-25092005></SPAN><SPAN =
class=3D163282615-25092005><FONT=20
face=3DGeorgia><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005> =20
CodeSet1,</SPAN></FONT><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005> QueryExtension2,</SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005> =20
QueryRestriction3, =
etc.</SPAN></FONT></SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT></SPAN></FONT>&nb=
sp;</DIV></BLOCKQUOTE>
<DIV dir=3Dltr align=3Dleft></SPAN></FONT></FONT></FONT><SPAN=20
class=3D163282615-25092005><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005>Or, =
something like=20
this?:</SPAN></FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D163282615-25092005><SPAN=20
class=3D163282615-25092005><SPAN class=3D163282615-25092005>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>Policy-1 for CourtRecord ( MDE 1=20
)</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D163282615-25092005><SPAN=20
=
class=3D163282615-25092005> =20
CodeSet1,</SPAN><FONT face=3DGeorgia color=3D#0000ff size=3D2><SPAN =
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005> QueryExtension2,</SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005> =20
QueryRestriction3,=20
=
etc.</SPAN></FONT></SPAN></FONT></SPAN></FONT></SPAN></FONT></FONT></FON=
T></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia><FONT =
color=3D#0000ff><FONT
size=3D2><SPAN class=3D163282615-25092005><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN=20
=
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT></SPAN></FONT></S=
PAN></FONT></FONT></FONT><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005>Policy-2 =
for=20
FilingReview ( MDE 2 )</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D163282615-25092005><SPAN=20
class=3D163282615-25092005></SPAN><SPAN =
class=3D163282615-25092005><FONT=20
face=3DGeorgia><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D163282615-25092005><SPAN=20
=
class=3D163282615-25092005> =20
CodeSet1,</SPAN><FONT face=3DGeorgia color=3D#0000ff size=3D2><SPAN =
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005> QueryExtension2,</SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005> =20
QueryRestriction3,=20
=
etc.</SPAN></FONT></SPAN></FONT></SPAN></FONT></SPAN></FONT></FONT></FON=
T></DIV></BLOCKQUOTE>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2></FONT><FONT=20
face=3DGeorgia color=3D#0000ff size=3D2></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2></FONT><FONT face=3DGeorgia color=3D#0000ff =
size=3D2></FONT><FONT=20
face=3DGeorgia color=3D#0000ff size=3D2></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2></FONT><FONT face=3DGeorgia color=3D#0000ff =
size=3D2></FONT><FONT=20
face=3DGeorgia color=3D#0000ff=20
=
size=3D2></FONT></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN><FONT=20
size=3D+0><SPAN class=3D163282615-25092005><SPAN =
class=3D163282615-25092005><FONT=20
face=3DGeorgia color=3D#0000ff size=3D2><SPAN=20
=
class=3D163282615-25092005></SPAN></FONT></SPAN></SPAN></FONT> </DI=
V>
<DIV dir=3Dltr align=3Dleft><FONT size=3D+0><SPAN =
class=3D163282615-25092005><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>Now, I look around me for another =
real-world=20
example of the proposed singleton approach.</SPAN></FONT></DIV></DIV>
<DIV dir=3Dltr align=3Dleft>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>I can think of none.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>
<DIV dir=3Dltr align=3Dleft></SPAN></FONT><SPAN =
class=3D163282615-25092005><FONT=20
face=3DGeorgia color=3D#0000ff size=3D2><SPAN =
class=3D163282615-25092005>- Some may=20
refer to Windows registry as an example of a consolidated set of=20
rules</SPAN></FONT></DIV></DIV>
<DIV dir=3Dltr align=3Dleft>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>First of all, this is a bad example:=20
WindowsRegistry isn't really intended to be a way for system =
components=20
to describe themselves to one =
another. </SPAN></FONT><FONT=20
face=3DGeorgia color=3D#0000ff size=3D2><SPAN =
class=3D163282615-25092005>The=20
registry might persist component settings but it is not intended to =
be a=20
publisher of settings. For example: MicrosoftWord has a =
documented API=20
by which you can learn of its settings - you are not supposed to go =
poking=20
through WindowsRegistry to learn about word's=20
settings. </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>Nevertheless, we'll run with this=20
example....</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>....if you were to look at =
<EM>distributed</EM>=20
systems that rely on WindowsRegistry to persist settings, you =
would=20
find that a single windows registry is not used to capture all =
settings=20
of the <EM>entire</EM> system. If you were =
running in a=20
Windows environment, each of your distributed components (on =
separate=20
machines) would use their local windows registry=20
to manage their settings. And, in a =
distributed=20
environment, there would not exist a single registry from =
which all=20
components exchange their configurations. Component-A =
doesn't=20
learn about Component-B by means of a=20
shared WindowsRegistry. In windows (COM or DCOM),=20
Component-A typically learns about Component-B's settings... by =
directly=20
interacting with Component-B's API. </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>(Note: Component-A learns about<STRONG> =
<EM>the=20
existence of</EM></STRONG> Component-B through another =
mechanism,=20
which we have referred to as a 'directory'. 'Directory' =
describes=20
the location of a component - it is not related=20
=
to 'policy'. )</SPAN></FONT></DIV></BLOCKQUOTE></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>- Some might think of DNS as an =
example of a=20
consolidated set of rules.</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>DNS is, in fact, an example of a =
directory of=20
other systems. It provides a consolidated means to find other =
systems.=20
It does not represent a consolidated set of rules for =
interacting with=20
those systems. It is little more than a list of=20
=
addresses.</SPAN></FONT></DIV></BLOCKQUOTE></SPAN></FONT></DIV></SPAN></=
FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005>- Some may =
refer to UDDI,=20
for WebServices, as an example of consolidated =
rules.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>UDDI is an excellent example of how =
components=20
might publish their 'rules of engagement. However, UDDI =
does not=20
represent the singleton approach. </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>UDDI represents a singular =
<STRONG>access=20
point</STRONG> for <EM>finding or =
obtaining</EM> individual rules=20
(i.e. WSDLs - the syntactical rules of a=20
WebService). A consumer still=20
asks the UDDI host for WSDLs, one by one. =
The=20
WebService rules are *still* organized, and segregated, by the =
individual WebServices. </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>(Truth be told, I feel that UDDI is a =
much better=20
example of the position I am advocating than as an example of the =
singleton=20
approach.)</SPAN></FONT></DIV></BLOCKQUOTE>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>I have further basis for my position on =
this=20
issue. </SPAN></FONT></SPAN></FONT><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005><FONT face=3DGeorgia =
color=3D#0000ff=20
size=3D2><SPAN class=3D163282615-25092005>I drafted a larger =
email=20
illustrating how the singleton approach gets to be=20
very difficult to implement once the system begins to=20
incorporate multiple CourtRecordMDEs (court-1 and court-2 =
policy), or if=20
the system begins to incorporate FilingAssembly=20
queries... </SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005>....but, =
for now, I'm=20
going to pause here for feedback on this=20
much:</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005>Consider:</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV></SPA=
N></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>1) Do we agree that Policies are MDE-specif=
ic (=20
</SPAN></FONT></SPAN></FONT><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>Such as MDE-query =
extensions/restrictions? =20
)</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT></SPAN></FONT></S=
PAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>2) If so, then, can we agree that Policies =
should=20
then be organized by MDE (MDE-1's policies vs. MDE-2's=20
=
policies)?</SPAN></FONT></SPAN></FONT></SPAN></FONT></SPAN></FONT></DIV>=
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT></SPAN></FONT></S=
PAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>3) Can we agree that the proposed =
'singleton'=20
approach is inconsistent with other types of distributed =
multi-component=20
systems?</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>If we can agree on that much, then why =
would we=20
want to adopt the proposed 'singleton'=20
approach?</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>If I left my position at this=20
much:</SPAN></FONT></SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005> <STRONG>'MDE policies' is an =
approach=20
that is most consistent with other distributed system designs=20
(UDDI)</STRONG>....</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>or , =
conversely,</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005> <STRONG>'PolicyMDE' is an =
approach that=20
is <EM>in</EM>consistent with other distributed system=20
=
designs</STRONG>....</SPAN></FONT></SPAN></FONT></DIV></SPAN></FONT></SP=
AN></FONT></DIV></BLOCKQUOTE>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>....then, is anyone able to disagree =
with that=20
assessment?</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>...and/or, is anyone willing to=20
provide an explanation of how the 'singleton'=20
approach is still better and worthy of=20
pursuit?</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN class=3D163282615-25092005><FONT =
face=3DGeorgia=20
color=3D#0000ff size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>Will my dissenters please=20
stand?</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005>- Shane</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005>LexisNexis</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
class=3D163282615-25092005><FONT face=3DGeorgia color=3D#0000ff =
size=3D2><SPAN=20
=
class=3D163282615-25092005></SPAN></FONT></SPAN></FONT></SPAN></SPAN></S=
PAN></FONT> </DIV></DIV></DIV></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C5C3A0.FA5A77C6--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]