legalxml-courtfiling — archive

Artifacts posted

From: Scott Came
To: [email protected]
Date: Sun, 26 Jun 2005 22:42:00 -0000

 MHonArc v2.5.0b2 -->
















legalxml-courtfiling message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Artifacts posted




From: "Scott Came" <[email protected]>
To: [email protected]
Date: Sun, 26 Jun 2005 15:41:45 -0700 (PDT)






The IEPD domain modeling and mapping work to-date has been posted to the TC's KAVI area.� (Several prior versions have
been posted to the Requirements Subcommittee KAVI area over the past couple of weeks.� If you're interested in more
frequent updates, or want to participate in or observe the email traffic around the requirements and IEPD work, please
join the subcommittee.)

I have created a folder in KAVI in the TC area called "Court Filing Blue (3.0)
IEPD Process Artifacts".� Under this folder, I have created a subfolder for the artifacts in this posting.�
Future postings will get their own folder.� I've done this because there are several artifacts, and it's useful to
group them together.

The DomainModels.zargo file is the raw ArgoUML model file.� You would need ArgoUML
(Google will take you there) to read/edit this file.� If you just want to see the models, use the gifs (described
below.)

The blue-gjxdm-mapping.xls file is the mapping spreadsheet, that associates classes, attributes,
and associations in the domain model with structures in GJXDM, UBL, and the ECF-specific XML vocabulary.

The DomainModelDocumentation.html file is, well, documentation associated with the domain model.� Basically,
definitions of the classes, attributes, and associations.

Finally, the set of GIF files is just an image of
each of the UML class diagrams in the model.� You can view this same information in the .zargo file, but we didn't
want TC members to have to download and install Argo just to view them.

Happy reviewing!

Thanks.
--Scott (on behalf of those members who have been running the IEPD process to document ECF 3.0's
message structures)














[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]