· Web viewFor example: ordering bail, pleading of not guilty, filing an affidavit. An activity...

LegalXML System Blue SpecificationWorking Draft 03, June 5, 2005Document identifier:

document.doc

Location:http://www.oasis-open.org/apps/org/workgroup/legalxml-courtfiling/

Editor:[List your editors here; check whether “Editor” header should be plural]

Contributors:Shane Durham, LexisNexisEric Tingom, eCorridor, Inc.Tom Clarke, Washington State Administrator for the CourtsScott Came, Justice Integration Solutions, Inc.Dallas Powell, Tybera Development Group, IncJames Cabral, MTG Management Consultants, LLC.Rex McElrath, Judicial Council of GeorgiaDonald Bergeron, LexisNexisJames Cusick, Wolters KluwerJohn M. Greacen, Greacen Associates, LLCRoger Winters, King County, Department of Judicial Administration

Abstract:This document defines the LegalXML BLUE Specification, consisting of a set of non-proprietary Web services and ebXML specifications, along with clarifications and amendments to those specifications, which promote interoperability.

Status:This document is a Working Group Draft and has NOT been accepted by the Working Group as reflecting but is to serve as the basis for discussions. It is a work in progress, and should not be considered authoritative or final; other documents will superseded this document.

Committee members should send comments on this specification to the [email protected] list. Others should subscribe to and send comments to the mailto:[email protected] list. To subscribe, send an email message to mailto:[email protected]?subject=Subscribe with the word "subscribe" as the body of the message.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the XXX TC web page.

[If a Committee Specification or OASIS Standard:] The errata page for this specification is at http://www.oasis-open.org/committees/xxx/yyy.

document.doc 5-Jun-05

Copyright © OASIS Open 2005. All Rights Reserved. of 74

1

2

3

45

67

89

10111213141516171819202122

23242526

27282930

31323334

353637

3839

1

2

3

4

5

6

7

http://www.oasis-open.org/committees/xxx/yyy

http://www.oasis-open.org/committees/xxx/yyy

mailto:[email protected]?subject=Subscribe

mailto:[email protected]

mailto:[email protected]

http://www.oasis-open.org/spectools/docs/

Table of Contents1 Introduction................................................................................................................................................................3

1.1 Message Types.........................................................................................................................................................31.1.1 Notational Conventions.....................................................................................................................................31.1.2 Review Filing.....................................................................................................................................................31.1.3 Record Docketing.............................................................................................................................................81.1.4 Record Docketing Callback.............................................................................................................................121.1.5 Review Filing Callback....................................................................................................................................131.1.6 Query Message...............................................................................................................................................141.1.7 Response Message........................................................................................................................................141.1.8 Get Filing.........................................................................................................................................................141.1.9 Get Filing Status.............................................................................................................................................151.1.10 Get Filing List................................................................................................................................................161.1.11 Get Case.......................................................................................................................................................171.1.12 Get Case List................................................................................................................................................181.1.13 Get Document...............................................................................................................................................191.1.14 Get Calculated Fees.....................................................................................................................................201.1.15 Get Available Service Recipients List............................................................................................................21

1.2 Business Rules........................................................................................................................................................231.3 Court Policy.............................................................................................................................................................23

2 Message Profiles.....................................................................................................................................................242.1 Introduction.............................................................................................................................................................24

2.1.1 Guiding Principles...........................................................................................................................................262.1.2 Notational Conventions...................................................................................................................................27

2.2 Core Profile.............................................................................................................................................................272.3 Web Services Messaging Profile.............................................................................................................................27

2.3.1 Web Services Notational Conventions............................................................................................................272.3.2 Profile Conformance.......................................................................................................................................272.3.3 Service Description.........................................................................................................................................282.3.4 WS-Interoperability Basic Profile 1.1 provides................................................................................................292.3.5 WS-I Attachments Profile 1.0 with Soap Messages with Attachments provides..............................................302.3.6 WS-I Basic Security Profile 1.0 with WS-Security and SAML provides...........................................................332.3.7 WS-Reliability 1.1 provides.............................................................................................................................332.3.8 BPEL or BTP or others provides.....................................................................................................................342.3.9 UDDI...............................................................................................................................................................35

2.4 ebXML Messaging Profile........................................................................................................................................352.4.1 ebXML – ebMessaging Services (ebMS V3.0 ) Stack.....................................................................................35

3 GJXDM Element Map..............................................................................................................................................374 References..............................................................................................................................................................66

4.1 Normative................................................................................................................................................................66Appendix A. Acknowledgments..........................................................................................................................................67Appendix B. Revision History.............................................................................................................................................69Appendix C. Notices...........................................................................................................................................................70



40

414243444546474849505152535455565758596061626364656667686970717273747576777879808182

83

8

9

10

11

12

13

14

1 Introduction[Provide an introductory chapter, indicating if any parts of it are non-normative.]

1.1 Message Types[Provide an introductory chapter, indicating if any parts of it are non-normative.]

1.1.1 Notational Conventions The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119.

1.1.2 Review Filing The structure of a Filing including any Payment Information will be documented in this section. This describes the filing transaction between the Filing Assembly MDE and the Filing Review MDE. This information will become part of the Record Docketing between the Filing Review MDE and the Court Record MDE but does not necessarily describe the information that is actually stored in the Court Record.

This is a draft and may need to be broken out by case type, although there may be quite a bit of information that is standard across all case types.

This information will lead directly to schemas that define the standard acceptable structures in the Core Profile.

All Review Filing Messages MUST include:

Filing ID A (universally unique) identifier for a Review Filing

Submission Date The date the Review Filing Message left the control of the Filer

Submission Time The time the Review Filing Message left the control of the Filer.

Submitter ID A unique identifier for a person or organization which submits a Review Filing Message. This may refer to any combination of the assembler, authorizer, or the represented party in the filing.

Receiver ID A unique identifier for the Receiver of a Review Filing Message.

Assembling MDE ID A unique identifier the machine from which it came.

Court ID A unique identifier for the court in which the filing is made.

Document The pleading, motion or order that is the main document in a Filing. A Document may have Attachments.

Document Metadata Document descriptors (title, type description, etc.) for the Document. This is meant to include all the information about the document that is needed to index it into the Case Management System and enter it into the Document Management System.



8485

8687

888990

9192939495

969798

99100

101102

103

15

16

17

18

19

20

21

Document Metadata: Document ID A unique and unambiguous reference to the resource within a given context.

Document Metadata: Document Sequence ID

An identifier that determines the document order in a set or related documents.

Document Metadata: Document Title Text

A name given to a resource, typically a name by which it is formally known.

Document Metadata: Document Subject Text

A subject that is typically expressed as keywords, phrases, or classification codes that describe a topic of the resource.

Payment Information Information provided by the Filing Assembly MDE to the Filing Review MDE that identifies how the Filer intends to pay, is paying, or has paid any court Fees associated with a Filing. The form or payment may include credit, debit, electronic transfer, cash, or check transactions. The Filer gives money to some third-party; the court collects from the third-party. When the Filing Assembly MDE has collected or will collect monies from the Filer, the court still collects payment from the Filer via the Filing Assembly MDE.

Filing Fee A fee or price required to submit a document.

Payment Information: Card Account

Information that directly relates to a credit or debit card, a small plastic card issued by a financial institution, bank or building society, allowing the holder to make purchases against the card.

Payment Information: Paid Amount Information directly relating to the means of payment.

Payment Information: Card Account Primary Account Number ID


Payment Information: Card Account Holder


Payment Information: Card Account Expiry Date


All Review Filing Message MAY include:

Requests To Seal An indicator that the Filer requests that the Court receiving a Review Filing Message seal one or more of Document and Attachments.

Requests To Seal: Document ID A unique and unambiguous reference to the resource within a given context.

Attachment A document included in a Filing that supports the Document.

Attachment Metadata Document descriptors (title, type description, etc. ) for an Attachment.

Attachment Metadata: Document ID

A unique and unambiguous reference to the resource within a given context.

Attachment Metadata: Document Sequence ID


Attachment Metadata: Document Title Text


Attachment Metadata: Document Subject Text


Case Title An official name of a Case.

Case Type Specific Information A set of information for initiating a particular case that is specific to the Case Type.



104105

106

22

23

24

25

26

27

28

Case Category Text A category type of a court case, e.g. criminal, civil, juvenile, family.

Case Participants Details about the participants involved in a court Case.

Case Participants: Participant ID A unique and unambiguous reference to the participant within a given context.

Case Participants: Case Respondent Party Organization

The person, organization, or property in a court case that is required to answer a petition for a court order or writ requiring the respondent to take some action, halt an activity or obey a court's direction. In such matters the moving party (the one filing the petition) is usually called the "petitioner." Thus, the respondent is equivalent to a defendant in a lawsuit. On an appeal, the party who must respond to an appeal by the losing party in the trial court (called "appellant") in the appeals court. The accused in a domestic violence case or civil action; a person responding to a Request or Petition for Protection filed by a petitioner.

Case Participants: Case Respondent Party Person


Case Participants: Case Respondent Party Property


Case Participants: Case Defense Attorney

An attorney who defends a case. (Note Additional Attorney types were being added)

Case Participants: Case Initiating Party Organization

A person, organization, or property that brings charges or a suit against another in a court of law. Can be either a victim in a criminal case or a plaintiff in a civil case.

Case Participants: Case Initiating Party Person


Case Participants: Case Initiating Party Property


Case Participants: Case Judge A judicial official assigned to a case.

Case Participants: Case Prosecution Attorney

An attorney who prosecutes a case. (Note Additional Attorney types were being added)

Served Participants

Served Participants: Participant ID A unique and unambiguous reference to the participant within a given context.

Served Participants: Case Witness The person/entity who has information relating to the activity or who testifies in court.

Served Participants: Case Other Actor Organization

A miscellaneous person, organization, or property involved in a court case.

Served Participants: Case Other Actor Person


Served Participants: Case Other Actor Property


Served Participants: Service Method

A value of either “e-service” or “non e-service”

Served Participants: eService Provider

A unique identifier for a person or organization which serves a Participant.



29

30

31

32

33

34

35

This will include each participant's eServiceProfile.

If the filing is into an existing case, the Review Filing Message MUST include:

Case ID A number used to track a Case.



107

108

109110111

112

113

36

37

38

39

40

41

42

If the filing is initiating a new case, the Review Filing Message MUST include:





















Case Type A first-level classification or categorization of a Case (e.g. civil, criminal).

Case Sub Type A second-level classification or categorization of a Case (e.g., felony, misdemeanor) in addition to Case Type


If the filing is initiating a new case, the Review Filing Message MAY include:



114115

116

117118119

120

43

44

45

46

47

48

49

Related Case ID(s)

1.1.3 Record DocketingThe structure of a Record Docketing Message will be documented in this section. This describes the Record Docketing transaction between the Filing Review MDE and the Court Record MDE. This information will become part of the Record Docketing Callback between the Court Record MDE and the Filing Review MDE but does not necessarily describe the information that is actually stored in the Court Record.

This is a draft


All Record Docketing Messages MUST include:

Docketing ID A (universally unique) identifier for a Record Docketing





Docketing Date The date the Record Docketing Message left the control of the Filing Review.

Docketing Time The time the Record Docketing Message left the control of the Filing Review.

Recorder ID A unique identifier for a person or organization which submits a Record Docketing Message. This may refer to any combination of the reviewer or authorizer.

Receiver ID A unique identifier for the Receiver of a Review Filing Message











Document Type The code value set by court policy for a particular document.



121

122123124125126

127128

129130

131132

133

50

51

52

53

54

55

56

All Record Docketing Message MAY include:

Requests To Seal An indicator that the Filer requests that the Court receiving a Review Filing Message seal one or more of Document and Attachments.

Requests To Seal: Document ID A unique and unambiguous reference to the resource within a given context.

Attachment A document included in a Filing that supports the Document.













Case Tracking ID A number used to track a case.




134135

57

58

59

60

61

62

63



















Next Scheduled Event The filing request for a scheduled event to occur on the courts calendar.

Next Scheduled Event: Court Event Sequence ID

A unique identifier for a court case event record.

Next Scheduled Event: Court Event Activity

A court-related action associated with a court case event. There must be at least one activity for each event. For example: ordering bail, pleading of not guilty, filing an affidavit. An activity may have conditions attached to it.

Next Scheduled Event: Court Event Schedule

Details about the days for which a court event is scheduled.

Next Scheduled Event: Court Event Court

A court in which a court event occurs.

Next Scheduled Event: Court Event Judge

