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
 
Fee Schema
Last Updated: 2008-10-01
 

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Fee/03/
Schema Prefix
Fee
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Fee/03/Fee.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. Fee
  1.2. CourtKeys
  1.3. CourtKey
  1.4. Name
  1.5. Value
  1.6. Alias
  1.7. Category
  1.8. Subcategory
  1.9. Currency
  1.10. Cost
  1.11. SubsequentPages
  1.12. EffectiveDate
  1.13. ExpirationDate
  1.14. LastUpdated
  1.15. Note
  1.16. FirstPaper
  1.17. CaseTypes
  1.18. CaseType
  1.19. AmountInControversy
  1.20. JurisdictionalAmount
  1.21. DocumentTypes
  1.22. DocumentType
  1.23. DocumentGenericTypes
  1.24. DocumentGenericType
  1.25. DocumentKey
  1.26. Filters
  1.27. Include
 External
  1.28. Filter
2. Simple Types
  2.1. AmountThresholds
  2.2. YesNo
  2.3. JurisdictionalAmounts
  2.4. ValueTypes
3. Imported Schemas
  3.1. Attributes
  3.2. Filter
4. Change History
  4.1. 2003-02-03
  4.2. 2003-02-18
  4.3. 2003-03-01
  4.4. 2003-05-10
  4.5. 2003-05-10
  4.6. 2003-06-16
  4.7. 2003-07-02
  4.8. 2003-07-27
  4.9. 2004-02-29
  4.10. 2004-04-29
  4.11. 2004-04-31
  4.12. 2004-05-10
  4.13. 2004-08-04
  4.14. 2004-08-05
  4.15. 2005-06-13
  4.16. 2008-10-01
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. Fee:Fee
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
CourtKeys11
Name11
Value11
Alias01
Category01
Subcategory01
Currency01
Cost11
SubsequentPages01
EffectiveDate01
ExpirationDate01
LastUpdated01
Note01
FirstPaper01
CaseTypes01
AmountInControversy01
JurisdictionalAmount01
DocumentTypes01
DocumentGenericTypes01
DocumentKey01
Filters01
Include01

Attribute(s)typeusefixed/default
TotalPagesxsd:integeroptionalNone

[1]  Fee is an amount of money that a court charges for filing a document or performing a document-related service. For example, a court may charge a fee for filing a complaint. A different fee may be charged for filing a complaint with service of process.

[2]  Fee has a TotalPages attribute. This optional attribute provides the total pages of the document to which a fee applies in a situations where (a) the fee for the first page is different than the fee for subsequent pages or (b) where the fee depends on the total number of pages. If there is no difference in fees with respect to the first and subsequent pages or the total number of pages, then the TotalPages attribute should not be included.

1.2. Fee:CourtKeys
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
CourtKey1unbounded

[3]  Fee:CourtKeys is a container element for one or more Fee:CourtKey elements. Multiple Fee:CourtKey elements can be associated with one fee.

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

[4]  Fee:CourtKey is a unique identifier for a court, a division of a court, or other subdivision of a court. The Fee:CourtKeyis used to associate a fee with a court subdivision.

1.4. Fee:Name
Data Type: xsd:string
go to top

[5]  Fee:Name is a human-readable name for the entire fee. There is no defined format for Fee:Name value, although this value should match the exact string value given by the court. If the court publishes a court policy, the fee name and other information should be in the policy.

1.5. Fee:Value
Data Type: xsd:string
go to top

[6]  Fee:Value is a code value that represents the fee.

1.6. Fee:Alias
Data Type: xsd:string
go to top

[7]  Fee:Alias is a human-readable name for the fee. There is no specific format for Fee:Alias value. This value can be a value used by applications to display other, similar (perhaps more common) fee names and map the common fee name to the court's fee name in Fee:FullName.

1.7. Fee:Category
Data Type: xsd:string
go to top

[8]  Fee:Category is an optional element used to categorize fees.

1.8. Fee:Subcategory
Data Type: xsd:string
go to top

[9]  Fee:Subcategory is an optional element used to subcategorize fees.

1.9. Fee:Currency
Data Type: xsd:string
go to top

[10]  Fee:Currency is an optional value used to distinguish the type of currency used. If absent, applications should assume that the currency used in the jurisdiction is the intended currency.

1.10. Fee:Cost
Data Type: xsd:decimal
go to top

