All Element Summary (local elements unified by type) |
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
certificate (type xsd:hexBinary) |
|
|||||||||
This element encapsulates information about this entity's manager, assistant,
company, department, and so on.
|
||||||||||
date (type xsd:date) |
|
|||||||||
This is the other part of the fully qualified member name.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
A complete name is usually the combination of title, givenName, middleName, surname, and
suffix.
|
||||||||||
|
||||||||||
|
||||||||||
This optional element is used to store the first portion of a name.
|
||||||||||
|
||||||||||
|
||||||||||
This element specifies the job title for this piece of work information.
|
||||||||||
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.
|
||||||||||
|
||||||||||
A member name is a combination of a user name portion and a domain name portion.
|
||||||||||
This optional element is used to store the middle portion or initial of a name.
|
||||||||||
|
||||||||||
This element encapsulates the content document for this service.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
This element contains the actual identification number value.
|
||||||||||
This element specifies the office location for this piece of work information.
|
||||||||||
|
||||||||||
|
||||||||||
This optional element specifies the entity's profession within this
particular workInformation element.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
This optional element is used to store a suffix associated with the name (for example, 'Jr
|
||||||||||
This optional element is used to store the last portion of a name.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
This element supplies the base time zone preference for this entity.
|
||||||||||
This optional element is used to store a title or prefix associated with the name (for example,'Mr
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
Complex Type Summary |
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
This element encapsulates an electronic address for this entity.
|
||||||||||
|
||||||||||
|
||||||||||
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).
|
||||||||||
|
||||||||||
This node wraps member-specific public information for this entity.
|
||||||||||
|
||||||||||
This element encapsulates a name associated with the identity.
|
||||||||||
This element encapsulates and defines the basic myProfile types for the
Microsoft® .NET Profile service.
|
||||||||||
|
||||||||||
|
||||||||||
This optional element encapsulates a URL that points to a picture of the identity.
|
||||||||||
|
||||||||||
This element encapsulates an electronic address for this entity.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
This element encapsulates a date that is important to this entity.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
This element encapsulates an electronic address for this entity.
|
||||||||||
|
||||||||||
This element encapsulates information related to work or occupation for this
entity.
|
Simple Type Summary |
||||||
This element specifies the gender for this entity.
|
<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>
</xsd:annotation>
Schema for .NET Profile service
</xsd:documentation>
Copyright (c) 2001 Microsoft Corporation. All rights reserved.
<xdb:index id="1" select="/myProfile/address">
</xsd:appinfo>
<xdb:indexComponent select="$docId"/>
</xdb:index>
<xdb:indexComponent select="./@id"/>
<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:namespaceMap>
<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"/>
<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:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element encapsulates the content document for this service. This element
</xsd:documentation>
establishes a global cache scope for the service and contains other root-level system attributes for this instance of the service.
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element encapsulates and defines the basic myProfile types for the
</xsd:documentation>
Microsoft® .NET Profile service. <xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
</xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="memberInformation" type="memberInformationType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="languagePreference" type="languagePreferenceType">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element specifies the preferred language code
</xsd:documentation>
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:element maxOccurs="unbounded" minOccurs="0" name="timeZonePreference" type="timeZonePreferenceType">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element supplies the base time zone preference for this entity.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="userReference" type="categorizedUserReferenceBlueType"/>
<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="telephoneNumber" type="telephoneNumberBlueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="securityCertificate" type="securityCertificateBlueType"/>
<!-- standard attributes for the root element -->
<!--
// // myNameType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element encapsulates a name associated with the identity. An identity
</xsd:documentation>
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:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
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:documentation>
</xsd:annotation>
This optional element is used to store the first portion of a name.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element is used to store the middle portion or initial of a name.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element is used to store the last portion of a name.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
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:documentation>
</xsd:annotation>
A complete name is usually the combination of
</xsd:documentation>
<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. <!-- sgfix: required for wsdl (because myContacts references it) -->
<!-- NameType: myName type plus blue node attributes -->
</xsd:complexType>
<xsd:simpleContent>
</xsd:complexType>
<xsd:extension base="hs:string">
</xsd:simpleContent>
<xsd:attributeGroup ref="hs:standardBlueAttributeGroup"/>
</xsd:extension>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This attribute indicates how well this language is understood by this identity. Valid
</xsd:documentation>
values include: <ul>
<li>native</li>
</ul>
<li>fluent</li>
<li>intermediate</li>
<li>beginner</li>
<xsd:restriction base="hs:string">
</xsd:simpleType>
<xsd:enumeration value="native"/>
</xsd:restriction>
<xsd:enumeration value="fluent"/>
<xsd:enumeration value="intermediate"/>
<xsd:enumeration value="beginner"/>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!-- gender stuff -->
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:annotation>
</xsd:simpleType>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element specifies the gender for this entity.
</xsd:documentation>
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:maxLength value="1"/>
</xsd:restriction>
<xsd:enumeration value="f"/>
<xsd:enumeration value="m"/>
<!-- memberInformation stuff -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This node wraps member-specific public information for this entity. The information
</xsd:documentation>
cannot be changed. This is reflected in the schemas that modify the content document. <xsd:sequence>
<xsd:element name="memberNamePortion" type="hs:localizableString">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
A member name is a combination of a user name portion and a domain name portion.
</xsd:documentation>
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:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This is the other part of the fully qualified member name.
</xsd:documentation>
This element contains the domain name portion. For a fully qualified member name of someone@microsoft.com, this element contains the value 'microsoft.com'. <!-- specialDate stuff -->
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:annotation>
</xsd:complexType>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element encapsulates a date that is important to this entity.
</xsd:documentation>
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:sequence>
</xsd:sequence>
<!-- userReference stuff -->
<!-- needed for wsdl generation (because myContacts references it) -->
<xsd:complexContent>
</xsd:complexType>
<xsd:extension base="hs:userReferenceCategorized">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<!--
</xsd:sequence>
// paulste: since these are blue nodes they should have {any} // elements as well //--> <!-- picture stuff -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This optional element encapsulates a URL that points to a picture of the identity.
</xsd:documentation>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the URL that points to the actual picture.
</xsd:documentation>
<!-- sgfix: required for wsdl (because myContacts references it) -->
</xsd:complexType>
<!-- identificationNumber stuff -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This optional element encapsulates an identification number
</xsd:documentation>
for the entity (for example, an employee ID number, social security number, national ID number, or driver's license number). <xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the actual identification number value.
</xsd:documentation>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:complexContent>
</xsd:complexContent>
</xsd:complexType>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element encapsulates information related to work or occupation for this
</xsd:documentation>
entity. <xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element specifies the entity's profession within this
</xsd:documentation>
particular <b>workInformation</b>
element.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element specifies the job title for this piece of work information.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element specifies the office location for this piece of work information.
</xsd:documentation>
<p/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="coworkerOrDepartment" type="hs:userReferenceCategorized">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element encapsulates information about this entity's manager, assistant,
</xsd:documentation>
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:complexContent>
</xsd:complexContent>
</xsd:complexType>
<!--
// // address // - public type for address // --> <!-- sgfix: required for wsdl (because myContacts references it) -->
</xsd:complexType>
<!--
// // webSiteType // //--> <!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:annotation>
</xsd:complexType>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element encapsulates an electronic address for this entity. Specifically,
</xsd:documentation>
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:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the URL for this Web site. If the site is accessible
</xsd:documentation>
through multiple URLs, this element can be repeated the corresponding number of times. <!--
// // emailAddressType // //--> <!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="1" minOccurs="1" name="email" type="hs:string">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the actual value of the e-mail address (for example, someone@microsoft.com).
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element encapsulates an electronic address for this entity. Specifically,
</xsd:documentation>
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:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the actual value of the e-mail address (for example, someone@microsoft.com).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the friendly or display name associated
</xsd:documentation>
with this e-mail address. <!--
// // screenNameType // - open issue: how do we indicate where this screen name is commonly used? // //-->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element encapsulates an electronic address for this entity. Specifically,
</xsd:documentation>
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:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!-- sgfix: required for wsdl (because myContacts references it) -->
</xsd:complexType>
<!--
// telephoneNumber Type --> <!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:complexContent>
</xsd:complexContent>
</xsd:complexType>
<!--
// securityCertificateType // open issue: what type should <certificate> be? -->
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!-- sgfix: required for wsdl (because myContacts references it) -->
<xsd:complexContent>
</xsd:complexContent>
</xsd:complexType>
<!--
// securityCertificateType // open issue: what type should <certificate> be? --> </xsd:schema>
|