A judge associated with a court event.

Filing Related Party Details about the filing related participants involved in a court Case.



136

64

65

66

67

68

69

70

If the filing is into an existing case, the Record Docketing Message MUST include:

Case ID A number used to track a Case.

If the filing is initiating a new case, the Record Docketing Message MUST include:





















Case Type A first-level classification or categorization of a Case (e.g. civil, criminal).

Case Sub Type A second-level classification or categorization of a Case (e.g., felony, misdemeanor) in addition to Case Type.



137138

139

140141142

143

71

72

73

74

75

76

77


If the filing is initiating a new case, the Record Docketing Message MAY include:

Related Case ID(s) A number used to track a Case.

1.1.4 Record Docketing CallbackThe structure of a Record Docketing Callback Message will be documented in this section.

This is a draft


All Record Docketing Callback Messages MUST include:

Docketing ID A (universally unique) identifier for a Record Docketing

Filing ID A (universally unique) identifier from the Review Filing Message




Recording Date The date the Record Docketing Message was recorded.

Recording Time The time the Record Docketing Message was recorded.



Filing Status Details about a status of an filing activity or process.






144145146

147

148

149150

151

152153

154155

156

78

79

80

81

82

83

84








Document Status Details about a status of an document’s process.

1.1.5 Review Filing CallbackThe structure of a Review Filing Callback Message will be documented in this section.

This is a draft


All Review Filing Callback Messages MUST include:







Recorder ID A unique identifier for a person or organization which submits a Record Docketing Message. This may refer to any combination of the reviewer or authorizer.



Filing Status Details about a status of an activity or process.






157

158159

160

161162

163164

165

85

86

87

88

89

90

91








Document Status Details about a status of an document’s process.

1.1.6 Query Message

The query message is a request for the information is made from the court identified by CourtID.

All Query Messages MUST include:

XXQuery ID A (universally unique) identifier from the Review Filing Message

Inquirer ID A unique identifier for a person or organization which submits a query Get Filing Message. This may refer to any combination of the assembler, authorizer, or the represented party in the filing.


1.1.7 Response Message

This response message to a Query Message.

All Query Messages MUST include:

Filing Query ID A (universally unique) identifier from the Review Filing Message

Court ID A unique identifier for the court in which the query is made.

If Error then either

Filing Error Only used if no elements are returned from query

Or

Policy Reference URI Uniform Resource Identifier

1.1.8 Get FilingThe query message is a request for the information is made from the court. Identified by FilingID.



166

167168

169170

171

172

173

174175

176177

178

179

180181

182

92

93

94

95

96

97

98

All Get Filing Messages MUST include:

Filing Query Id A unique identifier for the query.




Response Message



Court ID A unique identifier for the court.

Filing Number A number assigned by the court for a filing.

Case Tracking Id A number used to track a case.






Or


1.1.9 Get Filing StatusThis is query to get a filing’s status by Filer Identification, Case Identifier, or Filing Number.

All Get Filing Status Messages MUST include:






183

184

185

186

187

188

189190

191192

193

99

100

101

102

103

104

105

Filer ID A unique identifier for a person or organization which requests information.

Either


Or

Case ID A number used to track a Case

Or


Response Message












Or


1.1.10 Get Filing ListThis is query to get a list of filings by Filer Identification, Case Identifier, or Filing Number.

All Get Filing List Messages MUST include:


Inquirer ID A unique identifier for a person or organization which submits a query Get Filing Message. This may refer to any combination of the assembler, authorizer, or the



194195

196

197

198199

200201

202

106

107

108

109

110

111

112

represented party in the filing.


Filer ID A unique identifier for a person or organization which requests information.

Multiple Either


Or

Case ID A number used to track a Case

Or


Response Message












Or


1.1.11 Get Case This is a query for a list of cases that match a set of criteria including case participants, case classification, case status, and date of the case was initiated.

All Get Case Messages MUST include:



203204

205

206

207208209

210211

212

113

114

115

116

117

118

119





Case Subset Text An xpath relative location use to select a subset of a Case

Response Message








1.1.12 Get Case ListThis is a query for a list of cases that match a set of criteria including case participants, case classification, case status, and date of the case was initiated.

All Get Case List Messages MUST include:




Case Initiated Date Range A date range the case was initiated.

Case Status Text A status of the case.

Case Classification A classification or categorization of a case.

Case Participants Details about the participants involved in a court Case

Response Message



213214

215

216

217218219

220221

222

223

224

225

120

121

122

123

124

125

126








1.1.13 Get Document This query is a request for an electronic copy of one or more documents in a case.

All Get Case Messages MUST include:





Case Docket Id A number used to identify a case docket.

Response Message





Case Docket Id A number used to identify a case docket.




226

227228

229230

231

232233

234

127

128

129

130

131

132

133









Document Binary The pleading, motion or order that is the main document in a Filing.

1.1.14 Get Calculated Fees This query is a request for an court fees of one or more documents in a case.

All Get Calculated Fees Messages MUST include:







Document Type The code value set by court policy for a particular document

Document Binary The pleading, motion or order that is the main document in a Filing.












235

236237

238239

240

134

135

136

137

138

139

140









Attachment Metadata: Binary The pleading, motion or order that is the main document in a Filing.

Response Message







Payment Information Information provided by the Filing Assembly MDE to the Filing Review MDE that identifies how the Filer intends to pay, is paying, or has paid any court Fees associated with a Filing. The form or payment may include credit, debit, electronic transfer, cash, or check transactions. The Filer gives money to some third-party; the court collects from the third-party. When the Filing Assembly MDE has collected or will collect monies from the Filer, the court still collects payment from the Filer via the Filing Assembly MDE.

Filing Fee A fee or price required to submit a document.

1.1.15 Get Available Service Recipients ListThis query is a request for case’s Available Service Recipients List.

All Get Available Service Recipients List Messages MUST include:







241242

243

244

245246

247248

249

250

141

142

143

144

145

146

147

Response Message
























Served Participants



251

148

149

150

151

152

153

154

Served Participants: Participant ID A unique and unambiguous reference to the participant within a given context.

Served Participants: Case Witness The person/entity who has information relating to the activity or who testifies in court.

Served Participants: Case Other Actor Organization


Served Participants: Case Other Actor Person


Served Participants: Case Other Actor Property


Served Participants: Service Method

A value of either “e-service” or “non e-service”

Served Participants: eService Provider

A unique identifier for a person or organization which serves a Participant.

1.2 Business RulesReview Filing Validity Rules

The Review Filing has the correct structure

The Review Filing has the correct content

The Review Filing is acceptable according to the court's Court Policy

The Review Filing contains appropriate security

The Review Filing contains no Viruses

The Review Filing message integrity passes

1.3 Court PolicyA set of court specific rules for Filings. The court publishes this so that each Filer or Party knows the expectations and/or constraints placed on the data elements and other aspects of a given Electronic Filing system.

This section includes court specific information, including court identification and contact information, rules, policies, and local extension to the LegalXML Blue Court Filing Specification. Court Policy must include Court and Rule elements.

Court Rules will define the rules for filings that the court will accept the following elements will be included in the schema.

Accept Document URL Indicator

Accept Documents Requiring Fee Indicator

Accept Sealed Documents Indicator

Accept Multiple Filings

Court Policy defines court specific policies for electronic filing.

Policy ID

Name Text

Description Text



252

253254

255

256

257

258

259

260

261262263

264265266

267268

269

270

271

272

273

274

275

276

277

278

279

155

156

157

158

159

160

161

Eric J Tingom, 06/05/05,

2 Message Profiles2.1 Introduction The following profiles have been identified:

Core Profile

Web Services Messaging Profile

EbXML Messaging Profile

The Core Profile standardizes the message structure for the electronic filing of documents, and as such satisfies the Use Cases for Blue. It specification is to remain standard for each flavor of "messaging profile." The messaging profiles standardize on a "stack" of other industry standards to satisfy the Non Functional Requirements of Blue.

As of now, two messaging profiles have been identified: one utilizing the "WS-*" stack of standards (basically, WS-I plus WS-Security plus WS-Reliability), and the other utilizing the ebXML stack.

What layers within Web Services are the ebXML Messaging Services Specified?Web Services at its’ most basic definition is defined as http + SOAP + XML or a transport layer (http), XML messaging format layer (SOAP) and the XML data layer. ebXML Messaging Services specifies additional elements in the SOAP – envelope header and header tags for the MIME object(s) in the data layer (XML) to support standard XML tags and placement of those tags to support Digital Certificates, Digital Signatures, synchronous and asynchronous messaging, zero-to-many attachments (MIME), Message Acknowledgements, message splitting and forwarding of signed payloads to different services, auditing and logging of message paths, placement of WS-Security tags, SAML tags and specific restrictions on the methods to use in utilizing the WS-* Security specifications. These tags are defined in the SOAP – envelope header.

Functional Court filing elements would be contained in the SOAP body or one or more MIME attachments.



280

281282

283

284

285

286287288289

290291292

293294295

296297298299300301302303

304305

162

163

164

165

166

167

168



306

169

170

171

172

173

174

175

2.1.1 Guiding Principles All of the profiles are being developed according to a set of principles that, together, form the Core Profile, as it relates to bringing about interoperability. This section documents these guidelines.

Focus profiling effort The focus of the profile is the specifications that are explicitly defined as in-scope for the profile.

Testability When possible, the Profile makes statements that are testable. However, such testability is not required. Preferably, testing is achieved in a non-intrusive manner.

Strength of requirements The Profile makes strong requirements (e.g., MUST, MUST NOT) wherever feasible; if there are legitimate cases where such a requirement cannot be met, conditional requirements (e.g., SHOULD, SHOULD NOT) are used. Optional and conditional requirements introduce ambiguity and mismatches between implementations.

Restriction vs. relaxation When amplifying the requirements of referenced specifications (including the Basic Profile 1.1 ), the Profile may restrict them, but does not relax them (e.g., change a MUST to a MAY).

Multiple mechanisms If a referenced specification allows multiple mechanisms to be used interchangeably, the Profile selects those that are well understood, widely implemented and useful. Extraneous or underspecified mechanisms and extensions introduce complexity and therefore reduce interoperability.

Future compatibility When possible, the Profile aligns its requirements with in-progress revisions to the specifications it references (e.g., basically, WS-I plus WS-Security plus WS-Reliability). This aids implementers by enabling a graceful transition, and assures that WS-I does not 'fork' from these efforts. When the Profile cannot address an issue in a specification it references, this information is communicated to the appropriate body to assure its consideration.

Compatibility with deployed services Backwards compatibility with deployed Web services is not a goal for the Profile, but due consideration is given to it; the Profile does not introduce a change to the requirements of a referenced specification unless doing so addresses specific interoperability issues.

Focus on interoperability Although there are potentially a number of inconsistencies and design flaws in the referenced specifications, the Profile only addresses those that affect interoperability.

Conformance targets Where possible, the Profile places requirements on artifacts (e.g., WSDL descriptions, ebXML messages) rather than the producing or consuming software's behaviors or roles. Artifacts are concrete, making them easier to verify and therefore making conformance easier to understand and less error-prone.

Lower-layer interoperability The Profile speaks to interoperability at the web-services layer only; it assumes that interoperability of lower-layer protocols ( e.g. TCP, HTTP ) and technologies (e.g. encryption and signature algorithms ) is adequate and well-understood. WS-I does not attempt to assure the interoperability of these protocols and technologies as a whole. This assures that WS-I's expertise in and focus on Web services standards is used effectively.

Do no harm Interoperability of technologies does not in and of itself ensure security, and the act of combining new technologies and protocols is especially susceptible to security threats. The profile takes steps to avoid introducing new security threats.

Application semanticsAlthough communication of application semantics can be facilitated by the technologies that comprise the Profile, assuring the common understanding of those semantics is not addressed by it.



307308309

310

311

312

313314

315

316317318

319

320321

322

323324325

326

327328329330

331

332333334

335

336337

338

339340341

342

343344345346

347

348349

350

351352

353

176

177

178

179

180

181

182

2.1.2 Notational Conventions The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119.

2.2 Core ProfileA profile that describes an implementation specification for the structure of all types of messages documented in the Use Cases.

This profile provides an implementation specification for the functional requirements (Use Cases); the message profiles provide an implementation specification for the Non Functional Requirements.

This profile will consist largely as a set of schemas, one for each type of message structure that was previously addressed in Section 1. The schemas are based on GJXDM as much as possible.

2.3 Web Services Messaging Profile

