Second Generation Electronic Filing Specifications
 

Staff and Consultants
Winchel "Todd" Vincent III, Author
WTVIII, Inc. and <xmlLegal>
Todd.Vincent@xmllegal.org
Christopher Smith,
Senior Business Systems Analyst
California Administrative Office of the Courts
christopher.smith@jud.ca.gov
 
CourtDetails Schema
Last Updated: 2008-09-30
 

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/CourtDetails/03/
Schema Prefix
CourtDetails
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/CourtDetails/03/CourtDetails.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. CourtDetails
  1.2. OrganizationKey
  1.3. CourtKey
  1.4. Country
  1.5. State
  1.6. County
  1.7. CourtType
  1.8. Division
  1.9. Subdivision
  1.10. Group
  1.11. Location
  1.12. Department
  1.13. CourtCode
  1.14. Include
 External
  1.15. Court
2. Simple Types
  2.1. TwoCharacters
  2.2. YesNo
3. Imported Schemas
  3.1. Attributes
  3.2. Organization
4. Change History
  4.1. 2003-02-18
  4.2. 2003-03-01
  4.3. 2003-06-14
  4.4. 2003-06-14
  4.5. 2003-06-14
  4.6. 2003-06-15
  4.7. 2003-07-02
  4.8. 2003-07-23
  4.9. 2003-07-27
  4.10. 2003-07-27
  4.11. 2004-02-29
  4.12. 2004-04-29
  4.13. 2004-04-30
  4.14. 2004-05-10
  4.15. 2004-08-04
  4.16. 2004-08-05
  4.17. 2005-06-13
  4.18. 2005-10-25
  4.19. 2008-09-30
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. CourtDetails:CourtDetails
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
OrganizationKey11
CourtKey11
Court11
Country11
State11
County11
CourtType11
Division01
Subdivision01
Group01
Location01
Department01
CourtCode01
Include01

[1]  CourtDetails is the intended root element of the schema.

1.2. CourtDetails:OrganizationKey
Data Type: xsd:string
go to top

[2]  CourtDetails:OrganizationKey is a unique identifier for a court. It is different than CourtDetails:CourtKey, which is a unique identifier for a division of a court. If a court has only one division, then the CourtDetails:OrganizationKey value and the CourtDetails:CourtKey value should be the same. For example, if a Juvenile Court had only one division, called Juvenile, then the CourtDetails:OrganizationKey value and the CourtDetails:CourtKey value would both be, as an example, USGADouglasJuvenile. In a court with multiple divisions, the CourtDetails:OrganizationKey value might be USCASacramentoSuperior for all divisions, with other divisions having CourtDetails:CourtKey values such as USCASacramentoSuperiorCivil, USCASacramentoSuperiorCriminal, or USCASacramentoSuperiorSmallClaims.

1.3. CourtDetails:CourtKey
Data Type: xsd:string
go to top

[3]  CourtDetails:CourtKey is a unique identifier for a court, a division of a court, or other subdivision of a court. Each division of a court should have a CourtDetails:CourtKey. A list of court keys for each court should be in the court's Policy XML, if it exists.

1.4. CourtDetails:Country
Data Type: TwoCharacters
go to top

[4]  CourtDetails:Country is the two letter ISO country code in which the court has jurisdiction.

1.5. CourtDetails:State
Data Type: TwoCharacters
go to top

[5]  CourtDetails:State is the two letter state code in which the court has jurisdiction. Courts in countries that use something other than two letter state codes should change this element accordingly.

1.6. CourtDetails:County
Data Type: xsd:string
go to top

[6]  CourtDetails:County is the county in which the court has jurisdiction.

1.7. CourtDetails:CourtType
Data Type: xsd:string
go to top

[7]  CourtDetails:CourtType is the type of court, such as Superior, Juvenile, Magistrate, or Probate.

1.8. CourtDetails:Division
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
Codexsd:stringoptionalNone
Numberxsd:stringoptionalNone

[8]  CourtDetails:Division is the division of the court into which a document is being filed.

[9]  The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.

1.9. CourtDetails:Subdivision
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
Codexsd:stringoptionalNone
Numberxsd:stringoptionalNone

[10]  CourtDetails:Subdivision is the subdivision of the court, if it exists, into which a document is being filed.

[11]  The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.

1.10. CourtDetails:Group
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
Codexsd:stringoptionalNone
Numberxsd:stringoptionalNone

[12]  CourtDetails:Group is the group of judges (sitting en banc or in a panel within a court division) within a court, if it exists, into which a document is being filed.

[13]  The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.

