legalxml-courtfiling — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [legalxml-courtfiling] Information to be tagged for redaction
MHonArc v2.5.2 -->legalxml-courtfiling message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [legalxml-courtfiling] Information to be tagged for redaction
- From: "Poindexter, Gary W" <[email protected]>
- To: 'Allen Jensen' <[email protected]>, [email protected],[email protected], [email protected]
- Date: Thu, 18 Jul 2002 14:54:17 -0400
True and I agree without qualification. With that said, there are applications (i.e. a justice integration engine, message broker or court public access application) that will be given the responsibility for eliminating/redacting content dependent upon the inquiry source (for queries) or destination (a destination dependent transformation). For this reason a tag or attribute that indicates information that is to be redacted, with as much detail as to the conditions under which it should be redacted, is important. This makes the business rules more generic and more easily understood by receiving systems. I would like to see a list of content classes of potentially redacted information (I believe this could be extracted from this thread) and an attribute/tag for these classes that indicates the content class such as "protected juvenile", "protected witness", "witness family", "SSN", etc. The fewer the classes, the fewer the variations in the business rules; the greater the number of classes the finer the granularity of the business rules. gary
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]