2.3.1 Web Services Notational Conventions This specification uses a number of namespace prefixes throughout; their associated URIs is listed below. Note that the choice of any namespace prefix is arbitrary and not semantically significant.

soap - "http://schemas.xmlsoap.org/soap/envelope/"

xsi - "http://www.w3.org/2001/XMLSchema-instance"

xsd - "http://www.w3.org/2001/XMLSchema"

soapenc - "http://schemas.xmlsoap.org/soap/encoding/"

wsdl - "http://schemas.xmlsoap.org/wsdl/"

soapbind - "http://schemas.xmlsoap.org/wsdl/soap/"

uddi - "urn:uddi-org:api_v2"

2.3.1.1 Profile Identification and VersioningVersion numbers are composed of a major and minor portion, in the form "major.minor".

One can also use this information to determine whether two instances of a profile are backwards-compatible; that is, whether one can assume that conformance to an earlier profile instance implies conformance to a later one.

2.3.2 Profile ConformanceConformance to the Profile is defined by adherence to the set of requirements defined for a specific target, within the scope of the Profile.

2.3.2.1 Conformance RequirementsAll requirements in the Profile are considered normative, and those in the specifications it references that are in scope should likewise be considered normative. When requirements in the Profile and its referenced specifications contradict each other, the Profile's requirements take precedence for purposes of Profile conformance.

Definitions of terms in the Profile are considered authoritative for the purposes of determining conformance.



354355356

357

358359360

361362363

364365366

367

368369370

371

372

373

374

375

376

377

378379

380381382

383

384385386

387388389390

391

183

184

185

186

187

188

189

None of the requirements in the Profile, regardless of their conformance level, should be interpreted as limiting the ability of an otherwise conforming implementation to apply security countermeasures in response to a real or perceived threat.

2.3.2.2 Conformance TargetsConformance targets identify what artifacts (e.g., SOAP message, WSDL description, UDDI registry data) or parties (e.g., SOAP processor, end user) requirements apply to.

This allows for the definition of conformance in different contexts, to assure unambiguous interpretation of the applicability of requirements, and to allow conformance testing of artifacts (e.g., SOAP messages and WSDL descriptions) and the behavior of various parties to a Web service (e.g., clients and service instances).

Requirements' conformance targets are physical artifacts wherever possible, to simplify testing and avoid ambiguity.

The following conformance targets are used in the Profile:

MESSAGE - protocol elements that transport the ENVELOPE (e.g., SOAP/HTTP messages)

ENVELOPE - the serialization of the soap:Envelope element and its content

DESCRIPTION - descriptions of types, messages, interfaces and their concrete protocol and data format bindings, and the network access points associated with Web services (e.g., WSDL descriptions) (from Basic Profile 1.0)

INSTANCE - software that implements a wsdl:port or a uddi:binding Template (from Basic Profile 1.0)

SENDER - software that invokes an INSTANCE (from Basic Profile 1.0)

SENDER - software that generates a message according to the protocol(s) associated with it (from Basic Profile 1.0)

RECEIVER - software that consumes a message according to the protocol(s) associated with it (e.g., SOAP processors) (from Basic Profile 1.0)

REGDATA - registry elements that are involved in the registration and discovery of Web services (e.g. UDDI models) (from Basic Profile 1.0)

2.3.2.3 Conformance ScopeThe Profile only attempts to improve interoperability within its own scope

2.3.3 Service DescriptionThe Profile uses Web Services Description Language (WSDL) to enable description of services as sets of endpoints operating on messages.

This section of the Profile incorporates the following specifications by reference, and defines extensibility points within them:

Extensible Markup Language (XML) 1.0 (Second Edition)

Namespaces in XML 1.0

XML Schema Part 1: Structures

Extensibility points:

Schema annotations - XML Schema allows for annotations, which may be used to convey additional information about data structures.

XML Schema Part 2: Data Types

Web Services Description Language (WSDL) 1.1

Extensibility points:

WSDL extensions - WSDL allows extension elements in certain places; use of such extensions requires out-of-band negotiation.

Validation mode - whether the parser used to read WSDL and XML Schema documents performs schema validation or not.



392393

394395396

397398399

400401

402

403

404

405406407

408

409

410411

412413

414415

416417

418419420

421422

423

424

425

426

427428

429

430

431

432433

434435

190

191

192

193

194

195

196

Fetching of external resources - whether the parser used to read WSDL and XML Schema documents fetches external entities and schema s. Relative URIs - WSDL does not adequately specify the use of relative URIs for the following: soapbind:body/@namespace, soapbind:address/@location, wsdl:import/@location, xsd:schema/@targetNamespace and xsd:import/@schemaLocation.

2.3.3.1 Required Description An INSTANCE's WSDL 1.1 description, its UDDI binding template, or both MUST be available to an authorized

SENDER upon request.

A service instance may provide run-time access to WSDL documents from a server, but is not required to do so in order to be considered conformant.

2.3.3.2 Document Structure A DESCRIPTION using the WSDL namespace (prefixed "wsdl" in this Profile) MUST be valid according to the

XML Schema found at "http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd".

A DESCRIPTION using the WSDL SOAP binding namespace (prefixed "soapbind" in this Profile) MUST be valid according to the XML Schema found at"http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.xsd".

A DESCRIPTION MUST only use the WSDL "import" statement to import another WSDL description. To import XML Schema Definitions, a DESCRIPTION MUST use the XML Schema "import" statement.

A DESCRIPTION MUST use the XML Schema "import" statement only within the xsd:schema element of the types section.

In a DESCRIPTION the schemaLocation attribute of an xsd:import element MUST NOT resolve to any document whose root element is not "schema" from the namespace

An XML Schema directly or indirectly imported by a DESCRIPTION MAY include the Unicode Byte Order Mark (BOM).

An XML Schema directly or indirectly imported by a DESCRIPTION MUST use either UTF-8 or UTF-16 encoding.

An XML Schema directly or indirectly imported by a DESCRIPTION MUST use version 1.0 of the eXtensible Markup Language W3C Recommendation.

A DESCRIPTION MUST specify a non-empty location attribute on the wsdl:import element

A SENDER MAY, but need not, retrieve a WSDL description from the URI specified in the location attribute on a wsdl:import element.

A DESCRIPTION MUST use version 1.0 of the eXtensible Markup Language W3C Recommendation.

A DESCRIPTION SHOULD NOT contain the namespace declaration xmlns:xml="http://www.w3.org/XML/1998/namespace".

The targetNamespace attribute on the wsdl:definitions element of a description that is being imported MUST have same the value as the namespace attribute on the wsdl:import element in the importing DESCRIPTION.

A DESCRIPTION containing WSDL extensions MUST NOT use them to contradict other requirements of the Profile.

A DESCRIPTION SHOULD NOT include extension elements with a wsdl:required attribute value of "true" on any WSDL construct (wsdl:binding, wsdl:portType, wsdl:message, wsdl:types or wsdl:import) that claims conformance to the Profile.

If during the processing of a description, a sender encounters a WSDL extension element that has a wsdl:required attribute with a boolean value of "true" that the sender does not understand or cannot process, the SENDER MUST fail processing.

2.3.4 WS-Interoperability Basic Profile 1.1 provides

2.3.4.1 Asynchronicity Of MessagingSender of message must not expect to receive a response (other than acknowledgement of receipt) from recipient immediately



436437438439

440441442

443444

445446447

448449

450451

452453

454455

456457

458459

460461

462

463464

465

466467

468469

470471

472473474

475476477

478

479480481

197

198

199

200

201

202

203

If sender does not receive a “full” response immediately, then sender must be able to receive that response at some later time

If original message sender is not available to receive response at the time original recipient wishes to send it, then response is queued for later retrieval by original sender

2.3.4.2 Message Acknowledgement Sender can receive an acknowledgement of message receipt by recipient that allows sender to verify that message was received unmodified by recipient.

2.3.5 WS-I Attachments Profile 1.0 with Soap Messages with Attachments provides

When a Receiving Message Party implementing this specification uses the W3C Note “SOAP Messages with Attachments” specification [SOAP with Attachments], it MUST follow the following rules:

1) The Sending Receiving Message Party MUST include the whole SOAP envelope containing the WS-Reliability header elements in the first MIME part.

2) It MUST set the Charest parameter of the Content-Type header of the first MIME part to either UTF-8 or UTF-16.

3) It MAY include zero or more additional MIME parts in a Reliable Message.

4) The Receiving Message Party MUST deliver all MIME parts in a Reliable Message to the SENDER.

2.3.5.1 Document Size and FormatDocuments being filed along with (or as part of) messages can be of unlimited size (true?) and can be in any of these formats:

Microsoft Word

WordPerfect

PDF

TIFF

MIME and DIME

RTF

TEXT

XML

2.3.5.2 Attachments PackagingMIME parts - SOAP Messages with Attachments places no restriction on the type of any non-root part in a multipart/related message.

SOAP Messages with Attachments defines a MIME multipart/related structure for packaging SOAP envelope with attachments. The Profile mandates the use of that structure, and places the following constraints on its use:

The entity body of the root part of multipart/related MESSAGE MUST be a soap:Envelope.

The Content-Type HTTP header field-value in a MESSAGE MUST be either "multipart/related" or "text/xml".

If the Content-Type HTTP header field-value in a MESSAGE has a media-type of "multipart/related" then the Content-Type HTTP header field-value in that message MUST have the type parameter with a value of "text/xml".

Media Type of Message If the WSDL description lists at least one non-root MIME part, the corresponding MESSAGE MUST have a Content-Type HTTP header field-value with a media-type of "multipart/related".

2.3.5.2.1 Messages with No Attachments If a receiver expects zero or more attachments in a message, the sender of that message can use the text/xml

media type for a message that has no attachments.



482483

484485

486487488

489490491492

493494

495

496

497

498499500

501

502

503

504

505

506

507

508

509510511

512513

514

515

516517518

519520

521522523

204

205

206

207

208

209

210

A MESSAGE containing zero attachment parts MUST be sent using a content-type of either "text/xml" as though a SOAP HTTP binding were used or "multipart/related" when the WSDL description for the message specifies the mime:multipartRelated element on the corresponding wsdl:input or wsdl:output element in its wsdl:binding.

A SENDER MUST NOT send a message using SOAP with Attachments if the corresponding wsdl:input or wsdl:output element in the wsdl:binding does not specify the WSDL MIME Binding.

2.3.5.2.2 Dereferencing AttachmentsAlthough attachments can be used to provide content which is identified with a URI, implementations are not required to prefer attached content, to use it exclusively, or to use it at all. Likewise, applications may choose to ignore the specified dereference function of a URI (e.g., fetching content from a network) and only use attached content.

A RECEIVER MAY ignore a URI reference to an attachment in an envelope.

2.3.5.2.3 Carrying Additional SOAP EnvelopesThe Profile places no constraints on the content of attachment parts. Additional XML documents that contain a soap:Envelope may be sent as attachments, but only the root-part of the MIME message should be treated as the primary soap envelope in a MIME package.

A MESSAGE MAY contain soap:Envelopes carried as attachments in parts that are not the root part of the message.

2.3.5.2.4 Fault Messages with AttachmentsAn INSTANCE MAY send a fault with attachments if and only if the wsdl:output element is described using the WSDL MIME binding.

2.3.5.2.5 Ordering of MIME PartsIntermediaries might reorder the parts in a multipart/related message. Hence semantics should be neither given to, nor implied by the ordering of parts in a message.

A RECEIVER MUST NOT infer any semantics from the ordering of non-root MIME parts in a message.

A MESSAGE MAY have its MIME parts in any order provided that the identity of the root part is maintained.

2.3.5.2.6 MIME Boundary StringIn a MESSAGE, all MIME encapsulation boundary strings MUST be preceded with the ASCII characters CR (13) and LF (10) in that sequence.

RFC2046 section 5.5.1 clearly requires that all encapsulation boundaries must be preceded with a CRLF (carriage-return line-feed).

2.3.5.3 Attachments DescriptionThe Profile permits the use of the WSDL MIME binding, but limits it to the SOAP Messages with Attachments protocol. The Profile places the following constraints on its use:

2.3.5.3.1 Use of MIME Binding ExtensionA DESCRIPTION MUST use either the WSDL MIME Binding as described in WSDL 1.1 Section 5 or WSDL SOAP binding as described in WSDL 1.1 Section 3 on each of the wsdl:input or wsdl:output elements of a wsdl:binding.

2.3.5.3.2 Unbound portType Element ContentsA wsdl:binding in a DESCRIPTION SHOULD bind every wsdl:part of a wsdl:message in the wsdl:portType to which it refers to one of soapbind:body, soapbind:header, soapbind:fault , soapbind:headerfault, or mime:content



