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
 
Code Schema
Last Updated: 2008-11-13
 

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/02/CodeTable/Code/01/
Schema Prefix
Code
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/02/CodeTable/Code/01/Code.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. Code
  1.2. Name
  1.3. Value
  1.4. Alias
  1.5. GenericType
  1.6. Filters
  1.7. Include
 External
  1.8. Filter
2. Simple Types
  2.1. YesNo
3. Imported Schemas
  3.1. Attributes
  3.2. Filter
4. Change History
  4.1. 2003-02-18
  4.2. 2003-02-23
  4.3. 2003-04-29
  4.4. 2003-07-01
  4.5. 2003-07-02
  4.6. 2003-07-16
  4.7. 2003-07-23
  4.8. 2003-07-27
  4.9. 2004-02-29
  4.10. 2004-04-20
  4.11. 2004-04-26
  4.12. 2004-04-29
  4.13. 2004-04-30
  4.14. 2004-08-02
  4.15. 2004-08-05
  4.16. 2004-09-14
  4.17. 2005-06-05
  4.18. 2005-06-25
  4.19. 2005-10-06
  4.20. 2008-10-01
  4.21. 2008-10-01
  4.22. 2008-11-13
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. Code:Code
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
Name11
Value01
Alias01
GenericType01
Filters01
Include01

[1]   The Code element is the intended root element of the schema. The Code element contains information about a specific code in a code table. Many courts use a string value plus a numeric or alphanumeric code value to represent one piece of information. As a result, the Code element includes both Code:Name and Code:Value elements as children elements. The Code element also includes a Code:Alias element so other values can be mapped to Code:Name values. Finally, the Code element includes a Code:GenericType element so generic type values can be mapped to more specific Code:Name values.

[2]  The following table illustrates a simple code table and four code values. Assume the code table below has a CodeTable:Name value equal to Document Type.

NameValueAliasGeneric Type
MOTION FOR SUMMARY JUDGMENT0001Motion: Summary JudgmentMotion
MOTION FOR A NEW TRIAL0002Motion: New TrialMotion
MOTION FOR A DIRECTED VERDICT0003Motion: Directed VerdictMotion
MOTION FOR FEE WAIVER0004Motion: Fee WaiverFee Waiver

[3]  Notice in the example above that code 0004 has a generic type equal to Fee Waiver, which is different than the generic types for the other motions. This is an illustration of how a generic type can be used to trigger special processing. See the Document:GenericType element in Filing XML for more information.

[4]  See also the CodeTable schema.

1.2. Code:Name
Data Type: xsd:string
go to top

[5]  Code:Name is a human-readable name associated with the code value taken from a case management system code table. There must be a one-to-one relationship between the values in Code:Name and Code:Value.

1.3. Code:Value
Data Type: xsd:string
go to top

[6]  Code:Value is a numeric or alphanumeric code value taken from a case management system code table. There must be a one-to-one relationship between the values in Code:Name and Code:Value.

1.4. Code:Alias
Data Type: xsd:string
go to top

[7]  Code:Alias is an alias for a Code:Name value. The Code:Alias can be used to (a) provide a more user friendly code name or (b) to map a Code:Name value or Code:Value value to a standard set of codes harmonized and used in one jurisdiction for many courts. For example, Court A might use Motion: Summary Judgment as a Code:Name value, while Court B might use Motion for Summary Judgment as a Code:Name value. If the State standardizes on the string Motion: Summary Judgment, Court B can use the Code:Alias element to map its Code:Name value to the State's standard code name. If values for both Code:Name and Code:Alias are present, then applications should present users with Code:Alias rather than Code:Name.

1.5. Code:GenericType
Data Type: xsd:string
go to top

[8]  Code:GenericType is a generic value for one or more values expressed in Code:Name elements. The Code:GenericType element can be used to map general values to more specific values. For example, a court might have the following document types: (a) Motion for Summary Judgment, (b) Motion for a New Hearing, and (c) Motion for Attorney Fees and Costs. Each of these values would be listed in a Code:Name element. The corresponding Code:GenericType for each of the values above might be Motion. This allows applications to develop rules and workflow for a Motion, instead of having to consider each individual document type.

1.6. Code:Filters
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
Filter1unbounded

[9]  Code:Filters is a container element for the Code:Filter element. See Code:Filter element for more information.

1.7. Code:Include
Data Type: YesNo
go to top

