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

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/CCMS/DataFiles/Civil/SmallClaims/01/
Schema Prefix
SmallClaims
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/CCMS/DataFiles/Civil/SmallClaims/01/SmallClaims.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. SmallClaims
  1.2. DemandAmount
  1.3. DemandReason
  1.4. IncidentDate
  1.5. IncidentEndDate
  1.6. MoneyCalculation
  1.7. MoneyDemanded
  1.8. VenueReasons
  1.9. VenueReasonA
  1.10. VenueReasonB
  1.11. VenueReasonC
  1.12. VenueReasonD
  1.13. VenueReasonOther
  1.14. AttorneyClientFeeDispute
  1.15. GovernmentClaim
  1.16. FrequentFiler
  1.17. AutomobileAccidentRelated
 External
2. Simple Types
  2.1. Memo
3. Imported Schemas
  3.1. Attributes
4. Change History
  4.1. 2006-08-17
  4.2. 2006-08-17
  4.3. 2007-07-03
  4.4. 2007-07-03
  4.5. 2007-07-05
  4.6. 2007-07-05
  4.7. 2008-09-28
  4.8. 2008-10-03
  4.9. 2008-10-03
  4.10. 2008-11-13
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. SmallClaims:SmallClaims
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
DemandAmount11
DemandReason01
IncidentDate01
IncidentEndDate01
MoneyCalculation01
MoneyDemanded11
VenueReasons01
VenueReasonOther01
AttorneyClientFeeDispute01
GovernmentClaim01
FrequentFiler01
AutomobileAccidentRelated01

[1]  The SmallClaims element is the intended root element of the schema. The data collected in this schema is based on CCMS V3, Release 6 requirements as well as the California Judicial Council's Small Claims SC-100, published January 1, 2007.

1.2. SmallClaims:DemandAmount
Data Type: xsd:decimal
go to top

[2]  The DemandAmount element is a required decimal value. The value is the amount the plaintiff claims that the defendant owes the plaintiff.

1.3. SmallClaims:DemandReason
Data Type: xsd:string
go to top

[3]  The DemandReason is an optional string value. The DemandReason is the plaintiff's reasons for demanding money from the defendant.

1.4. SmallClaims:IncidentDate
Data Type: xsd:date
go to top

[4]  The IncidentDate a required element of type date. The IncidentDate is the date on which the incident occurred or the date (or estimated date) on which the incident started. If the incident occurred over a range of dates, then the IncidentDate element must be accompanied by the IncidentEndDate. If the IncidentEndDate is not present, then this signals that the incident occurred only on one day.

[5]  If the date is an estimated date, then IncidentDate should be the earliest possible date and IncidentEndDate should be the latest possible date.

1.5. SmallClaims:IncidentEndDate
Data Type: xsd:date
go to top

[6]  The IncidentEndDate is an optional element of type date. The IncidentEndDate must accompany the IncidentDate element in situations where the incident occurred on more than one day or where the dates are estimated. If the incident occurred on the same day, then the IncidentEndDate should be omitted.

1.6. SmallClaims:MoneyCalculation
Data Type: Memo
go to top

[7]  The MoneyCalculation element is an optional element of type Memo, which is a string that can be larger than 255 characters. The MoneyCalculation element provides the plaintiff's explanation of how the plaintiff calculated the DemandAmount value (the demand amount and the money calculation must not include court costs and fees for service).

1.7. SmallClaims:MoneyDemanded
Data Type: xsd:boolean
go to top
Attribute(s)typeusefixed/default
MoneyNotDemandedReasonMemooptionalNone

[8]  The MoneyDemanded element is an optional element of type boolean. If set to True, the plaintiff has asked the defendant (in person, in writing, or by phone) to pay prior to the plaintiff's suit.

[9]  If the MoneyDemanded element is set to False, then the optional attribute MoneyNotDemandedReason must include an explanation for why the plaintiff has not asked the defendant for payment.

1.8. SmallClaims:VenueReasons
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
VenueReasonA11
VenueReasonB11
VenueReasonC11
VenueReasonD11
VenueReasonOther01

[10]  The VenueReasons element is a container element for elements that describe the reason the plaintiff is filing the claim in the destination courthouse. The plaintiff is able to select one or more values. Accordingly, all five child elements are required and are of type boolean.

1.9. SmallClaims:VenueReasonA
Data Type: xsd:boolean
go to top

[11]  The VenueReasonA element maps to question 5a on the SC-100. This value should be set to True if the filer filed the complaint in the target courthouse because the courthouse covers the area (a) where the Defendant lives or does business (b) where the plaintiff's property was damaged (c) where the plaintiff was injured (d) where a contract (written or spoken) was made, signed, performed, or broken by the defendant or where the defendant made the contract.

1.10. SmallClaims:VenueReasonB
Data Type: xsd:boolean
go to top

[12]  The VenueReasonB element maps to question 5b on the SC-100. The VenueReasonB element must be set to True when the target courthouse covers the area where the buyer or lessee signed the contract, lives now, or lived when the contract was made, if the claim is about an offer or contract for personal, family, or household goods, services, or loans. See Code Civ. Proc., s 395(b).

1.11. SmallClaims:VenueReasonC
Data Type: xsd:boolean
go to top

