[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 Type | Address | Preference |
---|
Web/HTTP | http://www.lawfirm.com/MyNoticeAddress.asp | 1 | Email | john.smith@lawfirm.com | 2 | Fax | (999) 123-4567 | 3 | Postal | 123 State St., San Mateo, CA | 4 |
[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.
[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. [6] The Address:Descriptor element is a generic description of the address. [7] Address:BuildingName is a building name. [8] Address:StreetNumber is the number of the address on a street. [9] Address:StreetName is the name of the street. [10] Address:StreetSuffix is the type of street, such as Drive, Lane, or Route. [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. [12] Address:UnitNumber is the unit number on a house or building. [13] Address:ApartmentNumber is an apartment number. [14] Address:POBox is a post office box. [15] Address:Suite is the name and number of a suite in for an office address. [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. [17] Address:City is a city. Attribute(s) | type | use | fixed/default | Province | xsd:boolean | optional | None |
[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. [20] Address:County is a county. [21] Address:PostalCode is the postal code. This is equivalent to the zip code in the United States. [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. |