524525526527

528529

530531532533

534

535536537538

539540

541542543

544545546

547

548

549550551

552553

554555556

557558559

560561562

211

212

213

214

215

216

217

2.3.5.3.3 Referencing Message Parts A mime:content element in a DESCRIPTION MUST NOT reference a wsdl:part that is not present in the

respective wsdl:input or wsdl:output of the corresponding wsdl:operation of the corresponding wsdl:portType..

A mime:content element in a DESCRIPTION MUST NOT be bound to a sub-component of an element or type referenced by a wsdl:part.

In a DESCRIPTION, a mime:content element MUST include the part attribute.

2.3.5.3.4 Referencing Attachments from the SOAP EnvelopePlease note that there is no way in a WSDL1.1 description to correlate an attachment reference (defined using swaRef) with an attachment (defined using a wsdl:part bound to mime:content). As a best practice, the Profile recommends that when ref:swaRef is used, the corresponding attachment should not be described, and vice versa.

In a DESCRIPTION, a wsdl:part defined with the ref:swaRef schema type SHOULD only be bound to a soapbind:body, or a soapbind:header in a MIME binding.

In an ENVELOPE, a URI reference that is typed using the ref:swaRef schema type MUST resolve to a MIME part in the same message as the envelope.

2.3.5.3.5 Specifying Root PartSOAP Messages with Attachments requires that the root part of the multipart/related package must contain the SOAP envelope, but the WSDL MIME binding is unclear on how this is described.

A mime:multipartRelated element in a DESCRIPTION MUST contain exactly one mime:part element, amongst its child mime:part elements, containing a soapbind:body child.

2.3.5.3.6 WSDL Parts A mime:content in a DESCRIPTION MUST reference a wsdl:part that is defined using either the type attribute

or the element attribute.

In a MESSAGE, a message part bound to a mime:content that refers to global element declaration (via the element attribute of the wsdl:part element) MUST be serialized within the MIME part as a serialization of an XML infoset whose root element is described by the referenced element.

In a DESCRIPTION, if a message part is bound to a mime:content that refers to a type (via the type attribute of the wsdl:part element), then the value of that type attribute MUST be ignored in favor of media type of the type attribute of the mime:content element.

In a DESCRIPTION, if a wsdl:part element refers to a global element declaration (via the element attribute of the wsdl:part element) then the value of the type attribute of a mime:content element that binds that part MUST be a content type suitable for carrying an XML serialization.

2.3.5.3.7 Ordering of Parts A RECEIVER MUST NOT assume that the order of mime:part elements specified in a WSDL description is the

same as the order of MIME parts in the message.

In a DESRIPTION, a mime:part element that contains a soapbind:body child element MAY appear in any position amongst the other child elements of a mime:multipartRelated element.

2.3.5.3.8 Sending Fault MessagesA Fault MESSAGE MAY be serialized as either text/xml or multipart/related, if the wsdl:output child element of the corresponding binding operation in a description has a child mime:multipartRelated element.

2.3.5.3.9 Describing FaultsA wsdl:fault element in a DESCRIPTION MUST NOT have mime:multipartRelated element as its child element.



563564565

566567

568

569570571572

573574

575576

577578579

580581

582583584

585586587

588589590

591592593

594595596

597598

599600601

602603604

218

219

220

221

222

223

224

2.3.5.3.10 Sending Additional Parts Not Described in WSDLAdditional MIME parts may be included in the message beyond those described in the WSDL, and their position or order within the MIME package is not important.

A SENDER MAY send non-root MIME parts not described in the WSDL MIME binding.

A MESSAGE MUST include all of the MIME parts described by its WSDL MIME binding

2.3.5.3.11 Conformance of SOAP MessagesProfile conformance criteria for the conformance target ENVELOPE only apply to the SOAP envelope contained in the root part of the MIME package. SOAP envelopes in non-root parts may be described in a WSDL description as attachments, in which case, conformance criteria for non-root parts listed in the WSDL description apply.

The root part of a MESSAGE MUST be conformant with all the requirements for an envelope in version 1.1 of the Basic Profile.

2.3.6 WS-I Basic Security Profile 1.0 with WS-Security and SAML provides

2.3.6.1 Message Integrity Message recipient can verify that message contents are identical to what they were when they left the recipient’s control.

For the reliability mechanisms described here to fulfill the reliability contract, this specification strongly RECOMMENDS that message header integrity be guaranteed end-to-end by using adequate security options such as those described in Web Services Security:

2.3.6.2 Message Confidentiality Message contents are only readable by authorized persons/entities. This can apply to entire messages or parts of messages; “parts” in this sense includes attachments to the message body.

Also known as "encryption", but that's technically an implementation technique, not a requirement.

Individuals should be able to access certain encrypted parts of messages, while leaving others obscured.

2.3.6.3 Message Non Repudiation Sender of message cannot deny having sent it at a particular date and time. Also, sender can later prove having sent the message at a particular date and time.

2.3.6.4 Message Authentication The component receiving a message must be provided with information (credentials) so that it can verify the identity of the sending component.

2.3.7 WS-Reliability 1.1 provides

2.3.7.1 Message Reliability Delivery of each message (or else notification of failure) is guaranteed (assured); duplicate messages are eliminated



605606607

608

609

610611612613

614615

616617

618619

620621622623

624625626

627628

629630

631

632633634

635636637

639

640641

642

225

226

227

228

229

230

231

A Reliable Message Agreement is a list of Agreement Items.

A Sending Component MUST be capable of (1) taking knowledge (whether by configuration, an API call, a message, the result of an algorithm or any other means) of a set of values that represent the Reliable Message Agreement Items described in this specification and (2) processing them according to the semantics described in this specification.

A Receiving Component MUST be capable of (1) taking knowledge of the Agreement items as they are communicated via the header elements of Reliable Messages and (2) processing them according to the semantics described in this specification.

The following table is the Agreement Items this specification uses.

Name Value Definition

GuaranteedDelivery enabled/disabled Guaranteed Delivery

NoDuplicateDelivery enabled/disabled Message delivery without duplicates or Duplicate Elimination

OrderedDelivery enabled/disabled Guaranteed Message Ordering

GroupMaxIdleDuration number of seconds The elapsed time limit from the last message sent or received in a group, after which the group can be terminated. The value MUST NOT be zero or smaller.

GroupExpiryTime date/time The date and time after which the group can be terminated.

ExpiryTime date/time The date and time after which a message must not be delivered to the SENDER.

ReplyPattern "Response", "Callback", "Poll"

The mode of response for Acknowledgments or Faults.

2.3.7.2 Transactional Messaging Transactional messaging ensures the integrity of exchange patterns that involve possibly several messages. Failure conditions may involve application-level decisions based on message payload interpretation. This specification is concerned with the reliability of individual messages from submission to delivery; it ignores any interpretation of these messages.

2.3.8 BPEL or BTP or others provides Work in Progress



643

644645646647

648649650651

652653

654

655656657658659

660661

662

232

233

234

235

236

237

238

2.3.9 UDDI

2.3.9.1 Directory Of Components It has been identified as a general necessity for the LegalXML System Components to be aware of all other accessible components within the system.

Specifically, this information is necessary for the peer-to-peer Electronic Service processes, where each Service Provider MDE is expected to be aware of all other accessible Service Provider MDE.

A Directory Of Components expresses this information:

For each component participating in the system:

Id A value that uniquely identifies the component from all others in the system.

ComponentType A value indicating if the component is a Filing Review component, Filing Assembly component, Court Record component, or Service Provider component. This indicates the processes and queries it is intended to support.

Interface Address(es) The address(s) of the component's interfaces.

Each of the component's transaction, query, event, and policy interfaces must be identified such that other components are aware of where to access the API.

2.4 ebXML Messaging ProfileThis profile provides an implementation specification for Blue Nonfunctional Requirements. This specification incorporates and builds upon elements from the ebXML / eGov technology stack.

This specification incorporates and builds upon a mature stack of open industry "electronic business XML" family of standards known as ebXML. These standards were developed to extend the Electronic Data Interchange (EDI) standards of the past 20 years to take advantage of new Internet technologies and the emergence of XML as an Electronic Data Interchange format. When new evolving Web Services standards overlap or extend ebXML functions the ebXML standard utilizes Web Services functions consistent with the interoperability recommendations of the Web Services Interoperability group.

The ebXML Messaging Services specification is the Core Profile for Blue Nonfunctional Requirements and specifies how to standardize the packaging of both Web Services components and ebXML components to support a wide variety of e-government information exchanges proposed in Blue:

2.4.1 ebXML – ebMessaging Services (ebMS V3.0 ) Stack Web Services Standards incorporated include:

HTTP(RFC 2616), FTP

SOAP 1.2

SOAP Messaging with Attachments

WS-Reliability Integration

WS-Security (Point-to-Point)

WS-I Basic profile 1.1 (Security and Attachments)

WS-Context



663

664665666

667668669

670671

672673

674

675676677

678

679680681

682683684

685686687688689690691

692693694695

696

697698

699

700

701

702

703

704

705

706

239

240

241

242

243

244

245

Complies with WS-Interoperability

Complies with WS-Interoperability Basic Profile 1.1 for Asynchronicity Of Messaging

Message Acknowledgement

Complies with WS-I Attachments Profile 1.0 with Soap Messages with Attachments for Unlimited Document Size And Format (adoption of MTOM)

Complies with WS-I Basic Security Profile 1.0 with WS-Security and SAML for Message Integrity

Message Confidentiality

Message Non Repudiation

Message Authentication

Integrates WS-Reliability 1.1 for Message Reliability

ebXML Collaboration Protocol Profile Version 2.x (optionally for Court Policy)

It is possible that some Blue Nonfunctional Requirements will not be met by an element in this stack; in this case, the profile will add a new element (either from the eGov ebXML Extensions)



707

708709

710

711

712713714

715

716717718

719

720

721

722

723724

725

726727728

729730731

246

247

248

249

250

251

252

3 GJXDM Element MapItems Used by Blue

I = Include

E = Excluded Not Used

GJXDM XML Header GJXDM Definition

j:CaseParticipants (uses and extends Person and Organization)

I CaseDefendantParty.Organization A person, organization, or property being charged or sued in a court of law. Sometimes referred to as the defendant.

I CaseDefendantParty.Person A person, organization, or property being charged or sued in a court of law. Sometimes referred to as the defendant.

I CaseDefendantParty.Property A person, organization, or property being charged or sued in a court of law. Sometimes referred to as the defendant.

I CaseDefenseAttorney An attorney who defends a case.

I CaseInitiatingParty.Organization A person, organization, or property that brings charges or a suit against another in a court of law. Can be either a victim in a criminal case or a plaintiff in a civil case.

I CaseInitiatingParty.Person A person, organization, or property that brings charges or a suit against another in a court of law. Can be either a victim in a criminal case or a plaintiff in a civil case.

I CaseInitiatingParty.Property A person, organization, or property that brings charges or a suit against another in a court of law. Can be either a victim in a criminal case or a plaintiff in a civil case.

I CaseJudge A judicial official assigned to a case.

E CaseJuror An empanelled juror or an alternate juror.

E CaseOfficial Details about a justice official's involvement in a court case.



732

253

254

255

256

257

258

259

Items Used by Blue

I = Include



E CaseOtherOfficial A miscellaneous person or organization involved in a court case.

I CaseOtherActor.Organization A miscellaneous person, organization, or property involved in a court case.

I CaseOtherActor.Person A miscellaneous person, organization, or property involved in a court case.

I CaseOtherActor.Property A miscellaneous person, organization, or property involved in a court case.

I CaseProsecutionAttorney An attorney who prosecutes a case.

I CaseRespondentParty.Organization The person, organization, or property in a court case that is required to answer a petition for a court order or writ requiring the respondent to take some action, halt an activity or obey a court's direction. In such matters the moving party (the one filing the petition) is usually called the "petitioner." Thus, the respondent is equivalent to a defendant in a lawsuit. On an appeal, the party who must respond to an appeal by the losing party in the trial court (called "appellant") in the appeals court. The accused in a domestic violence case or civil action; a person responding to a Request or Petition for Protection filed by a petitioner.

I CaseRespondentParty.Person The person, organization, or property in a court case that is required to answer a petition for a court order or writ requiring the respondent to take some action, halt an activity or obey a court's direction. In such matters the moving party (the one filing the petition) is usually called the "petitioner." Thus, the respondent is equivalent to a defendant in a lawsuit. On an appeal, the party who must respond to an appeal by the losing party in the trial court (called "appellant") in the appeals court. The accused in a domestic violence case or civil action; a person responding to a Request or Petition for Protection filed by a petitioner.

