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
 
Key Schema
Last Updated: 2005-10-25
 

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Key/03/
Schema Prefix
Key
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Key/03/Key.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. Key
  1.2. CourtKey
  1.3. Year
  1.4. Month
  1.5. Day
  1.6. Hour
  1.7. Minute
  1.8. Second
  1.9. OrganizationKey
  1.10. Application
  1.11. Version
  1.12. Suffix
 External
2. Simple Types
  2.1. TwoCharacters
  2.2. FourCharacters
3. Imported Schemas
  3.1. Attributes
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-16
  4.7. 2003-07-23
  4.8. 2003-07-27
  4.9. 2003-07-27
  4.10. 2004-02-29
  4.11. 2004-04-27
  4.12. 2004-04-30
  4.13. 2004-05-10
  4.14. 2004-08-05
  4.15. 2005-06-13
  4.16. 2005-10-25
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. Key:Key
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
CourtKey11
Year11
Month11
Day11
Hour11
Minute11
Second11
OrganizationKey11
Application11
Version11
Suffix11

[1]  Key is the intended root element of the schema. Key contains elements necessary to create a unique identifier that is meaningful within a specific jurisdiction, date, and time.

1.2. Key:CourtKey
Data Type: xsd:string
go to top

[2]  Key:CourtKey is a unique identifier for a court. If the Key schema is used in a situation where a court does not exist, then the organization key of the organization responsible for creating the XML should be used.

1.3. Key:Year
Data Type: FourCharacters
go to top

[3]  Key:Year is the four character year at time the key is created.

1.4. Key:Month
Data Type: TwoCharacters
go to top

[4]  Key:Month is the two character month at time the key is created.

1.5. Key:Day
Data Type: TwoCharacters
go to top

[5]  Key:Day is the two character day at time the key is created.

1.6. Key:Hour
Data Type: TwoCharacters
go to top

[6]  Key:Hour is the two character hour at time the key is created.

1.7. Key:Minute
Data Type: TwoCharacters
go to top

[7]  Key:Minute is the two character minute at time the key is created.

1.8. Key:Second
Data Type: TwoCharacters
go to top

[8]  Key:Second is the two character second at time the key is created.

1.9. Key:OrganizationKey
Data Type: xsd:string
go to top

[9]  Key:OrganizationKey is a unique identifier for the organization that is responsible for creating the XML. The unique identifier should be assigned by a policy authority in the jurisdiction in which the XML is being used. If no such policy authority exists to assign the identifier, then the organization should use its organization name, if its name is unique, or a domain name owned by the organization . For example, Key:OrganizationKey might be FileDocs, Inc. Used in combination with Key:Application and Key:Version, the Key element would identify the organization, application, and version that is responsible for the XML. For example, FileDocs, Inc. E-Filing Manager 0.0.3.

1.10. Key:Application
Data Type: xsd:string
go to top

[10]  Key:Application is a unique name or identifier for the application that is responsible for creating the the XML. For example, the application might be named E-Filing Manager. Used in combination with Key:OrganizationKey and Key:Version, the Key element would identify the organization, application, and version that is responsible for the XML. For example, FileDocs, Inc. E-Filing Manager 0.0.3.

1.11. Key:Version
Data Type: xsd:string
go to top

[11]  Key:Version is the version number of the application that is responsible for creating the XML. For example, the version might be 0.0.3. Used in combination with Key:OrganizationKey and Key:Application, the Key element would identify the organization, application, and version that is responsible for the XML. For example, FileDocs, Inc. E-Filing Manager 0.0.3.

1.12. Key:Suffix
Data Type: xsd:string
go to top

[12]  Key:Suffix is the variable-length character assigned randomly or as the sender sees fit. The purpose of the Key:Suffix is to ensure that two keys created at the same time are likely to be unique.

2. Simple Types

2.1. TwoCharacters
Data Type: xsd:string
maxLength: 2
minLength: 2
go to top
2.2. FourCharacters
Data Type: xsd:string
maxLength: 4
minLength: 4
go to top

3. Imported Schemas

3.1. Attributes
go to top
Namespace
  http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Attributes/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/Key/01/
go to top

Changed Suffix to be any string length.

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

Copied. Removed mixed content from Key element.

4.4. 2003-06-14
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/Filing/Tests/Filing/Test01/Key/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/Key/01/
go to top

Copied.

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

Normalized using xmlLegal Normalizer 0.0.9.

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

Copied.

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

Copied.

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

Normalized using xmlLegal Normalizer 0.0.9.

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

Made minor typographical changes.

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

Copied. Added Key:OrganizationKey, Key:CourtKey, Key:Application, and Key:Version with accompanying documentation. Deleted Key:Country, Key:State, Key:County, Key:Court.

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

Normalized using xmlLegal Normalizer 0.1.0.

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

Changed documentation to state that dates and times are to be created when the Key is created, rather than at transmission time because the Key is used in situations where the XML is not transmitted. Made minor typographical changes.

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

Normalized using xmlLegal Normalizer 0.1.0.

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

Copied. Changed Attributes schema to 03 version.

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

Minor edits to documentation.

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