Checked Requirements: 138 (73.40%)
|
|
Coverage of normative, in-scope requirements
|
|
Checkable requirements
|
188
|
|
Completely checked requirements
|
138 (73.40%)
|
|
Partially checked requirements
|
0 (0.00%)
|
|
Unchecked requirements
|
50 (26.60%)
|
|
Coverage of derived requirements
|
|
Derived requirements
|
33
|
|
Checked derived requirements
|
12 (36.36%)
|
|
Unchecked derived requirements
|
21 (63.64%)
|
|
Details:
|
|
Req ID
|
Description
|
Doc Sect
|
Scope
|
Status
|
Time Stamp
|
Log Files
|
|
MS-OXWSMSG_R304 |
[In t:ApprovalRequestDataType Complex Type] The IsUndecidedApprovalRequest element specifies a value that indicates whether this approval request is awaiting a moderator to approve or reject the request. |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R25 |
[In t:MessageType Complex Type] The Sender element is t:SingleRecipientType ([MS-OXWSCDATA] section <IP_ADDRESS>) type. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSCDATA_R168 |
[In t:MailboxTypeType Simple Type] The value "Mailbox" specifies a mail-enabled directory service object. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSCDATA_R188 |
[In t:NonEmptyStringType Simple Type] The NonEmptyStringType simple type specifies a string that MUST have a minimum of one character. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSMSG_R29 |
[In t:MessageType Complex Type] ToRecipients element is t:ArrayOfRecipientsType ([MS-OXWSCDATA] section <IP_ADDRESS>) type. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSMSG_R39 |
[In t:MessageType Complex Type] IsReadReceiptRequested element Specifies a Boolean value that indicates whether the sender of a message requests a read receipt. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSMSG_R43 |
[In t:MessageType Complex Type] IsDeliveryReceiptRequested element Specifies a Boolean value that indicates whether the sender of the message has requested a delivery receipt. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSMSG_R59 |
[In t:MessageType Complex Type] IsRead element Specifies a Boolean value that indicates whether the message has been read. |
<IP_ADDRESS> |
Server |
Verified |
-- |
-- |
|
MS-OXWSMSG_R62 |
[In t:MessageType Complex Type] IsResponseRequested element Specifies a Boolean value that indicates whether a response to an email has been requested. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSMSG_R4 |
[In Transport] The protocol SHOULD use secure communications via HTTPS, as defined in [RFC2818]. |
2.1 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R300 |
[In t:ApprovalRequestDataType Complex Type] The ApprovalRequestDataType complex type represents an approval request message.<6> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R313 |
[In t:ArrayOfVotingOptionDataType Complex Type] The ArrayOfVotingOptionDataType complex type specifies an array of voting options.<7> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R73003 |
[In t:MessageType Complex Type] [ApprovalRequestData] Specifies the approval state of an approval request message.<8> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R73005 |
[In t:MessageType Complex Type] [VotingInformation] Specifies voting information on messages that include voting buttons or voting response messages. <9> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R73007 |
[In t:MessageType Complex Type] [ReminderMessageData] Specifies the data in a reminder message. <10> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R318 |
[In t:ReminderMessageDataType Complex Type] The ReminderMessageDataType complex type specifies a reminder message.<11> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R331 |
[In t:VotingInformationType Complex Type] The VotingInformationType complex type specifies voting information.<12> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R338 |
[In t:VotingOptionDataType Complex Type]The VotingOptionDataType complex type specifies the voting option on a message.<13> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R346 |
[In t:SendPromptType Simple Type] The SendPromptType simple type specifies the prompt behavior associated with a voting option.<15> |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSCDATA_R1188 |
[In t:ItemResponseShapeType Complex Type] The element "IncludeMimeContent" with type "xs:boolean" specifies whether the MIME content of an item is returned in a response. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSCDATA_R1193 |
[In t:ItemResponseShapeType Complex Type] The element "FilterHtmlContent" with type "xs:boolean" Specifies whether HTML content filtering is enabled. |
<IP_ADDRESS> |
Both |
Verified |
-- |
-- |
|
MS-OXWSMSG_R1 |
[In Transport] This protocol uses SOAP 1.1.
|
2.1
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R3001 |
[In Transport] The protocol MUST support SOAP over HTTP, as specified in [RFC2616].
|
2.1
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R301 |
[In t:ApprovalRequestDataType Complex Type] The ApprovalRequestDataType schema is <xs:complexType name="ApprovalRequestDataType">
<xs:sequence>
<xs:element name="IsUndecidedApprovalRequest" type="xs:boolean" minOccurs="0"/>
<xs:element name="ApprovalDecision" type="xs:int" minOccurs="0"/>
<xs:element name="ApprovalDecisionMaker" type="xs:string" minOccurs="0"/>
xs:element name="ApprovalDecisionTime" type="xs:dateTime" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R303 |
[In t:ApprovalRequestDataType Complex Type] The IsUndecidedApprovalRequest element is xs:boolean ([XMLSCHEMA2]) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R307 |
[In t:ApprovalRequestDataType Complex Type]The ApprovalDecision element is xs:int ([XMLSCHEMA2]) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R308 |
[In t:ApprovalRequestDataType Complex Type] The ApprovalDecision element specifies the approval decision on the approval request message.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R309 |
[In t:ApprovalRequestDataType Complex Type]The ApprovalDecisionMaker element is xs:string ([XMLSCHEMA2]) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R310 |
[In t:ApprovalRequestDataType Complex Type] The ApprovalDecisionMaker element specifies the display name of the moderator who approved or rejected the request.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R311 |
[In t:ApprovalRequestDataType Complex Type]The ApprovalDecisionTime element is xs:dateTime ([XMLSCHEMA2]) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R312 |
[In t:ApprovalRequestDataType Complex Type] The ApprovalDecisionTime element specifies the time at which a moderator approved or rejected the request.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R314 |
[In t:ArrayOfVotingOptionDataType Complex Type] The ArrayOfVotingOptionDataType schema is <xs:complexType name="ArrayOfVotingOptionDataType">
<xs:sequence>
<xs:element name="VotingOptionData" type="t:VotingOptionDataType" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R316 |
[In t:ArrayOfVotingOptionDataType Complex Type] The VotingOptionData element is t:VotingOptionDataType (section <IP_ADDRESS>) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R317 |
[In t:ArrayOfVotingOptionDataType Complex Type] The VotingOptionData element specifies the voting options on a message.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R22 |
[In t:MessageType Complex Type] The MessageType complex type extends the ItemType complex type ([MS-OXWSCORE] section <IP_ADDRESS>).
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R23 |
[In t:MessageType Complex Type] The MessageType schema is <xs:complexType name="MessageType">
<xs:complexContent>
<xs:extension
base="t:ItemType"
>
<xs:sequence>
<xs:element name="Sender"
type="t:SingleRecipientType"
minOccurs="0"
/>
<xs:element name="ToRecipients"
type="t:ArrayOfRecipientsType"
minOccurs="0"
/>
<xs:element name="CcRecipients"
type="t:ArrayOfRecipientsType"
minOccurs="0"
/>
<xs:element name="BccRecipients"
type="t:ArrayOfRecipientsType"
minOccurs="0"
/>
<xs:element name="IsReadReceiptRequested"
type="xs:boolean"
minOccurs="0"
/>
<xs:element name="IsDeliveryReceiptRequested"
type="xs:boolean"
minOccurs="0"
/>
<xs:element name="ConversationIndex"
type="xs:base64Binary"
minOccurs="0"
/>
<xs:element name="ConversationTopic"
type="xs:string"
minOccurs="0"
/>
<xs:element name="From"
type="t:SingleRecipientType"
minOccurs="0"
/>
<xs:element name="InternetMessageId"
type="xs:string"
minOccurs="0"
/>
<xs:element name="IsRead"
type="xs:boolean"
minOccurs="0"
/>
<xs:element name="IsResponseRequested"
type="xs:boolean"
minOccurs="0"
/>
<xs:element name="References"
type="xs:string"
minOccurs="0"
/>
<xs:element name="ReplyTo"
type="t:ArrayOfRecipientsType"
minOccurs="0"
/>
<xs:element name="ReceivedBy"
type="t:SingleRecipientType"
minOccurs="0"
/>
<xs:element name="ReceivedRepresenting"
type="t:SingleRecipientType"
minOccurs="0"
/>
<xs:element name="ApprovalRequestData"
type="t:ApprovalRequestDataType"
minOccurs="0"
/>
<xs:element name="VotingInformation"
type="t:VotingInformationType"
minOccurs="0"
/>
<xs:element name="ReminderMessageData"
type="t:ReminderMessageDataType"
minOccurs="0"
/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R26 |
[In t:MessageType Complex Type] The Sender element Specifies the sender of a message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R27 |
[In t:MessageType Complex Type] [Sender element]This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R28 |
[In t:MessageType Complex Type] [Sender element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R30 |
[In t:MessageType Complex Type] ToRecipients element Specifies a collection of recipients of an email.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R31 |
[In t:MessageType Complex Type] [ToRecipients element] This element is required for sending a message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:57 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R32 |
[In t:MessageType Complex Type] [ToRecipients element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R184 |
[In t:MessageType Complex Type] CcRecipients element is t:ArrayOfRecipientsType type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R33 |
[In t:MessageType Complex Type] CcRecipients element Specifies a collection of recipients that receive a carbon copy (Cc) of an email.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R34 |
[In t:MessageType Complex Type] [CcRecipients element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R35 |
[In t:MessageType Complex Type] [CcRecipients element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R185 |
[In t:MessageType Complex Type] BccRecipients element is t:ArrayOfRecipientsType type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R36 |
[In t:MessageType Complex Type] BccRecipients element Specifies a collection of recipients that receive a blind carbon copy (Bcc) of an email.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R37 |
[In t:MessageType Complex Type] [BccRecipients element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R38 |
[In t:MessageType Complex Type] [BccRecipients element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R186 |
[In t:MessageType Complex Type] IsReadReceiptRequested element is xs:boolean ([XMLSCHEMA2] sec 3.2.2) type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R40 |
[In t:MessageType Complex Type] [IsReadReceiptRequested element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R41 |
[In t:MessageType Complex Type] [IsReadReceiptRequested element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R42 |
[In t:MessageType Complex Type] [IsReadReceiptRequested element] A text value of "true" indicates that a read receipt is requested from the recipient of the message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R187 |
[In t:MessageType Complex Type] IsDeliveryReceiptRequested element is xs:boolean type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R45 |
[In t:MessageType Complex Type] [IsDeliveryReceiptRequested element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R46 |
[In t:MessageType Complex Type] [IsDeliveryReceiptRequested element] A text value of "true" indicates that a delivery receipt has been requested from the recipient of the message.
|
<IP_ADDRESS>
|
Server
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R188 |
[In t:MessageType Complex Type] ConversationIndex element is xs:base64Binary ([XMLSCHEMA2] sec 3.2.16) type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R48 |
[In t:MessageType Complex Type] [ConversationIndex element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R49 |
[In t:MessageType Complex Type] [ConversationIndex element] This element is read-only.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:17 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R189 |
[In t:MessageType Complex Type] ConversationTopic element is xs:string ([XMLSCHEMA2] sec 3.2.1) type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R51 |
[In t:MessageType Complex Type] [ConversationTopic element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R52 |
[In t:MessageType Complex Type] [ConversationTopic element] This element is read-only.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:20 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R190 |
[In t:MessageType Complex Type] From element is t:SingleRecipientType type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R53 |
[In t:MessageType Complex Type] From element Specifies the addressee from whom the message was sent.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R54 |
[In t:MessageType Complex Type] [From element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R55 |
[In t:MessageType Complex Type] [From element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R191 |
[In t:MessageType Complex Type] InternetMessageId element is xs:string type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R57 |
[In t:MessageType Complex Type] [InternetMessageId element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R58 |
[In t:MessageType Complex Type] [InternetMessageId element] This element is read-only.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R192 |
[In t:MessageType Complex Type] IsRead element is xs:boolean type.
|
<IP_ADDRESS>
|
Server
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R60 |
[In t:MessageType Complex Type] [IsRead element] This is a read/write element.
|
<IP_ADDRESS>
|
Server
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R61 |
[In t:MessageType Complex Type] [IsRead element]The text value of "true" indicates that the message has been read.
|
<IP_ADDRESS>
|
Server
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R193 |
[In t:MessageType Complex Type] IsResponseRequested element is xs:boolean type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R63 |
[In t:MessageType Complex Type] [IsResponseRequested element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R64 |
[In t:MessageType Complex Type] [IsResponseRequested element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R65 |
[In t:MessageType Complex Type] [IsResponseRequested element] A text value of "true" indicates that a response has been requested.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R194 |
[In t:MessageType Complex Type] References element is xs:string type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R66 |
[In t:MessageType Complex Type] References element Specifies the Usenet header that is used to correlate replies with their original message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R67 |
[In t:MessageType Complex Type] [References element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R68 |
[In t:MessageType Complex Type] [References element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R195 |
[In t:MessageType Complex Type] ReplyTo element is t:ArrayOfRecipientsType type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R69 |
[In t:MessageType Complex Type] ReplyTo element Specifies a collection of addresses to send replies to.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R70 |
[In t:MessageType Complex Type] [ReplyTo element] This element is optional.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:14 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R71 |
[In t:MessageType Complex Type] [ReplyTo element] This is a read/write element.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R196 |
[In t:MessageType Complex Type] ReceivedBy element is t:SingleRecipientType type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:28 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R72 |
[In t:MessageType Complex Type] ReceivedBy element Identifies the delegate in a delegate access scenario.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:28 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R72001 |
[In t:MessageType Complex Type] [ReceivedBy element] This element is read-only.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:26 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R197 |
[In t:MessageType Complex Type] ReceivedRepresenting element is t:SingleRecipientType
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:28 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R73 |
[In t:MessageType Complex Type] ReceivedRepresenting element Identifies the principal in a delegate access scenario.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:28 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R73001 |
[In t:MessageType Complex Type] [ReceivedRepresenting element] This element is read-only.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:29 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R73002 |
[In t:MessageType Complex Type] The type of child element ApprovalRequestData is t:ApprovalRequestDataType (section <IP_ADDRESS>).
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R73008 |
[In t:MessageType Complex Type] [ApprovalRequestData] This element is read-only.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:33 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R73004 |
[In t:MessageType Complex Type] The type of child element VotingInformation is t:VotingInformationType (section <IP_ADDRESS>).
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R73009 |
[In t:MessageType Complex Type] [VotingInformation]This element is read-only.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:36 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R73006 |
[In t:MessageType Complex Type] The type of child element ReminderMessageData is t:ReminderMessageDataType ( section <IP_ADDRESS>).
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R73010 |
[In t:MessageType Complex Type] [ReminderMessageData]This element is read-only.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:39 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R319 |
[In t:ReminderMessageDataType Complex Type] The ReminderMessageDataType schema is <xs:complexType name="ReminderMessageDataType">
<xs:sequence>
<xs:element name="ReminderText" type="xs:string" minOccurs="0"/>
<xs:element name="Location" type="xs:string" minOccurs="0"/>
<xs:element name="StartTime" type="xs:dateTime" minOccurs="0"/>
<xs:element name="EndTime" type="xs:dateTime" minOccurs="0"/>
<xs:element name="AssociatedCalendarItemId" type="t:ItemIdType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R321 |
[In t:ReminderMessageDataType Complex Type] The ReminderText element is xs:string ([XMLSCHEMA2]) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R322 |
[In t:ReminderMessageDataType Complex Type] The ReminderText element specifies the reminder message text.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R323 |
[In t:ReminderMessageDataType Complex Type] The Location element is xs:string type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R324 |
[In t:ReminderMessageDataType Complex Type] The Location element specifies the location of the reminder's associated event.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R325 |
[In t:ReminderMessageDataType Complex Type] The StartTime element is xs:dateTime ([XMLSCHEMA2]) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R326 |
[In t:ReminderMessageDataType Complex Type] The StartTime element specifies the start time of the reminder's associated event.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R327 |
[In t:ReminderMessageDataType Complex Type] The EndTime element is xs:dateTime type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R328 |
[In t:ReminderMessageDataType Complex Type] The EndTime element specifies the end time of the reminder's associated event.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R329 |
[In t:ReminderMessageDataType Complex Type] The AssociatedCalendarItemId element is t:ItemIdType ([MS-OXWSCORE] section <IP_ADDRESS>) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R330 |
[In t:ReminderMessageDataType Complex Type] The AssociatedCalendarItemId element specifies the item id of the reminder's associated event.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R332 |
[In t:VotingInformationType Complex Type]The VotingInformationType schema is <xs:complexType name="VotingInformationType">
<xs:sequence>
<xs:element name="UserOptions" type="t:ArrayOfVotingOptionDataType" minOccurs="0"/>
<xs:element name="VotingResponse" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R334 |
[In t:VotingInformationType Complex Type]The UserOptions element is t:ArrayOfVotingOptionDataType (section <IP_ADDRESS>) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R335 |
[In t:VotingInformationType Complex Type] The UserOptions element specifies the list of voting options.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R336 |
[In t:VotingInformationType Complex Type]The VotingResponse element is xs:string ([XMLSCHEMA2]) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R337 |
[In t:VotingInformationType Complex Type]The VotingResponse element specifies voting response.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R339 |
[In t:VotingOptionDataType Complex Type]The VotingOptionDataType schema is <xs:complexType name="VotingOptionDataType">
<xs:sequence>
<xs:element name="DisplayName" type="xs:string" minOccurs="0"/>
<xs:element name="SendPrompt" type="t:SendPromptType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R341 |
[In t:VotingOptionDataType Complex Type]The DisplayName element is xs:string ([XMLSCHEMA2]) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R342 |
[In t:VotingOptionDataType Complex Type]The DisplayName element specifies the display name for the voting choice.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R343 |
[In t:VotingOptionDataType Complex Type]The SendPrompt element is t:SendPromptType (section <IP_ADDRESS>) type.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R344 |
[In t:VotingOptionDataType Complex Type]The SendPrompt element indicates the prompt behavior when the user selects this voting choice.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R80 |
[In t:MessageDispositionType Simple Type] The value "SaveOnly" means when used in the CreateItemType complex type ([MS-OXWSCORE] section <IP_ADDRESS>.3.2), the email message item is saved in the folder that is specified by the TargetFolderIdType complex type ([MS-OXWSFOLD] section <IP_ADDRESS>).
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:25 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R81 |
[In t:MessageDispositionType Simple Type] [when "SaveOnly" used in CreateItem Type element] Messages can be sent later by using the SendItem operation (section <IP_ADDRESS>) on an ExchangeServiceBinding object.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:30 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R82 |
[In t:MessageDispositionType Simple Type] [when "SaveOnly" used in CreateItem Type element] In this case, an item identifier is returned.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R83 |
[In t:MessageDispositionType Simple Type] The value "SendOnly" means when used in the CreateItemType complex type, the email message item is sent.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:26 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R203 |
[In t:MessageDispositionType Simple Type] The value "SendOnly" means when used in the CreateItemType complex type, the email message item [is sent] but no copy is saved.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:25 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R84 |
[In t:MessageDispositionType Simple Type] [When "SendOnly" used in CreateItem Type element] In this case, an item identifier is not returned.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:34 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R85 |
[In t:MessageDispositionType Simple Type] The value "SendAndSaveCopy" means when used in the CreateItemType complex type, the email message item is sent.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:33 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R204 |
[In t:MessageDispositionType Simple Type] The value "SendAndSaveCopy" means when used in the CreateItemType complex type, the email message item [is sent] and a copy is saved in the TargetFolderIdType complex type.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:31 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R86 |
[In t:MessageDispositionType Simple Type] [When "SendAndSaveCopy" used in CreateItem Type element] In this case, an item identifier is not returned.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:30 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R347 |
[In t:SendPromptType Simple Type]The schema is <xs:simpleType name="SendPromptType">
<xs:restriction base="xs:string">
<xs:enumeration value="None"/>
<xs:enumeration value="Send"/>
<xs:enumeration value="VotingOption"/>
</xs:restriction>
</xs:simpleType>
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R349 |
[In t:SendPromptType Simple Type]The value "None" means no prompt behavior is specified.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R350 |
[In t:SendPromptType Simple Type]The value "Send" means the response is sent immediately when the user chooses a voting option.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R351 |
[In t:SendPromptType Simple Type]The value "VotingOption" means the user is prompted to confirm their choice before sending a response.
|
<IP_ADDRESS>
|
Both
|
Unverified |
-- |
-- |
|
MS-OXWSMSG_R202 |
[In CopyItem] The following is the WSDL port type specification of the CopyItem operation. <wsdl:operation name="CopyItem">
<wsdl:input message="tns:CopyItemSoapIn" />
<wsdl:output message="tns:CopyItemSoapOut" />
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:48 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R166 |
[In CopyItem] The following is the WSDL binding specification of the CopyItem operation. <wsdl:operation name="CopyItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/CopyItem" />
<wsdl:input>
<soap:header message="tns:CopyItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:CopyItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:CopyItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="CopyItemResult" use="literal" />
<soap:header message="tns:CopyItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:48 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R168 |
[In CopyItem] The protocol client sends a CopyItemSoapIn request WSDL message, and the protocol server responds with a CopyItemSoapOut response WSDL message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:48 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R169 |
[In CopyItem] If the CreateItem WSDL operation request is successful, the server returns a CreateItemResponse element, as specified in [MS-OXWSCORE] section <IP_ADDRESS>.2.2, with the ResponseClass attribute, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the CreateItemResponseMessage element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, set to "Success".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:48 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R170 |
[In CopyItem] [A successful CopyItem operation request returns a CopyItemResponse element] The ResponseCode element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the CreateItemResponseMessage element is set to "NoError".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:48 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R170001 |
[In CopyItem] If the CreateItem WSDL operation is not successful, it returns a CreateItemResponse element with the ResponseClass attribute of the CreateItemResponseMessage element set to "Error".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:50 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R170002 |
[In CopyItem] [A unsuccessful CopyItem operation request returns a CopyItemResponse element] The ResponseCode element of the CreateItemResponseMessage element is set to one of the common errors defined in [MS-OXWSCDATA] section <IP_ADDRESS>.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:50 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R107 |
[In CreateItem] The following is the WSDL port type specification of the CreateItem operation.
<wsdl:operation name="CreateItem">
<wsdl:input message="tns:CreateItemSoapIn" />
<wsdl:output message="tns:CreateItemSoapOut" />
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R109 |
[In CreateItem] The following is the WSDL binding specification of the CreateItem operation. <wsdl:operation name="CreateItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/CreateItem" />
<wsdl:input>
<soap:header message="tns:CreateItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:CreateItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:CreateItemSoapIn" part="RequestVersion" use="literal"/>
<soap:header message="tns:CreateItemSoapIn" part="TimeZoneContext" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="CreateItemResult" use="literal" />
<soap:header message="tns:CreateItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R111 |
[In CreateItem] The protocol client sends a CreateItemSoapIn request WSDL message, and the protocol server responds with a CreateItemSoapOut response WSDL message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R112 |
[In CreateItem]If the CreateItem WSDL operation request is successful, the server returns a CreateItemResponse element, as specified in [MS-OXWSCORE] section <IP_ADDRESS>.2.2, with the ResponseClass attribute, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the CreateItemResponseMessage element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, set to "Success".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R113 |
[In CreateItem] [A successful CreateItem operation request returns a CreateItemResponse element] The ResponseCode element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the CreateItemResponseMessage element is set to "NoError".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R113001 |
[In CreateItem] If the CreateItem WSDL operation is not successful, it returns a CreateItemResponse element with the ResponseClass attribute of the CreateItemResponseMessage element set to "Error".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:16 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R113002 |
[In CreateItem] [A unsuccessful CreateItem operation request returns a CreateItemResponse element] The ResponseCode element of the CreateItemResponseMessage element is set to one of the common errors defined in [MS-OXWSCDATA] section <IP_ADDRESS>.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:16 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R148 |
[In DeleteItem] The following is the WSDL port type specification of the DeleteItem operation. <wsdl:operation name="DeleteItem">
<wsdl:input message="tns:DeleteItemSoapIn" />
<wsdl:output message="tns:DeleteItemSoapOut" />
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R150 |
[In DeleteItem] The following is the WSDL binding specification of the DeleteItem operation. <wsdl:operation name="DeleteItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/DeleteItem" />
<wsdl:input>
<soap:header message="tns:DeleteItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:DeleteItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:DeleteItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="DeleteItemResult" use="literal" />
<soap:header message="tns:DeleteItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R152 |
[In DeleteItem] The protocol client sends a DeleteItemSoapIn request WSDL message, and the protocol server responds with a DeleteItemSoapOut response WSDL message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R153 |
[In DeleteItem] If the DeleteItem WSDL operation request is successful, the server returns a DeleteItemResponse element, as specified in [MS-OXWSCORE] section <IP_ADDRESS>.2.2, with the ResponseClass attribute, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the DeleteItemResponseMessage element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, set to "Success".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R154 |
[In DeleteItem] [A successful DeleteItem operation request returns a DeleteItemResponse element] The ResponseCode element, as specified by [MS-OXWSCDATA] section <IP_ADDRESS>, of the DeleteItemResponseMessage element is set to "NoError".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R154001 |
[In DeleteItem] If the DeleteItem WSDL operation request is not successful, it returns a DeleteItemResponse element with the ResponseClass attribute of the DeleteItemResponseMessage element set to "Error".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:38 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R154002 |
[In DeleteItem] [A unsuccessful DeleteItem operation request returns a DeleteItemResponse element] The ResponseCode element of the DeleteItemResponseMessage element is set to one of the common errors defined in [MS-OXWSCDATA] section <IP_ADDRESS>.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:38 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R116 |
[In GetItem] The following is the WSDL port type specification of the GetItem operation.<wsdl:operation name="GetItem">
<wsdl:input message="tns:GetItemSoapIn" />
<wsdl:output message="tns:GetItemSoapOut" />
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R118 |
[In GetItem] The following is the WSDL binding specification of the GetItem operation. <wsdl:operation name="GetItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/GetItem" />
<wsdl:input>
<soap:header message="tns:GetItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:GetItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:GetItemSoapIn" part="RequestVersion" use="literal"/>
<soap:header message="tns:GetItemSoapIn" part="TimeZoneContext" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="GetItemResult" use="literal" />
<soap:header message="tns:GetItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R127 |
[In GetItem] [The BaseShape child element in ItemShape element] Set this element[BaseShape element] to IdOnly to return only the item ID.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:21 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R198 |
[In GetItem] [The BaseShape child element in ItemShape element] Set it[BaseShape element] to AllProperties to return all of the properties used by the server to construct a message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R133 |
[In GetItem] The protocol client sends a GetItemSoapIn request WSDL message, and the protocol server responds with a GetItemSoapOut response WSDL message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R134 |
[In GetItem] If the GetItem WSDL operation request is successful, the server returns a GetItemResponse element, as specified in [MS-OXWSCORE] section <IP_ADDRESS>.2.2, with the ResponseClass attribute, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the GetItemResponseMessage element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, set to "Success".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R135 |
[In GetItem] [A successful GetItem operation request returns a GetItemResponse element] The ResponseCode element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the GetItemResponseMessage element is set to "NoError".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R135001 |
[In GetItem] If the GetItem WSDL operation request is not successful, it returns a GetItemResponse element with the ResponseClass attribute of the GetItemResponseMessage element set to "Error".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:38 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R135002 |
[In GetItem] [A unsuccessful GetItem operation request returns a GetItemResponse element] The ResponseCode element of the GetItemResponseMessage element is set to one of the common errors defined in [MS-OXWSCDATA] section <IP_ADDRESS>.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:38 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R157 |
[In MoveItem] The following is the WSDL port type specification of the MoveItem operation. <wsdl:operation name="MoveItem">
<wsdl:input message="tns:MoveItemSoapIn" />
<wsdl:output message="tns:MoveItemSoapOut" />
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:51 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R159 |
[In MoveItem] The following is the WSDL binding specification of the MoveItem operation. <wsdl:operation name="MoveItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/MoveItem" />
<wsdl:input>
<soap:header message="tns:MoveItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:MoveItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:MoveItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="MoveItemResult" use="literal" />
<soap:header message="tns:MoveItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:51 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R161 |
[In MoveItem] The protocol client sends a MoveItemSoapIn request WSDL message, and the protocol server responds with a MoveItemSoapOut response WSDL message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:54 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R162 |
[In MoveItem] If the MoveItem WSDL operation request is successful, the server returns a MoveItemResponse element, as specified in [MS-OXWSCORE] section <IP_ADDRESS>.2.2, with the ResponseClass attribute, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the MoveItemResponseMessage element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, set to "Success".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:54 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R163 |
[In MoveItem] [A successful MoveItem operation request returns a MoveItemResponse element] The ResponseCode element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the MoveItemResponseMessage element is set to "NoError".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:54 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R163001 |
[In MoveItem] If the MoveItem WSDL operation request is not successful, it returns a MoveItemResponse element with the ResponseClass attribute of the MoveItemResponseMessage element set to "Error".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:55 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R163002 |
[In MoveItem] [A unsuccessful MoveItem operation request returns a MoveItemResponse element] The ResponseCode element of the MoveItemResponseMessage element is set to one of the common errors defined in [MS-OXWSCDATA] section <IP_ADDRESS>.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:55 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R173 |
[In SendItem] The following is the WSDL port type specification of the SendItem operation. <wsdl:operation name="SendItem ">
<wsdl:input message="tns:SendItemSoapIn" />
<wsdl:output message="tns:SendItemSoapOut" />
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:26 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R175 |
[In SendItem] The following is the WSDL binding specification of the SendItem operation. <wsdl:operation name="SendItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/SendItem" />
<wsdl:input>
<soap:header message="tns:SendItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:SendItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:SendItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="SendItemResult" use="literal" />
<soap:header message="tns:SendItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:26 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R177 |
[In SendItem] The protocol client sends a SendItemSoapIn request WSDL message, and the protocol server responds with a SendItemSoapOut response WSDL message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:56 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R178 |
[In SendItem] A successful SendItem operation request returns a SendItemResponse element with the ResponseClass attribute of the SendItemResponseMessage element set to "Success".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:56 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R179 |
[In SendItem] [A successful SendItem operation request returns a SendItemResponse element] The ResponseCode element of the SendItemResponse element is set to "NoError".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:56 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R137 |
[In UpdateItem] The following is the WSDL port type specification of the operation. <wsdl:operation name="UpdateItem">
<wsdl:input message="tns:UpdateItemSoapIn" />
<wsdl:output message="tns:UpdateItemSoapOut" />
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:45 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R139 |
[In UpdateItem] The following is the WSDL binding specification of the UpdateItem operation. <wsdl:operation name="UpdateItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/UpdateItem" />
<wsdl:input>
<soap:header message="tns:UpdateItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:UpdateItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:UpdateItemSoapIn" part="RequestVersion" use="literal"/>
<soap:header message="tns:UpdateItemSoapIn" part="TimeZoneContext" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="UpdateItemResult" use="literal" />
<soap:header message="tns:UpdateItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:45 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R143 |
[In UpdateItem] The protocol client sends an UpdateItemSoapIn request WSDL message, and the protocol server responds with an UpdateItemSoapOut response WSDL message.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:45 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R144 |
[In UpdateItem] If the UpdateItem WSDL operation request is successful, the server returns an UpdateItemResponse element, as specified in [MS-OXWSCORE] section <IP_ADDRESS>.2.2, with the ResponseClass attribute, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the UpdateItemResponseMessage element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, set to "Success".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:45 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R145 |
[In UpdateItem] [A successful UpdateItem operation request returns an UpdateItemResponse element] The ResponseCode element, as specified in [MS-OXWSCDATA] section <IP_ADDRESS>, of the UpdateItemResponseMessage element is set to "NoError".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:45 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R145001 |
[In UpdateItem] If the UpdateItem WSDL operation request is not successful, it returns an UpdateItemResponse element with the ResponseClass attribute of the UpdateItemResponseMessage element set to "Error".
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:17 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R145002 |
[In UpdateItem] [A unsuccessful UpdateItem operation request returns an UpdateItemResponse element] The ResponseCode element of the UpdateItemResponseMessage element is set to one of the common errors defined in [MS-OXWSCDATA] section <IP_ADDRESS>.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:33:17 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R163 |
[In t:MailboxTypeType Simple Type] The type [MailboxTypeType] is defined as follow:
<xs:simpleType name="MailboxTypeType">
<xs:restriction base="xs:string">
<xs:enumeration value="Unknown"/>
<xs:enumeration value="OneOff"/>
<xs:enumeration value="Contact"/>
<xs:enumeration value="Mailbox"/>
<xs:enumeration value="PrivateDL"/>
<xs:enumeration value="PublicDL"/>
<xs:enumeration value="PublicFolder"/>
<xs:enumeration value="GroupMailbox"/>
</xs:restriction>
</xs:simpleType>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R189 |
[In t:NonEmptyStringType Simple Type] The type [NonEmptyStringType] is defined as follow:
<xs:simpleType name="NonEmptyStringType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
</xs:restriction>
</xs:simpleType>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R1033 |
[In t:ArrayOfRecipientsType Complex Type] The type [ArrayOfRecipientsType] is defined as follow:
<xs:complexType name="ArrayOfRecipientsType">
<xs:choice
maxOccurs="unbounded"
minOccurs="0"
>
<xs:element name="Mailbox"
type="t:EmailAddressType"
/>
</xs:choice>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R1147 |
[In t:EmailAddessType Complex Type] The type [EmailAddressType] is defined as follow:
<xs:complexType name="EmailAddressType">
<xs:complexContent>
<xs:extension
base="t:BaseEmailAddressType"
>
<xs:sequence>
<xs:element name="Name"
type="xs:string"
minOccurs="0"
/>
<xs:element name="EmailAddress"
type="t:NonEmptyStringType"
minOccurs="0"
/>
<xs:element name="RoutingType"
type="t:NonEmptyStringType"
minOccurs="0"
/>
<xs:element name="MailboxType"
type="t:MailboxTypeType"
minOccurs="0"
/>
<xs:element name="ItemId"
type="t:ItemIdType"
minOccurs="0"
/>
<xs:element name="OriginalDisplayName"
type="xs:string"
minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R1190 |
[In t:ItemResponseShapeType Complex Type] The element "BodyType" with type "t:BodyTypeResponseType(section <IP_ADDRESS>)" specifies the requested body text format for the Body property that is returned in a response.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:42 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R1197 |
[In t:ItemResponseShapeType Complex Type] The element "AdditionalProperties" with type "t:NonEmptyArrayOfPathsToElementType" specifies a set of requested additional properties to return in a response.
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:32:43 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R1292 |
[In t:SingleRecipientType Complex Type] The type [SingleRecipientType] is defined as follow:
<xs:complexType name="SingleRecipientType">
<xs:choice>
<xs:element name="Mailbox"
type="t:EmailAddressType"
/>
</xs:choice>
</xs:complexType>
|
<IP_ADDRESS>
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R1428001 |
[In Appendix C: Product Behavior]<52> Section <IP_ADDRESS>: Exchange 2010 and above return the MailboxType element in the GetItem operation.
|
8
|
Both
|
Verified |
2020/8/3 7:31:23 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R305 |
[In t:IsUndecidedApprovalRequest Complex Type] [IsUndecidedApprovalRequest element] A text value of "true" indicates that this approval request is awaiting a moderator to approve. |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R306 |
[In t:ApprovalRequestDataType Complex Type] [IsUndecidedApprovalRequest element] A text value of "false" indicates that this approval request is awaiting a moderator to reject the request. |
<IP_ADDRESS> |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R2512 |
[In t:MessageType Complex Type] When the Mailbox element of Sender element include an MailboxType element of t:MailboxTypeType, the value "Mailbox" of t:MailboxTypeType specifies a mail-enabled directory service object. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R2516 |
[In t:MessageType Complex Type] When the Mailbox element of Sender element include an EmailAddress element of t:NonEmptyStringType, the t:NonEmptyStringType simple type specifies a string that MUST have a minimum of one character. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R2912 |
[In t:MessageType Complex Type]When the Mailbox element of ToRecipients element include an MailboxType element of t:MailboxTypeType, the value "Mailbox" of t:MailboxTypeType specifies a mail-enabled directory service object. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R2916 |
[In t:MessageType Complex Type] When the Mailbox element of ToRecipients element include an EmailAddress element of t:NonEmptyStringType, the t:NonEmptyStringType simple type specifies a string that MUST have a minimum of one character. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:31:22 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R4200 |
[In t:MessageType Complex Type] [IsReadReceiptRequested element] A text value of "false" indicates that a read receipt is not requested from the recipient of the message. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R4600 |
[In t:MessageType Complex Type] [IsDeliveryReceiptRequested element] A text value of "false" indicates that a delivery receipt has not been requested from the recipient of the message. |
<IP_ADDRESS> |
Server |
Complete Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R6100 |
[In t:MessageType Complex Type] [IsRead element]The text value of "false" indicates that the message has not been read. |
<IP_ADDRESS> |
Server |
Complete Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R6500 |
[In t:MessageType Complex Type] [IsResponseRequested element] A text value of "false" indicates that a response has not been requested. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:33:11 |
ms-oxwsmsg_log.xml |
|
MS-OXWSMSG_R183 |
[In Appendix C: Product Behavior] Implementation does uses secure communications via HTTPS, as defined in [RFC2818]. (The Exchange 2007 and above follow this behavior.) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R360 |
[In Appendix C: Product Behavior] Implementation does not support the ApprovalRequestDataType complex type. (<6> Section <IP_ADDRESS>: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the ovalRequestDataTypAppre complex type. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R361 |
[In Appendix C: Product Behavior] Implementation does introduce the ApprovalRequestDataType complex type. (This type was introduced in Microsoft Exchange Server 2013 Service Pack 1 (SP1).) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R362 |
[In Appendix C: Product Behavior] Implementation does not support the ArrayOfVotingOptionDataType complex type. (<7> Section <IP_ADDRESS>: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the ArrayOfVotingOptionDataType complex type. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R363 |
[In Appendix C: Product Behavior] Implementation does introduce the ArrayOfVotingOptionDataType complex type. (This type was introduced in Microsoft Exchange Server 2013 Service Pack 1 (SP1).) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R364 |
[In Appendix C: Product Behavior] Implementation does not support the ApprovalRequestData element. (<8> Section <IP_ADDRESS>: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the ApprovalRequestData element. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R365 |
[In Appendix C: Product Behavior] Implementation does introduce the ApprovalRequestData element. (This type was introduced in Microsoft Exchange Server 2013 Service Pack 1 (SP1).) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R182003 |
[In Appendix C: Product Behavior] Implementation does not support the VotingInformation element. (<9> Section <IP_ADDRESS>: Exchange 2007,Exchange 2010, and the initial release of Exchange 2013 do not support the VotingInformation element. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R182004 |
[In Appendix C: Product Behavior] Implementation does introduce the VotingInformation element. (This element was introduced in Exchange 2013 SP1.) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R182005 |
[In Appendix C: Product Behavior] Implementation does not support the ReminderMessageData element. (<10> Section <IP_ADDRESS>: Exchange 2007,Exchange 2010, and the initial release of Exchange 2013 do not support the ReminderMessageData element. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R182006 |
[In Appendix C: Product Behavior] Implementation does introduce the ReminderMessageData element. (This element was introduced in Exchange 2013 SP1.) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R366 |
[In Appendix C: Product Behavior] Implementation does not support the ReminderMessageDataType complex type. (<11> Section <IP_ADDRESS>: Exchange 2007,Exchange 2010, and the initial release of Exchange 2013 do not support the ReminderMessageDataType complex type. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R367 |
[In Appendix C: Product Behavior] Implementation does introduce the ReminderMessageDataType complex type. (This type was introduced in Exchange 2013 SP1.) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R368 |
[In Appendix C: Product Behavior] Implementation does not support the VotingInformationType complex type. (<12> Section <IP_ADDRESS>: Exchange 2007,Exchange 2010, and the initial release of Exchange 2013 do not support the VotingInformationType complex type. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R369 |
[In Appendix C: Product Behavior] Implementation does introduce the VotingInformationType complex type. (This type was introduced in Exchange 2013 SP1.) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R370 |
[In Appendix C: Product Behavior] Implementation does not support the VotingOptionDataType complex type. (<13> Section <IP_ADDRESS>: Exchange 2007,Exchange 2010, and the initial release of Exchange 2013 do not support the VotingOptionDataType complex type. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R371 |
[In Appendix C: Product Behavior] Implementation does introduce the VotingOptionDataType complex type. (This type was introduced in Exchange 2013 SP1.) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R374 |
[In Appendix C: Product Behavior] Implementation does not support the SendPromptType simple type. (<15> Section <IP_ADDRESS>: Exchange 2007,Exchange 2010, and the initial release of Exchange 2013 do not support the SendPromptType simple type. ) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSMSG_R375 |
[In Appendix C: Product Behavior] Implementation does introduce the SendPromptType complex type. (This type was introduced in Exchange 2013 SP1.) |
8 |
Both |
Unverified |
-- |
-- |
|
MS-OXWSCDATA_R21188 |
[In t:ItemResponseShapeType Complex Type] [IncludeMimeContent is] True, specifies the MIME content of an item is returned in a response. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:32:39 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R21189 |
[In t:ItemResponseShapeType Complex Type] otherwise [IncludeMimeContent is] false, specifies [the MIME content of an item is not returned in a response]. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:32:39 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R21193 |
[In t:ItemResponseShapeType Complex Type] [FilterHtmlContent is] True, specifies HTML content filtering is enabled. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:32:41 |
ms-oxwsmsg_log.xml |
|
MS-OXWSCDATA_R21194 |
[In t:ItemResponseShapeType Complex Type] otherwise [FilterHtmlContent is] false, specifies [HTML content filtering is not enabled]. |
<IP_ADDRESS> |
Both |
Complete Verified |
2020/8/3 7:32:41 |
ms-oxwsmsg_log.xml |


Man Utd team news: Solskjaer confirms duo to miss Sheffield Utd clash, timeline on return
by Ron CarneMan Utd boss Ole Gunnar Solskjaer will be without both Paul Pogba and Scott McTominay for their encounter with Sheffield Utd on Sunday.
The Red Devils return to action after the international break hoping to continue to climb the Premier League table as they currently sit in seventh place.
SEE MORE: ‘He is that level’ – Premier League boss says touted Man Utd target is good enough to make switch
A win this weekend could move them up to fifth spot, but time will tell if they can make it three wins in their four league outings as Solskjaer hopes to build some momentum heading into the festive period.
The visitors to Bramall Lane will have to do so without Pogba and McTominay though, as the club have noted on their official site that the midfield pair will both miss out.
It’s added from Solskjaer that McTominay could return from his ankle injury at the start of December for the encounters with Tottenham and Man City, while he noted that Pogba isn’t likely to be back for a while yet either.
The French international had his cast removed on his ankle over the international break, but naturally he will now enter the next phase of his rehabilitation to get his match fitness back and to be sharp enough to be considered for the senior side.
The report adds that Axel Tuanzebe, Diogo Dalot, Luke Shaw, Eric Bailly and Nemanja Matic have returned to some form of training and so time will tell how long it takes them to get up to speed and put themselves in contention for a place in the match day squad.
That in itself is encouraging though, as although it sounds as though Man Utd may have to be patient for a little longer, the fact that a number of first-team stars are edging closer to making their respective comebacks ahead of the festive period will provide Solskjaer with a huge boost in the weeks ahead.


Toggle navigation
COMPANY
Personal Info Management
Settings
Reload
Init DB
Delete DB
Employee List
New
Personal Info
Save
Number
Name
Gender
Date of Birth
Telephone
Emergency Contact Name
Emergency Contact Address
Emergency Contact Tel
Passport Number
Passport Date
Passport Name
Type of Lending


| EasyRoads3D V3 Manual |
Getting Started
IMPORTANT: always check the Release Notes section for important information! Download Files From www.unityterraintools.com The zip file contains the following items: 1. EasyRoads3D.unityPackage
Download Files From the Unity Asset Store The v3 betas are part of the asset store download as a separate unity package. The _Readme file in the EasyRoads3D root directory includes more info. Alternatively you can import the beta by deselecting all files in the import window after the download has finished. Keep the v3 beta package at the top selected. It will be imported in /Assets/EasyRoads3D/. Double click that file and the v3 beta import window will appear, import all files.
Menu > Assets > Import Package > Custom Package... This will open the file dialog window. Browse to the EasyRoads3D folder and select the EasyRoads3D.unityPackage. All necessary assets will be imported in your project. A new menu item EasyRoads3D will be available in the top menu. Click on an empty area in the top menu bar if the EasyRoads3D menu item is not visible.
After importing the package the following new menu item will be added to the main menu in the Unity Editor: Main Menu > GameObject > 3D Object > EasyRoads3D > New Road Network A new game object "Road Network" will be created in the scene hierarchy and auto selected. In the Inspector you will see the
The current beta requires activation with an EasyRoads3D Pro serial number (website version). If you have used the v2 package from our website before or the demo project, no activation is required. Otherwise you will see the activation box below.
Upgrading a v2 project is not yet part of the package. Scripts are available to turn a v2 road into a v3 road. Please contact us for this.
|
|||


Cultural Blog: Stereotype Threat
April 5, 2015
Up until now, I haven’t really thought about how other people’s stereo typing of me affects my actions. I’m originally from Mongolia, but, despite that fact, I am usually thrown in with all other Asians. I am, in many people’s eyes, Asian.
So, when people meet me, they think I’m passive, quiet and submissive. I often get lines thrown my way like “Oh, you must be very sweet” or “I have a friend who is from Japan and she is just a darling.” In my mind, I am wondering if I should say “Oh, I know someone from Wisconsin and they like to eat potatoes!”
However, now I am wondering if how other people see me actually changes the way I act. Do I say “sorry” too often? Am I less likely to speak my mind in a group setting because I already know what people are thinking of me?
Before I decided to dedicate my days and nights to coding at Dev Bootcamp, I was an interior designer. I spent hours with clients showcasing my designs to them, but there were times when they pushed back and made choices that I believed ruined the plan I had laid out for them. Though I protested, I wonder now if Stereotype Threat made me more submissive than I should have been.
After all, in my head, I knew what was right, but for some reason, I didn’t fully fight for what I believed to be correct. However, now that I am aware of the condition, I’ll make sure that I will act exactly how I feel is right rather than how other’s believe I should act. It’s very interesting to think that the energy of someone else’s opinion can influence you so firmly.
To other people out there who might come under a Stereotype Threat, I would urge them to listen to their guts in regards to what they should be saying or doing. Our society places people into these neat little boxes where you are expected to stay.
There is a great danger of doing so even if you are not fully aware you are doing it. For this reason, I will be mindful of my actions and urge others to be the same. After all, if you can control what you do, you’ll break free of the one person who could be holding you back:
Yourself.


First Bootstrap Page
First Name:
Last Name:
Sex:
Male
Female
Description:
Submit
Table
First Name
Last Name
Sex
Description
John
Doe
Male
Doctor
Mary
Moe
Female
Manager
July
Dooley
Female
Designer


GoFortune
Memorize a card from the deck then click
Continue
{{info}}
Select
Select
Select
Your card:
Your fortune (from Twitter):
loading ...
Start Over
View Scores
Source code:
https://github.com/gophergala2016/gofortune
Start Over
Card popularity:
{{card.Score}}


Psalms 83:18
That men may know that thou, whose name alone is JEHOVAH, art the most high over all the earth.


Innovation area and skills
Innovation area
Type
| Application number | Title | Lead organisation | Assigned | Notified | Accepted | Started | Submitted | Remove |
|---|---|---|---|---|---|---|---|---|
| 1 | Application name | Lead organisation | 3 | Yes | Yes | Yes | Yes | Remove |
No applications have been assigned to this assessor.
| Application number | Title | Lead organisation | Reason | Assessors |
|---|---|---|---|---|
| 1 | Application name | Lead organisation | 3 |
No applications have been rejected by this assessor.
| Application number | Title | Lead organisation | Assessors | Action |
|---|---|---|---|---|
| 1 | Application name | Lead organisation | 3 |
No applications have been previously assigned to this assessor.
Applications
These are the rest of the applications for this competition. You can assign more to this assessor.
2
Applications
| Application number | Title | Lead organisation | Assessors | Accepted | Submitted | Action |
|---|---|---|---|---|---|---|
| The potential for glucose based contact lens monitoring in the management of type 2 diabetes 123 | Wessex University | 4 | 2 | 1 |


The Bee Machine
a user-generated database for collecting honeybee population and health data
Honeybee Health Dataset


"BEZEK "lightning. (1.) The residence of Adoni-bezek, in the lot of Judah(Judges 1:5). It was in the mountains, not far from Jerusalem. Probably the modern Bezkah, 6 miles south-east of Lydda. (2.) The place where Saul numbered the forces of Israel and Judah (1 Samuel 11:8); somewhere in the centre of the country, near the Jordan valley. Probably the modern Ibzik, 13 miles north-east of Shechem.
"BEZEK "lightning. (1.) The residence of Adoni-bezek, in the lot of Judah(Judges 1:5). It was in the mountains, not far from Jerusalem. Probably the modern Bezkah, 6 miles south-east of Lydda.
(2.) The place where Saul numbered the forces of Israel and Judah (1 Samuel 11:8); somewhere in the centre of the country, near the Jordan valley. Probably the modern Ibzik, 13 miles north-east of Shechem.


Wayne Bennett predicts more Great Britain disappointment after Papua New Guinea defeat
PAPUA NEW GUINEA 28-10 GREAT BRITAIN: The Lions turned in a dismal second-half display to put an end to their woeful tour
by Julie StottLions coach Wayne Bennett has predicted more disappointment unless his bosses are up to the demands of international rugby.
The Lions self-destructed here in the second half in a bitterly disappointing end to a disastrous tour.
Tonga announced a national holiday in the wake of beating the Lions and Papua New Guinea may well do the same.
With New Zealand also winning twice, it is a tour that Bennett described as “obviously disappointing because we have underperformed”.
But the Aussie, now out of contract, insists the same could happen again if bosses don’t improve the preparation.
He said: “England or Great Britain cannot sit back and think that they can come out of a good competition and have good players and can come in under-prepared.
“Australia come in with an Origin Series behind them, New Zealand came in having played Australia at the end of the season.
“Everyone is doing more preparation than we are. If we want to compete with them, we have got to get back to that level.”
Neither the Lions nor England had a mid-season Test this year and the World Cup Nines also prevented the Lions having a proper training camp ahead of the tour.
England are expected to play the Kiwis in June and Bennett (above) said: “We definitely do need that. We didn’t have anything this year and it had a bit of impact on us.
“We have not nailed our preparation for the last couple of years.
“We need a 10-day to 12-day period otherwise there will continue to be disappointment.”
Bennett insists he wants a new deal to coach England through to the 2021 World Cup, saying: “I do not think anyone can say I haven’t got the appetite.”
The Lions dominated most of the first half, with Blake Austin touching down and Josh Hodgson grabbing a second try.
But they allowed Edwin Ipape to cross in the dying seconds of the half and the Kumuls then snuffed the life out of the Lions with four second- half tries.
Bennett said: “Whilst we have to swallow a bitter pill, the other side of the ledge is that the international game is getting stronger.”


Review your courses today.
RIT Student Government
encourages you to review your courses.
Course
Instructor
{{#each sections}}
{{ this.title }}
{{ this.instructor }}
Start Evaluation
{{/each}}


Hey,
Loving your work.
Can I suggest that "Bellow you see your personal favored threads. You can add new threads by click on the button "Add to favorites" at the top/bottom of a thread page. When you post at a thread, the thread is automatically favored to easy follow your discussions. Threads sorted by ID (newest first)."
is changed to
"Below you see your personal favourite threads. You can add new threads by clicking on the button "Add to favorites" at the top/bottom of a thread page. When you post in a thread, the thread is automatically added to your favourites so you can follow the discussion. Threads are sorted by ID (newest first)."
or similar.


--- layout: post status: publish published: true title: "迁徙的鸟，几个难忘的场景" author: Leask author_login: leask author_email<EMAIL_ADDRESS>author_url: https://leaskh.com wordpress_id: 25 wordpress_url: http://leaskh.wordpress.com/2010/02/09/%e8%bf%81%e5%be%99%e7%9a%84%e9%b8%9f%ef%bc%8c%e5%87%a0%e4%b8%aa%e9%9a%be%e5%bf%98%e7%9a%84%e5%9c%ba%e6%99%af date: '2010-02-09 14:37:25 +0800' date_gmt: '2010-02-09 14:37:25 +0800' categories: tags: [] comments: - id: 372 author: Xiaoni author_email: '' author_url: '' date: '2010-02-09 16:10:41 +0800' date_gmt: '2010-02-09 16:10:41 +0800' content: Beautiful.  ---


DWR generates Javascript code that is similar to the Java code that you remoted, using the <create ... > element, in your dwr.xml file.
The biggest challenge in creating a remote interface to match Java code across Ajax is the (usually) asynchronous nature of Ajax, compared to the synchronous nature of a normal Java call.
DWR solves this problem by introducing a callback function that is called when the data is returned from the server.
There are 2 recommended ways to make a call using DWR. Either by appending a callback function to the parameter list or by appending a call meta data object.
It is also possible to put the callback function at the start of the parameter list, however this option is not advised because there are some issues when dealing with automatic http objects (see "Alternative Method"). This method mostly remains for backwards compatibility.
Suppose we have a Java method that looks like this:
public class Remote { public String getData(int index) { ... } }
We can use this from Javascript as follows:
<script type="text/javascript" src="[WEBAPP]/dwr/interface/Remote.js"> </script> <script type="text/javascript" src="[WEBAPP]/dwr/engine.js"> </script> ... function handleGetData(str) { alert(str); } Remote.getData(42, handleGetData);
'42' is just the parameter to the getData()
Java function - see above.
Alternatively you can use the all-in-one-line version:
Remote.getData(42, function(str) { alert(str); });
The alternative syntax is to make use of a call meta-data object that specifies the callback function and (optionally) other options. The example above would become:
Remote.getData(42, { callback:function(str) { alert(str); } });
This method has some advantages: Depending on your style it may be easier to read, but more importantly it allows you to specify extra call options.
In addition to the callback meta data you can also specify a timeout and an errorHandler. For example:
Remote.getData(42, { callback:function(str) { alert(str); }, timeout:5000, errorHandler:function(message) { alert("Oops: " + message); } });
There are some instances when it might not be tricky to distinguish between the various callback placement options. (Remember that Javascript does not support overloaded functions). For example:
Remote.method({ timeout:3 }, { errorHandler:somefunc });
One of the 2 parameters is a bean parameter and the other is a call meta-data object but we have no way of telling which. In a cross-browser world we have to assume that null == undefined. So currently, the rules are:
Suppose you have an exposed Java method like this:
public class Remote { public void setPerson(Person p) { this.person = p; } }
And Person
looks like this:
public Person { private String name; private int age; private Date[] appointments; // getters and setters ... }
Then you can call this from Javascript like this:
var p = { name:"Fred Bloggs", age:42, appointments:[ new Date(), new Date("1 Jan 2008") ] }; Remote.setPerson(p);
Any fields missing from the Javascript representation will be left unset in the Java version.
Since the setter returned 'void' we did not need to use a callback and could just leave it out. If you want to be notified of the completion of a server-side method that returns void then you can include a callback method. Obviously DWR will not pass any data to it.


--- layout: post status: publish published: true title: 'ELCA: Software Development Engineer' author: display_name: PR Team login: prteam email<EMAIL_ADDRESS>url: '' author_login: prteam author_email<EMAIL_ADDRESS>wordpress_id: 982 wordpress_url: http://gatheringtalents.com/?p=982 date: '2012-06-07 11:53:43 +0000' date_gmt: '2012-06-07 03:53:43 +0000' categories: - Developer - Jobs tags: [] comments: [] ---
Responsibilities:
As a Software Development Engineer you will be in a team with other highly motivated engineers.
You will actively participate in the development of software applications for our customers.
Supported by state-of-the-art methods and technologies, you will have opportunities to be involved in the technical aspects of the complete project life-cycle, from requirements clarification and technical design to coding, testing, integration and deployment.
We offer:
- Professional working environment
- Projects using state-of-the-art technologies
- Extensive coaching and training
- Attractive remuneration packages
- Comfortable workplaces
- Travel opportunities
Requirements:
You hold a bachelor’s degree in Computer Science, Information and Communications Technology of Software Engineering, and maybe already have a first work experience in software development for the Java or .NET platform, for which you have a very strong interest in software design, programming and testing.
Being technically confident, flexibility, a strong team spirit, as well as good reading skills in English are essential for the job.
Company information:
ELCA is an independent Swiss IT Services Company and a leader in software development, system integration and business consulting. ELCA has helped its clients to leverage information technology innovations successfully for over 40 years. The company has 500 employees, more than 400 of whom are highly skilled engineers. With its headquarters in Lausanne, ELCA has subsidiaries in Zurich, Geneva, Berne, London, Paris, Madrid and Ho-Chi-Minh City (offshore development).
ELCA Vietnam plays a strategic role to maintain the group’s competiveness. Our continuous success is based on a strong commitment to quality and project management in combination with technological leadership and thorough business understanding. With our Quality System appraised at CMMI-ML3, we are able to deliver and maintain customized software for a large number of customers.


DRAGON CHOW A film review by Thomas E. Billings Copyright 1989 Thomas E. Billings
Synopsis: In modern West Germany, a young man from Pakistan, a "gastarbeiter" or guest worker, tries to gain legal residence. He eventually gets an illegal job in a Chinese restaurant. Later he and a Chinese waiter from the restaurant try to open their own restaurant. A human interest story detailing the difficulties faced by guest workers in Germany; a good (but not great) film.
West Germany (English subtitles), black-and-white, 1988, 75 minutes. Director/Writer: Jan Schutte
The film is centered on Shezad, a personable young man from Pakistan, who is in Hamburg, West Germany, trying to gain legal residence via political asylum. He is receiving welfare while his application is being processed. He lives with his friend Rashid, also from Pakistan and also applying for political asylum. They live in a seedy "welfare hotel," with immigrants and guest workers from other third world countries.
Eventually, with the help of a con man, Shezad gets an illegal job at a second-rate Chinese restaurant. The restaurant is owned by a Chinese man; the staff includes a Chinese waiter, Shezad and two other guest workers for kitchen help, and a tyrannical German cook. The cook has a very high opinion of himself and his cooking, and is very critical of his kitchen staff; he frequently refers to them as "wops."
Shezad and the Chinese waiter, Xiao, become friends. They share a common dream - to open their own restaurant. Xiao can satisfy the all the regulations necessary to open a restaurant under the German Restaurant Law, save one - the requirement of 5000 marks capital. Shezad and Xiao team up to pursue their dream of owning a restaurant, and the story continues from there.
This film appears to have been done on a low-budget, and is mostly a human relations study. It principally deals with the aspirations of third- world immigrants and guest workers in West Germany. These immigrants are depicted as forming a lower (economic) class, with limited interaction with German society; a society that is indifferent and sometimes hostile to them.
The major attraction of the film is the characters; as the film progresses you begin to identify with the main characters and understand the difficult situation they face. Gaining legal residence in West Germany is difficult; many apply but few are chosen.
Overall, this is a good film (it has won many awards at film festivals all over the world). However, it has a slow pace and is oriented towards human relations; it is not an "action" film.
Print Source: New Yorker Films; no information available on release plans.
Reviewer: Thomas E. Billings, Department of Statistics University of California, Berkeley Reviewer contact<EMAIL_ADDRESS>.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Tiger Update - Smaller rating stars on Floater
-
NATO
I am quite new to Synergy, fantastic program, really can't use iTunes without it these days! Well worth 5
-
Jamvan
I've noticed the same thing and I don't know of a way to change them. I noticed a change with some other third party products in Tiger too who's font size changed so I don't think it's specific to just Synergy.
-
NATO
Yeah, it's strange how Tiger has changed a few subtle things with 3rd party apps.. right now the smaller stars isn't mission-critical, but it is a little hard to see from a distance, and I definitely loved it the way it was
-
Greg Hurrell
Known issue, fixed in Synergy Advance. Hope to have a fix ready in Synergy Classic soon:
https://wincent.com/a/support/bugs/show_bug.cgi?id=179
Please file any further comments against that bug report.
Reply
This topic is now closed.


The $location service parses the URL in the browser address bar (based on the window.location) and makes the URL available to your application. Changes to the URL in the address bar are reflected into $location service and changes to $location are reflected into the browser address bar.
The $location service:
For more information see Developer Guide: Using $location
absUrl();
This method is getter only.
Return full url representation with all segments encoded according to rules specified in RFC 3986.
| string | full url |
url([url]);
This method is getter / setter.
Return url (e.g. /path?a=b#hash
) when called without any parameter.
Change path, search and hash, when called with parameter and return $location
.
| Param | Type | Details |
|---|---|---|
|
url
(optional)
|
string |
New url without base prefix (e.g. |
| string | url |
protocol();
This method is getter only.
Return protocol of current url.
| string | protocol of current url |
host();
This method is getter only.
Return host of current url.
| string | host of current url. |
port();
This method is getter only.
Return port of current url.
| Number | port |
path([path]);
This method is getter / setter.
Return path of current url when called without any parameter.
Change path when called with parameter and return $location
.
Note: Path should always begin with forward slash (/), this method will add the forward slash if it is missing.
| Param | Type | Details |
|---|---|---|
|
path
(optional)
|
stringnumber |
New path |
| string | path |
search(search, [paramValue]);
This method is getter / setter.
Return search part (as object) of current url when called without any parameter.
Change search part when called with parameter and return $location
.
// given url http://example.com/#/some/path?foo=bar&baz=xoxo
var searchObject = $location.search();
// => {foo: 'bar', baz: 'xoxo'}
// set foo to 'yipee'
$location.search('foo', 'yipee');
// => $location
| Param | Type | Details |
|---|---|---|
| search | stringObject.<string>Object.<Array.<string>> |
New search params - string or hash object. When called with a single argument the method acts as a setter, setting the If the argument is a hash object containing an array of values, these values will be encoded as duplicate search parameters in the url. |
|
paramValue
(optional)
|
stringNumberArray.<string>boolean |
If If If If |
| Object | If called with no arguments returns the parsed |
hash([hash]);
This method is getter / setter.
Return hash fragment when called without any parameter.
Change hash fragment when called with parameter and return $location
.
| Param | Type | Details |
|---|---|---|
|
hash
(optional)
|
stringnumber |
New hash fragment |
| string | hash |
replace();
If called, all changes to $location during current $digest
will be replacing current history
record, instead of adding new one.
Broadcasted before a URL will change. This change can be prevented by calling
preventDefault
method of the event. See $rootScope.Scope
for more
details about event object. Upon successful change
$locationChangeSuccess is fired.
Broadcasted after a URL was changed.


Icthus is a Bible app for iPhone and iPad. Its goal is to present the text of the Bible in a clean, modern interface.
Most of our Bibles are designed for reference. Icthus is designed for reading.
Icthus removes chapter headings and footnotes. Chapter and verse numbers are hidden until you need them. The font is large with plenty of space between lines. No red text, no narrow columns, nothing to interrupt your time with the Word.
Features
Extremely Readable
Icthus removes distractions so you can read the Bible like any other book.
Free and Open Source
Icthus is completely free. You can even have the source code.
Easy Navigation
No matter where you are, you can get to any chapter in the Bible in just a few taps.
Saved History
Reading multiple books at once? Icthus keeps track of where you've been so you can keep your place in as many books as you need.
iCloud Sync
Icthus keeps your History the same on all your devices, so you can always pick up where you left off.
Multiple Translations
Icthus offers the World English Bible, the American Standard Version, and the King James Version.
Ready to download Icthus?
Want to get in touch? Check out the contact page.


I graduated from East China Normal University in Shanghai for my bachelor degree, andmy major was landscape architecture. In that experience, I started to learn the basicknowledge of design. My major courses were environmental analysis, plants in landscape,construction drawing, studio work, and some software courses. The study aboutanthropology and psychology interested me greatly. For my graduation design project, Iapplied praxeology and environmental psychology to the project. I found that humanisticcare is the most important thing we need to notice in the process of design. My project wasa transformation of an old park. The goal of this design was trying to create an interestingathletic oriented park and play area for kids, this design consistently received high praisefrom my professors. In this project I used AutoCAD, Sketch Up, Adobe CS (Photoshop andIllustrator especially), and also Microsoft Office Suites
I feel confident that, given the opportunity, I can make an immediate contribution to anycorporation. I would appreciate the opportunity to meet with you to discuss yourrequirements. I have enclosed a resume as well as my portfolio for your review
I graduated from East China Normal University in Shanghai for my bachelor degree, andmy major was landscape architecture. In that experience, I started to learn the basicknowledge of design. My major courses were environmental analysis, plants in landscape,construction drawing, studio work, and some software courses
An internship job in Huanyi Studiao in the East China NormalUniversity. (2011.7 - 2011.8)An internship job in Shanghai Xian Dai Architectural DesignCompany. (2015.5 - 2015.8)Teaching assistant job in the department of LandscapeArchitecture in the University of Guelph.( 2015.9 - 2016.4)
GPA: 3.23
GPA: 3.56
Got the Second Prize Scholarship in the academic year of2011-2012 of East China Normal University.The Excellent Prize in the students’ work exhibition of 9thNational Higher Art College Landscape and Environmental ArtDesign Annual Teaching Meeting.Got the W.E. Coates Memorial Scholarship (2014.11
When forced indoors, I follow a number of sci-fi and fantasy genre movies and television shows, I am an aspiring chef, and I spend a large amount of my free time exploring the latest technolgy advancements in the front-end web development world.


{% load i18n %} {% comment %} Paymill requires a custom form with some JS. {% endcomment %} {% comment %} This is the form that will hold the actual token that will be sent to the server {% endcomment %} You have to enable JavaScript to be able to pay
{% trans "Card number" %} {% trans "The digits on front of your credit card" %}
{% trans "Expiry date" %} {% trans "The date your credit card expires. Find this on the front of your credit card" %}
{% trans "Name" %} {% trans "The name as it appears on your credit card" %}
{% trans "CVC" %} {% trans "Three digits on the back of your card for security" %}
{% trans "Account number" %}
{% trans "Bank code" %}
{% trans "Account holder" %}


Book Title
Author:
Category:
Horror
Page Count:
150
Rating:
5/5
SUMMARY:
AMAZON
BARNES & NOBLE
OPEN LIBRARY


National parks in India are IUCN category II protected areas. India's first national park was established in 1936 as Hailey National Park, now known as Jim Corbett National Park, Uttarakhand.
Jim Corbett National Park
Jim Corbett National Park is the oldest national park in India and was established in 1936 as Hailey National Park to protect the endangered Bengal tiger. It is located in Nainital district of Uttarakhand and was named after Jim Corbett who played a key role in its establishment. The park was the first to come
under the Project Tiger initiative. The park has sub-Himalayan belt geographical and ecological characteristics. An ecotourism destination, it contains 488 different species of plants and a diverse variety of fauna. Corbett National Park comprises 520.8 km2 (201.1 sq mi) area of hills, riverine belts, marshy depressions, grasslands and a large lake. The elevation ranges from 1,300 to 4,000 ft (400 to 1,220 m). Winter nights are cold but the days are bright and sunny. It rains from July to September. Dense moist deciduous forest mainly consists of sal, haldu, peepal, rohini and mango trees. Forest covers almost 73%
of the park, 10% of the area consists of grasslands. It houses around 110 tree species, 50 species of mammals, 580 bird species and 25 reptile species.
Rajaji National Park
Rajaji National Park is an Indian national park and tiger reserve that encompasses the Shivaliks, near the foothills of the Himalayas. The park is spread
over 820 km2. In 1983, three wildlife sanctuaries in the area namely, Chilla, Motichur and Rajaji sanctuaries were merged into one. Rajaji National Park has
been named after C. Rajagopalachari (Rajaji), a prominent leader of the Freedom Struggle, the second and last Governor-General of independent India and one of the first recipients of India's highest civilian award Bharat Ratna (in 1954). Rajaji became the second tiger reserve in Uttarakhand on 15 April 2015.
Gangotri National Park
Gangotri National Park is a national park located in Uttarkashi District Garhwal Range of Uttarakhand, India. The size of this national park is about 2,390 square km. It is the third largest National park of India. The park provides majestic beauty of coniferous forests and grandeur of glacial world combined with lush green meadows.
Govind Pashu Vihar National Park and Sanctuary
Govind Pashu Vihar National Park and Sanctuary is a national park in Uttarakhand, India established initially as a wildlife sanctuary in 1955, and later converted into a national park. It is named after a prominent Indian freedom fighter and politician Govind Ballabh Pant, who became Home Minister in 1950 and is remembered for his achievement in establishing Hindi as an official language. The park was established on March 1, 1955, and is situated in the Uttarkashi district in the Indian state of Uttarakhand. The park lies in the higher reaches of the Garhwal Himalayas. The total area of Govind Pashu Vihar National Park and Sanctuary is 958 km2 (370 sq mi). The Snow Leopard Project started by the Government of India is being managed at this sanctuary. Also,
it is one of the remaining strongholds in the Himalayas of the bearded vulture, a vital ecological catalyst.
Valley of Flowers National Park
Valley of Flowers National Park is an Indian national park, located in West Himalaya, in the state of Uttarakhand and is known for its meadows of endemic alpine flowers and the variety of flora. This richly diverse area is also home to rare and endangered animals, including the Asiatic black bear, snow leopard, musk deer, brown bear, red fox, and blue sheep. Birds found in the park include Himalayan monal pheasant and other high altitude birds.
At 3352 to 3658 meters above sea level, the gentle landscape of the Valley of Flowers National Park complements the rugged mountain wilderness of Nanda Devi
National Park to the east. Together, they encompass a unique transition zone between the mountain ranges of the Zanskar and Great Himalaya. The park stretches over an expanse of 87.50 km2 and it is about 8 km long and 2 km wide. Both parks are encompassed in the Nanda Devi Biosphere Reserve (223,674 ha) which is further surrounded by a buffer zone (5,148.57 km2).
Nanda Devi National Park
The Nanda Devi National Park or Nanda Devi Biosphere Reserve, established in 1988 , is a national park situated around the peak of Nanda Devi (7816 m) in the state of Uttarakhand in northern India. The entire park lies at an elevation of more than 3,500 m (11,500 ft) above mean sea level. The National Park was inscribed a World Heritage Site by UNESCO in 1988. The latter was expanded and renamed to Nanda Devi and Valley of Flowers National Parks in 2005.
Within the National Park lies the Nanda Devi Sanctuary, a glacial basin surrounded by a ring of peaks between 6,000 metres (19,700 ft) and 7,500 m (24,600 ft) high, and drained by the Rishi Ganga through the Rishi Ganga Gorge, a steep, almost impassable defile. The National Park is embedded in the 2,236.74 km2
(863.61 sq mi) sized Nanda Devi Biosphere Reserve, which, in turn, is encompassed in the 5,148.57 km2 (1,987.87 sq mi) buffer zone around the Nanda Devi and
Valley of Flowers National Parks UNESCO site.


Does not validate JavaScript code; incorrect JavaScript code may lead to unexpected results.
Enter/Paste JavaScript code in the text box below.
Copy bookmarklet code from the text box below or drag the below bookmarklet to your bookmarks.
Bookmarklet


CY Tech
by Code Yellow BV
Posts
About
Code:
Django Binder
MobXspine
Real Time
© 2017 Code Yellow.
All rights reserved.


Web Design
107 Abbott St. Apt. 13
Providence, RI 02906
(401)-649-3887
<EMAIL_ADDRESS>Skills
- Basic computer knowledge
- collaborative
Experience
PVD Elite Coders, 41 Fricker St, Providence, RI, 02903 - Html internship
August 05, 2019- August 26, 2019
Education
E-Cubed Academy,812 Branch Ave, Providence, RI 02904 - High School Diploma
Sep 4, 2014 - Jun 4, 2018
Activities
I go to church every Thursdays and Sundays, I also play the piano for church and other church activities where we give out clothes,food and donate blood. I do a little bit of gaming in my spare time. sometimes go camping with my church or go to theme parks every year. I am also currently in college. I'm passionate about working with technology, and playing music.


I like stuff. Like crossfit and rockclimbing and music. And coding :)
I like code and stuff.
Send a bird (no doves, please) with a written note attached to the leg.Twitter.


@(httpMethod: String, d2path: String, headers: String, requestBody: Option[String], responseBody: Option[String], metadata: com.linkedin.data.DataMap, csrfProvider: com.linkedin.restsearch.security.CsrfProvider)(implicit request: play.api.mvc.RequestHeader) @import play.filters.csrf.CSRF @main("restli: HTTP Console") {
When you click 'Send', a request is made against live services running in @metadata.get("environment"). Please keep this in mind, particularly when creating, updating and deleting data.
Pre-filled examples contains random generated values for keys and field values. Please substitute in appropriate values.
The "Permlink" button will create a link that captures all current input values. You can send the link to anybody who wants to replicate what you see here.


width 50%, no min or max
width 80%, max of 1000px
width 30%, min of 200px
the height is set to 25%, but there is no affect
this height is also set to 25%, and since it's within a div containing block who has a set height of 500px this p will resize in relation to that.


If you’re ready to see the world and be left speechless, we welcome you to come on a journey with WayFinder.