[11]  Fee:Cost is the amount charged for filing the document. Some courts charge different fees for the first page of a filing and for subsequent pages. In California, filing fees are not different for the first page and subsequent pages; however, copying or other fees may be different for the first page and subsequent pages. As a result, this Fee Schema includes elements for the amount of the first page and the amount of the second and subsequent pages. If the fee is not based on the number of pages, then this is the total fee for the filing.

1.11. Fee:SubsequentPages
Data Type: xsd:decimal
go to top

[12]  Fee:SubsequentPages is the amount charged for all subsequent pages of a document. In California, filing fees are not different for the first page and subsequent pages; however, copying or other fees may be different for the first page and subsequent pages.

1.12. Fee:EffectiveDate
Data Type: xsd:date
go to top

[13]  Fee:EffectiveDate is the date on which the fee came into effect or will come into effect by statute or order.

1.13. Fee:ExpirationDate
Data Type: xsd:date
go to top

[14]  Fee:ExpirationDate is a future date on which the fee is set to expire.

1.14. Fee:LastUpdated
Data Type: xsd:string
go to top

[15]  Fee:LastUpdated is the date on which the fee information was last updated.

1.15. Fee:Note
Data Type: xsd:string
go to top

[16]  Fee:Note is additional information about the fee.

1.16. Fee:FirstPaper
Data Type: YesNo
go to top

[17]  Fee:FirstPaper is a characteristic of a filing used to calculate fees in California. The value can be either Yes or No. If Fee:FirstPaper is true, then this means the filer is submitting its first document to the court. In this situation, filing fees are more than if the filer had already filed a document.

1.17. Fee:CaseTypes
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
CaseType1unbounded

[18]  The Fee:CaseTypes element is a container element for one or more Fee:CaseType elements.

1.18. Fee:CaseType
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
ValueTypeValueTypesrequiredNone

[19]  The Fee:CaseType element provides the ability to associate a case type with a fee.

1.19. Fee:AmountInControversy
Data Type: xsd:decimal
go to top
Attribute(s)typeusefixed/default
AmountThresholdAmountThresholdsrequiredNone

[20]  The Fee:AmountInControversy element provides the ability to associate a an amount in controversy with a fee. See Filing:AmountInControversy

1.20. Fee:JurisdictionalAmount
Data Type: JurisdictionalAmounts
go to top

[21]  The Fee:JurisdictionalAmount element provides the ability to associate a jurisdictional amount with a fee. See Filing:JurisdictionalAmount

1.21. Fee:DocumentTypes
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
DocumentType1unbounded

[22]  Fee:DocumentTypes is a container element for one or more Fee:DocumentType elements. Multiple Fee:DocumentType elements can be associated with one fee.

1.22. Fee:DocumentType
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
ValueTypeValueTypesrequiredNone

[23]  Fee:DocumentType is a document type that is associated with a fee. Fee:DocumentType can be used in both Filing XML and Court Policy XML to associate fees and document types.

[24]  In Filing XML, for each document within a filing that results in a filing fee (disregarding the same document transmitted in the filing in multiple electronic formats), the value in Fee:DocumentType can be matched with the value in Document:Type to associate the document and the fee. For example, if the value in Document:Type were Motion for Summary Judgment then the Fee:DocumentType value would also be Motion for Summary Judgment.

[25]  In Policy XML, each fee listed in the Court Policy can be associated with one more more document types by listing the document types in Fee:DocumentTypes. This provides a means of helping the filer determine which fee is associated with certain document types, so that the proper fee will be submitted in the filing. Further, if the information is listed correctly in the Court Policy, then filing applications can simply mirror it in the filing, thus providing very accurate fee payment.

[26]  The ValueType attribute has the enumerated values Name, Alias, Code. This provides a means to tell whether the document type to fee association with the Code:Name, Code:Alias, or Code:Value element from the document type court policy table.

1.23. Fee:DocumentGenericTypes
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
DocumentGenericType1unbounded

[27]  Fee:DocumentGenericTypes is a container element for one or more Fee:DocumentGenericType elements. Multiple Fee:DocumentGenericType elements can be associated with one fee.

1.24. Fee:DocumentGenericType
Data Type: xsd:string
go to top

[28]  Fee:DocumentGenericType is a general document type that is associated with a fee. Fee:DocumentGenericType can be used in both Filing XML and Court Policy XML to associate fees and general document types.

[29]  In Filing XML, for each document within a filing that results in a filing fee (disregarding the same document transmitted in the filing in multiple electronic formats), the value in Fee:DocumentGenericType can be matched with the value in Document:GenericType to associate the document and the fee. For example, if the value in Document:GenericType were Motion then the Fee:DocumentGenericType value would also be Motion.

