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
 
Error Schema
Last Updated: 2005-06-27
 

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Error/03/
Schema Prefix
Error
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Error/03/Error.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. Error
  1.2. Message
  1.3. Code
  1.4. Line
  1.5. LinePosition
  1.6. FilePosition
  1.7. SourceText
  1.8. ParserCode
  1.9. ParserReason
  1.10. ParserName
 External
2. Simple Types
  There are no Simple Types.
3. Imported Schemas
  3.1. Attributes
4. Change History
  4.1. 2005-06-26
  4.2. 2005-06-26
  4.3. 2005-06-27
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. Error:Error
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
Message11
Code01
Line01
LinePosition01
FilePosition01
SourceText01
ParserCode01
ParserReason01
ParserName01

[1]  Error is a container element for information about an error that has occurred in a receiving application and is being reported back to the sending application by the receiving application in which the error occurred. Error includes one required child element, Error:Message. Error includes nine optional child elements (a) Error:Code, (b) Error:Line, (c) Error:LinePosition, (d) Error:FilePosition, (e) Error:SourceText, (f) Error:ParserCode, (g) Error:ParserReason, and (f) Error:ParserName.

[2]  Error:Message and Error:Code may be related to any error experience by the receiving application. The error may, but must not, be related to XML parsing or validation.

[3]  Error:Line, Error:LinePosition, Error:FilePosition, Error:SourceText, Error:ParserCode, and Error:ParserReason contain error information related to XML parsing and validation. Error information for these elements is expected to be the actual error message reported from the validating parser, if the parser is capable of generating such error information. Different parsers return different types of error messages. Applications should send back as much parser error message as possible, but are not required to send back information that the parser does not or cannot generate.

1.2. Error:Message
Data Type: xsd:string
go to top

[4]  Error:Message is a human readable error message. Error:Message may be related to any error experience by the receiving application. The Error:Message value should be understandable to, and appropriate for, a non-technical user. The application sending the Error:Message value should anticipate that the receiving application will, or may, display the Error:Message value to a non-technical user. The receiving application is not, however, required to display the value of the Error:Message to its users.

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

[5]  Error:Code is a code value that corresponds to the Error:Message. Error:Code may be related to any error experience by the receiving application. For the code value to be useful, implementations must standardize Error:Code values and meanings and use the standard codes accordingly. 2GEFS currently does not include standard Error:Code values. Implementations should define and publish standard Error:Code values. Implementations are encouraged to harmonize code values with code values of other implementations.

[6]  If applications do not trust that the Error:Message will be appropriate for its users, then it should rely on standard Error:Code values and then match Error:Code values to a library of its own error messages.

1.4. Error:Line
Data Type: xsd:string
go to top

[7]  Error:Line is the line number of the text file in which the error occurred. The Error:Line value should be generated by the validating parser.

1.5. Error:LinePosition
Data Type: xsd:string
go to top

[8]  Error:LinePosition is a number corresponding to the position of the character on the line reported in Error:Line. The Error:LinePosition value should be generated by the validating parser.

1.6. Error:FilePosition
Data Type: xsd:string
go to top

[9]  Error:FilePosition is a number corresponding to the position of the character in the text file in which the error occurred. The Error:FilePosition value should be generated by the validating parser.

1.7. Error:SourceText
Data Type: xsd:string
go to top

[10]  Error:SourcText is the source text or node in which the parsing or validation error occurred.

1.8. Error:ParserCode
Data Type: xsd:string
go to top

[11]  Error:ParserCode is the parser code value generated by the validating parser for the error.

1.9. Error:ParserReason
Data Type: xsd:string
go to top

[12]  Error:ParserReason is the human-readable reason generated by the validating parser for the error.

1.10. Error:ParserName
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
ParserVersionxsd:stringrequiredNone

[13]  Error:ParserName is the commonly used name of the parser, such as MSXML or Xerces, without the version of the parser. Error:ParserName includes a required attribute ParserVersion. ParserVersion must include the version of the named parser.

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. 2005-06-26
Editor: Winchel Vincent
go to top

Created

4.2. 2005-06-26
Editor: Winchel Vincent
go to top

Normalized using xmlLegal Normalizer 0.1.1.

4.3. 2005-06-27
Editor: Winchel Vincent
go to top

Documented 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