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
 
Role Schema
Last Updated: 2005-06-13
 

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Role/03/
Schema Prefix
Role
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Role/03/Role.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. Role
  1.2. Name
  1.3. GenericName
  1.4. Qualifier
  1.5. Associations
  1.6. Association
  1.7. Reference
 External
2. Simple Types
  There are no Simple Types.
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-30
  4.12. 2004-05-10
  4.13. 2004-08-04
  4.14. 2004-08-05
  4.15. 2004-08-05
  4.16. 2005-06-13
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. Role:Role
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
Name11
GenericName01
Qualifier11
Associations01

[1]  Role is the intended root element of the schema. Role contains information that describes the role a person, organization, or thing has in a case as well as information that associates the person, organization, or thing with other people, organizations, and things.

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

[2]  Role:Name is a role name specified in one or more tables in a court's CMS. CMSs often have multiple tables with role names, such as party types, official types, filer types. These tables should be specified in a court's Court Policy XML. Business rules will vary in different courts as to what code tables are suitable as roles.

1.3. Role:GenericName
Data Type: xsd:string
go to top

[3]  Role:GenericName is used to associate 'standard' role values for application use. Certain roles require the invocation of specific business rules or workflow. Role:GenericName values provide a means for different applications to communicate using a common vocabulary. These tables should be specified in a court's Court Policy XML.

1.4. Role:Qualifier
Data Type: xsd:ID
go to top

[4]  Role:Qualifier is used to qualify and uniquely identify a Role:Name or Role:GenericName within a filing. For example, there may be multiple plaintiffs in a filing. In a filing where there are two plaintiffs that are people, both people would have the same Role:Name (e.g., Plaintiff), but the first person would have a Role:Qualifier with a value of Plaintiff1 and the second person would have an Role:Qualifier with a value of Plaintiff2.

[5]  The Role:Qualifier is defined as an xsd:ID data type. This means that the value in Role:Qualifier must be unique within the Filing XML. When the XML parser validates the instance document, if there are duplicate values in any Role:Qualifier elements, then the instance document will not validate.

[6]  By definition, a value of type xsd:ID must begin with a character from the alphabet. The character cannot be numeric, for instance. Although the xsd:ID data type will enforce uniqueness within the instance document, it will not enforce a format for the value. Application should use the same string as the string used in Role:GenericName (or Role:Name if Role:GenericName is not present) with a number appended to it sequentially in document order. For example, in a filing that has two plaintiffs and two defendants, the values for the Role:Qualifier elements should be Plaintiff1, Plaintiff2, Defendant1, and Defendant2.

1.5. Role:Associations
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
Association1unbounded

[7]  Role:Associations is a container element for zero or more Role:Association elements.

1.6. Role:Association
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
Name11
GenericName01
Reference11

[8]  Role:Association includes the same elements as Role that can be used to associate a different person or organization in the same filing to the specified person.

1.7. Role:Reference
Data Type: xsd:IDREF
go to top

[9]  Role:Reference is used to associate a the role of a person, organization, or thing with with role of another person, organization, or thing by referencing the value in the target's Role:Qualifier element. Role:Reference is defined as an xsd:IDREF data type. This means that the value in Role:Reference must be a value that occurs in a Role:Qualifier element (or other element of type xsd:ID).

2. Simple Types

There are no Simple Types.

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/PersonRole/01/
go to top

Copied.

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

Copied. Removed mixed content from PersonRole. Made GenericName, Qualifier, and Associations optional to be consistent with OrganizationRole.

4.4. 2003-06-14
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/Filing/Tests/Filing/Test01/PersonRole/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/PersonRole/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/PersonRole/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. 2003-07-27
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/Test02/PersonRole/01/
go to top

Copied.

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

Made minor typographical changes.

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

Changed OrganizationRole:SpecificName to OrganizationRole:GenericName. Eliminated GenericNames simpleType. Made PersonRole:Qualifier required.

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

Made minor typographical changes.

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

Copied. Changed PersonRole:GenericName under Associations element from required to optional.

4.14. 2004-08-05
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/PersonRole/02/
go to top

Copied. Created Role generically to be used with Person, Organization, and Thing.

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

Normalized using xmlLegal Normalizer 0.1.0.

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

Copied. Changed Attributes schema to 03 version.

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