[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [legalxml-courtfiling-comment] Extending ECF 4
Gary, I apologize for the delay in responding to your question about
extending ECF 4. I took a little time off earlier this month and have
been slowly making up for everything I missed… I believe both of the extension mechanisms you described are
acceptable. The slight advantage in using an Augmentation class to group multiple
extensions is to make the set of extensions reusable. For example, If you
wanted to also add <nc:DocumenTitleText> and
<nc:DocumentCategoryName> to another Document type (e.g., <FilingConnectedDocument>),
then you would only need to define the <DocumentAugmentation> once and then
add <DocumentAugmentation> to each document (<FilingLeadDocument>
and <FilingConnectedDocument>). Does this help? Jim Cabral Helping
our clients make a difference in the lives of the people they serve. The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged
material. If you received this in error, please contact the sender and
delete the material from any computer. From: Graham, Gary
[mailto:GGraham@courts.az.gov] What
is the proper or best way to extend ECF? The ECF
spec, in section 2.4.3 Case-Type and Court Extensions recommends ‘element
substitution’ (as is used to substitute CivilCase for Case) for extending
ECF. Note this
is a recommendation and does not appear to preclude other extension approaches.
However, in section 1.6 Normative References, it lists [NIEM Techniques]
Techniques for Building and Extending NIEM http://www.niem.gov/topicindex.php?topic=techPDF,
Georgia Tech Research Institute, August 2007. This NIEM
document prescribes several techniques for extending NIEM. Some techniques only
apply to extending the NIEM vocabulary (e.g. creating new NIEM types or adding
to existing types). These techniques would not apply to domain model
extensions. For domain model extensions, the document describes several
techniques, such as Augmentation or Metadata. The augmentation technique
appears to have been used in ECF, such as in CivilCase –
j:CaseAugmentation and ecf:CaseAugmentation. Let’s
say that a court needed to extend ECF by adding a couple of additional NIEM
elements to what is already defined for ECF. For
example, let’s say a court wishes to add <nc:DocumenTitleText> and
<nc:DocumentCategoryName> to FilingLeadDocument. How should this be done? One
approach would be to just add them in under FilingLeadDocument where they fit
by sequence, such as: <FilingLeadDocument>
<nc:DocumentSequenceID>10</nc:DocumentSequenceID>
<nc:DocumentTitletext>Title of Document</nc:DocumentTitleText>
<nc:DocumentCategoryName>Motion</nc:DocumentCategoryName>
<nc:DocumentStatus>Pending Review</nc:DocumentStatus> </FilingLeadDocument> Another
approach would seem to be to use ‘augmentation’, such as: <FilingLeadDocument>
<nc:DocumentSequenceID>10</nc:DocumentSequenceID>
<nc:DocumentStatus>Pending Review</nc:DocumentStatus>
<DocumentAugmentation>
<nc:DocumentTitletext>Title of Document</nc:DocumentTitleText>
<nc:DocumentCategoryName>Motion</nc:DocumentCategoryName>
</DocumentAugmentation> </FilingLeadDocument> There
may be other possibilities as well such as defining a new message type (e.g.
CourtSpecific message?). Which
approach is recommended or required? Is there any documentation or
examples available for extending ECF 4.0? |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]