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

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/02/Calendar/01/
Schema Prefix
Calendar
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/02/Calendar/01/Calendar.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. Calendar
  1.2. CaseTitle
  1.3. CaseNumber
  1.4. CourtDepartmentNumber
  1.5. Date
  1.6. Events
  1.7. Event
  1.8. CausalDocument
  1.9. CalenderType
  1.10. EventType
  1.11. ResourceType
  1.12. ResourceName
  1.13. ResourcePlace
  1.14. ResourceLocation
  1.15. ResourceDivision
  1.16. ResourceDepartment
  1.17. Time
  1.18. NightCourt
  1.19. EstimatedDuration
  1.20. EventDescription
  1.21. StatutoryPriority
  1.22. Status
 External
2. Simple Types
  2.1. Statuses
  2.2. Memo
3. Imported Schemas
  3.1. Attributes
4. Change History
  4.1. 2003-07-26
  4.2. 2003-07-27
  4.3. 2003-07-29
  4.4. 2004-02-29
  4.5. 2004-03-25
  4.6. 2004-08-02
  4.7. 2004-08-05
  4.8. 2004-09-14
  4.9. 2005-06-25
  4.10. 2005-10-25
  4.11. 2005-12-03
  4.12. 2008-09-30
  4.13. 2008-11-13
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. Calendar:Calendar
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
CourtDepartmentNumber01
Date11
Events11

[1]  Calendar is the intended root element of the schema. Calendar contains information about events on a calendar. A Calendar represents a single day. Filing applications should use Calendar in a filing to request a hearing or some other scheduled event.

[2]  EFM and clerk review applications should send information about a scheduled or rescheduled event in a confirmation.

1.2. Calendar:CaseTitle
Data Type: xsd:string
go to top

[3]  Calendar:CaseTitle is the title or style of the case for a event. For example, Jones v. Harris. Calendar:CaseTitle is equivalent to Case:Title and Coversheet:CaseTitle.

1.3. Calendar:CaseNumber
Data Type: xsd:string
go to top

[4]  Calendar:CaseNumber is the case number of the case for an event. Calendar:CaseNumber is equivalent to Case:Number.

1.4. Calendar:CourtDepartmentNumber
Data Type: xsd:string
go to top

[5]  Calendar:CourtDepartmentNumber is a the department number of the court.

1.5. Calendar:Date
Data Type: xsd:date
go to top

[6]  Calendar:Date is the date on which an event or events are scheduled to take place or are requested to take place. If Calendar:Date exists in a filing, then this must be interpreted as a request by the sender to schedule the event(s) on the specified date. If the Calendar:Date exists in a confirmation, then this is a confirmation by the court of the date the event(s) has been scheduled, rescheduled, or rejected. See Calendar:Status element.

1.6. Calendar:Events
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
Event1unbounded

[7]  Calendar:Events is a container element for one or more Calendar:Event elements. Calendar:Events are events that are scheduled to take place on the day of the calendar.

1.7. Calendar:Event
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
CaseTitle11
CaseNumber11
CausalDocument11
CalenderType11
EventType11
ResourceType11
Time11
NightCourt01
EstimatedDuration01
EventDescription01
StatutoryPriority01
Status01

[8]  Calendar:Event is an event that is scheduled to take place on the day of the calendar.

1.8. Calendar:CausalDocument
Data Type: xsd:string
go to top

[9]  To be done.

1.9. Calendar:CalenderType
Data Type: xsd:string
go to top

[10]  To be done.

1.10. Calendar:EventType
Data Type: xsd:string
go to top

[11]  To be done.

1.11. Calendar:ResourceType
Content Model: choice
go to top
Child Element(s)minOccursmaxOccurs
ResourceName11
ResourcePlace11

[12]  To be done.

1.12. Calendar:ResourceName
Data Type: xsd:string
go to top

[13]  To be done.

1.13. Calendar:ResourcePlace
Content Model: sequence
go to top
Child Element(s)minOccursmaxOccurs
ResourceLocation11
ResourceDivision01
ResourceDepartment11

[14]  To be done.

1.14. Calendar:ResourceLocation
Data Type: xsd:string
go to top

[15]  To be done.

1.15. Calendar:ResourceDivision
Data Type: xsd:string
go to top

[16]  To be done.

1.16. Calendar:ResourceDepartment
Data Type: xsd:string
go to top

[17]  To be done.

1.17. Calendar:Time
Data Type: xsd:time
go to top

[18]  Calendar:Time is the start time of a scheduled event.

1.18. Calendar:NightCourt
Data Type: xsd:boolean
go to top

[19]  To be done.

1.19. Calendar:EstimatedDuration
Data Type: xsd:string
go to top

[20]  Calendar:Duration is the duration or estimated duration of a scheduled event.

1.20. Calendar:EventDescription
Data Type: Memo
go to top

[21]  Calendar:Description is a description of a scheduled event.

1.21. Calendar:StatutoryPriority
Data Type: xsd:boolean
go to top

[22]  Calendar:StatutoryPriority is a boolean value that, when true, is a representation by a filer that the filer believes the event has a statutory priority to be calendared before other events.

1.22. Calendar:Status
Data Type: Statuses
go to top

[23]  Calendar:Status is the status of a calendared event. Calendar:Status can have one of the following values (a) Request (b) Scheduled (c) Rescheduled (d) RequestRejected (e) Unknown. When a calendar event is sent in a filing, the calendar event should be a Request for the event to be scheduled. For example, the filer may request a hearing date. When a calendar event is sent in a confirmation, the event should be a confirmation that the event has been Scheduled on the calendar, but it could also be a RequestRejected. A subsequent asynchronous confirmation may also show that a calendared event has been Rescheduled.

2. Simple Types

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

Value
Request
Scheduled
Rescheduled
RequestRejected
Unknown
2.2. 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. 2003-07-26
Editor: Winchel Vincent
go to top

Created.

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

Normalized using xmlLegal Normalizer 0.0.9.

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

Copied. Added StatutoryPriority element.

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

Added introductory text to Calendar element.

4.5. 2004-03-25
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/Test03/Calendar/01/
go to top

Copied.

4.6. 2004-08-02
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/Test04/Calendar/01/
go to top

Copied.

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

Normalized using xmlLegal Normalizer 0.1.0.

4.8. 2004-09-14
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/Test05/Calendar/01/
go to top

Copied.

4.9. 2005-06-25
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/01/Calendar/01/
go to top

Copied. Changed Attributes to 03 version. Edited documentation for clarity, but made no significant changes.

4.10. 2005-10-25
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/02/Calendar/01/
go to top

Copied.

4.11. 2005-12-03
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/Test06/Calendar/01/
go to top

Copied.

4.12. 2008-09-30
Editor: Schema Generator
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.5.

4.13. 2008-11-13
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/Court/US/California/2GEFS/Filing/Test07/Calendar/01/
go to top

Copied. Added Calendar:CausalDocument. Added Calendar:CalendarType. Added Calendar:EventType. Added Calendar:ResourceType as choice between Added Calendar:ResourceName and Calendar:ResourcePlace. Added Calendar:ResourceName. Added Calendar:ResourcePlace. Added Calendar:ResourceLocation. Added Calendar:ResourceDivision. Added Calendar:ResourceDepartment. Added Calendar:NightCourt as xsd:boolean. Changed Calendar:Duration to Changed Calendar:EstimatedDuration. Changed Calendar:Description to Changed Calendar:EventDescription.

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