1.11. CourtDetails:Location
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
Codexsd:stringoptionalNone
Numberxsd:stringoptionalNone

[14]  CourtDetails:Location is a human-readable descriptive location of the court.

[15]  The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.

1.12. CourtDetails:Department
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
Codexsd:stringoptionalNone
Numberxsd:stringoptionalNone

[16]  CourtDetails:Department is the department of the court, if it exists, into which a document is being filed.

[17]  The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.

1.13. CourtDetails:CourtCode
Data Type: xsd:string
go to top

[18]  CourtDetails:CourtCode is used for backwards compatibility with Court Filing 1.0 EFMs that use the Qualifier attribute on the Location element. Use of this element is discouraged.

1.14. CourtDetails:Include
Data Type: YesNo
go to top

[19]  CourtDetails:Include is a flag that courts can use to tell applications whether the information on the court is public or not. This flag allows a court to communicate to service providers information needed to submit a filing while limiting some of the information from being published to the public.

1.15. CourtDetails:Court
Data Type: Organization:Organization
go to top

[20]  CourtDetails:Court is the name, address, phone numbers, and other contact information associated with a court. Some of the information in CourtDetails:Court is redundant with the other elements defined in this schema. For example, there is CourtDetails:County and Address:County. The elements declared here are to make it easier to group and organize the information. Sending applications should populate elements in this schema as a first priority and receiving applications should rely on elements in this schema.

2. Simple Types

2.1. TwoCharacters
Data Type: xsd:string
maxLength: 2
minLength: 2
go to top
2.2. YesNo
Data Type: xsd:string
go to top
Enumeration(s)

Value
Yes
No

3. Imported Schemas

3.1. Attributes
go to top
Namespace
  http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Attributes/03/
  
3.2. Organization
go to top
Namespace
  http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Organization/03/
  

4. Change History

4.1. 2003-02-18
Editor: Winchel Vincent
go to top

Added Structured Copyright and Update History.

4.2. 2003-03-01
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/Filing/02/CourtDetails/01/
go to top

Added Country, State, and County elements for determining the court's jurisdiction. Added Location element to provide human readable location of court. Changed Division, Subdivision and Group to optional elements.

4.3. 2003-06-14
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/Filing/Test01/CourtDetails/01/
go to top

Copied.

4.4. 2003-06-14
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/Filing/Tests/Filing/Test01/CourtDetails/01/
go to top

Copied.

4.5. 2003-06-14
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/Filing/Tests/Filing/Test02/CourtDetails/01/
go to top

Copied.

4.6. 2003-06-15
Editor: Winchel Vincent
go to top

Normalized using xmlLegal Normalizer 0.0.9.

4.7. 2003-07-02
Editor: Winchel Vincent
go to top

Changed CourtCode to be optional. Added CourtType.

4.8. 2003-07-23
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/Test01/CourtDetails/01/
go to top

Copied.

4.9. 2003-07-27
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/Test02/CourtDetails/01/
go to top

Copied.

4.10. 2003-07-27
Editor: Winchel Vincent
go to top

Normalized using xmlLegal Normalizer 0.0.9. Changed Person and Organization namespaces.

4.11. 2004-02-29
Editor: Winchel Vincent
go to top

Made minor typographical changes.

4.12. 2004-04-29
Editor: Winchel Vincent
go to top

Added CourtDetails:Include element because CourtKey schema has been replaced and this element was used in CourtKey.

4.13. 2004-04-30
Editor: Winchel Vincent
go to top

Normalized using xmlLegal Normalizer 0.1.0.

4.14. 2004-05-10
Editor: Winchel Vincent
go to top

Made minor changes to documentation. Added example for CourtDetails:OrganizationKey and CourtDetails:CourtKey. Made minor edit to CourtDetails:CourtKey definition.

4.15. 2004-08-04
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/CourtDetails/01/
go to top

Copied. No changes made except the namespace versions.

4.16. 2004-08-05
Editor: Winchel Vincent
go to top

Normalized using xmlLegal Normalizer 0.1.0.

4.17. 2005-06-13
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/CourtDetails/02/
go to top

Copied. Changed Attributes schema and Organization schema to 03 version.

4.18. 2005-10-25
Editor: Winchel Vincent
go to top

Minor edits to documentation.

4.19. 2008-09-30
Editor: Winchel Vincent
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.5. Added CourtDetails:Department element. Added new attributes Code and Number to CourtDetails:Division, CourtDetails:Subdivision, CourtDetails:Group, CourtDetails:Location, and CourtDetails:Department.

5. Legal Notices