[13]  The VenueReasonC element maps to question 5c on the SC-100. The VenueReasonC element must be set to True when the target courthouse covers the area where the buyer signed the contract, lives now, or lived when the contract was made, if this claim is about a retail installment contract (like a credit card). See Civil Code, s 1812.10.

1.12. SmallClaims:VenueReasonD
Data Type: xsd:boolean
go to top

[14]  The VenueReasonD element maps to question 5d on the SC-100. The VenueReasonD element must be set to True when the target courthouse covers the area where the buyer signed the contract, lives now, or lived when the contract was made, or where the vehicle is permanently garaged, if this claim is about a vehicle finance sale. See Civil Code, s 2984.4.

1.13. SmallClaims:VenueReasonOther
Data Type: Memo
go to top

[15]  The VenueReasonOther element maps to question 5e on the SC-100. Unlike the other VenueReason elements, the VenueReasonOther element is optional and is a type Memo, which is a long string over 255 characters. The other VenueReason elements must be present and must be set to True or False. The VenueReasonOther element is deemed to be true if present and deemed to be false if absent. If present, the element must include text that describes the other reason(s) why the plaintiff filed the claim in the target courthouse.

1.14. SmallClaims:AttorneyClientFeeDispute
Data Type: xsd:boolean
go to top
Attribute(s)typeusefixed/default
Arbitrationxsd:booleanrequiredNone

[16]  The AttorneyClientFeeDispute element is an optional element of type boolean. If set to True, the plaintiff's claim is an attorney-client dispute. If the element is absent or set to False, then the claim is not an attorney-client dispute.

[17]  The AttorneyCleintFeeDispute element includes a required Arbitration attribute. If the AttorneyClientFeeDispute element is present and set to True, then the Arbitration attribute must be set to True if arbitration has occurred or set to False if arbitration has not occurred.

[18]  If the AttorneyCleintFeeDispute element is set to False, then the required Arbitration attribute must also be set to False. If the optional AttorneyCleintFeeDispute element is absent, then the Arbitration attribute will necessarily be absent, in which case both values are deemed to be False.

1.15. SmallClaims:GovernmentClaim
Data Type: xsd:boolean
go to top
Attribute(s)typeusefixed/default
ClaimDatexsd:daterequiredNone

[19]  The GovernmentClaim element is an optional element of type boolean. If set to True, the plaintiff filing a claim against a public entity. If the element is absent or set to False, the plaintiff is not filing a claim against a public entity.

[20]  If the plaintiff is filing against a public entity, the California Small Claims SC-100 states that the filer must have filed a written claim with the public entity first. If the public entity denies the claim or does not answer within the time allowed by law, then the plaintiff may file an SC-100.

[21]  The GovernmentClaim element includes a required ClaimDate attribute of type date. If the GovernmentClaim is equal to True, then the ClaimDate must be the date on which the plaintiff filed a written claim with the public entity.

[22]  If the GovernmentClaim element is set to False, then the required ClaimDate attribute can include any value and should be ignored by the receiving application. If the GovernmentClaim element is absent (and deemed False), then the ClaimDate attribute is necessarily also absent.

1.16. SmallClaims:FrequentFiler
Data Type: xsd:boolean
go to top

[23]  The FrequentFiler element is an optional element of type boolean. If set to True, the plaintiff has filed more than 12 small claims in California within the past 12 months. If the element is absent or set to False, the plaintiff has not filed 12 small claims in the last 12 months in California.

1.17. SmallClaims:AutomobileAccidentRelated
Data Type: xsd:boolean
go to top

[24]  The AutomobileAccidentRelated element is an optional element of type boolean. If set to True, the small claims complaint is related to an automobile accident. If the element is absent or set to False, the small claims complaint is not related to an automobile accident.

2. Simple Types

2.1. Memo
Data Type: xsd:string
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. 2006-08-17
Editor: Winchel Vincent
go to top

Created

4.2. 2006-08-17
Editor: Winchel Vincent
go to top

Normalized using xmlLegal Normalizer 0.1.1.

4.3. 2007-07-03
Editor: Winchel Vincent
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.4.

4.4. 2007-07-03
Editor: Winchel Vincent
go to top

Changed Attributes 03 schema to Attributes 01 schema.

4.5. 2007-07-05
Editor: Winchel Vincent
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.4. Changed IncidentStartDate and IncidentEndDate from xsd:string to xsd:date. Added documentation. Deleted IncidentStartDate as it is redundant. Made IncidentDate required. Changed MoneyOwed to MoneyCalculation. Deleted AttorneyCleintFeeDisputeArbitration element and created an attribute Arbitration attribute on the AttorneyCleintFeeDispute to replace it. Deleted GovernmentClaimDate and included new ClaimDate attribute on GovernmentClaim element. Deleted VenueReasonE as unnecessary. Deleted MoneyDemandedReason element and replaced with ReasonMoneyNotDemanded attribute on MoneyDemanded element.

4.6. 2007-07-05
Editor: Winchel Vincent
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.4.

4.7. 2008-09-28
Editor: Winchel Vincent
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.5.

4.8. 2008-10-03
Editor: Winchel Vincent
go to top

Changed IncidentDate from required to optional.

4.9. 2008-10-03
Editor: Winchel Vincent
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.5.

4.10. 2008-11-13
Editor:
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/CCMS/DataFiles/Civil/SmallClaims/Test01/
go to top

Copied.

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