I CaseRespondentParty.Property The person, organization, or property in a court case that is required to answer a petition for a court order or writ requiring the respondent to take some action, halt an activity or obey a court's direction. In such matters the moving party (the one filing the petition) is usually called the "petitioner." Thus, the respondent is equivalent to a defendant in a lawsuit. On an appeal, the party who must respond to an appeal by the losing party in the trial court (called "appellant") in the appeals court. The accused in a domestic violence case or civil action; a person responding to a Request or Petition for Protection filed by a petitioner.



260

261

262

263

264

265

266

Items Used by Blue

I = Include



E CaseWitness The person/entity who has information relating to the activity or who testifies in court.

J:Court (extends Organization)

I CourtName A name of a unit of a court.

I CourtAdministrativeUnitText A unit within a court system responsible for record maintenance.

I CourtDivisionText An area of case processing and the law governing specific types of matters before the court and governed by distinct court rule and processes, e.g., criminal, juvenile, family, civil, etc.

I CourtTypeCode A type of court, e.g., district court, appellate court, state superior court.

E CourtSupervisingAgency A supervising agency that performs court services for a court unit.

J:Organization

I OrganizationName A name of an organization.

I OrganizationID An identifier of an organization based on the type of organization it is, e.g., for a school, this would be a school identifier, for a lien holder, this would be a lien holder identifier, for a court, this would be a court identifier.

I OrganizationORIID A unique identifier assigned to a justice-related organization by the federal government. Sometimes referred to as ORI, ORI code, Originating Agency Code.

E OrganizationTaxID A federal tax identifier assigned to an organization. Sometimes referred to as a Federal Employer Identification Number, FEIN, an Employer Identification Number, or an EIN.

I OrganizationLocalID An identifier assigned on a local level to an organization.

E OrganizationOtherID A generic identifier assigned to an organization.

I OrganizationTypeText A general functional type of an organization

E OrganizationTypeCode.ncicORIAgency A code that identifies the functional type of an organization.

E OrganizationTypeCode.ncicTYPO A code that identifies the functional type of an organization.

I OrganizationDescriptionText A description of an organization



267

268

269

270

271

272

273

Items Used by Blue

I = Include



I OrganizationLocation A location of an organization.

E PrimaryContactInformation Information on a preferred or primary contact mechanism.

I OrganizationDoingBusinessAsName A name an organization uses for conducting business. Sometimes referred to as a DBA.

E OrganizationGovernmentLevelCode A code that identifies a governmental level of an organization: local, county, state, federal, or nongovernmental.

E OrganizationAbbreviationText An abbreviation, acronym, or code for an organization name, e.g., FBI, NCIC.

I OrganizationUnitName A name of a high-level division of an organization, e.g., department, agency.

I OrganizationSubunitName A name of a subdivision of a high-level division of an organization, e.g., division.

E OrganizationActivityText An activity that an organization is known or thought to be involved with, e.g., law enforcement, supervision.

E OrganizationStatusText An overall status of an organization, e.g., active/inactive/...

E OrganizationJurisdiction An area of service or jurisdiction an organization has over a region.

E OrganizationParent.Affiliate A person or organization that owns, controls, or operates the organization.

E OrganizationParent.Organization A person or organization that owns, controls, or operates the organization.

E OrganizationSubsidiary A person or organization that is owned, controlled, or operated by the organization.

E OrganizationMember A person or organization that has joined an organization.

E OrganizationAffiliate A person or organization that has some relationship or association with an organization.

I OrganizationIncorporatedIndicator True if an organization is incorporated (e.g., corporation); false otherwise (e.g., proprietorship or partnership).

I OrganizationPrincipalOfficial A chief or high ranking executive of an organization.

E OrganizationEstablishedDate A date an organization was started.



274

275

276

277

278

279

280

Items Used by Blue

I = Include



E OrganizationTerminationDate A date an organization went out of business.

I OrganizationBranchName A name or number of the chapter or branch an organization is known by within a larger group of organizations.

E OrganizationDayContact The contact information that is valid during daytime hours.

E OrganizationEmergencyContact The contact information should be used to contact the person during an emergency only.

E OrganizationEveningContact The contact information that is valid during evening (early night) hours.

E OrganizationEmploymentHistory An employment history or an employee of an organization or company.

E OrganizationNightContact The contact information that is valid during night hours.

E OrganizationOccupiedStructure Indicates that the named organization occupies at least part of the structure.

E OrganizationPrimaryContact The preferred contact for an individual. Use this designation only when more specific ones (e.g. home or work) are not available.

E OrganizationUnspecifiedContact The contact information should be used to contact the person under unspecified circumstances.

I OrganizationName A name of an organization.

J:Person

I PersonName A name by which a person is known.

I PersonAlternateName An alternate name used by a person. Sometimes referred to as an AKA.

E Residence Details about the place in which a person lives.

E ResidenceTypeText A type of place at which a person lives, e.g., house, apartment, homeless.

E ResidenceDescriptionText A general description of a place in which a person lives.

E ResidenceStartDate A date a person began living at a residence.

E ResidenceEndDate A date a person stopped living at a residence.

E ResidenceOccupancyTypeText A person's type of occupancy of a residence, e.g., owns, rents.

E ResidencePaymentAmount An amount of money a person pays each payment period to live at a place



281

282

283

284

285

286

287

Items Used by Blue

I = Include



of residence. This may include a mortgage payment amount or a rent amount.



288

289

290

291

292

293

294

Items Used by Blue

I = Include



E ResidencePaymentPeriodText An interval or period for which a person is required to make regular residence payments.

E PrimaryContactInformation Information on a preferred or primary contact mechanism.

E Employment Details about the employment of a person.

E PersonDescriptionText A general description of a person.

E PersonBirthDate A date a person was born.

E PersonBirthLocation Details about a place where a person was born.

E PersonBirthPlaceCode A code identifying the state or country of a person's birth.

E PersonDeathDate A date a person died or was declared legally dead.

E PersonAgeMeasure A measurement of the age of a person.

E PersonAgeMeasure.Range A measurement of the age of a person.

E PersonAgeDescriptionText A description of the age of a person.

E PersonLivingIndicator True if a person is alive, false if a person is dead. This may be useful if death date is not known.

I PersonAssignedIDDetails A set of details about identifications issued to a person.

E PersonPhysicalDetails A set of details about the physical appearance of a person.

E PersonSocialDetails A set of details about the social characteristics of a person.

E PersonBiometricDetails A set of details about measurable biological or behavioral characteristics, which can reliably recognize the identity, or verify the claimed identity, of a person.

E PersonMedicalDetails A set of details about the medical condition of a person.

E PersonAccompliceActivity An activity with which a subject has some relation or degree of involvement

E PersonAccompliceWithSubject A person who is an accomplice with a subject person.

E PersonDrivingIncident A driving accident in which a person is involved.

E PersonAcquaintance The associate is an acquaintance of the subject.



295

296

297

298

299

300

301

Items Used by Blue

I = Include



E PersonAdoptedChild A person who is an adopted child of the person.

E PersonAdoptiveParent A person who is an adoptive parent of the person.

I PersonAffiliationOrganization Other organization a person is affiliated with

E PersonAlias A name and set of personal demographics describing the same person using alternative descriptors, e.g., an AKA.

E PersonAssignmentUnit.EnforcementUnit The unit assigned to or associated with a person.

E PersonAssignmentUnit.Organization The unit assigned to or associated with a person.

E PersonTemporaryAssignmentUnit The organizational unit to which a person is assigned, specifically a temporary assignment.

E PersonAuthorityFigure Indicates that the Subject had a trusted position of authority over associate subject (i.e. priest, teacher, boy scout leader, counselor, therapist, etc.)

E PersonBabysittee The person being watched by the babysitter.

E PersonBabysitter The person performing the babysitting.

E PersonBiologicalChild A person who is a biological child of the person.

E PersonBiologicalParent A person who is the biological parent of the person.

E PersonCharge A sequence of charges against a person. This context generally includes an index

E PersonChild A person who is a child of the person.

E PersonCohabitant The associate shares a common residence with the subject

E PersonCommonLawSpouse The associate is a common-law spouse of the subject.

E PersonDayContact The contact information should be used during daylight hours only.

E PersonDetainedLocation.Location The location or structure at which a person is or was detained.

E PersonDetainedLocation.Structure The location or structure at which a person is or was detained.

E PersonDomesticPartner The associate is the domestic partner of the subject.

E PersonDriversLicense A driver's license.



302

303

304

305

306

307

308

Items Used by Blue

I = Include



E PersonEmergencyContact The contact information should be used to contact the person during an emergency only.

e PersonEveningContact The contact information should be used during evening hours (early night) only.

E PersonFamilyRelation The associate and the subject are members of the same family, but the precise relationship is not clear or not noted.

E PersonFosterChild The associate is a legal foster parent of the subject

E PersonFosterParent The associate is a legal foster child of the subject

E PersonGangAffiliation A gang a person is affiliated with

E PersonGuardian A person who is a legal guardian of the person.

E PersonGuardianRecipient A person who is under the legal guardianship of the person.

E PersonEmploymentHistory Details about an employment record of a person.

E PersonIssuedTitle.PropertyRegistration A title which has been issued to a person.

E PersonIssuedTitle.PropertyTitle A title which has been issued to a person.

E PersonMarriagePartner The associate is legally married to the subject.

E PersonModusOperandi A methodology of action, particularly a criminal action, known to be routinely associated with a persons crimes.

E PersonNeighbor The associate is a neighbor of the subject.

E PersonNightContact The contact information should be used during night hours only. If there is no evening contact, this information may be used during the evening as well.

E PersonParent The associated person is a parent of the main person. Use this context when a more specific relationship is not relevant or not important

E PersonPrimaryWorker A primary social worker or other overseer assigned to a person that is not a caregiver.

E PersonReferralWorker Employee of State assigned to the particular juvenile



309

310

311

312

313

314

315

Items Used by Blue

I = Include



E PersonSocialFriend The associate is a friend of the subject, in a social setting. This includes relationships such as "boy friend" and "girl friend".

E PersonSpouse The associate is a spouse of the subject. Used when the legal status of the relationship (marriage, common-law) is not known.

E PersonStranger The associate has no known or admitted knowledge of the subject

E PersonUnspecifiedContact The contact information should be used to contact the person under unspecified circumstances.

E PersonWasCommonLawSpouse The associate was at one time the common-law spouse of the subject but has legally separated or divorced.

E PersonWasDomesticPartner The associate was at one time the domestic partner of the subject but has dissolved the relationship.

E PersonWasMarriedTo The associate was at one time married to the subject but has legally divorced.

E PersonWasSpouse The associate was at one time a spouse of the subject but has divorced or otherwise legally severed the relationship. Used when the legal status of the relationship (marriage, common-law) is not known.

E PersonWorkContact The contact information should be used when the person is expected to be or might be at work.

E PersonWorkLocation.Location The work address or structure of a person. This association is used when the person's employer is not known. If the employer is known, use an Organization which in turn has a Location.

E PersonWorkLocation.Structure The work address or structure of a person. This association is used when the person's employer is not known. If the employer is known, use an Organization which in turn has a Location.

J:PersonAssignedIDDetails

E PersonSSNID A 9-digit numeric identifier assigned to a living person by the U.S. Social Security Administration. A social security number of a person. Sometimes referred to as a SSN.

E PersonTaxID An identifier used to refer to a specific person within the tax system of a



316

317

318

319

320

321

322

Items Used by Blue

I = Include



country. Within the U.S., this identifier may also be a persons social security number (SSN) or another identifier.



323

324

325

326

327

328

329

Items Used by Blue

I = Include



E PersonDriverLicenseID Information about an identifier used to refer to a specific person who has obtained a driver's license. Sometimes referred to as driver license number, dlNumber.

E DrivingJurisdictionAuthorityCode A federal or state organization, such as a department of motor vehicles (DMV), with jurisdiction over a person's driving privileges.

E PersonFBIID A number issued by the FBI's Automated Fingerprint Identification System (AFIS) based on submitted fingerprints.

E PersonStateID A number issued by a state Automated Fingerprint Identification System (AFIS) based on submitted fingerprints. Sometimes referred to as a State ID number or a SID.

E PersonAFISID A number issued by a local agency (county) Automated Fingerprint Identification System (AFIS) based on submitted fingerprints.

