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

Schema Namespace and Documentation
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Address/03/
Schema Prefix
Address
Schema Repository Location
http://www.xmllegal.org/Schema/Court/US/California/2GEFS/BuildingBlocks/Primitives/Address/03/Address.xsd
 
Table of Contents
1. Elements
 Internal
  1.1. Address
  1.2. Line
  1.3. Descriptor
  1.4. BuildingName
  1.5. StreetNumber
  1.6. StreetName
  1.7. StreetSuffix
  1.8. Directional
  1.9. UnitNumber
  1.10. ApartmentNumber
  1.11. POBox
  1.12. Suite
  1.13. Suburb
  1.14. City
  1.15. State
  1.16. County
  1.17. PostalCode
  1.18. Country
 External
2. Simple Types
  2.1. AddressTypes
  2.2. Statuses
3. Imported Schemas
  3.1. Attributes
4. Change History
  4.1. 2002-09-14
  4.2. 2002-10-14
  4.3. 2003-02-18
  4.4. 2003-02-23
  4.5. 2003-03-30
  4.6. 2003-04-28
  4.7. 2003-05-10
  4.8. 2003-06-03
  4.9. 2003-07-27
  4.10. 2004-02-29
  4.11. 2004-05-10
  4.12. 2004-08-02
  4.13. 2004-08-05
  4.14. 2005-06-13
  4.15. 2005-10-25
  4.16. 2008-09-30
  4.17. 2008-11-13
5. Legal Notices
6. Authors and Contributors

1. Elements

1.1. Address:Address
Content Model: sequence
Mixed: true
go to top
Child Element(s)minOccursmaxOccurs
Line05
Suburb01
City01
State01
County01
PostalCode01
Country01

Attribute(s)typeusefixed/default
AddressTypeAddressTypesoptionalNone
StatusStatusesoptionalNone
StatusDatexsd:dateoptionalNone
NoticePriorityxsd:integeroptionalNone

[1]   The Address element is the intended root element of the schema. The Address element has four attributes (a) AddressType (b) Status (c) StatusDate and (d) NoticePriority, all of which are optional. AddressType is the type of address, such as Home or Work. Status is a reference in time fixed by the StatusDate. For example, if the StatusDate value is equivalent to April 3rd, 2003 and the Status is Current then the Address is current as of April 3rd, 2003. If Status were Past then the address would have become a past address as of April 3rd, 2003.

[2]  The NoticePriority attribute is applicable to Notice List XML. The NoticePriority attribute is an integer that allows a person to use numbers to assign the priority or preference to several types of addresses, where 1 is the highest preference and higher numbers, such as 2, 3, or 4, signify a lower preference.

[3]  For example, an electronic filer can specify the following preferences:

Address TypeAddressPreference
Web/HTTPhttp://www.lawfirm.com/MyNoticeAddress.asp1
Emailjohn.smith@lawfirm.com2
Fax(999) 123-45673
Postal123 State St., San Mateo, CA4

[4]  In the example above, the electronic filer states a preference to receive notices at an HTTP address (using Notice XML or Confirmation XML). The electronic filer recognizes that other parties may not have the ability to send notices to an HTTP address. As a result, the electronic filer states a second preference for notice to be sent to an email address. Notices sent to email addresses should include a means of acknowledging receipt of the email. As a third preference, the electronic filer provides a fax number. As a final preference, and for the benefit of paper filers, the electronic filer provides a postal address. See the Notice List XML specification for more information.

1.2. Address:Line
Content Model: all
Mixed: true
go to top
Child Element(s)minOccursmaxOccurs
Descriptor01
BuildingName01
StreetNumber01
StreetName01
StreetSuffix01
Directional01
UnitNumber01
Suite01
ApartmentNumber01
POBox01

[5]  Address:Line is one line of an address. Address:Line is mixed content and may or may not have children elements interspersed with text. Address:Line content model is all. As a result, children elements may come in any order. The schema validates content; it does not strictly validate logic. For example, it is possible to create a valid schema that has a street name and number along with a post office box. It is up to the application to ensure that logical errors do not occur.

1.3. Address:Descriptor
Data Type: xsd:string
go to top

[6]  The Address:Descriptor element is a generic description of the address.

1.4. Address:BuildingName
Data Type: xsd:string
go to top

[7]  Address:BuildingName is a building name.

1.5. Address:StreetNumber
Data Type: xsd:string
go to top

[8]  Address:StreetNumber is the number of the address on a street.

1.6. Address:StreetName
Data Type: xsd:string
go to top