[30]  In Policy XML, each fee listed in the Court Policy can be associated with one more more generic document types by listing the generic document types in Fee:DocumentGenericTypes. This provides a means of helping the filer determine which fee is associated with a general class of document types, so that the proper fee will be submitted in the filing. Further, if the information is listed correctly in the Court Policy, then filing applications can simply mirror it in the filing, thus providing very accurate fee payment.

[31]  Using Fee:DocumentGenericType in Court Policy XML is slightly different than using Fee:DocumentType. Fee:DocumentGenericType uses a more general value, such as Motion, which means that one fee can be associated with many motions with only a single value. This makes creating the policy easier and makes the size of the policy smaller. However, using a single value may be too general in some situations.

1.25. Fee:DocumentKey
Data Type: xsd:string
go to top

[32]  Fee:DocumentKey is a unique identifier for a document used to match a fee with a document in Filing XML. To match a fee with a document in Filing XML, the Fee:DocumentKey value and the Document:Key value should be the same. Using the Document:Key element provides an exact match, rather than a more general match when using Fee:DocumentType or Fee:DocumentGenericType.

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

[33]  The Fee:Filters element is a container element for one or more Fee:Filter elements.

1.27. Fee:Include
Data Type: YesNo
go to top

[34]  Fee:Include is a flag that tells applications whether to publish the Court's fee schedule publicly or not.

1.28. Fee:Filter
Data Type: Filter:Filter
go to top

[35]  The Fee:Filter element provides the ability to associate cutom filters to a fee.

2. Simple Types

2.1. AmountThresholds
Data Type: xsd:string
go to top
Enumeration(s)

Value
Exact
Does Not Exceed
Exceeds
2.2. YesNo
Data Type: xsd:string
go to top
Enumeration(s)

Value
Yes
No
2.3. JurisdictionalAmounts
Data Type: xsd:string
go to top
Enumeration(s)

Value
$1 to $10,000
$10,000 to $25,000
Over $25,000
2.4. ValueTypes
Data Type: xsd:string
go to top
Enumeration(s)

Value
Name
Alias
Code

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-03
Editor: Winchel Vincent
go to top

Changed fee schema to accommodate difference in price in first and second pages. Added effective date.

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

Added structured copyright and update history.

4.3. 2003-03-01
Editor: Winchel Vincent
go to top

Changed AmountSecondPage element to AmountSubsequentPages. Added Alias element. Moved documentation to elements.

4.4. 2003-05-10
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/BuildingBlocks/Primitives/Fee/01/
go to top

Copied

4.5. 2003-05-10
Editor: Winchel Vincent
go to top

Normalized using xmlLegal Normalizer 0.0.7

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

Normalized using xmlLegal Normalizer 0.0.9. Changed Name element to FullName element. Added Name element as child of Description element. Added FirstPaper, Descriptions, Description, CodeSection, Cost, LastUpdated, and Note elements. Changed AmountFirstPage to FirstPage and AmountSubsequentPages to SubsequentPages. Moved Include to last position in sequence. Removed blank value from YesNo simpleType.

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

Added CourtKey and added back Currency.

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

Made minor typographical changes.

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

Added Fee:ExpirationDate. Added Fee:DocumentTypes, Fee:DocumentType, Fee:DocumentGenericTypes, Fee:DocumentGenericType, Fee:DocumentKey and documentation explaining how these elements can be used to associate fees with documents either in Filing XML or in Court Policy XML. Added element Fee:CourtKeys as a container element for Fee:CourtKey so that a fee can be associated with more than one division of a court.

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

Normalized using xmlLegal Normalizer 0.1.0.

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

Made minor edit to Fee:CourtKey definition. Added example to Fee:FirstPaper.

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

Copied. No changes made except the namespace version.

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/Fee/02/
go to top

Copied. Changed Attributes schema to 03 version.

4.16. 2008-10-01
Editor: Winchel Vincent
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.5. Added Fee:JurisdictionalAmount element and associated JurisdictionalAmounts simpleType. Added new ValueTypes simpleType. Added Fee:CaseTypes and Fee:CaseType elements. Added Filter schema and Fee:Filters and Fee:Filter elements. Deleted Fee:Cost, Fee:CodeSection, Fee:Name, Fee:Description, and Fee:Descriptions elements. Changed Fee:FullName to Fee:Name. Changed Fee:FirstPage to Fee:Cost. Reordered elements Fee:Name, Fee:Alias, and Fee:Value to match the order in the Code schema.

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