I PersonOtherID Information about an identifier with a type that is not explicitly defined in the standard that refers to a person within a certain domain, e.g., state ID cards or other non-license and non-fingerprint based IDs.

I PersonIDTypeCode A code the identifies a type of identifier assigned to a person.

E PersonRegisteredOffenderIndicator True if a person is required to register as an offender; false otherwise.

E PersonFirearmSalesDisqualifiedIndicator True if a person is prohibited from purchasing firearms; false otherwise.

E PersonLicenseID A string that identifies a license, certification, or registration of a person for some purpose; may be granted to certify professional occupation or skill, e.g., medical license, pilot license, professional engineer.

E PersonGeneralLedgerID A general-ledger account number associated with a person.

E PersonHumanResourcesID A human resources id or assigned number for a person, such as a badge number.

E PersonVendorID Vendor number for a person

E PersonNationalID A general ID that identifies a person within a country but is not based on fingerprint.



733

330

331

332

333

334

335

336



734

337

338

339

340

341

342

343

Status XML Header Definition

j:AppellateCase

AppellateCaseNotice A request filed with an appellate court to start an appellate case. Sometimes referred to as a Notice of Appeal.

AppellateCaseNoticeFilingCourt An appellate court where a notice of appeal is filed in hopes of being reviewed.

AppellateCaseNoticeOriginalCourt A court where a case was originally tried.

AppellateCaseNoticeReasonText A statement explaining the reason for an appeal.

AppellateCaseNoticeDefendingAgency A firm reported in an appellate case notice that originally defended a case.

AppellateCaseNoticeDefendantActor.Organization A person, organization, or property that was originally tried in a case.

AppellateCaseNoticeDefendantActor.Person A person, organization, or property that was originally tried in a case.

AppellateCaseNoticeDefendantActor.Property A person, organization, or property that was originally tried in a case.

AppellateCaseNoticeProsecutingAgency A firm reported in an appellate case notice that originally tried a case.

AppellateCaseNoticeProsecutingAttorney An attorney reported in an appellate case notice that originally tried a case.

AppellateCaseBrief A document written by prosecution or defense summarizing why a lower court acted correctly or incorrectly.

AppellateCaseDecision A statement by a judge or court of a decision reached in regard to an appeal. This may be an opinion or an order.

AppellateCaseDecisionName A name of an opinion or order that is a result of an appellate case decision.

AppellateCaseDecisionID An identifier of an appellate case decision.

AppellateCaseDecisionText A decision of the appellate court about a case. For example, Reaffirming, Dismissal, Order Opinion, etc.

AppellateCaseDecisionDescriptionText A description of an appellate case decision.

AppellateCaseDecisionDate A date that an issuing judge signs an Opinion or issues an Order.

AppellateCaseDecisionTypeText A type of appellate case decision made, e.g., opinion, order.

AppellateCaseDecisionIssuingJudge A judge that issues, orders, or authors an appellate case decision.

AppellateCaseDecisionOpinionIndicator True if an appellate case decision refers to an opinion issued; false if it refers to an order issued.



344

345

346

347

348

349

350




351

352

353

354

355

356

357


AppellateCaseDecisionPrecedenceIndicator True if an appellate case decision opinion or order is worthy of setting an example or justification for a later decision; false otherwise.

AppellateCaseDecisionReliefIndicator True if an appellate case decision states any relief assistance be provided to a defendant; false otherwise.

AppellateCaseDecisionReliefEffectiveDate A date relief is to be made to a person as stated in an appellate case decision.

AppellateCaseJudgePanel A panel of judges presiding over an appellate case. Normally there are three appellate judges, but there may be the entire membership of the Court of Appeals or Supreme Court.

AppellateCaseOriginalCase An original case that is being retried in an appellate court.

AppellateCaseRelatedCase A case related to a case being tried in an appellate court.

AppellateCaseSanction A sanction ordered for a subject by a judge or a supervising agency as a result of a disposition of a charge.

j:Address

AddressFullText A complete address to be used when the address components cannot be broken down into the GJXDM components.

AddressRecipientName A person, organization, or other recipient associated with an address to whom paper mail may be sent.

AddressPrivateMailboxText Identifies a private mailbox within a company. Sometimes referred to as a Mail stop Code.

LocationBuilding Details about a building at a location.

BuildingFullText A complete reference that identifies a building.

BuildingName A name of a building, e.g., "Electronic Research Building"

BuildingNumberText A number or text associated with a building, e.g., 115C.

BuildingSubUnitText A department, group, division, or other subcomponent of a building.

LocationStreet Details about a street.

LocationSecondaryUnitText A piece of information used to identify a particular unit within a specific location. Examples of this could be an apartment number or a suite number.

AddressRouteName The name and number of a postal route.

AddressMailDeliveryUnitText A complete Post Office box number or other mail delivery point for a location, e.g., "PO BOX 12345"

AddressRegionFullText A single reference to a city, state, and postal code. This is customarily the third line in an address.

LocationCityName A name of a city or town.



358

359

360

361

362

363

364


LocationCountyName A name of a county, parish, or vicinage.

LocationCountyCode A code identifying a county, parish, or vicinage.

LocationStateName A name of a state, commonwealth, province, or other subregion of a country.

LocationStateCode.CanadianProvince A code identifying a state.

LocationStateCode.fips10-4International A code identifying a state.

LocationStateCode.fips5-2Alpha A code identifying a state.

LocationStateCode.fips5-2Numeric A code identifying a state.

LocationStateCode.ncicLIS A code identifying a state.

LocationStateCode.ncicLSTA A code identifying a state.

LocationStateCode.ncicRES A code identifying a state.

LocationStateCode.USPostalService A code identifying a state.

LocationPostalCodeID A zip code or postal code.

LocationPostalCodeExtensionID An extension of a zip code or postal code.

LocationCountryName A name of a country.

LocationCountryCode.fips10-4 A code that identifies a country, territory, or dependency.

LocationCountryCode.iso3166Alpha2 A code that identifies a country, territory, or dependency.

LocationCountryCode.iso3166Alpha3 A code that identifies a country, territory, or dependency.

LocationCountryCode.iso3166Numeric A code that identifies a country, territory, or dependency.

AddressOther An undefined address component to be labeled and tracked.

AddressComponentText A value of the miscellaneous address component.

AddressComponentDescriptionText A description of a miscellaneous address component.

j:Case

CaseTypeText Identifies the type of case being considered, e.g., law enforcement, prosecution, court, public safety, department of human services, department of health.

CaseTitleText An official name of a case.

CaseYearDate A year a case is tried.

CaseTrackingID A number used to track a case.



365

366

367

368

369

370

371


CaseDocketID A number used to identify a case docket.

CaseOtherID A miscellaneous identifier for a case.

CaseAmendedCharge A charge different than the original charge a person is being tried for in a court of law.

CaseCharge A charge or accusation a person is being tried for in a court of law.

CaseClassification A classification or categorization of a case.

CaseCategoryText A category type of a court case, e.g. criminal, civil, juvenile, family.

CaseSeverityText A severity of a case, e.g., felony, misdemeanor, infraction.

CaseCourt A court of law in which the case is being tried.

CaseCourtEvent A court occurrence. It generally refers to an appearance (Appearance, Arraignment, Findings, Sentencing, etc.) but may include clerical events such as filing an affidavit or cash register events.

CaseDetails Additional information about a case.

CaseDisposition An outcome or processing of a case.

CaseExhibit An item admitted in court as evidence.

CaseFiling A submission from a prosecutor that initiates a court case.

CaseHearing An appearance before a judicial official conducted in person, by telephone, or by video.

CaseLineageCase A description of a case at a previous stage.

CaseParticipants Details about the participants involved in a court case

CasePendingCourtEvent A court event or activity that is postponed or pending.

CaseRelatedCase Details about a related case.

CaseStatus A status of a case.

CaseTrial A type of hearing during which the final disposition of a case is determined.

CaseConvictionReportingRequirements Details about the requirements placed on a person convicted in a case to report to a supervising agency.

PersonLicenseID A string that identifies a license, certification, or registration of a person for some purpose; may be granted to certify professional occupation or skill, e.g., medical license, pilot license, professional engineer.

ConvictionReportingProfessionName A name of the profession or occupation of an arrested professional.

ConvictionReportingRequirementText A description of when the court is required to file a special report, e.g. when complaint is filed, at conviction.

j:CaseDetails

CaseCapiasDate A date where subject proceeds directly to court, without being able to post bond. Similar to a Failure to Appear



372

373

374

375

376

377

378


CaseDefendantQuantityText A number of defendants being tried at once for a case.

CaseDefendantSelfRepresentationIndicator True if a defendant waived the right to have a defense attorney and is representing him or her self; false otherwise.

CaseSubtypeText Second level of case category classification, e.g. employment to further define a civil case, or homicide to further define a felony case.

CaseContinuanceDate A date a court case is set to resume after being postponed.

CaseInformationAdmissibleText A piece of new trial information that may be admissible in court.

CaseInformationUnadmissibleText A piece of new trial information that is not admissible in court.

CaseOriginalCourt A court that originally heard or tried a case before it was transferred or appealed.

CaseProceedingTypeText A type of case proceeding, e.g., hearing, trial, arraignment.

CaseResolutionText A result of a case.

CaseRestrictionText A restriction imposed upon a party, e.g., a restraining order.

CaseRestrictionDate A date a restriction is placed on a person by a court order.

CaseSecurityText A level of case security required from low to high

CaseTerminationStageText A stage of termination for a case.

CaseTerminationTypeText A type of termination for a case.

CaseInformationAdmissibleIndicator True if new trial information may be entered from an appellate ruling/decision; false otherwise.

CaseDomesticViolenceIndicator True if the case involves domestic violence; false otherwise.

CaseDrivingImpairedIndicator True if the case involves a person who was driving with the presence of illegal or un prescribed prescription drugs in his or her system; false otherwise.

CaseDrivingIntoxicatedIndicator True if a case involves a person who was driving with blood alcohol level that is higher than the law allows; false otherwise.

CaseProtectionOrderIndicator True if a Domestic Violence Protection Order or Anti harassment Order is filed with the Judgment and Sentence; false otherwise.

CaseVerdictGivenIndicator True if a verdict is given by judge or jury; false otherwise.

CaseVictimNotProsecutingIndicator True if a victim is not or was not willing to prosecute; false otherwise.

j:CaseParticipants (uses Person and Organization)

CaseDefendantParty.Organization A person, organization, or property being charged or sued in a court of law. Sometimes referred to as the defendant.



379

380

381

382

383

384

385


CaseDefendantParty.Person A person, organization, or property being charged or sued in a court of law. Sometimes referred to as the defendant.

CaseDefendantParty.Property A person, organization, or property being charged or sued in a court of law. Sometimes referred to as the defendant.

CaseDefenseAttorney An attorney who defends a case.

CaseInitiatingParty.Organization A person, organization, or property that brings charges or a suit against another in a court of law. Can be either a victim in a criminal case or a plaintiff in a civil case.

CaseInitiatingParty.Person A person, organization, or property that brings charges or a suit against another in a court of law. Can be either a victim in a criminal case or a plaintiff in a civil case.

CaseInitiatingParty.Property A person, organization, or property that brings charges or a suit against another in a court of law. Can be either a victim in a criminal case or a plaintiff in a civil case.

CaseJudge A judicial official assigned to a case.

CaseJuror An empanelled juror or an alternate juror.

CaseOfficial Details about a justice official's involvement in a court case.

CaseOtherOfficial A miscellaneous person or organization involved in a court case.

CaseOtherActor.Organization A miscellaneous person, organization, or property involved in a court case.

CaseOtherActor.Person A miscellaneous person, organization, or property involved in a court case.

CaseOtherActor.Property A miscellaneous person, organization, or property involved in a court case.

CaseProsecutionAttorney An attorney who prosecutes a case.

CaseRespondentParty.Organization The person, organization, or property in a court case that is required to answer a petition for a court order or writ requiring the respondent to take some action, halt an activity or obey a court's direction. In such matters the moving party (the one filing the petition) is usually called the "petitioner." Thus, the respondent is equivalent to a defendant in a lawsuit. On an appeal, the party who must respond to an appeal by the losing party in the trial court (called "appellant") in the appeals court. The accused in a domestic violence case or civil action; a person responding to a Request or Petition for Protection filed by a petitioner.