Unless otherwise agreed, All Rights Reserved except those granted by xmlLegal General Public License at:

LICENSED WORKS ARE PROVIDED "AS IS," AND HOLDERS OF INTELLECTUAL PROPERTY RIGHTS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE LICENSED WORKS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

HOLDERS OF INTELLECTUAL PROPERTY WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE LICENSED WORKS.

Contact Winchel "Todd" Vincent III (Todd.Vincent@xmllegal.org) or xmlLegal Help (help@xmllegal.org) for more information.

6. Authors and Contributors


Staff and Consultants
Winchel "Todd" Vincent, III, Author
WTVIII, Inc. and <xmlLegal>
Todd.Vincent@xmllegal.org
Kevin Stannard, Original Editor
Swiftnet Solutions, Ltd.
kevin.stannard@swiftnet-solutions.com
Charlene Hammitt, Project Director
California Administrative Office of the Courts
charlene.hammitt@jud.ca.gov
Christopher Smith, Senior Business Systems Analyst
California Administrative Office of the Courts
christopher.smith@jud.ca.gov
Tom Smith, Consultant
AVI/IT Decision
tjsmith@itdecision.com
Courts
Contra Costa Superior Court (http://cc-courts.org/)
Kathy Ridgeway, KRIDG@sc.co.contra-costa.ca.us
Karen Ortega, KORTE@sc.co.contra-costa.ca.us
Orange Superior Court (http://www.occourts.org/)
Allen Jensen, ajensen@occourts.org
SacramentoSuperior Court (http://www.saccourt.com/)
Doug Kauffroath, KauffrD@saccourt.com
Ryan Hurlock, HurlocR@saccourt.com
Judith Kerrin, KerrinJ@saccourt.com
Marcia Barclay, BarclaM@saccourt.com
Huldeni "Zito" Souza, SouzaH@saccourt.com
Michael Alexander, AlexanM@saccourt.com
Gary Nishi, NishiG@saccourt.com
San Mateo Superior Court (http://www.sanmateocourt.org/)
Tim Benton, tbenton@co.sanmateo.ca.us
Rick Walery, rwalery@sanmateocourt.org
Bill Harven, wharven@sanmateocourt.org
Carrie Warren, cwarren@sanmateocourt.org
Santa Clara Superior Court (http://www.sccsuperiorcourt.org/)
Barry Lynch, blynch@scscourt.org
Deborah Barker, dbarker@scscourt.org
Francine Collier, fcollier@scscourt.org
 
Contributors
counterclaim, inc. (http://www.counterclaim.com)
Shogan Naidoo, shogan@counterclaim.com
Michelle Naidoo, mnaidoo@counterclaim.com
Jim Beard, beard@counterclaim.com
Jason Van Cleve, jason@vancleve.com
Deloitte Consulting (http://www.deloitte.com/)
Bruce Scheffle, bscheffel@deloitte.com
E-Filing.com (http://www.e-filing.com)
Mohammed Shaikh, mohammed@e-filing.com
Amrit Singh Nandrey, amrit@imagexx.com
Prabhath Pallati, prabhath@imagexx.com
Essential Publishers (http://www.essentialpublishers.com)
Martin Dean, dean@epubs.org
George Rothbart, george@softsci.com
Glotrans (http://www.glotrans.com)
Andy Jamieson, ajam@glotrans.com
Conor Dixon, conordixon@comcast.net
Intresys (http://www.intresys.com)
Yegor Borovikov, yegorb@intresys.com
Tania Wasser, taniaw@intresys.com
ISD Corporation (http://www.essentialpublishers.com)
Rob Beach, Ron.Beach@isd-corp.com
Holly Ramirez, Holly.Ramirez@isd-corp.com
John Coughlin, john.coughlin@isd-corp.com
Bob Gehringer, bob.gehringer@isd-corp.com
Robert Entrican, robert@entrican.com
Lexis-Nexis (http://www.lexisnexis.com)
Jonathan Gill, jonathan.gill@lexisnexis.com
Shane Durham, shane.durham@lexisnexis.com
One Legal, Inc. (http://www.onelegal.com)
Robert DeFilippis, rtd@onelegal.com
Matt Marshall, matt@mattmarshall.com
Bryan Barringer, bbarringer@onelegal.com
Bill Porterfield, billp@servicehub.com
Patrick Zanone, patrick.zanone@macroburst.com
U.S. Court Forms/American LegalNet (http://www.uscourtforms.com)
Erez Bustan, erez@uscourtforms.com
Kin Lee, kin@uscourtforms.com
Harry Thakkar, Hthakkar@uscourtforms.com