XML Schema "myProfile.xsd"
Target Namespace:
http://schemas.microsoft.com/hs/2001/10/myProfile
Version:
1.0
Defined Components:
elements (15 global + 49 local), complexTypes (27), simpleTypes (1)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Projects\Microsoft Hailstorm\xsd\myProfile.xsd; see XML source
Imports Schemas (2):
hscommon.xsd [src], myCalendar.xsd [src]
Imported by Schemas (1):
myContacts.xsd [src]
Annotation
Schema for .NET Profile service Copyright (c) 2001 Microsoft Corporation. All rights reserved.
All Element Summary (local elements unified by type)
address
Type:
Content:
complex, 3 attributes, 14 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
address (in myProfile)
Type:
Content:
complex, 3 attributes, 14 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
cat (type hs:catType)
Type:
Content:
empty, 1 attribute
Defined:
locally at 10 locations
certificate (type xsd:hexBinary)
Type:
xsd:hexBinary
Content:
simple
Defined:
coworkerOrDepartment (type hs:userReferenceCategorized)
This element encapsulates information about this entity's manager, assistant, company, department, and so on.
Type:
Content:
complex, 4 elements
Defined:
locally within workInformationType complexType; see XML source
date (type xsd:date)
Type:
xsd:date
Content:
simple
Defined:
locally within specialDateType complexType; see XML source
domainNamePortion (in memberInformation)
This is the other part of the fully qualified member name.
Type:
Content:
simple
Defined:
locally within memberInformationType complexType; see XML source
email (type hs:string)
Type:
Content:
simple
Defined:
locally at 2 locations
emailAddress
Type:
Content:
complex, 3 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
emailAddress (in myProfile)
Type:
Content:
complex, 3 attributes, 3 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
fileAsName (type hs:localizableString)
A complete name is usually the combination of title, givenName, middleName, surname, and suffix.
Type:
Content:
simple, 2 attributes
Defined:
locally within myNameType complexType; see XML source
gender
Type:
Content:
simple
Defined:
globally; see XML source
Used:
never
gender (in myProfile)
Type:
Content:
simple, 3 attributes
Defined:
locally within myProfileType complexType; see XML source
givenName (type hs:localizableString)
This optional element is used to store the first portion of a name.
Type:
Content:
simple, 2 attributes
Defined:
locally within myNameType complexType; see XML source
identificationNumber
Type:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
identificationNumber (in myProfile)
Type:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
jobTitle (type hs:localizableString)
This element specifies the job title for this piece of work information.
Type:
Content:
simple, 2 attributes
Defined:
locally within workInformationType complexType; see XML source
languagePreference (in myProfile)
This element specifies the preferred language code of the identity encoded using ISO 639 language codes or ISO 3166 country codes, as defined by RFC 1766.
Type:
Content:
simple, 4 attributes
Defined:
locally within myProfileType complexType; see XML source
memberInformation (in myProfile)
Type:
Content:
complex, 3 attributes, 2 elements
Defined:
locally within myProfileType complexType; see XML source
memberNamePortion (in memberInformation)
A member name is a combination of a user name portion and a domain name portion.
Type:
Content:
simple, 2 attributes
Defined:
locally within memberInformationType complexType; see XML source
middleName (type hs:localizableString)
This optional element is used to store the middle portion or initial of a name.
Type:
Content:
simple, 2 attributes
Defined:
locally within myNameType complexType; see XML source
minimalEmailAddress
Type:
Content:
complex, 1 element
Defined:
globally; see XML source
Used:
never
myProfile
This element encapsulates the content document for this service.
Type:
Content:
complex, 2 attributes, 17 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
name
Type:
Content:
complex, 3 attributes, 7 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
name (in myProfile)
Type:
Content:
complex, 3 attributes, 7 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
name (type hs:localizableString)
Type:
Content:
simple, 2 attributes
Defined:
locally at 2 locations
number (type hs:string)
This element contains the actual identification number value.
Type:
Content:
simple
Defined:
officeLocation (type hs:localizableString)
This element specifies the office location for this piece of work information.
Type:
Content:
simple, 2 attributes
Defined:
locally within workInformationType complexType; see XML source
picture
Type:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
picture (in myProfile)
Type:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
profession (type hs:localizableString)
This optional element specifies the entity's profession within this particular workInformation element.
Type:
Content:
simple, 2 attributes
Defined:
locally within workInformationType complexType; see XML source
screenName
Type:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
screenName (in myProfile)
Type:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
securityCertificate
Type:
Content:
complex, 3 attributes, 2 elements
Defined:
globally; see XML source
Used:
never
securityCertificate (in myProfile)
Type:
Content:
complex, 3 attributes, 2 elements
Defined:
locally within myProfileType complexType; see XML source
specialDate
Type:
Content:
complex, 4 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
specialDate (in myProfile)
Type:
Content:
complex, 4 attributes, 2 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
subscription (in myProfile)
Type:
Content:
complex, 3 attributes, 4 elements
Defined:
locally within myProfileType complexType; see XML source
suffix (type hs:localizableString)
This optional element is used to store a suffix associated with the name (for example, 'Jr
Type:
Content:
simple, 2 attributes
Defined:
locally within myNameType complexType; see XML source
surname (type hs:localizableString)
This optional element is used to store the last portion of a name.
Type:
Content:
simple, 2 attributes
Defined:
locally within myNameType complexType; see XML source
telephoneNumber
Type:
Content:
complex, 3 attributes, 6 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
telephoneNumber (in myProfile)
Type:
Content:
complex, 3 attributes, 6 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
timeZone (in timeZonePreference)
Type:
Content:
simple
Defined:
locally within timeZonePreferenceType complexType; see XML source
timeZonePreference (in myProfile)
This element supplies the base time zone preference for this entity.
Type:
Content:
complex, 3 attributes, 2 elements
Defined:
locally within myProfileType complexType; see XML source
title (type hs:localizableString)
This optional element is used to store a title or prefix associated with the name (for example,'Mr
Type:
Content:
simple, 2 attributes
Defined:
locally within myNameType complexType; see XML source
url (type hs:string)
Type:
Content:
simple
Defined:
locally at 2 locations
userReference
Type:
Content:
complex, 3 attributes, 4 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
userReference (in myProfile)
Type:
Content:
complex, 3 attributes, 4 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
webSite
Type:
Content:
complex, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
webSite (in myProfile)
Type:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
workInformation
Type:
Content:
complex, 5 elements, elem. wildcard
Defined:
globally; see XML source
Used:
never
workInformation (in myProfile)
Type:
Content:
complex, 3 attributes, 5 elements, elem. wildcard
Defined:
locally within myProfileType complexType; see XML source
Complex Type Summary
Content:
complex, 3 attributes, 14 elements, elem. wildcard
Defined:
globally; see XML source
Used:
Content:
complex, 3 attributes, 4 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definition of elem. wildcard
Used:
Content:
complex, 3 attributes, 3 elements, elem. wildcard
Defined:
globally; see XML source
Used:
This element encapsulates an electronic address for this entity.
Content:
complex, 3 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 3 elements, elem. wildcard
Used:
Content:
simple, 3 attributes
Defined:
globally; see XML source
Used:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
This optional element encapsulates an identification number for the entity (for example, an employee ID number, social security number, national ID number, or driver's license number).
Content:
complex, 2 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 2 elements, elem. wildcard
Used:
Content:
simple, 4 attributes
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
This node wraps member-specific public information for this entity.
Content:
complex, 3 attributes, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
This element encapsulates a name associated with the identity.
Content:
complex, 7 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 7 elements, elem. wildcard
Used:
This element encapsulates and defines the basic myProfile types for the Microsoft® .NET Profile service.
Content:
complex, 2 attributes, 17 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 17 elements, elem. wildcard
Used:
Content:
complex, 3 attributes, 7 elements, elem. wildcard
Defined:
globally; see XML source
Used:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
This optional element encapsulates a URL that points to a picture of the identity.
Content:
complex, 2 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 2 elements, elem. wildcard
Used:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
This element encapsulates an electronic address for this entity.
Content:
complex, 2 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 2 elements, elem. wildcard
Used:
Content:
complex, 3 attributes, 2 elements
Defined:
globally; see XML source
Used:
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Content:
complex, 4 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
This element encapsulates a date that is important to this entity.
Content:
complex, 1 attribute, 2 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 2 elements, elem. wildcard
Used:
Content:
complex, 3 attributes, 6 elements, elem. wildcard
Defined:
globally; see XML source
Used:
Content:
complex, 3 attributes, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Content:
complex, 3 attributes, 2 elements, elem. wildcard
Defined:
globally; see XML source
Used:
This element encapsulates an electronic address for this entity.
Content:
complex, 2 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 2 elements, elem. wildcard
Used:
Content:
complex, 3 attributes, 5 elements, elem. wildcard
Defined:
globally; see XML source
Used:
This element encapsulates information related to work or occupation for this entity.
Content:
complex, 5 elements, elem. wildcard
Defined:
globally; see XML source
Includes:
definitions of 5 elements, elem. wildcard
Used:
Simple Type Summary
This element specifies the gender for this entity.
Defined:
globally; see XML source
Used:
XML Source
<xsd:schema elementFormDefault="qualified" targetNamespace="http://schemas.microsoft.com/hs/2001/10/myProfile" version="1.0" xmlns="http://schemas.microsoft.com/hs/2001/10/myProfile" xmlns:hs="http://schemas.microsoft.com/hs/2001/10/core" xmlns:mc="http://schemas.microsoft.com/hs/2001/10/myCalendar" xmlns:xdb="urn:schemas-microsoft-com:xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:documentation>
Schema for .NET Profile service
Copyright (c) 2001 Microsoft Corporation. All rights reserved.
</xsd:documentation>
<xsd:appinfo>
<xdb:index id="1" select="/myProfile/address">
<xdb:indexComponent select="$docId"/>
<xdb:indexComponent select="./@id"/>
</xdb:index>
<xdb:blue select="/myProfile"/>
<xdb:blue select="/myProfile/*"/>
<xdb:red select="//@id"/>
<xdb:red select="//@creator"/>
<xdb:red select="//@changeNumber"/>
<xdb:red select="//cat"/>
<xdb:red select="//cat/@ref"/>
<xdb:red select="/myProfile/address/$any"/>
<xdb:red select="/myProfile/webSite/$any"/>
<xdb:red select="/myProfile/emailAddress/$any"/>
<xdb:red select="/myProfile/screenName/$any"/>
<xdb:red select="/myProfile/telephoneNumber/$any"/>
<xdb:red select="/myProfile/name/$any"/>
<xdb:red select="/myProfile/specialDate/$any"/>
<xdb:red select="/myProfile/userReference/$any"/>
<xdb:red select="/myProfile/picture/$any"/>
<xdb:red select="/myProfile/identificationNumber/$any"/>
<xdb:red select="/myProfile/workInformation/$any"/>
<xdb:red select="/myProfile/subscription/context/$any"/>
<xdb:sqlScript source="myProfileCustomSQL.sql"/>
<xdb:namespaceMap>
<xdb:mapping alias="m" uri="http://schemas.microsoft.com/hs/2001/10/myProfile"/>
<xdb:mapping alias="mc" uri="http://schemas.microsoft.com/hs/2001/10/myCalendar"/>
<xdb:mapping alias="hs" uri="http://schemas.microsoft.com/hs/2001/10/core"/>
</xdb:namespaceMap>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://schemas.microsoft.com/hs/2001/10/core" schemaLocation="hscommon.xsd"/>
<xsd:import namespace="http://schemas.microsoft.com/hs/2001/10/myCalendar" schemaLocation="myCalendar.xsd"/>
<!--
//
// myProfile
// - root element for the .NET Profile service
//
-->
<xsd:element name="myProfile" type="myProfileType">
<xsd:annotation>
<xsd:documentation>
This element encapsulates the content document for this service. This element
establishes a global cache scope for the service and contains other
root-level system attributes for this instance of the service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="myProfileType">
<xsd:annotation>
<xsd:documentation>
This element encapsulates and defines the basic myProfile types for the
Microsoft&#174; .NET Profile service.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="name" type="nameType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="memberInformation" type="memberInformationType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="languagePreference" type="languagePreferenceType">
<xsd:annotation>
<xsd:documentation>
This element specifies the preferred language code
of the identity encoded using ISO 639 language codes
or ISO 3166 country codes, as defined by
<a href="http://www.ietf.org/rfc/rfc1766.txt">RFC 1766</a>
.
The purpose of this value in this service is to indicate the languages understood
by this identity. When manipulating localizable content, choose from an appropriate language
preference. When encountering localized content not falling within this set, the software should translate
into a language understood by this set.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="timeZonePreference" type="timeZonePreferenceType">
<xsd:annotation>
<xsd:documentation>
This element supplies the base time zone preference for this entity.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="specialDate" type="specialDateBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="userReference" type="categorizedUserReferenceBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="picture" type="pictureBlueType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="gender" type="genderBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="identificationNumber" type="identificationNumberBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="workInformation" type="workInformationBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="address" type="addressBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="webSite" type="webSiteBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="emailAddress" type="emailAddressBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="screenName" type="screenNameBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="telephoneNumber" type="telephoneNumberBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="subscription" type="hs:subscriptionType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="securityCertificate" type="securityCertificateBlueType"/>
</xsd:sequence>
<!-- standard attributes for the root element -->
<xsd:attributeGroup ref="hs:documentRootAttributeGroup"/>
</xsd:complexType>
<!--
//
// myNameType
//
-->
<xsd:complexType name="myNameType">
<xsd:annotation>
<xsd:documentation>
This element encapsulates a name associated with the identity. An identity
can have multiple names associated with it. These name nodes are not
intended to be used to store screen or other electronic names, but
rather to store a name commonly used for the entity.
Names contain five parts and should be combined in proper
order, with spaces
separating the parts and empty content parts excluded.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="title" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This optional element is used to store a title or prefix associated with the name (for example,'Mr.', 'Mrs.', 'Dr.', or any other commonly used name title or prefix).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="givenName" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This optional element is used to store the first portion of a name.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="middleName" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This optional element is used to store the middle portion or initial of a name.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="surname" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This optional element is used to store the last portion of a name.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="suffix" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This optional element is used to store a suffix associated with the name (for example, 'Jr.', 'Sr.', 'III', or any other commonly used name suffix).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="fileAsName" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
A complete name is usually the combination of
<b>title</b>
,
<b>givenName</b>
,
<b>middleName</b>
,
<b>surname</b>
, and
<b>suffix</b>
. The presence of this optional element indicates that a different order should be used
or that the identity prefers to have the name filed differently.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
</xsd:sequence>
</xsd:complexType>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="name" type="nameType"/>
<!-- NameType: myName type plus blue node attributes -->
<xsd:complexType name="nameType">
<xsd:complexContent>
<xsd:extension base="myNameType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="languagePreferenceType">
<xsd:simpleContent>
<xsd:extension base="hs:string">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
<xsd:attribute name="level" use="required">
<xsd:annotation>
<xsd:documentation>
This attribute indicates how well this language is understood by this identity. Valid
values include:
<ul>
<li>native</li>
<li>fluent</li>
<li>intermediate</li>
<li>beginner</li>
</ul>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="hs:string">
<xsd:enumeration value="native"/>
<xsd:enumeration value="fluent"/>
<xsd:enumeration value="intermediate"/>
<xsd:enumeration value="beginner"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="timeZonePreferenceType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:element maxOccurs="1" minOccurs="1" name="timeZone" type="hs:string"/>
</xsd:sequence>
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:complexType>
<!-- gender stuff -->
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="gender" type="genderType"/>
<xsd:simpleType name="genderType">
<xsd:annotation>
<xsd:documentation>
This element specifies the gender for this entity.
An entity can be associated with only one gender.
The format of this element is a single, 7-bit ASCII character with
one of two possible values: 'm' for male and 'f' for female.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="hs:string">
<xsd:maxLength value="1"/>
<xsd:enumeration value="f"/>
<xsd:enumeration value="m"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="genderBlueType">
<xsd:simpleContent>
<xsd:extension base="genderType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- memberInformation stuff -->
<xsd:complexType name="memberInformationType">
<xsd:annotation>
<xsd:documentation>
This node wraps member-specific public information for this entity. The information
cannot be changed. This is reflected in the schemas that modify the content document.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="memberNamePortion" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
A member name is a combination of a user name portion and a domain name portion.
These names separated by an '@' character form a fully qualified
member name. This element contains the user name portion of the name. For
a fully qualified member name of someone@microsoft.com, this element contains the value
'someone'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="domainNamePortion" type="hs:string">
<xsd:annotation>
<xsd:documentation>
This is the other part of the fully qualified member name.
This element contains the domain name portion. For
a fully qualified member name of someone@microsoft.com, this element contains the value
'microsoft.com'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:complexType>
<!-- specialDate stuff -->
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="specialDate" type="specialDateBlueType"/>
<xsd:complexType name="specialDateType">
<xsd:annotation>
<xsd:documentation>
This element encapsulates a date that is important to this entity.
Multiple special date nodes can exist. This is not a substitute for dates stored
on an entity's
<a href="#myCalendar">.NET Calendar</a>
service. Its purpose
is to provide a convenient place to store a birthdate or anniversary because
these dates are frequently imported into a contact record.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
<xsd:element maxOccurs="1" minOccurs="1" name="date" type="xsd:date"/>
</xsd:sequence>
<xsd:attribute name="calendarType" type="mc:calendarLocaleEnum" use="required"/>
</xsd:complexType>
<xsd:complexType name="specialDateBlueType">
<xsd:complexContent>
<xsd:extension base="specialDateType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- userReference stuff -->
<!-- needed for wsdl generation (because myContacts references it) -->
<xsd:element name="userReference" type="categorizedUserReferenceBlueType"/>
<xsd:complexType name="categorizedUserReferenceBlueType">
<xsd:complexContent>
<xsd:extension base="hs:userReferenceCategorized">
<xsd:sequence>
<!--
// paulste: since these are blue nodes they should have {any}
// elements as well
//
-->
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
</xsd:sequence>
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- picture stuff -->
<xsd:complexType name="pictureType">
<xsd:annotation>
<xsd:documentation>
This optional element encapsulates a URL that points to a picture of the identity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
<xsd:element maxOccurs="1" minOccurs="1" name="url" type="hs:string">
<xsd:annotation>
<xsd:documentation>
This element contains the URL that points to the actual picture.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="picture" type="pictureBlueType"/>
<xsd:complexType name="pictureBlueType">
<xsd:complexContent>
<xsd:extension base="pictureType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- identificationNumber stuff -->
<xsd:complexType name="identificationNumberType">
<xsd:annotation>
<xsd:documentation>
This optional element encapsulates an identification number
for the entity (for example, an employee ID number, social security number,
national ID number, or driver's license number).
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
<xsd:element maxOccurs="1" minOccurs="1" name="number" type="hs:string">
<xsd:annotation>
<xsd:documentation>
This element contains the actual identification number value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:complexType name="identificationNumberBlueType">
<xsd:complexContent>
<xsd:extension base="identificationNumberType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="workInformation" type="workInformationType"/>
<xsd:complexType name="workInformationType">
<xsd:annotation>
<xsd:documentation>
This element encapsulates information related to work or occupation for this
entity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
<xsd:element maxOccurs="1" minOccurs="0" name="profession" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This optional element specifies the entity's profession within this
particular
<b>workInformation</b>
element.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="jobTitle" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This element specifies the job title for this piece of work information.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="officeLocation" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This element specifies the office location for this piece of work information.
<p/>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="coworkerOrDepartment" type="hs:userReferenceCategorized">
<xsd:annotation>
<xsd:documentation>
This element encapsulates information about this entity's manager, assistant,
company, department, and so on. The information can include its name, Microsoft .NET Passport Unique ID (PUID)
and e-mail address. Using this anchor information, additional details can be
obtained.
The required
<b>cat</b>
element indicates the relationship of the element to this entity
(that is, ref="system#manager").
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="workInformationBlueType">
<xsd:complexContent>
<xsd:extension base="workInformationType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--
//
// address
// - public type for address
//
-->
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="address" type="addressBlueType"/>
<xsd:complexType name="addressBlueType">
<xsd:complexContent>
<xsd:extension base="hs:addressType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--
//
// webSiteType
//
//
-->
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="webSite" type="webSiteType"/>
<xsd:complexType name="webSiteType">
<xsd:annotation>
<xsd:documentation>
This element encapsulates an electronic address for this entity. Specifically,
it contains a Website or URL associated with this identity.
This element
can be repeated. Typically, one
<b>webSite</b>
element is used for each Web site associated with this identity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
<xsd:element maxOccurs="1" minOccurs="1" name="url" type="hs:string">
<xsd:annotation>
<xsd:documentation>
This element contains the URL for this Web site. If the site is accessible
through multiple URLs, this element can be repeated the corresponding
number of times.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="webSiteBlueType">
<xsd:complexContent>
<xsd:extension base="webSiteType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--
//
// emailAddressType
//
//
-->
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="minimalEmailAddress" type="minimalEmailAddressType"/>
<xsd:element name="emailAddress" type="emailAddressType"/>
<xsd:complexType name="minimalEmailAddressType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="email" type="hs:string">
<xsd:annotation>
<xsd:documentation>
This element contains the actual value of the e-mail address (for example, someone@microsoft.com).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="emailAddressType">
<xsd:annotation>
<xsd:documentation>
This element encapsulates an electronic address for this entity. Specifically,
it contains an e-mail address associated with this identity.
This element
can be repeated. Typically, one
<b>emailAddress</b>
element is used
for each e-mail address associated with this identity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
<xsd:element name="email" type="hs:string">
<xsd:annotation>
<xsd:documentation>
This element contains the actual value of the e-mail address (for example, someone@microsoft.com).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="name" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This element contains the friendly or display name associated
with this e-mail address.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="emailAddressBlueType">
<xsd:complexContent>
<xsd:extension base="emailAddressType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--
//
// screenNameType
// - open issue: how do we indicate where this screen name is commonly used?
//
//
-->
<xsd:complexType name="screenNameType">
<xsd:annotation>
<xsd:documentation>
This element encapsulates an electronic address for this entity. Specifically,
it contains a screen name commonly used in real-time communication
applications, such as instant messaging, chat rooms, and so on.
This element
can be repeated. The
<b>type</b>
attribute can be used
for simple classifications on the
<b>screenName</b>
.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
<xsd:element name="name" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
This element contains the value of the screen name.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="screenName" type="screenNameBlueType"/>
<xsd:complexType name="screenNameBlueType">
<xsd:complexContent>
<xsd:extension base="screenNameType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--
// telephoneNumber Type
-->
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:element name="telephoneNumber" type="telephoneNumberBlueType"/>
<xsd:complexType name="telephoneNumberBlueType">
<xsd:complexContent>
<xsd:extension base="hs:telephoneNumberType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--
// securityCertificateType
// open issue: what type should <certificate> be?
-->
<xsd:complexType name="securityCertificateType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
<xsd:element maxOccurs="1" minOccurs="1" name="certificate" type="xsd:hexBinary"/>
</xsd:sequence>
</xsd:complexType>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:complexType name="securityCertificateBlueType">
<xsd:complexContent>
<xsd:extension base="securityCertificateType">
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--
// securityCertificateType
// open issue: what type should <certificate> be?
-->
</xsd:schema>