CaseRespondentParty.Person The person, organization, or property in a court case that is required to answer a petition for a court order or writ requiring the respondent to take some action, halt an activity or obey a court's direction. In such matters the moving party (the one filing the petition) is usually called the "petitioner." Thus, the respondent is equivalent to a defendant in a lawsuit. On an appeal, the party who must respond to an appeal by the losing party in the trial court (called "appellant") in the appeals court. The accused in a domestic violence case or civil action; a person responding to a Request or Petition for Protection filed by a petitioner.

CaseRespondentParty.Property The person, organization, or property in a court case that is required to answer a petition for a court order or



386

387

388

389

390

391

392


writ requiring the respondent to take some action, halt an activity or obey a court's direction. In such matters the moving party (the one filing the petition) is usually called the "petitioner." Thus, the respondent is equivalent to a defendant in a lawsuit. On an appeal, the party who must respond to an appeal by the losing party in the trial court (called "appellant") in the appeals court. The accused in a domestic violence case or civil action; a person responding to a Request or Petition for Protection filed by a petitioner.



393

394

395

396

397

398

399


CaseWitness The person/entity who has information relating to the activity or who testifies in court.

j:Court (extends Organization)

CourtName A name of a unit of a court.

CourtAdministrativeUnitText A unit within a court system responsible for record maintenance.

CourtDivisionText An area of case processing and the law governing specific types of matters before the court and governed by distinct court rule and processes, e.g., criminal, juvenile, family, civil, etc.

CourtTypeCode A type of court, e.g., district court, appellate court, state superior court.

CourtSupervisingAgency A supervising agency that performs court services for a court unit.

j:CourtEvent

CourtEventSequenceID A unique identifier for a court case event record.

CourtEventActivity A court-related action associated with a court case event. There must be at least one activity for each event. For example: ordering bail, pleading of not guilty, filing an affidavit. An activity may have conditions attached to it.

CourtEventAppearance An appearance in court required of a party

CourtEventCase A case associated with a court event.

CourtEventCourt A court in which a court event occurs.

CourtEventJudge A judge associated with a court event.

CourtEventMotion A request made to a court for a ruling or an order.

CourtEventSchedule Details about the days for which a court event is scheduled.

j:DocumentDescriptionMetadata

DocumentID A unique and unambiguous reference to the resource within a given context.

DocumentSequenceID An identifier that determines the document order in a set or related documents.

DocumentGroupID An identifier of a group to which a document belongs.

DocumentFileControlID A number assigned to a document that identifies the location of a file is located within a file control system.

DocumentFileName A file name of an electronic copy of a document.

DocumentFileExtensionText A file extension of an electronic copy of a document.

DocumentSupplementalMarkingText A marking made on a document.

DocumentTitleText A name given to a resource, typically a name by which it is formally known.



400

401

402

403

404

405

406


DocumentAlternativeTitleText Any form of the title used as a substitute or alternative to the formal title of the resource.

DocumentSubjectText A subject that is typically expressed as keywords, phrases, or classification codes that describe a topic of the resource.

DocumentDescriptionText A brief account of the content of a resource. May include but not limited to an abstract, table of contents, graphical, or free-text account of the content.

DocumentContentTableText A subunit of the content of the resource usually containing a list of the information content of the resource.

DocumentAbstractText A summary of the content of the resource.

DocumentTypeText A nature or genre of the content of the resource. Includes terms describing general categories, functions, or genres. To describe the physical or digital manifestation of the resource use the Format property.

DocumentSummaryText A short description of the document subject, contents, and any "bottom line" point the document is trying to convey.

DocumentLocation Details about the location of a physical document.

DocumentStatus Indicates the document's status, e.g., approved, submitted, awaiting revision.

DocumentApprovedIndicator True if a document has been approved; false otherwise.

DocumentCommentText A general comment about a document.

DocumentKeywordText A keyword or words that describe the overall content of the document, or the main topic of discussion.

DocumentMediaTypeText A physical device on which a document is stored.

DocumentMediumText The makeup of the material or physical carrier of the resource.

DocumentFormatText The specific structural format of the binary object or file, e.g., "image/jpeg", "text/plain".

DocumentFormatTypeText The classification system used to define the specific format of the binary object or file, e.g., "MIME", "DIME".

DocumentLanguageCode.iso639-2b A language of the intellectual content of the resource.

DocumentLanguageCode.iso639-2t A language of the intellectual content of the resource.

DocumentCreationDate A date of the creation of the resource.

DocumentCutDate A cutoff date for information in a document. Sometimes referred to as Information Cutoff Date, ICOD.

DocumentEffectiveDate A date the information in a document becomes valid.

DocumentExpirationDate A date a document should be removed from a registry or index.

DocumentFiledDate A date a document was filed.

DocumentLastModifiedDate The date that a document was last updated.



407

408

409

410

411

412

413


DocumentFiledTime The time that the a document is officially filed. The circumstance of the official time is dictated by local policy and procedure, therefore the time recorded reflects the application of this policy.

DocumentPostDate A date a document is posted to Intelink.

DocumentPublicationDate A date of the first public dissemination of the content in any media.

DocumentReceivedDate A date a transmitted document was received.

DocumentCreator.Organization An entity primarily responsible for making the content of the resource.

DocumentCreator.Person An entity primarily responsible for making the content of the resource.

DocumentAuthor.Organization A person or organization primarily responsible for creating the intellectual content of the resource, e.g., author for written documents, artist, photographer or illustrator for visual resources.

DocumentAuthor.Person A person or organization primarily responsible for creating the intellectual content of the resource, e.g., author for written documents, artist, photographer or illustrator for visual resources.

DocumentSubmitter.Organization An entity responsible for making the resource available. May include a person, organization or service.

DocumentSubmitter.Person An entity responsible for making the resource available. May include a person, organization or service.

DocumentContributor.Organization An entity responsible for making contributions to the content of the resource. May include a person, organization, or service.

DocumentContributor.Person An entity responsible for making contributions to the content of the resource. May include a person, organization, or service.

DocumentSourceText A reference to a source from which the present resource is derived.

DocumentOtherAddresseeName A name of additional addressees.

DocumentApplicationName A name of the application used to create the document.

@applicationVersionText A version of an application.

DocumentLocationURI A URI (Uniform Resource Identifier) for the referenced document which may indicate the HTTP or Intelink address.

DocumentCoverageText.Address An extent or scope of the content of the resource. May include a spatial location, temporal period, or a jurisdiction.

DocumentCoverageText.Date An extent or scope of the content of the resource. May include a spatial location, temporal period, or a jurisdiction.

DocumentCoverageText.Text An extent or scope of the content of the resource. May include a spatial location, temporal period, or a jurisdiction.

DocumentCoverageText.Time An extent or scope of the content of the resource. May include a spatial location, temporal period, or a



414

415

416

417

418

419

420


jurisdiction.



421

422

423

424

425

426

427


DocumentIntelligenceTypeCode A nature or genre of the resource. Type is specified as an intelligence discipline, e.g., HUMINT, IMINT.

DocumentRelatedResourceText A reference to a related resource.

DocumentRelationText Another document related to this document instance.

DocumentRightsText Rights held in and over the resource. Rights are the constraints applied to assure the protection of privacy or intellectual property, and any special restrictions, limitations or warning on using a shared resource.

DocumentDisputedIndicator True if the accuracy of a document is disputed; false otherwise.

DocumentDisputedReasonCodeText A local code indicating a reason why the accuracy of a document is being disputed.

DocumentDisputedReasonText A reason why the accuracy of a document is being disputed.

j:JudicialOfficial (extends Person)

JudicialOfficialTypeText A type of judicial official, e.g., Judge, Attorney, DA, etc.

JudicialOfficialRegistrationID An identifier assigned to a judicial official after registering within a state or region.

JudicialOfficialBarMembership Details about a legal capacity in which a judicial official is able to practice law.

JudicialOfficialBarID An identifier assigned to a judicial official after meeting the requirement to practice law in a region. Includes information about the issuing authority.

JudicialOfficialBarStatus A status of a judicial officials bar membership.

JudicialOfficialPanelID An identifier or name of a panel or group to which a judicial official is assigned. Sometimes referred to as judges panel.

JudicialOfficialCourt A court unit to which a judicial official is assigned.

JudicialOfficialFirm An agency at which a judicial official works.

j:Location

LocationName A name of a location.

LocationTypeText A functional description of a location, e.g., residence, school, agency, park.

LocationTypeCode A code identifying a functional description of a location, e.g., residence, school, agency, park.

LocationDescriptionText A description of a location.

LocationSurroundingAreaDescriptionText A description of an area surrounding a location.

LocationRangeDescriptionText A description of the boundary or range of a location.

LocationAddress Details about a postal address for a location.

LocationAddressGrid Details about a specific geographic area of a Law Enforcement Agency's jurisdiction within a location.



428

429

430

431

432

433

434


LocationArea Details about the boundaries of a geographic area of location.

LocationContactInformation Details about contact information for a location.

LocationCrossStreet Details about a cross street or intersecting street near a location.

LocationHighway Details about a major public road at a location.

LocationLandmarkText A name or description of a distinguishing physical feature at a location.

LocationLocale Details about a geo-political area location.

LocationMapLocation Details about a location identified by map coordinate.

LocationRelativeLocation Details about a location relative to another location.

LocationElevation Details about a height or elevation of a location.

@elevationUnitCode The unit of measurement for an elevation.

LocationGeographicCoordinate Details about the latitude and longitude of a location.

LocationMGRSCoordinate Details about a coordinate from the Military Grid Reference System (MGRS). This coordinate represents a location with a Universal Transverse Mercator (UTM) coordinate and a unique military grid square.

LocationUTMCoordinate Details about a coordinate from the Universal Transverse Mercator (UTM) Coordinate System. This coordinate represents a location as with a grid zone, an easting value, and a northing value.

LocationContainsOrganization Indicates that a particular location contains the indicated organization. For example, the locale might be a neighborhood that contains a particular watch organization; a municipal complex might contain the Sherrifs organization.

LocationEmergencyServices The emergency services department or agency associated with a particular location

LocationNeighbor The associate lives in the general neighborhood of the location.

LocationPoliceDepartment The police department associated with a particular location.

J:Organization

OrganizationName A name of an organization.

OrganizationID An identifier of an organization based on the type of organization it is, e.g., for a school, this would be a school identifier, for a lien holder, this would be a lien holder identifier, for a court, this would be a court identifier.

OrganizationORIID A unique identifier assigned to a justice-related organization by the federal government. Sometimes referred to as ORI, ORI code, Originating Agency Code.

OrganizationTaxID A federal tax identifier assigned to an organization. Sometimes referred to as a Federal Employer Identification Number, FEIN, an Employer Identification Number, or an EIN.



435

436

437

438

439

440

441


OrganizationLocalID An identifier assigned on a local level to an organization.

OrganizationOtherID A generic identifier assigned to an organization.

OrganizationTypeText A general functional type of an organization

OrganizationTypeCode.ncicORIAgency A code that identifies the functional type of an organization.

OrganizationTypeCode.ncicTYPO A code that identifies the functional type of an organization.

OrganizationDescriptionText A description of an organization

OrganizationLocation A location of an organization.

PrimaryContactInformation Information on a preferred or primary contact mechanism.

OrganizationDoingBusinessAsName A name an organization uses for conducting business. Sometimes referred to as a DBA.

OrganizationGovernmentLevelCode A code that identifies a governmental level of an organization: local, county, state, federal, or nongovernmental.

OrganizationAbbreviationText An abbreviation, acronym, or code for an organization name, e.g., FBI, NCIC.

OrganizationUnitName A name of a high-level division of an organization, e.g., department, agency.

OrganizationSubunitName A name of a subdivision of a high-level division of an organization, e.g., division.

OrganizationActivityText An activity that an organization is known or thought to be involved with, e.g., law enforcement, supervision.

OrganizationStatusText An overall status of an organization, e.g., active/inactive/...

OrganizationJurisdiction An area of service or jurisdiction an organization has over a region.

OrganizationParent.Affiliate A person or organization that owns, controls, or operates the organization.

OrganizationParent.Organization A person or organization that owns, controls, or operates the organization.

OrganizationSubsidiary A person or organization that is owned, controlled, or operated by the organization.

OrganizationMember A person or organization that has joined an organization.

OrganizationAffiliate A person or organization that has some relationship or association with an organization.

OrganizationIncorporatedIndicator True if an organization is incorporated (e.g., corporation); false otherwise (e.g., proprietorship or partnership).

OrganizationPrincipalOfficial A chief or high ranking executive of an organization.

OrganizationEstablishedDate A date an organization was started.

OrganizationTerminationDate A date an organization went out of business.