[9]  Address:StreetName is the name of the street.

1.7. Address:StreetSuffix
Data Type: xsd:string
go to top

[10]  Address:StreetSuffix is the type of street, such as Drive, Lane, or Route.

1.8. Address:Directional
Data Type: xsd:string
go to top

[11]  The Address:Directional element indicates a portion of the street based on its directional location. For example, the value West in West 405 Street is the directional indicator.

1.9. Address:UnitNumber
Data Type: xsd:string
go to top

[12]  Address:UnitNumber is the unit number on a house or building.

1.10. Address:ApartmentNumber
Data Type: xsd:string
go to top

[13]  Address:ApartmentNumber is an apartment number.

1.11. Address:POBox
Data Type: xsd:string
go to top

[14]  Address:POBox is a post office box.

1.12. Address:Suite
Data Type: xsd:string
go to top

[15]  Address:Suite is the name and number of a suite in for an office address.

1.13. Address:Suburb
Data Type: xsd:string
go to top

[16]  Address:Suburb is the suburb of a city. For example, a suburb of Atlanta might be Virginia Highlands or Buckhead. A suburb of New York might be Soho or The Village. In San Francisco, a suburb might be Chinatown.

1.14. Address:City
Data Type: xsd:string
go to top

[17]  Address:City is a city.

1.15. Address:State
Data Type: xsd:string
go to top
Attribute(s)typeusefixed/default
Provincexsd:booleanoptionalNone

[18]  Address:State is a state. There is no validation on the length of the state nor are there enumerations of the valid states. The reason for this is that, in practice, Address:State is used for states, provinces, or territories of foreign countries. This list varies by locality (e.g., Southern California might include Mexican values), so creating a strict list of enumerated values is problematic. Enumerated values may be specified in Policy XML.

[19]  The attribute Province is a boolean value. When true, it means that the Address:State is a province not a state. If the value is a province, then state values in Policy XML must not be used. Similary, provide values, if any, in Policy XML must be used.

1.16. Address:County
Data Type: xsd:string
go to top

[20]  Address:County is a county.

1.17. Address:PostalCode
Data Type: xsd:string
go to top

[21]  Address:PostalCode is the postal code. This is equivalent to the zip code in the United States.

1.18. Address:Country
Data Type: xsd:string
go to top

[22]  Address:Country is a country. There is no validation on the length of the country nor are there enumerations of valid countries. Enumerated values may be specified in Policy XML.

2. Simple Types

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

Value
Mailing
Home
Work
Other
2.2. Statuses
Data Type: xsd:string
go to top
Enumeration(s)

Value
Current
Past
Future
Other

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. 2002-09-14
Editor: Winchel Vincent
go to top

Added copyright and update history. Corrected Primatives misspelling.

4.2. 2002-10-14
Editor: Dhiraj Torane
go to top

Added attributeGroup reference to "Attributes:Global" in complexType declaration for Line.

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

Added structured copyright and update history.

4.4. 2003-02-23
Editor: Winchel Vincent
go to top

Changed relative path for Attributes to add 'Schema'.

4.5. 2003-03-30
Editor: Winchel Vincent
Copied From: http://www.xmllegal.org/Schema/BuildingBlocks/Primitives/Address/01/
go to top

Copied.

4.6. 2003-04-28
Editor: Winchel Vincent
go to top

Uploaded to repository.

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

Normalized using xmlLegal Normalizer 0.0.7. Added documentation.

4.8. 2003-06-03
Editor: Winchel Vincent
go to top

Normalized using xmlLegal Normalizer 0.0.8.

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

Normalized using xmlLegal Normalizer 0.0.9. Eliminated Relationships attribute. Eliminated blank enumerations.

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

Made minor typographical changes.

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

Made minor typographical changes to documentation. Added example for suburb.

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

Copied. No changes made except the namespace version.

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

Normalized using xmlLegal Normalizer 0.1.0.

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

Copied. Changed Attributes schema to 03 version. Added NoticePriority to provide support for Notice List priorities.

4.15. 2005-10-25
Editor: Winchel Vincent
go to top

Minor edits to documentation.

4.16. 2008-09-30
Editor: Winchel Vincent
go to top

Normalized using xmlSchemaGenerator Normalizer 0.1.5.

4.17. 2008-11-13
Editor: Winchel Vincent
go to top

Added enumerated value Mailing to AddressType. Added Address:Directional element. Added Address:Descriptor element. Changed order of of Address:BuildingName (which should not affect validation becuase it is within xsd:all). Added Province attribute to Address:State element.

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