Assessments
Recommendation, 2007 April 15
Editor:
Chuck Allen, HR-XML Consortium
Kim Bartkus, HR-XML Consortium
Authors:
Romuald Restout, Humanuo; Drew Cox, ePredix
Contributors:
Doug Walner, PSI; Chris Simpson, Oracle; Bill Kerr, Oracle; Brad Whitney, American Background Check; Craig Corner, First Advantage; and other members of the Assessment Order project.
Copyright statement
©2005 HR-XML. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher.
Abstract
This document describes order requests to providers of assessment and testing services. It also includes the return of assessment status and results.
Status of this Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Table of Contents
1.4.1 Items within the Design Scope
1.4.2 Items Outside of Design Scope
2 Supported Business Processes
3.2 AssessmentOrderAcknowledgement
4 Implementation Considerations
4.2 Laws Governing Consumer/Investigative Reports
5 Appendix A - Document Version History
6 Appendix B – Related Documents
7 Appendix C – Grade/Band vs. Score
8 Appendix D – Reference Examples
8.2 Assessment Order Acknowledgement
The Assessments specification and schemas support order requests to providers of assessment and testing services. The specification also is designed to support the return of assessment status and results. This specification includes the following schemas:
· AssessmentOrderAcknowledgement
· AssessmentOrderRequest
· AssessmentStatusRequest
· AssessmentCancelRequest
· AssessmentResult
An additional schema is also included in the specification that merely acts as a placeholder for types that are used throughout other schemas
· AssessmentTypes
Also see the related Assessment Catalog specification, which allows for the exchange of, and queries against, an assessment catalog (see Appendix B – Related Documents).
Assessments have always been part of the HR function. At selection or evaluation time, managers have always tried to evaluate the skills of candidates/employees.
Companies are now provided with numerous tools and/or services to help managers assess individuals. Those tool and services are most often offered by assessment providers, which perform and/or evaluate the assessment on behalf of companies.
Currently HR systems, customer systems, and the assessment vendor systems are unable to universally exchange information. This leaves HR customers with the burden of keying data to multiple systems or writing programs to facilitate a particular vendor. The requirement to develop custom interfaces to each assessment firm makes it more difficult and expensive for employers or HR service partners to establish business relationships with background checking firms.
Employers are increasingly interested in using the assessment instruments, tools, and expertise offered by third-party assessment services. While many third-party assessment tools have been well established as valid predictors of performance, it can be difficult and expensive to integrate a collection of these third-party assessments within HR systems. Integration is important, since employers want to monitor assessment statuses and apply assessment results within the workflow and decision-support framework provided by their HR or recruiting systems.
Additional results
When passing assessment results from the provider to the customer, some information cannot be passed with the current specification. Some examples of the missing information are: a graph representing the distribution of subjects into grades, an hyperlink to a more detailed report, an official transcript, etc.
Need IDs for Scores.
Technical Issue: Currently, there is no guaranteed way to
reference a score from the UserArea element. While there are many ways to
refer to a score, using the XSD ID type on an optional attribute would offload
work to the XML Parser being used and allow many different XML Viewers.
Business Issue: Often there is a relationship between individual scores in a set of results. Depending on the business relationship or consumer of the XML (EAI usage of HR-XML can’t be ruled out), it might be necessary to show this relationship. Using ID and IDREF, this can easily be accomplished. This is not the only business reason for the change as there are probably many other uses of an ID attribute.
The term “assessment” can encompass a wide variety of tests, screenings, and instruments. Assessments can include tests of both “hard skills” (generally, technical abilities acquired through training and education) and/or “soft skills” (a diverse range of abilities or personal characteristics such as customer orientation, analytical thinking, leadership skills, team-building skills, listening skills, diplomacy, etc.). The instruments used to assess hard skills and soft skills can be very complex. Depending on the instrument, understanding the assessment results may be relatively straightforward or the results may require interpretation by an expert before they can be applied to a decision.
Multiple schemas
The assessment lifecycle was separated into five schemas to allow for:
Backward Compatibility
All changes to existing schemas are done in a way that enables continuing
support of Assessment 1.0 specification.
Thus, all XML instances that validate against an Assessment 1.0 schema must still validate against a 1.1 schema
Multi-phase approach
The objectives will be filled using a multi-phase approach.
Support of other standards
Some specifications from other
standard bodies have been identified as being potentially similar to
Assessments, on a process perspective. Among them are OAGI Order and UBL Order.
One project requirement was to support, if applicable, existing specification.
It appeared after evaluation
that these specifications didn’t meet Assessments objectives, and
therefore were not taken into account when designing Assessments schemas.
Existing specifications were aiming at order of physical goods rather than
order of services.
A challenge faced by the HR-XML Consortium’s Assessment Order project was to manage the potential complexity involved in designing a specification to support assessments. One of the important ways the project team managed complexity was to limit the initial scope of its work.
The HR-XML Assessments specification includes six schemas:
· Assessment Order Request - A schema to support assessment requests to assessment providers. The schema is flexible enough to transmit information required to execute assessments that a client might arrange with an assessment provider
· Assessment Order Acknowledgement - A schema to support acknowledgment of an assessment order. The schema provides also for handling assessment setting details as provided by the assessment provider
· Assessment Result - A schema to transmit assessment results to a client of an assessment provider
· Assessment Cancel Request – A schema to transmit the cancellation of an assessment order from a client to an assessment provider.
· Assessment Status Request - A schema to query the status of a particular assessment order.
· Assessment Types - A schema that is used within acknowledgment and results schemas to handle the information related to the status of the assessment order.
Outside of the design scope of the Assessment Order specification is the transmission of:
· Question sets or the content of assessment instruments.
· Orders or results for consumer or investigative reports and evaluations. (See Section 4.2, Laws Governing Consumer/Investigative Reports)
In this version of the HR-XML Consortium’s assessment specification, it is assumed that trading partners (for example, an employer’s applicant tracking solution and a third-party testing service) agree in advance on a set of assessment instruments or "packages" that can be ordered. The package may be requested through the catalog using the Id. This greatly simplifies assessment requests since it is not necessary to transmit detailed assessment content in an assessment order. Because packages have been agreed upon in advance, a company ordering an assessment needs only to transmit an identifier for the particular assessment package ordered rather than having to pass any detailed assessment content. Similarly, the assessment project team simplified the return of assessment results by focusing on a simple, but flexible structure for result information.
The Assessment Order specification is sufficiently generalized to be useful in a wide variety of scenarios. Examples of processes that are supported by the specification are:
· Candidate Selection. During the selection process, companies want to make sure they hire the right person. To do so, they will need to check the particular competencies of the candidate. This includes, but is not limited to:
· Employee evaluation. Regular employees are evaluated for compensation, promotion planning, training estimates or other purposes. This includes, but is not limited to:
The transactions supported by this specification are typically between an employer and an assessment provider. However, assessment transactions also are likely to take place between an assessment provider and the agent of an employer, such as an Applicant Tracking System or a Staffing company.
The third actor involved in the assessment process is the subject. This is actually the person who is taking the assessment.
The diagram depicted below (Figure 1) illustrates a supported assessment scenario in the context of recruiting.
The acknowledgement process is recommended but optional.
Either the customer or assessment provider, depending on the trading partner agreement, is responsible for inviting the subject to take an assessment.
The use-cases describe in a more detailed fashion all activities that deal with the recruiting process.
Figure 1: Assessment Process (Recruiting Context)
Use Cases
The following diagram shows what use cases will be supported by the Assessments specification. Note that the diagram includes a use case for the package query. Details on the package query are found in the Assessment Catalog document (see Appendix B – Related Documents).
Figure 2 - Assessment Use Cases
Client initiates three of those use cases.
The vendor initiates the fourth use case
4. The vendor can at any time notify his client about a change in the status of the assessment (candidate declines to take the assessment, candidate takes the test, assessment results are processed).
The following diagram details the typical scenario of a customer requesting an assessment, and the subsequent activities.
Figure 3 – Request an Assessment
A typical scenario within one of the processes described in section 2 Reported Business Processes would be:
· The recruiter (or manager) wants a subject to be assessed.
· The recruiter selects a package to evaluate against, based on a Trading Partner Agreement (TPA) that was defined when the customer and assessment provider decided to work together.
· The request is sent to the assessment provider, including the assessment package, the subject to assess, the context of the assessment, and a formal reference such as a P.O. number.
·
The assessment provider processes the request, and acknowledges
it.
If the request presents any error such as a wrong package or no subject, the
acknowledgment will contain an “error” status (see lifecycle).
If the request is correct, the acknowledgment will set the request to
“acknowledged”, and provide necessary information for inviting the
candidate to the assessment.
·
The recruiter can then invite the subject to be assessed using
the most appropriate way to communicate this: email with facility address for a
proctored assessment, URL for a direct web assessment, etc.
Alternately, subject’s invitation can be done directly by the assessment
provider.
· At some point in time, the subject takes the assessment.
·
Then, the assessment provider processes the subject’s
answers, the outcome being the subject’s results. Results can contain an
overall score as well as detailed scores.
These results are sent to the recruiter who includes them into the selection
decision.
The following diagram details the typical scenario of a customer canceling an assessment, and the subsequent activities.
Figure 4 - Cancel an Assessment
A typical scenario would be:
· An assessment request has been transmitted to the assessment provider. However, a recruiter (or manager) determines there is no longer a need to assess the subject. This may be due to many causes: background check results received, position cancelled or filled, etc.
· The manager sends a cancellation request to the assessment provider.
· The vendor cancels the request.
· The vendor sends verification of the cancellation to the customer.
The following diagram details the typical scenario of a customer querying an assessment, and the subsequent activities.
Figure 5 - Query Assessment Status
The following diagram shows the typical lifecycle of an assessment. Please note, this lifecycle is suggested, not required.
Figure 6 - Assessment Lifecycle
When the request is sent to the assessment provider, the assessment is pending, until the customer receives a message from the assessment provider: an acknowledgment, or partial or complete results.
If the acknowledgment process is supported, the assessment
will be acknowledged after receiving the AssessmentAcknowledgment from the
assessment provider.
The provider or customer can invite the subject, thus having the assessment
being scheduled.
As soon as the subject starts the assessment, and the provider starts to obtain
partial results, the assessment is in progress, until the candidate completes
everything.
During any time in the process, the assessment can be cancelled by the customer, declined by the candidate, or may fail and receive an error.
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- AssessmentOrderRequestType - (1/1) |
Container for AssessmentOrderRequest schema, which is designed to hold data necessary to initiate an assessment request. |
|
/
AssessmentOrderRequest/ |
- EntityIdType - S (1/1) |
A value
that uniquely identifies a client for the 3rd party vendor (assessor). It is
up to the vendor to provide the client its identifier. |
|
/
AssessmentOrderRequest/ |
- EntityIdType - S (1/1) |
A unique identifier for a Background Search or Assessment Package. Context definition: Identifies the package of assessments being ordered for the Subject. PackageIds are supplied by the Assessment Vendor to the Client in a Trading Partner Agreement. |
|
/
AssessmentOrderRequest/ |
- EntityIdType - S (0/1) |
A unique
identifier for the provider. |
|
/
AssessmentOrderRequest/ |
- EntityIdType - S (0/*) |
Indicates
the group(s) this assessment should be included in when comparing assessment
results. |
|
/
AssessmentOrderRequest/ |
- EntityIdType - S (1/1) |
A unique
identifier, for the client, to identify the order. |
|
/
AssessmentOrderRequest/ |
- xsd:string - S (1/1) |
The individual that makes the request for the assessment. |
|
/
AssessmentOrderRequest/ |
SubjectId
- EntityIdType - S
(1/1) |
The person who will be the subject of the assessment. |
|
/
AssessmentOrderRequest/ AssessmentSubject/ |
- EntityIdType - S (1/1) |
A unique
identifier for the person (subject) taking the assessment . |
|
/
AssessmentOrderRequest/ AssessmentSubject/ |
- ContactMethodType - S (0/*) |
Defines
the methods to contact a person or organizations. |
|
/
AssessmentOrderRequest/ |
- AssessmentPersonDescriptorsType - S (0/1) |
A set of demographic characteristics collected for purposes of test analysis or government compliance. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ |
- AssessmentLegalIdentifiersType - S (0/1) |
Legal
identifiers for a person. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ LegalIdentifiers/ |
- PersonLegalIdType - S (0/*) |
A legal
id, such as a social insurance or taxpayer identification number. A unique
government or other legal identifier for a person. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ LegalIdentifiers/ |
xsd:extension base: xsd:string |
Describes whether a person’s is currently a member of the military and other information regarding military status. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ LegalIdentifiers/ MilitaryStatus/ |
- xsd:string - |
Further defines the associated element in the context provided. |
|
|
/ AssessmentOrderRequest/ AssessmentPersonDescriptors/ |
- AssessmentDemographicDescriptorsType - S (0/1) |
A collection of demographic descriptors for a person. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ DemographicDescriptors/ |
- xsd:string - S (0/*) |
Describes the race of the person. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ DemographicDescriptors/ |
- xsd:string - S (0/*) |
The ethnicity of the person. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ DemographicDescriptors/ |
- xsd:string - S (0/*) |
The
person's status for belonging to a particular nation by origin, birth, or
naturalization. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ DemographicDescriptors/ |
- LanguageCodeType - S (0/*) |
A
person’s primary or preferred language. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ |
- AssessmentBiologicalDescriptorsType - S (0/1) |
A collection of biological descriptors for a person. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ BiologicalDescriptors/ |
- xsd:date - C (0/1) |
A
person's birth date. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ BiologicalDescriptors/ |
- xsd:gMonthDay - C (0/1) |
The month and day of a person's birth date. The month and day of a person's birth date. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ BiologicalDescriptors/ |
AgeNumeric
- xsd:nonNegativeInteger - C (1/1) |
The age of a person, specified in years. The age of a person, specified in years. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ BiologicalDescriptors/ Age/ |
- xsd:nonNegativeInteger - C (1/1) |
A person’s age in years. |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ BiologicalDescriptors/ Age/ |
|
A designated band in which the person’s age falls. [Example(s): 20 - 30; 31 – 40; 41-50, etc. ] |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ BiologicalDescriptors/ |
- GenderCodeType - S (0/1) |
Describes the gender of a person. [BusinessRule(s): Values are represented in accordance with ISO 5218. Those values are: 0 = None; 1 = Male; 2 = Female; 9 = None Specified ] |
|
|
/
AssessmentOrderRequest/
AssessmentPersonDescriptors/ BiologicalDescriptors/ |
- DisabilityInfoType - S (0/*) |
Contains information about a person's physical or psychological impairment. |
|
|
/
AssessmentOrderRequest/ |
- xsd:language - S (0/*) |
The
language in which the assessment is available or was taken. |
|
|
/
AssessmentOrderRequest/ |
- xsd:language - S (0/*) |
The language in which results are available. |
|
|
Global types |
ContentModel* |
Definition |
|
/ |
xml:lang
- - |
Globally scoped data type. See element or attribute declaration for definition. |
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition
|
|
/ |
- AssessmentOrderAcknowledgementType - (1/1) |
Container for AssessmentOrderAcknowledgment schema, which is designed to hold data necessary to acknowledge an assessment request. |
|
/ AssessmentOrderAcknowledgement/ |
- EntityIdType - S (1/1) |
A value that uniquely identifies
a client for the 3rd party vendor (assessor). It is up to the vendor to
provide the client its identifier. |
|
/ AssessmentOrderAcknowledgement/ |
- EntityIdType - S (0/1) |
A unique identifier for the provider.
|
|
/ AssessmentOrderAcknowledgement/ |
- EntityIdType - S (0/1) |
A unique identifier supplied by
the assessment provider that will allow the client to know how to request
updates. |
|
/ AssessmentOrderAcknowledgement/ |
- EntityIdType - S (1/1) |
A unique identifier, for the
client, to identify the order. |
|
/ AssessmentOrderAcknowledgement/ |
xsd:extension base: ContactMethodType |
The way to access the Assessment, including the contact method and login information. |
|
/ AssessmentOrderAcknowledgement/
AccessPoint/ |
- xsd:string - S (0/1) |
Describes the contextual
information relating to a specific element. Context definition: Instructions
for the subject to access the assessment via this access point. |
|
/ AssessmentOrderAcknowledgement/
AccessPoint/ |
validTo – LocalDateType - Optional validFrom – LocalDateType - Optional Token - xsd:string
- S (0/1) |
The login information used to access the assessment. Optional “validTo” and “validFrom” attributes are available to communicate the period during which the login credential is valid. |
|
/ AssessmentOrderAcknowledgement/
AccessPoint/ Login/ |
- xsd:string - S (0/1) |
A authentication credential other than or in addition to a user name and password. |
|
/ AssessmentOrderAcknowledgement/
AccessPoint/ Login/ |
- xsd:string - S (0/1) |
The user name a person (subject)
uses to access a web-based tool or application. |
|
/ AssessmentOrderAcknowledgement/
AccessPoint/ Login/ |
- xsd:string - S (0/1) |
A password. |
|
/ AssessmentOrderAcknowledgement/ |
- AssessmentStatusType - S (1/1) |
Container for information relating to the status of the assessment. |
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- AssessmentResultType - (1/1) |
Container for AssessmentResult schema, which is designed to hold data necessary to convey information on the results of the assessment. |
|
/
AssessmentResult/ |
- EntityIdType - S (1/1) |
A value
that uniquely identifies a client for the 3rd party vendor (assessor). It is
up to the vendor to provide the client its identifier. |
|
/
AssessmentResult/ |
- EntityIdType - S (0/1) |
A unique
identifier for the provider. |
|
/
AssessmentResult/ |
- EntityIdType - S (1/1) |
A unique
identifier, for the client, to identify the order. |
|
/
AssessmentResult/ |
- EntityIdType - S (0/1) |
A unique
identifier supplied by the assessment provider that will allow the client to
know how to request updates. |
|
/
AssessmentResult/ |
- AssessmentSingleResultType - S (0/*) |
The information provided as a response to a query, screening, assessment or other investigative request. |
|
/
AssessmentResult/ Results/ |
- xsd:string - S (0/1) |
Context definition: The name of this set of results. Commonly used to distinguish between multiple Results elements, for example to indicate the normative group applied to the scoring. |
|
/
AssessmentResult/ Results/ |
- AssessmentResultsType - S (0/1) |
A summary or "high-level" view of the result of the assessment. |
|
/
AssessmentResult/ Results/ OverallResult/ |
- EntityIdType - S (0/1) |
A unique identifier of the score. |
|
/
AssessmentResult/ Results/ OverallResult/ |
- xsd:boolean - S (0/1) |
A Boolean expression that denotes whether the subject passed or failed the assessment. |
|
/
AssessmentResult/ Results/ OverallResult/ |
- xsd:string - S (0/1) |
Describes the contextual information relating to a specific element. Context definition: The label of the score. |
|
/
AssessmentResult/ Results/ OverallResult/ |
- CompetencyReferenceType - S (0/1) |
References
the competencies the assessment is intended to evaluate. |
|
/
AssessmentResult/ Results/ OverallResult/ |
xsd:extension base: xsd:float |
The raw value of the score. |
|
/
AssessmentResult/ Results/ OverallResult/ Score/ |
- AssessmentResultTypes - |
Enumerated
values are: percentile; raw score; stanine; sten; t-score; z-score;
intelligence quotient; number attempted; and other. Other values are
permitted if preceded by “x:”. |
|
/
AssessmentResult/ Results/ OverallResult/ |
- xsd:string - S (0/1) |
A
textual label to indicate the range of possible values for this score. |
|
/
AssessmentResult/ Results/ OverallResult/ |
- xsd:string - S (0/1) |
Provides
for categorizing or grouping of results or other information. This is not a
hierarchical grouping. |
|
/
AssessmentResult/ Results/ OverallResult/ |
- xsd:string - S (0/1) |
Describes the contextual information relating to a group of elements. Context definition: A textual description that provides the opinion of the assessment vendor. It may be based on criteria that have been defined between the client and the vendor. |
|
/
AssessmentResult/ Results/ |
- AssessmentResultsType - S (0/*) |
The detailed results for the assessment requested. |
|
/
AssessmentResult/ Results/ DetailResult/ |
- EntityIdType - S (0/1) |
A unique identifier of the score. |
|
/
AssessmentResult/ Results/ DetailResult/ |
- xsd:boolean - S (0/1) |
A Boolean expression that denotes whether the subject passed or failed the assessment. |
|
/
AssessmentResult/ Results/ DetailResult/ |
- xsd:string - S (0/1) |
Describes
the contextual information relating to a specific element. Context
definition: The label of the score. |
|
/
AssessmentResult/ Results/ DetailResult/ |
- CompetencyReferenceType - S (0/1) |
References
the competencies the assessment is intended to evaluate. |
|
/
AssessmentResult/ Results/ DetailResult/ |
xsd:extension base: xsd:float |
The raw value of the score. |
|
/
AssessmentResult/ Results/ DetailResult/ Score/ |
- AssessmentResultTypes - |
Enumerated
values are: percentile; raw score; stanine; sten; t-score; z-score;
intelligence quotient; number attempted; and other. Other values are
permitted if preceded by “x:”. |
|
/
AssessmentResult/ Results/ DetailResult/ |
- xsd:string - S (0/1) |
A
textual label to indicate the range of possible values for this score. |
|
/
AssessmentResult/ Results/ DetailResult/ |
- xsd:string - S (0/1) |
Provides
for categorizing or grouping of results or other information. This is not a
hierarchical grouping. |
|
/ AssessmentResult/
Results/ DetailResult/ |
- xsd:string - S (0/1) |
Describes the contextual information relating to a group of elements. Context definition: A textual description that provides the opinion of the assessment vendor. It may be based on criteria that have been defined between the client and the vendor. |
|
/
AssessmentResult/ |
- AssessmentStatusType - S (1/1) |
Container for information relating to the status of the assessment. |
|
/
AssessmentResult/ |
- xsd:language - S (0/1) |
The
language in which the assessment is available or was taken. |
|
Global types |
ContentModel* |
Definition |
|
/ |
ScoreId
- EntityIdType - S
(0/1) |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: AssessmentScoreEnumTypes, xStringPatternExtensionType |
Enumerated values are: percentile; raw score; stanine; sten; t-score; z-score; intelligence quotient; number attempted; and other. Other values are permitted if preceded by “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: percentile, raw score, other |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
xml:lang
- - optional |
Globally scoped data type. See element or attribute declaration for definition. |
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- AssessmentRequestType – (1/1) |
Container for AssessmentStatusRequest schema, which is designed to hold data necessary to request the status of a particular assessment. |
|
/
[AssessmentRequestType]/ |
- EntityIdType - S (1/1) |
A value
that uniquely identifies a client for the 3rd party vendor (assessor). It is
up to the vendor to provide the client its identifier. |
|
/
[AssessmentRequestType]/ |
- EntityIdType - S (0/1) |
A unique
identifier for the provider. |
|
/
[AssessmentRequestType]/ |
- EntityIdType - S (1/1) |
A unique
identifier, for the client, to identify the order. |
|
/
[AssessmentRequestType]/ |
- EntityIdType - S (0/1) |
A unique
identifier supplied by the assessment provider that will allow the client to
know how to request updates. |
|
Elements and Attributes [Global types listed alphabetically in following table.] |
ContentModel* |
Definition |
|
/ |
- AssessmentRequestType – (1/1) |
Container for AssessmentCancelRequest schema, which is designed to hold data necessary to cancel a particular assessment. |
|
/
[AssessmentRequestType]/ |
- EntityIdType - S (1/1) |
A value
that uniquely identifies a client for the 3rd party vendor (assessor). It is
up to the vendor to provide the client its identifier. |
|
/
[AssessmentRequestType]/ |
- EntityIdType - S (0/1) |
A unique
identifier for the provider. |
|
/
[AssessmentRequestType]/ |
- EntityIdType - S (1/1) |
A unique
identifier, for the client, to identify the order. |
|
/
[AssessmentRequestType]/ |
- EntityIdType - S (0/1) |
A unique
identifier supplied by the assessment provider that will allow the client to
know how to request updates. |
Human resources data, by its very nature, is personal data. The laws of many jurisdictions as well as codes of fair information practice require organizations to handle personal data in a way that protects individuals from loss of privacy.
The data exchange specifications developed by the HR-XML Consortium are designed to be useful across many jurisdictions and within a variety of business contexts. It is not feasible for the HR-XML Consortium to develop specific privacy guidance for every jurisdiction or business context in which the Consortium's specifications might be implemented. When implementing data exchanges using the HR-XML Consortium's data definitions (or, for that matter, using any other type of data exchange mechanism), organizations are advised to examine the privacy protections that may be required under applicable law and codes of fair information practice.
For information on protecting personal data, general references include: European Union Data Protection Directive (95/46/EC); the Association Computing Machinery Code of Ethics (1992); Canadian Standards Association Model Code for the Protection of Personal Information (1995 – PIPEDA); and U.S.-EU Safe Harbor Principles and FAQs (2000).
Consumer or investigative reports or evaluations (such as those involving an individual’s credit history) are regulated within the United States and within other jurisdictions. The HR-XML Consortium’s Assessment Order specification was not designed to support the ordering of regulated consumer and investigative reports. HR-XML Consortium’s Background Checking specification is better suited for ordering these types of regulated reports.
Implementers of both the HR-XML Consortium’s Assessment Order and Background Checking are strongly advised to review applicable law in the jurisdictions in which they operate and to seek the advice of competent legal counsel.
A validity period specifies the period for which assessment results are valid. In practice, a candidate or applicant would not be assessed against a specific AssessmentPackage, AssessmentGroup, or AssessmentItem if he or she has results for that AssessmentPackage, AssessmentGroup, or AssessmentItem that fall within the specified validity period. Once the validity period has expired, the applicant or candidate would be allowed to be reassessed for the particular AssessmentPackage, AssessmentGroup, or AssessmentItem in question.
As mentioned above, validity periods for AssessmentPackageContent exist at three different levels within the schema: AssessmentPackage, AssessmentGroup, and AssessmentItem. This is because assessment vendors need to specify the validity periods at different levels. In some cases, it may be necessary to provide different validity periods for certain AssessmentItems within an AssessmentGroup, or different validity periods for certain AssessmentGroups within an AssessmentPackage.
|
Date |
Description |
|
2003-Aug-21 |
Draft |
|
2003-Aug-26 |
Added Examples and related documents. Renamed doc to Assessments.doc |
|
2003-Sep-03 |
Submitted to TSC/CPO for review. |
|
2003-Oct-03 |
Made following changes based on TSC/CPO review: Renamed OverallScore to OverallResult, ScoreDetail to DetailResult. Replaced userId and password with Login structure. Changed Status enumerations to extensible. Submit for membership review. |
|
2003-Nov |
Approved by membership |
|
2004-07-06 |
AssessmentOrderAcknowledgment and Assessment OrderRequest schema: An optional attribute xml:lang was added to the root element. AssessmentResult schema: · Score element changed from xsd:int to xsd:float. · An optional attribute xml:lang was added to the root element. · ScoreId element was added to the AssessmentsResultsType. |
|
2005-Jan-03 |
Updated document with enhancements. See overview for details. |
|
2005-Jan-18 |
Updated based on WG feedback. |
|
2005-Feb-28 |
Updated diagrams, tables, and examples for AssessmentOrderRequest and AssessmentResult. |
|
2005-Jun-30 |
CPO approved with minor wording changes. |
|
2006-Feb-28 |
Approved by consortium |
|
2007-Feb-13 |
Updated. See New in This Version. |
The diagram below explains the difference between the score and the grade/band.
Assessment statistical repartition is similar for any “assessable” characteristic. For each characteristic, it has first to be defined where grade/band A starts and finishes.
So, score alone is not enough to rank an assessment subject.
<AssessmentOrderRequest xmlns="http://ns.hr-xml.org/2004-08-02" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ns.hr-xml.org AssessmentOrderRequest.xsd ">
<ClientId idOwner="Provider Inc">
<IdValue name="ClientCode">OurClient-1342</IdValue>
</ClientId>
<PackageId validFrom="2003-01-24" idOwner="Provider Inc">
<IdValue name="PackageName">Acct.2002.r1</IdValue>
</PackageId>
<ProviderId idOwner="Customer Inc">
<IdValue>ePredix</IdValue>
</ProviderId>
<ComparisonGroupId>
<IdValue name="Requisition Contest Number">ACCT-1023-58</IdValue>
</ComparisonGroupId>
<ClientOrderId>
<IdValue name="PO Number">53RR20031618</IdValue>
<IdValue name="Department Name">Administration</IdValue>
</ClientOrderId>
<AssessmentRequester>Romuald Restout</AssessmentRequester>
<AssessmentSubject>
<SubjectId idOwner="Recruitsoft">
<IdValue name="Candidate No">12345</IdValue>
</SubjectId>
<PersonName>
<FormattedName type="presentation">Drew Cox</FormattedName>
<LegalName>Cox</LegalName>
<GivenName>Drew</GivenName>
</PersonName>
<ContactMethod>
<Use>business</Use>
<EMAIL_ADDRESS></ContactMethod>
</AssessmentSubject>
<AssessmentLanguage>EN-US</AssessmentLanguage>
<AssessmentLanguage>DE</AssessmentLanguage>
<ResultLanguage>en-US</ResultLanguage>
<UserArea/>
</AssessmentOrderRequest>
<AssessmentOrderAcknowledgement>
<ClientId idOwner="Provider Inc">
<IdValue name="ClientCode">OurClient-1342</IdValue>
</ClientId>
<ProviderId idOwner="Customer Inc">
<IdValue>ePredix</IdValue>
</ProviderId>
<ReceiptId idOwner="Provider Inc">
<IdValue>Seq-22345354</IdValue>
</ReceiptId>
<ClientOrderId idOwner="Customer Inc">
<IdValue name="PO Number">53RR20031618</IdValue>
<IdValue name="Department Name">Administration</IdValue>
</ClientOrderId>
<AccessPoint>
<Use>business</Use>
<InternetWebAddress>http://test.vendor.com/start?id=22345354</InternetWebAddress>
<Description>URL for subject to access assessment.</Description>
<Login>
<EMAIL_ADDRESS><Password>just4fun!</Password>
</Login>
</AccessPoint>
<AssessmentStatus>
<Status>Acknowledged</Status>
<Details>The assessment order has been processed. Please have the subject access the provided URL with the specified login credentials.</Details>
<StatusDate>2003-04-24</StatusDate>
</AssessmentStatus>
<UserArea/>
</AssessmentOrderAcknowledgement>
<AssessmentResult xmlns="http://ns.hr-xml.org/2004-08-02" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dc="http://purl.org/dc/elements/1.1/" xsi:schemaLocation="http://ns.hr-xml.org/2004-08-02.xsd">
<ClientId idOwner="Provider Inc">
<IdValue name="ClientCode">OurClient-1342</IdValue>
</ClientId>
<ProviderId idOwner="Customer Inc">
<IdValue>ePredix</IdValue>
</ProviderId>
<ClientOrderId>
<IdValue name="PO Number">53RR20031618</IdValue>
<IdValue name="Department Name">Administration</IdValue>
</ClientOrderId>
<Results xml:lang="en-US">
<Profile>Customer Service</Profile>
<SupportingMaterials>
<Id idOwner="ePredix Inc">
<IdValue name="ReportId">DR-12343-1</IdValue>
</Id>
<EffectiveDate>
<StartDate>2004-03-08</StartDate>
<EndDate>2005-03-08</EndDate>
</EffectiveDate>
<dc:title>Assessment Detailed Narrative Report</dc:title>
<dc:format>text/html</dc:format>
<ExtendedMetadata>
<dc:subject>Robert Jones</dc:subject>
<dc:publisher>ePredix Inc</dc:publisher>
<dc:date>2004-03-08</dc:date>
</ExtendedMetadata>
<ReferenceInfo>
<InternetWebAddress>https://integrate.epredix.com/hrxml/report/detail?sk=197e23sa</InternetWebAddress>
</ReferenceInfo>
<AccessInfo>
<AccessCredential type="UserName">partner25</AccessCredential>
<AccessCredential type="Password">4sure8yut</AccessCredential>
<Instructions>Request the referenced report from the included URL. Use the supplied username and password credentials.</Instructions>
</AccessInfo>
<UsageRestrictions>ePredix Client confidential. Access restructed to authorized parties only.</UsageRestrictions>
<Comments>The referenced HTML report may be displayed in a frameset.</Comments>
</SupportingMaterials>
<OverallResult>
<Description>Executive Manager</Description>
<CompetencyAssessed>
<TaxonomyId validFrom="notKnown" validTo="notKnown" idOwner="TBD">
<IdValue name="TBD">TBD</IdValue>
<IdValue name="TBD">TBD</IdValue>
</TaxonomyId>
<CompetencyId validFrom="notKnown" validTo="notKnown" idOwner="TBD">
<IdValue name="TBD">TBD</IdValue>
<IdValue name="TBD">TBD</IdValue>
</CompetencyId>
</CompetencyAssessed>
<Score type="raw score">51</Score>
<Score type="percentile">65</Score>
<Scale>40-60</Scale>
<Band>A</Band>
<Comments>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." </Comments>
</OverallResult>
<DetailResult>
<Description>Education and Work Experience</Description>
<CompetencyAssessed>
<TaxonomyId validFrom="notKnown" validTo="notKnown" idOwner="TBD">
<IdValue name="TBD">TBD</IdValue>
<IdValue name="TBD">TBD</IdValue>
</TaxonomyId>
<CompetencyId validFrom="notKnown" validTo="notKnown" idOwner="TBD">
<IdValue name="TBD">TBD</IdValue>
<IdValue name="TBD">TBD</IdValue>
</CompetencyId>
</CompetencyAssessed>
<Score type="percentile">80</Score>
<Scale>1-100</Scale>
<Band>High</Band>
<Comments>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." </Comments>
</DetailResult>
<DetailResult>
<Description>Conscientiousness</Description>
<CompetencyAssessed>
<TaxonomyId validFrom="notKnown" validTo="notKnown" idOwner="TBD">
<IdValue name="TBD">TBD</IdValue>
<IdValue name="TBD">TBD</IdValue>
</TaxonomyId>
<CompetencyId validFrom="notKnown" validTo="notKnown" idOwner="TBD">
<IdValue name="TBD">TBD</IdValue>
<IdValue name="TBD">TBD</IdValue>
</CompetencyId>
</CompetencyAssessed>
<Score type="raw score">62</Score>
<Scale>1-140</Scale>
<Band>Med</Band>
<Comments>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." </Comments>
</DetailResult>
</Results>
<Results xml:lang="en-US">
<Profile>Operations</Profile>
<SupportingMaterials>
<Id idOwner="Sterling Testing Systems">
<IdValue name="OrderNumber">1380001</IdValue>
</Id>
<Id idOwner="ABC Company">
<IdValue name="CandidateId">123456789</IdValue>
</Id>
<EffectiveDate>
<StartDate>2004-05-04</StartDate>
<EndDate>2004-06-04</EndDate>
</EffectiveDate>
<dc:title>123456789.tif</dc:title>
<dc:format>image/tiff</dc:format>
<ExtendedMetadata>
<dc:creator>Sterling Testing Systems</dc:creator>
<dc:subject>Consent and Disclosure Form for Mark Smith</dc:subject>
<dc:date>2004-05-04</dc:date>
</ExtendedMetadata>
<AttachmentInfo>
<AttachmentId>
<IdValue>1</IdValue>
</AttachmentId>
<OriginalFileName>123456789.tif</OriginalFileName>
</AttachmentInfo>
<UsageRestrictions>This Consent and Disclosure form is only to be used for the candidate within this transaction</UsageRestrictions>
<Comments>Consent and Disclosure form required for Education Verification</Comments>
</SupportingMaterials>
<OverallResult>
<Description>Executive Manager</Description>
<CompetencyAssessed>
<TaxonomyId validFrom="notKnown" validTo="notKnown" idOwner="TBD">
<IdValue name="TBD">TBD</IdValue>
<IdValue name="TBD">TBD</IdValue>
</TaxonomyId>
<CompetencyId validFrom="notKnown" validTo="notKnown" idOwner="TBD">
<IdValue name="TBD">TBD</IdValue>
<IdValue name="TBD">TBD</IdValue>
</CompetencyId>
</CompetencyAssessed>
<Score type="raw score">51</Score>
<Score type="percentile">80</Score>
<Scale>40-60</Scale>
</OverallResult>
</Results>
<AssessmentStatus>
<Status>In Progress</Status>
<Details>Remains: "GAAP Basic Knowledge"</Details>
<StatusDate>2003-04-05</StatusDate>
</AssessmentStatus>
<AssessmentLanguage>en-US</AssessmentLanguage>
<UserArea/>
</AssessmentResult>
<AssessmentStatusRequest>
<ClientId idOwner="Provider Inc">
<IdValue name="ClientCode">OurClient-1342</IdValue>
</ClientId>
<ProviderId idOwner="Customer Inc">
<IdValue>Recruitsoft</IdValue>
</ProviderId>
<ClientOrderId>
<IdValue name="PO Number">53RR20031618</IdValue>
<IdValue name="Department Name">Administration</IdValue>
</ClientOrderId>
<ReceiptId idOwner="AssessmentProvider Inc">
<IdValue>Seq-22345354</IdValue>
</ReceiptId>
<UserArea/>
</AssessmentStatusRequest>
<AssessmentCancelRequest>
<ClientId idOwner="Provider Inc">
<IdValue name="ClientCode">OurClient-1342</IdValue>
</ClientId>
<ProviderId idOwner="Customer Inc">
<IdValue>ePredix</IdValue>
</ProviderId>
<ClientOrderId>
<IdValue name="PO Number">53RR20031618</IdValue>
<IdValue name="Department Name">Administration</IdValue>
</ClientOrderId>
<ReceiptId idOwner="AssessmentProvider Inc">
<IdValue>Seq-22345354</IdValue>
</ReceiptId>
<UserArea/>
</AssessmentCancelRequest>


6036 Richmond hwy, Alexandria, VA USA 22303
Mon – Sat: 9:00am–18:00pm. Sunday CLOSED
+1 (409) 987–5874


Recovered
+{{rowData.deltarecovered}}
{{rowData.recovered}}
Confirmed
+{{rowData.deltaconfirmed}}
{{rowData.confirmed}}
Deaths
+{{rowData.deltadeaths}}
{{rowData.deaths}}
Active
{{rowData.active}}
Recovery Rate
{{this.recoveryRatePer.toFixed(2)}}%
For every 100 confirmed cases, {{this.recoveryRatePer.toFixed(0)}} were recovered
Growth Rate
{{growthRatePer.toFixed(2)}}%
{{secondDate}} to {{firstDate}}, active cases registered count


WHERE THE MONEY IS (2000) by John Sylva, associate of OFCS (www.ofcs.org)
Rating: B-
There are nurses who treat and care for their patients in nursing homes as if they were a part of their own family.   Well, not too many nurses do that, but that's what the unbelievable comedic caper "Where the Money Is" is trying to sell. Linda Fiorentino stars as Carol Ann McKay, nursing home employee responsible for watching over the home's newest patient, Henry Manning (Paul Newman). What results from a humorous, delightful setup is an unbelievable, over the top caper flick that is moderately entertaining, but never escapes the "been there done that" feeling that so many films of this genre carry.
Carol discovers that her new patient was once, or possibly still is, a well-known bank robber, who has supposedly suffered from a stroke, and as a result, cannot communicate or hardly move. Catching onto what seems to be a cleverly planned scheme, she eventually tricks him into snapping out of his stroke act, and starts to bond with the old timer, as the stroke routine was part of his plan to pull off his next big heist. From here, the two, along with Carol's husband, Wayne (Dermot Mulroney), decide to go on a series of robberies that will eventually land the team 2 million dollars.
As the film's lead, Paul Newman is hilarious in his comic portrayal of his aging bank robber, giving a performance that is unquestionably worth watching. The 75 year old actor has wonderful comic timing, and steals the show, turning what could have been a total flop into a pretty decent picture. The legendary Newman deserves better than "Where the Money Is," but it's apparent he wanted to travel into his older, crime caper days with this one.
Linda Fiorentino handles several of her scenes with comic pizzaz and energy, and falls flat as a pancake in others. The actress can't decide whether or not she's putting on a comedic performance or a mysterious one, changing Carol's personality from scene to scene, resulting in her character coming off dull, uneven, and unlikable others-which should probably be credited to the screenplay, which gave her an unclear character. As her husband, Dermot Mulroney is a complete misfire, ruining almost every one of his lines with a cocky, unrealistic tone of voice, and awful facial expressions.
Under the direction of Marek Kanievska, "Where the Money Is" is surprisingly good in some moments; surprisingly bad in others. Although flawed, some of the film's laughs cannot be ignored or go unmentioned, as a few choice moments are worth being rewound repeatedly when the flick comes to video. Kanievska wastes much of the film's screen time, especially with a totally unnecessary, 3 minute plus opening credit, and overly long scenes, present only to fill time. At a mere 88 minutes, one would think the screenplay would be from the desk of one, first time amateur screenwriter, but "Money"'s script gives credit to three screenwriters, E. Max Frye, Topper Lilien, and Carol Cartwright.  Every character in the film is under-developed, and with a little more effort and time, could have been transformed into well rounded, likable beings. A lot more effort and time could have gone a long way in other areas of the screenplay as well, as the plot jumps from too many elements in such a short time to come off with any realism. The film is too unfocused to be very effective, but during many bright moments, you can tell a great movie is trying to squeeze through the cracks. Still, despite its few ups, "Where the Money Is" would have been better left for the video store.
The Bottom Line: "Where the Money Is" is where the money won't be at the box office; but it's a fine choice for a video rental.
Film reviewed: April 13th, 2000.
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


Thank you for your interest to donate to Love of the Game. Please click on Donate button which will redirect you to the University of Massachusetts at Lowell's Difference Makers' donation page. Please note, once on this page, specify Love of the Game in the "Other Fund Name" form box.
Gain a stronger sense of
Confidence
Be yourself and come out of your shell!
Camaraderie
Let us introduce you to your second family!
Joy
Learn to love sport from those who love it the most!


ACRT Instructions
To access ACRT User Guide:
- Locate the instructions in the Resources folder.(The instructions are available in Word and PDF formats.) Or
- SelectACRT User Guide to open within the application.
Create Report
- Select Create Report in the menu to begin a new Report.
- Select Choose File and load a JSON file:
- First time use Trusted Tester v.5.1.1 (for web) or Trusted Tester v.4 (for software) (TT5.1.1 or TT4) located in the 'Resources' folder. Or
- Use previously created JSON report file.
- Select Load File button.
- Open Product and Testing Information to complete each form and the required fields.
- Add/Edit Test Results.
- Select Save button or the keyboard shortcut (Alt+S).
View Report
- Select View Report in the top menu to open an existing report that contains at least one valid test result.
- Select Choose File and load JSON file with test results.
- Select Open.
- Select Load Results button.
- View the Test Results.
- Select the Save as HTML button at the bottom or use Alt+S to generate a printer-friendly version of the report and save JSON file for future use.


BoxError
public enum BoxError : Error
Defines error values for the whole SDK
-
Result of an API request. Contains specific BoxAPIError.
Declaration
Swift
case apiError(error: BoxAPIError)
Parameters
error
BoxApiError specifying the issue.
-
Could not encode an object.
Declaration
Swift
case encoding(error: Error)
-
Could not decode an object.
Declaration
Swift
case decoding(error: Error)
Parameters
error
Thrown error - either BoxDecodingError or standard swift decoding Error.
-
Request had its maximum number of retries.
Declaration
Swift
case rateLimitMaxRetries
-
Response body was a different type than expected. Usually did not find expected JSON.
Declaration
Swift
case invalidResponse
-
Network failure.
Declaration
Swift
case network(message: String)
-
Access token has expired.
Declaration
Swift
case expiredToken
-
Tried to use a BoxClient instance that was already destroyed.
Declaration
Swift
case clientDestroyed
-
Expected result is not found in a valid request response.
Declaration
Swift
case notFound
-
Unsuccessful token retrieval. Token was not found.
Declaration
Swift
case tokenRetrieval
-
Unsuccessful refresh token retrieval. Token was not found in the retrieved TokenInfo object.
Declaration
Swift
case refreshTokenNotFound
-
Unauthorized request.
Declaration
Swift
case unauthorizedAccess
-
Failed OAuth web session authorization.
Declaration
Swift
case invalidOAuthRedirectConfiguration
-
Couldn’t obtain authorization code from OAuth web session success result.
Declaration
Swift
case invalidOAuthState
-
Authorization with JWT token failed.
Declaration
Swift
case jwtAuthError(error: Error)
Parameters
error
Thrown error.
-
Object needed in closure was already deallocated.
Declaration
Swift
case instanceDeallocated
-
The provided value is not valid in this context.
Declaration
Swift
case invalidValue
-
Could not finish and operation (write, read or clear) on TokenStore object.
Declaration
Swift
case tokenStoreFailure(error: Error)
Parameters
error
Thrown error.
-
Could not decode or encode data for or from keychain.
Declaration
Swift
case keychainDataConversionError
-
Unhandled keychain error
Declaration
Swift
case keychainUnhandledError(message: String)
Parameters
message
Error message.
-
Unspecified unhandled keychain error
Declaration
Swift
case keychainUhandledError
-
Value not found in Keychain.
Declaration
Swift
case keychainNoValue
-
The file representation could not be made.
Declaration
Swift
case representationCreationFailed


{% extends "master.html" %} {% block title %}404: page not found{% endblock %} {% block content %}
We're sorry, but the requested page could not be found.


| A nanny, working for a family whose son has just passed away, finds herself put in charge of caring for a lifelike doll that the couple treat as a real child. | |
| Genres: | Horror, Mystery, Thriller |
| Director: | William Brent Bell |
| Writer: | Stacey Menear |
Cast: | Greta Evans - Lauren Cohan Malcolm - Rupert Evans Brahms Heelshire - James Russell Mr. Heelshire - Jim Norton Mrs. Heelshire - Diana Hardcastle Cole - Ben Robson Brahms - Jett Klyne Emily Cribbs - Lily Pater Taxi Driver - Matthew Walker Sandy - Stephanie Lemelin |


--- layout: default ---
Getting Started with the Redlink Platform is easy. Jump right into the API documentation, download the SDK, or manage your apps.
The Redlink Platform consists of a number of services that are offered to users through a REST API. The Platform provides three main services: Redlink Content Analysis, Redlink Linked Data Publishing and Redlink Semantic Search.
The Redlink Platform is implemented as "software as a service" (SaaS) running on a distributed cloud infrastructure. Users can access the system here through a uniform web service API using a private key to identify themselves. For the most common web frameworks, we will provide plugins providing out-of-the-box services. All requests to the API are handled by a single gateway which takes care of accounting and forwards the requests to backend clusters providing the necessary functionality.
You can register at my.redlink.io for getting free access to the platform for a trial period of 42 days (pricing details).
The Redlink API provides a set of RESTful web services, grouped according their purpose: content analysis, semantic search and linked data publishing. It provides full support for implementing semantic enrichment and content discovery workflow.
It covers the entire workflow enterprises may need with a seamless platform and technology by providing APIs to access the platform SDKs for major programming languages, where plugins could be developed for leading content management platforms. For further details, please refer to the normative API documentation.
The Redlink API provides a set of RESTful web services, grouped according their purpose: content analysis, semantic search and linked data publishing. It provides full support for implementing semantic enrichment and content discovery workflow.
select your content analysis needs
entity extraction, NLP analysis, classification, content segmentation
push enhanced/linked data to your business processes
defined by partners, semantic search for example
When the API will be fully functionall, such workflow would allow you to:
Beyond another NLP engine, Redlink gets the best of all available NLP tools for providing a more advanced experience based on both generic and custom datasets.
The Redlink SDK gives you a group of APIs along with client libraries, language-specific examples, and documentation to help you develop awesome appications that integrate with Redlink.
If you're a new Redlink developer, we recommend you download the SDK bundle to quickly start developing against our API. The SDK is provided for a limited set of languages; so if it does not covers yours, contact us for further information.


Id: 161
Name: Hydrogen-F
Status: Alive
Species: Alien
Type: Alphabetrian
Gender: Female
OriginName: Alphabetrium
OriginUrl: https://rickandmortyapi.com/api/location/43
LocationName: Alphabetrium
LocationUrl: https://rickandmortyapi.com/api/location/43
Image: https://rickandmortyapi.com/api/character/avatar/161.jpeg
Episode: ['https://rickandmortyapi.com/api/episode/16']
Url: https://rickandmortyapi.com/api/character/161
Created: 2017-12-29T16:10:40.290Z


represents a vertex in 2 dimensions
More...
#include <Vertex.h>
|
|
| Vertex2D () |
| | Initializes an "empty" vertex.
|
| |
|
| Vertex2D (crvec2 p) |
| | Initializes a white, textureless vertex with given position.
|
| |
|
| Vertex2D (crvec2 p, crvec4 c) |
| | Initializes textureless, colorful vertex.
|
| |
|
| Vertex2D (crvec2 p, crvec4 c, crvec2 u, float t=1.0) |
| | Initializes a vertex with everything.
|
| |
|
| Vertex2D (crvec4 c, crvec2 u, float t=1.0) |
| | Initializes vertex with everything except position.
|
| |
|
void | setPosition (float x, float y) |
| | sets the position of the vertex
|
| |
|
void | setColor (float r, float g, float b, float a) |
| | sets the color of the vertex
|
| |
|
void | setColor (crvec3 c) |
| |
|
void | setUV (float u, float v) |
| | sets the uv coordinates of the vertex
|
| |
|
|
glm::vec2 | pos |
| | the vertex's position, color, and uv coordinates, respectively
|
| |
|
glm::vec4 | color |
| |
|
glm::vec2 | uv |
| |
|
float | hasTexture |
| |
represents a vertex in 2 dimensions
Definition at line 26 of file Vertex.h.
◆ attribs
Initial value:= {
{3, 1, GL_FLOAT, GL_FALSE,
sizeof(
Vertex2D), (
void*)offsetof(
Vertex2D, hasTexture)}
}
Definition at line 71 of file Vertex.h.
The documentation for this struct was generated from the following files:


From sketch to an awesome product
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged.
We have business guys
-
Albert Finney
Co-founder and CEO -
Danyel Hadnin
Co-founder
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type.
... creatives guys
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the.
-
Albert Finney
Creative director -
Mike Smith
Designer -
Jereth Finney
Designer
... development guys
-
Albert Finney
Artist -
Mike Smith
Artist -
Jereth Finney
Artist
... actually we have all the guys you need to create a great product


@(user: securesocial.core.Identity)(implicit request: RequestHeader, lang: Lang) @import securesocial.core.IdentityProvider
Your new Akvaario account, with the username @user.email, is ready.
Click here to log in.
This message was sent by Akvaario.