Introduction[1] Organization is the intended root element of the schema. Organization includes information about a organization's names; addresses; phone numbers; email addresses; identifiers, such as a federal taxpayer ID; and roles, such as Plaintiff or Defendant. Attributes[2] The Organization element has four optional attributes (a) OrganizationKey, (b) NoticeType, (c) NoticeRole, and (d) NoticeSwitch. Although these attributes are optional in most situations, they are all required when used in Notice List XML. Organization Key[3] The OrganizationKey value is a unique identifier for an organization. In Notice List XML, no two Organization elements may have the same OrganizationKey value. Notice Type[4] The NoticeType attribute can have the value (a) Paper or (b) Electronic. The value Paper means the person wishes to send and receive notices using paper. The value Electronic means the person wishes to send and receive notices electronically. Notice Role and Notice Switch[5] Notice List XML defines a number of notice roles. Notice roles are associated with people and organizations using the NoticeRole attribute that is on both the Person schema's root element and the Organization schema's root element. Notice roles are divided into three categories as follows: Right to NoticeUnrepresented LitigantRepresentativeJudgeClerkOfficialOn Behalf OfRepresented LitigantNo Right to NoticeMediaWitnessVictimOther[6] In the Right to Notice category are Unrepresented Litigant, Representative, Judge, Clerk, and Official. An Unrepresented Litigant is a party to a case that does not have an attorney. A Representative is an attorney that is engaged by a party and that is to receive service instead of the party. A Judge is the judge assigned to the case. A Clerk is the clerk managing the case. An Official is any other court staff, law enforcement, or other official that is not a judge, a clerk, or a party to the case, but that should nevertheless receive notice of a filing. Any person with one of these notice roles must have a right to receive service. The default rule for delivering notice to people with one of these roles is that service of notice must be delivered. [7] In the On Behalf Of category is Represented Litigant. A Represented Litigant is a party that has a right to receive notice, but generally does not receive notice, since notice is served on the party's representative. The default rule for delivering notice to people that have a notice role equal to Represented Litigant is that service of notice should not be delivered. [8] In the No Right to Notice category are Media, Witness, Victim, and Other. Media is a member of the press. Witness is a person that may be called in the case to testify, but is not a party to the case. Victim is a person who has suffered some injury related to the case, but is not a party to the case. Other is any other person wishing to receive notice in the case that does not have a right to receive notice. The default rule for delivering notice to people with one of these roles is that service of notice must not be delivered. [9] The default rules above can be overridden using the NoticeSwitch attribute that is on both the Person schema's root element and the Organization schema's root element. The NoticeSwitch attribute is a boolean value. When set to true, the value signifies the person's desire to receive notice. When set to false, the value signifies the person's desire not to receive notice. [10] The operation of the NoticeSwitch attribute varies depending on the notice role. If the NoticeSwitch value is equal to true for a Represented Litigant, then notice applications must serve notice on the Represented Litigant. If, however, the NoticeSwitch value is equal to true for any of the notice roles in the No Right to Notice category, then notice applications may deliver notice depending on the circumstances of the litigation. Likewise, if the NoticeSwitch value is equal to false for any of the notice roles in the Right to Notice category, then notice applications may elect not to deliver notice depending on the circumstances of the litigation. [11] It is permissible for applications that publish notice lists to filter Notice List XML based on notice roles. For example, a notice list application may maintain information about victims, but it is not required to publish information about victims in Notice List XML. Default Rules for Parties Served Notice of Discovery and Other Documents[12] Not all document types are filed and served on the court. For example, discovery must be served on the party responsible for answering the discovery, but is generally not required to be served on the court. The default rules, stated above, must change for discovery and other documents based on the rules of service for those documents. See California Rule of Court Rule 201.5, Limitations on the filing of papers. [13] Organization:ContactPerson is one or more contact people associated with the organization. Child Element(s) | minOccurs | maxOccurs | Address | 1 | unbounded |
[14] Organization:Addresses is a container element for one or more Organization:Address elements. Child Element(s) | minOccurs | maxOccurs | Phone | 1 | unbounded |
[15] Organization:Phones is a container element for one or more Organization:Phone elements. Child Element(s) | minOccurs | maxOccurs | Email | 1 | unbounded |
[16] Organization:Emails is a container element for one or more Organization:Email elements. Child Element(s) | minOccurs | maxOccurs | Web | 1 | unbounded |
[17] Organization:WebAddressess is a container element for one or more Organization:Web elements. Child Element(s) | minOccurs | maxOccurs | Identifier | 1 | unbounded |
[18] Organization:Identifiers is a container element for one or more Organization:Identifier elements. Child Element(s) | minOccurs | maxOccurs | Role | 1 | unbounded |
[19] Organization:Roles is a container element for one or more Organization:Role elements.
Attribute(s) | type | use | fixed/default | OrganizationType | xsd:string | optional | None |
[20] Organization:Name is a container element for the entire string of all components that make up an organization's name. For example, Organization:Name could be International Business Machines, Inc. ("IBM") or World Wide Widgets, Inc. ("Widgets"). [21] Organization:Name has an attribute OrganizationType. The OrganizationType attribute holds information about the organization's status as a legal entity, such as Corporation, Limited Liability Company, or Government. [22] Organization:Name is has an all content model and is mixed content. As a result, it is possible to use its child elements in any order and with additional text. It is possible, for example, to do the following, International Business Machines, Inc. ("IBM"), where International Business Machines, Inc. is Organization:FullName and IBM is the Organization:Acronym. Likewise, it is possible to express World Wide Widgets, Inc. ("Widgets"), where World Wide Widgets, Inc. is Organization:FullName and Widgets is Organization:AbbreviatedName. [23] Organization:FullName is a container element for an organization's name without acronyms or abbreviations. For example, Organization:FullName would be International Business Machines, Inc. [24] Organization:AbbreviatedName is a shortened version of the organization's name. The abbreviated name and an acronym are not the same. An abbreviated name for World Wide Widgets, Inc. would be Widgets. [25] Organization:Acronym is the first letter of each word of the organization's name as one string. The acronym name and the abbreviated name are not the same. An acronym for World Wide Widgets, Inc. would be WWW. Likewise, an acronym for International Business Machines, Inc. would be IBM.
[26] Organization:AlternateNames is a container element for one or more Organization:AlternateName elements.
Attribute(s) | type | use | fixed/default | OrganizationType | xsd:string | optional | None | AlternateNameType | xsd:string | optional | None |
[27] Organization:AlternateName is another name used by the organization named in Organization:Name. Organization:AlternateName has an attribute AlternateNameType. The values for AlternateNameType should be included in Court Policy XML. See Organization:Name for more information.
[28] Organization:Identifier is a container element for one of several organization identifiers, such as FederalTaxpayerID or StateTaxID. [29] Organization:ORI is an identifier used for court and justice organization as an originating agency identifier. [30] Organization:FederalTaxID is an organization's federal taxpayer identification number, also called an EIN, issued by the United State Internal Revenue Service. [31] Organization:StateTaxID is a taxpayer identification number issued by a state government revenue or similar department. [32] Organization:StateIdentification is an identifier issued by a state government other than a taxpayer identification number.
[33] Organization:OtherIdentification is a container element for other types of identifiers not included in this schema. Other identifiers can be constructing using a name of the identifier, such as Australian Taxpayer ID, the value corresponding to the organization, and an optional definition or description of the identifier name. [34] Organization:OtherIdentificationName is the name of an identifier not already included in this schema. [35] Organization:OtherIdentificationValue is the value for an organization that corresponds to an identifier named in Organization:OtherIdentificationName. [36] Organization:OtherIdentificationDescription is the definition of an identifier other than the identifiers included in this schema. [37] Organization:Address is an organization's address. See Address Schema. [38] Organization:Phone is an organization's address. See Phone Schema. [39] Organization:Email is an organization's email address. See Email Schema. [40] Organization:Web is a uniform resource locator. See the Web schema. [41] Organization:Role is the role of the organization, such as Plaintiff, Court, or Law Enforcement. See Role Schema. |