[10]  Code:Include provides a simple filter mechanism. The Code:Include element provides a Yes or No value for each Code:Value, Code:Name, and Code:Alias combination. This allows either a court or a service provider to decide whether to include or not include a code for use in an application.

[11]  The Code:Include element functions based on the assumption that the following is allowed (a) a court publishes Policy XML in a Policy Repository with code values in it, and (b) an application is allowed to download the Policy XML locally, alter the policy, and create one or more derivative policies for its own internal uses. This means that while there is always one officially published Policy XML file maintained by the court or by a policy authority, local court policies can be manipulated for specific applications.

[12]  For example, assume a Policy XML has 100 Filer Types in it. However, the Policy XML, in a particular installation, only requires one of the Filer Types (for example, the value Sheriff/Law Enforcement). In this situation, the sheriff, a filer, does not need to see all of the possible Filer Types. The sheriff only needs the Sheriff/Law Enforcement Filer Type. In this situation, in the local Policy XML used by the sheriff, the Code:Include value for Sheriff/Law Enforcement could be set to Yes and all other values could be set to No. The application would be required, in this case, to show only the code values matching Code:Include elements with Yes values. This provides a simple means of filtering values and also ensures that the filer will not select the wrong value.

1.8. Code:Filter
Data Type: Filter:Filter
go to top

[13]  The selection of values in one code may create dependencies that limit the logical use of values in another table. Although representing such dependencies could be done with a longer court key, it would make the court key very long. Further, the court key would no longer represent a physical/logical division of the court, but rather a case type (or something else) of a division within a court. This is undesirable. CodeTable:Filter, therefore, is used to filter tables based on values in other tables.

[14]  Based on the assumptions that code dependencies (a) are complex, varied, and specific to an implementation and (b) do not always occur, the Policy XML filter mechanism uses simple, generic Code:Filter elements. Each code table or code may have one or more Code:Filter elements. Each Code:Filter element includes a Code:FilterName element and Code:FilterValue element. Either the court or a service provider may create its own filters by manipulating a local Policy XML file. The name/value pair may be any name and value. See CodeTable:Filter for an example.

2. Simple Types

2.1. 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. Filter
go to top
Namespace
  http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Filter/03/
  

4. Change History

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

Added structured copyright and update history.

4.2. 2003-02-23
Editor: Winchel Vincent
go to top

Changed documentation annotations from complexTypes to elements so they would show up in XML Spy.

4.3. 2003-04-29
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/Policy/01/CodeTable/Code/01/
go to top

4.4. 2003-07-01
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/Policy/Test01/CodeTable/Code/01/
go to top

Copied. Added Filters and Filter elements.

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

Normalized using xmlLegal Normalizer 0.0.9.

4.6. 2003-07-16
Editor: Winchel Vincent
go to top

Corrected incorrect schemaLocation paths.

4.7. 2003-07-23
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/Test01/CodeTable/Code/01/
go to top

Copied

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

Normalized using xmlLegal Normalizer 0.0.9.

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

Updated documentation. Added reference to CodeTable:Filter element for an example of how to use filters.

4.10. 2004-04-20
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/Test02/CodeTable/Code/01/
go to top

Copied.

4.11. 2004-04-26
Editor: Winchel Vincent
go to top

Deleted blank value from YesNo simpleType enumeration.

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

Made Code:Value optional. Added Code:GenericType and documentation.

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

Normalized using xmlLegal Normalizer 0.1.0.

4.14. 2004-08-02
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/Test03/CodeTable/Code/01/
go to top

Copied.

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

Normalized using xmlLegal Normalizer 0.1.0.

4.16. 2004-09-14
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/Test04/CodeTable/Code/01/
go to top

Copied.

4.17. 2005-06-05
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/01/CodeTable/Code/01/
go to top

Copied.

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

Changed Attributes to 03 version.

4.19. 2005-10-06
Editor: Winchel Vincent
go to top

Edited documentation for formatting and clarity. No substantive changes were made.

4.20. 2008-10-01
Editor: Schema Generator
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/Test05/CodeTable/Code/01/
go to top

Copied.

4.21. 2008-10-01
Editor: Schema Generator
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.5.

4.22. 2008-11-13
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Policy/Test06/CodeTable/Code/01/
go to top

Copied. Replaced Filter elements with Filter schema. Made Code:Include element optional.

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