OrganizationBranchName A name or number of the chapter or branch an organization is known by within a larger group of organizations.



442

443

444

445

446

447

448


OrganizationDayContact The contact information that is valid during daytime hours.

OrganizationEmergencyContact The contact information should be used to contact the person during an emergency only.

OrganizationEveningContact The contact information that is valid during evening (early night) hours.

OrganizationEmploymentHistory An employment history or an employee of an organization or company.

OrganizationNightContact The contact information that is valid during night hours.

OrganizationOccupiedStructure Indicates that the named organization occupies at least part of the structure.

OrganizationPrimaryContact The preferred contact for an individual. Use this designation only when more specific ones (e.g. home or work) are not available.

OrganizationUnspecifiedContact The contact information should be used to contact the person under unspecified circumstances.

OrganizationName A name of an organization.

J:Person

PersonName A name by which a person is known.

PersonAlternateName An alternate name used by a person. Sometimes referred to as an AKA.

Residence Details about the place in which a person lives.

ResidenceTypeText A type of place at which a person lives, e.g., house, apartment, homeless.

ResidenceDescriptionText A general description of a place in which a person lives.

ResidenceStartDate A date a person began living at a residence.

ResidenceEndDate A date a person stopped living at a residence.

ResidenceOccupancyTypeText A person's type of occupancy of a residence, e.g., owns, rents.

ResidencePaymentAmount An amount of money a person pays each payment period to live at a place of residence. This may include a mortgage payment amount or a rent amount.

ResidencePaymentPeriodText An interval or period for which a person is required to make regular residence payments.

PrimaryContactInformation Information on a preferred or primary contact mechanism.

Employment Details about the employment of a person.

PersonDescriptionText A general description of a person.

PersonBirthDate A date a person was born.

PersonBirthLocation Details about a place where a person was born.

PersonBirthPlaceCode A code identifying the state or country of a person's birth.



449

450

451

452

453

454

455


PersonDeathDate A date a person died or was declared legally dead.

PersonAgeMeasure A measurement of the age of a person.

PersonAgeMeasure.Range A measurement of the age of a person.

PersonAgeDescriptionText A description of the age of a person.

PersonLivingIndicator True if a person is alive, false if a person is dead. This may be useful if death date is not known.

PersonAssignedIDDetails A set of details about identifications issued to a person.

PersonPhysicalDetails A set of details about the physical appearance of a person.

PersonSocialDetails A set of details about the social characteristics of a person.

PersonBiometricDetails A set of details about measurable biological or behavioral characteristics, which can reliably recognize the identity, or verify the claimed identity, of a person.

PersonMedicalDetails A set of details about the medical condition of a person.

PersonAccompliceActivity An activity with which a subject has some relation or degree of involvement

PersonAccompliceWithSubject A person who is an accomplice with a subject person.

PersonDrivingIncident A driving accident in which a person is involved.

PersonAcquaintance The associate is an acquaintance of the subject.

PersonAdoptedChild A person who is an adopted child of the person.

PersonAdoptiveParent A person who is an adoptive parent of the person.

PersonAffiliationOrganization Other organization a person is affiliated with

PersonAlias A name and set of personal demographics describing the same person using alternative descriptors, e.g., an AKA.

PersonAssignmentUnit.EnforcementUnit The unit assigned to or associated with a person.

PersonAssignmentUnit.Organization The unit assigned to or associated with a person.

PersonTemporaryAssignmentUnit The organizational unit to which a person is assigned, specifically a temporary assignment.

PersonAuthorityFigure Indicates that the Subject had a trusted position of authority over associate subject (i.e. priest, teacher, boy scout leader, counselor, therapist, etc.)

PersonBabysittee The person being watched by the babysitter.

PersonBabysitter The person performing the babysitting.

PersonBiologicalChild A person who is a biological child of the person.



456

457

458

459

460

461

462


PersonBiologicalParent A person who is the biological parent of the person.

PersonCharge A sequence of charges against a person. This context generally includes an index

PersonChild A person who is a child of the person.

PersonCohabitant The associate shares a common residence with the subject

PersonCommonLawSpouse The associate is a common-law spouse of the subject.

PersonDayContact The contact information should be used during daylight hours only.

PersonDetainedLocation.Location The location or structure at which a person is or was detained.

PersonDetainedLocation.Structure The location or structure at which a person is or was detained.

PersonDomesticPartner The associate is the domestic partner of the subject.

PersonDriversLicense A driver's license.

PersonEmergencyContact The contact information should be used to contact the person during an emergency only.

PersonEveningContact The contact information should be used during evening hours (early night) only.

PersonFamilyRelation The associate and the subject are members of the same family, but the precise relationship is not clear or not noted.

PersonFosterChild The associate is a legal foster parent of the subject

PersonFosterParent The associate is a legal foster child of the subject

PersonGangAffiliation A gang a person is affiliated with

PersonGuardian A person who is a legal guardian of the person.

PersonGuardianRecipient A person who is under the legal guardianship of the person.

PersonEmploymentHistory Details about an employment record of a person.

PersonIssuedTitle.PropertyRegistration A title which has been issued to a person.

PersonIssuedTitle.PropertyTitle A title which has been issued to a person.

PersonMarriagePartner The associate is legally married to the subject.

PersonModusOperandi A methodology of action, particularly a criminal action, known to be routinely associated with a persons crimes.

PersonNeighbor The associate is a neighbor of the subject.

PersonNightContact The contact information should be used during night hours only. If there is no evening contact, this information may be used during the evening as well.



463

464

465

466

467

468

469


PersonParent The associated person is a parent of the main person. Use this context when a more specific relationship is not relevant or not important

PersonPrimaryWorker A primary social worker or other overseer assigned to a person that is not a caregiver.

PersonReferralWorker Employee of State assigned to the particular juvenile

PersonSocialFriend The associate is a friend of the subject, in a social setting. This includes relationships such as "boy friend" and "girl friend".

PersonSpouse The associate is a spouse of the subject. Used when the legal status of the relationship (marriage, common-law) is not known.

PersonStranger The associate has no known or admitted knowledge of the subject

PersonUnspecifiedContact The contact information should be used to contact the person under unspecified circumstances.

PersonWasCommonLawSpouse The associate was at one time the common-law spouse of the subject but has legally separated or divorced.

PersonWasDomesticPartner The associate was at one time the domestic partner of the subject but has dissolved the relationship.

PersonWasMarriedTo The associate was at one time married to the subject but has legally divorced.

PersonWasSpouse The associate was at one time a spouse of the subject but has divorced or otherwise legally severed the relationship. Used when the legal status of the relationship (marriage, common-law) is not known.

PersonWorkContact The contact information should be used when the person is expected to be or might be at work.

PersonWorkLocation.Location The work address or structure of a person. This association is used when the person's employer is not known. If the employer is known, use an Organization which in turn has a Location.

PersonWorkLocation.Structure The work address or structure of a person. This association is used when the person's employer is not known. If the employer is known, use an Organization which in turn has a Location.

J:PersonAssignedIDDetails

PersonSSNID A 9-digit numeric identifier assigned to a living person by the U.S. Social Security Administration. A social security number of a person. Sometimes referred to as a SSN.

PersonTaxID An identifier used to refer to a specific person within the tax system of a country. Within the U.S., this identifier may also be a persons social security number (SSN) or another identifier.

PersonDriverLicenseID Information about an identifier used to refer to a specific person who has obtained a driver's license. Sometimes referred to as driver license number, dlNumber.

DrivingJurisdictionAuthorityCode A federal or state organization, such as a department of motor vehicles (DMV), with jurisdiction over a person's driving privileges.

PersonFBIID A number issued by the FBI's Automated Fingerprint Identification System (AFIS) based on submitted fingerprints.



470

471

472

473

474

475

476


PersonStateID A number issued by a state Automated Fingerprint Identification System (AFIS) based on submitted fingerprints. Sometimes referred to as a State ID number or a SID.

PersonAFISID A number issued by a local agency (county) Automated Fingerprint Identification System (AFIS) based on submitted fingerprints.

PersonOtherID Information about an identifier with a type that is not explicitly defined in the standard that refers to a person within a certain domain, e.g., state ID cards or other non-license and non-fingerprint based IDs.

PersonIDTypeCode A code the identifies a type of identifier assigned to a person.

PersonRegisteredOffenderIndicator True if a person is required to register as an offender; false otherwise.

PersonFirearmSalesDisqualifiedIndicator True if a person is prohibited from purchasing firearms; false otherwise.

PersonLicenseID A string that identifies a license, certification, or registration of a person for some purpose; may be granted to certify professional occupation or skill, e.g., medical license, pilot license, professional engineer.

PersonGeneralLedgerID A general-ledger account number associated with a person.

PersonHumanResourcesID A human resources id or assigned number for a person, such as a badge number.

PersonVendorID Vendor number for a person

PersonNationalID A general ID that identifies a person within a country but is not based on fingerprint.

j:Submission

SubmissionSubmitter.Organization A person or organization which submits a document.

SubmissionSubmitter.Person A person or organization which submits a document.

SubmissionSubmittedDate A date a document left the control of the submitting party.

SubmissionSubmittedTime A time a document left the control of the submitting party.

SubmissionReceiver.Organization A person or organization which receives a document.

SubmissionReceiver.Person A person or organization which receives a document.

SubmissionReceivedDate A date the receiving party received the document.

SubmissionReceivedTime A time the receiving party received the document.

SubmissionDocument A document that is submitted.

SubmissionFee A fee or price required to submit a document.



477

478

479

480

481

482

483

4 References4.1 Normative

[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.



735

736737738

484

485

486

487

488

489

490

http://www.ietf.org/rfc/rfc2119.txt

Appendix A. AcknowledgmentsThe following individuals were members of the committee during the development of this specification:

Greacen, John

Brooks, Rex

Hagler, Franklin

Roth, David

Harris, Jim

Perry, Ellen

Ensign, Chet

Bergeron, Donald

Schumacher, Scott

Goodwin, David

Gibson, Robin

Gilliam, Charles

Powell, Dallas

Poindexter, Gary

Taylor, Steven

Bousquin, Terry

Aerts, John

Johnson, Jerry

Smith, Christopher

Messing, John

O'Brien, Robert

Leff, Laurence

Rutkowski, Tony

Ruegg, John

DeFilippis, Robert

Clarke, Tom

March, Robert

Keane, James

Midstokke, Brad

Barlow, Jeff

Pope, Nick

Durham, Christopher

Slosberg, Mark

O'Day, Dan

Cover, Robin

Cabral, James

Clark, Jim

Smith, T

Welsh, D



739

740

741

742

743

744

745

746

747

748

749

750

751

752

753

754

755

756

757

758

759

760

761

762

763

764

765

766

767

768

769

770

771

772

773

774

775

776

777

778

779

491

492

493

494

495

496

497

Webster, Larry

Dillon, Ann

Wagner, Winfield

Kasselman, Pieter

Karotkin, Jeff

Martin, Roger

Plummer, Catherine

Tingom, Eric

Winters, Roger

Waite, Mike

Jensen, Allen

Clark, James Bryce

Chambers, Rolly

Cusick, James

Snowdon, Kyle

McElrath, Rex

Came, Scott

Fiore, Steven

Rutter, Nancy

Harrop, Jason

Morgan, Rockie

Cameron, Ockert

Oldenburg, Mark

Baker, Richard

Carlson, Tom

Sweeney, Ann

Sawka, Dan

Edson, Scott

Naidoo, Shogan

Beard, Jim

Alpert, Jed



780

781

782

783

784

785

786

787

788

789

790

791

792

793

794

795

796

797

798

799

800

801

802

803

804

805

806

807

808

809

810

498

499

500

501

502

503

504

Appendix B. Revision History[This appendix is optional, but helpful. It should be removed for specifications that are at OASIS Standard level.]

Rev Date By Whom What

wd-01 2005-04-25 Eric Tingom Initial version

Wd-02 2005-05-17 Eric Tingom Updated Message Types

Wd-03 2005-06-05 Eric Tingom Message Profile WSDL Updated and Revised



811

812

813

505

506

507

508

509

510

511

Appendix C. NoticesOASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.

OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.

Copyright © OASIS Open 2002. All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself does not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an “AS IS” basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.



814

815816817818819820821

822823824

825

826827828829830831832

833

834835836837

512

513

514

515

516

517

518

· Web viewFor example: ordering bail, pleading of not guilty, filing an affidavit. An activity...

Documents

Transcript of · Web viewFor example: ordering bail, pleading of not guilty, filing an affidavit. An activity...