Background Reports: Credit Report
Recommendation, 2006 Feb 28
Editors: Craig Corner, HireCheck; Chuck
Allen, HR-XML Consortium, Inc.
Contributors:
Brad Whitney, American Background; Sue Morgan, HireCheck; Paul Kiel, HR-XML Consortium, Inc.; Mark Sulimirski, ChoicePoint; Charles Rieckhoff, HireRight; Owen Wilson, Total Information Services, Inc.
Copyright statement
©2006 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 contains the element definitions for the
HR-XML Consortium’s Credit Report schema (Credit.xsd). The schema is a
component of HR-XML’s Background Checking specification. For further
information on the Background Checking Specification, see:
http://ns.hr-xml.org/2_5/HR-XML-2_5/Screening/US/BackgroundChecking.html
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
3.1 Design Requirements: Interoperability With Credit Bureau Formats
3.2 Schema Element Descriptions
3.2.17 MostRecentAdverseRating
4 Implementation Considerations
4.2 Laws Governing Credit Checks
5 Appendix A – Document Version History
6 Appendix B – Related Documents
Credit reports are frequently used as part of a background check. Credit reports can help verify basic facts about the search subject, including prior employers, addresses, and other names the search subject may have used. This information may be be used as input for other screenings, such as employment verification and criminal records searches. For example, identifying prior addresses can be important for deciding which courts to target for a criminal records search. Of course, credit reports also provide valuable insight into a job applicant’s financial responsibility. This may be particularly important if a position involves handling cash, responsibility for managing money, or similar fiduciary responsibilities.
There are several private “bureaus” that provide credit reports for employment screening purposes. Within the United States, Experian’s Employee Insight™, Equifax’s Persona™, and Trans Union’s PEER™ are the most widely used services. Each service makes its data available in its own proprietary format.
The HR-XML Consortium’s Credit Report schema is intended to be granular and sufficiently detailed to capture all of the credit data relevant to employment screening. In designing the schema, members of the HR-XML Consortium’s Screening workgroup reviewed the reports produced by each of the credit bureaus. They were careful to ensure that the HR-XML Consortium Credit Reports schema could accommodate all the relevant data fields from the credit bureau report formats. The HR-XML Consortium schema has been designed so that where necessary, the credit bureau’s codes, scoring, and scoring model identifiers can be passed through within an HR-XML Credit Report instance document.
Implementors should note that the Consortium’s Credit Report schema is not necessarily suitable for purposes other than employment screening. Consider that the Mortgage Industry Standards Maintenance Organization (see http://www.mismo.org) has developed an XML specification for the capture of credit-report details necessary for the processing of mortgage applications. The MISMO specification captures the set of credit-report data pertinent to mortgage processing in the same way that the HR-XML specification captures credit report data pertinent to employment screening.
Credit Bureau. An agency that provides credit and collection data on consumers within a particular time frame (usually measured in years). This data includes people's credit histories, and can be released in the form of credit reports.
Credit score. This term is used to refer to credit bureau risk scores. It broadly refers to a number generated by a statistical model that is used to objectively evaluate information that pertains to making a credit decision.
Equifax. One of the three major credit bureaus.
Experian. One of the three major major credit bureaus, formerly known as TRW.
Inquiry. Every time a lender requests a credit report, a notation is made on the consumer's record describing the lender, the type of request, and the date. The request is called an “inquiry” and is used to moniter consumer requests for credit.
Installment Loan. A credit account in which the amount of the payment and the number of payments are predetermined or fixed.
Public Record. Information obtained by the credit bureau from public court records, such as liens, bankruptcy filings, and judgments. Public records are open to any person who requests them.
Revolving Account. An account which requires at least a specified minimum payment each month plus a service charge on the balance. As the balance declines, the amount of the service charge, or interest, also declines.
Trans Union. One of the three major credit bureaus.
The HR-XML Consortium’s Credit Report schema was
designed as a component of the HR-XML Consortium’s Background Checking
specification. For a description and illustration of supported business
processes, see:
http://ns.hr-xml.org/2_5/HR-XML-2_5/Screening/US/BackgroundChecking.html
The Credit Reporting schema also could be used on a “stand-alone”
basis. For example, the schema might be useful in building interfaces between
“credit reporting engines” and employment screening service
providers.
The HR-XML Consortium Credit schema was designed as much as possible to be interoperable with data formats used by major credit bureaus. The HR-XML Consortium’s Sreening workgroup tried to ensure that all data fields relevant to employment screening could be mapped from credit-bureau formats to the HR-XML Consortium’s interchange format. The schema is designed so that where necessary, credit bureau’s codes, scoring, and scoring model identifiers can be passed through within an HR-XML Credit Report instance document. Consequently, a full understanding of how to implement the HR-XML Credit Report schema may require some understanding of the source credit-bureau formats and codes. Implementers should contact the credit bureaus directly for technical details on their data formats and code sets.
|
Component Name [Global types listed at the end of the table.] |
ContentModel* |
Definition |
|
/ |
- CreditReportType - (1/1) |
Contains a report on the credit status/history of the search subject. A credit report is the result of a credit screening request. |
|
/
CreditReport/ |
- FlexibleDatesType - S (0/1) |
The date the report was processed or generated. This uses FlexibleDatesType, which can accommodate date information in a variety of formats, including a string. For example “Spring 2003.” This flexibility is necessary since source data often does not conform to a formal or complete date format. This type is used throughout the schema. |
|
/
CreditReport/ |
- CreditSSNVerifiedType - S (0/*) |
Personal and identifying data used as input to the credit search. |
|
/
CreditReport/ CreditFile/ |
- FlexibleDatesType - S (0/1) |
Date that credit file was established. |
|
/
CreditReport/ CreditFile/ |
- FlexibleDatesType - S (0/1) |
Date of last activity reported. |
|
/
CreditReport/ CreditFile/ |
- EntityIdType - S (0/1) |
File reference number as assigned by Credit Bureau. |
|
CreditFile/ |
- CreditPersonalDataType - S
(1/*) |
A collection of information containing descriptive elements, demographic and contact information about the search subject. |
|
/
[CreditPersonalDataType] / |
xsd:restriction base: xsd:string [Enumerations]: Alias, Other, Current, Prior, NotSpecified |
Further
defines the associated element in the context provided. |
|
/
[CreditPersonalDataType] / |
- xsd:string - |
May
contain a reference number of the company, and name if the member company
that provided the Personal data to the repository. |
|
/
[CreditPersonalDataType] / |
- xsd:string - |
The
actual source that is reporting the ID. |
|
/
[CreditPersonalDataType] / |
- xsd:boolean - |
Information
captured by the credit repository. |
|
/
[CreditPersonalDataType] / |
- xsd:positiveInteger - |
Used
within the FlexibleDetailType to identify the sequence of items. |
|
/
CreditFile/ PersonalData/ |
- EffectiveDateType - S (0/1) |
Date or
time interval on or during which information or events are effective. |
|
/
CreditFile/ PersonalData/ |
xsd:extension base: PersonNameType |
The name of a person. |
|
/
CreditFile/ PersonalData/ PersonName/ |
- PersonNameTypeType - |
Further
defines the associated element in the context provided. |
|
/
CreditFile/ PersonalData/ |
- CreditPostalAddressType - S (0/*) |
A
mailing address. Describes a postal address used for delivery of mail. The
address may include the country code, postal code, a region, municipality,
delivery address, and the recipient. |
|
/
CreditFile/ PersonalData/ PostalAddress/ |
- ReportedDateType - S (0/1) |
The date
the information was recorded or reported. |
|
/
CreditFile/ PersonalData/ PostalAddress/ |
- xsd:string - S (0/1) |
Entity last reporting the information. |
|
/
CreditFile/ PersonalData/ |
- ContactMethodType - S (0/*) |
Defines
the methods of contacting a person or organizations. |
|
/
CreditFile/ PersonalData/ |
- DemographicDetailType - S (0/1) |
A collection of government related and demographic information about the person. |
|
/
CreditFile/ PersonalData/ |
- ReportedDateType - S (0/1) |
The date
the information was recorded or reported. |
|
/
CreditFile/ PersonalData/ |
- xsd:string - S (0/1) |
Entity last reporting the information. |
|
/
CreditReport/ CreditFile/ PersonalData/ |
- DemographicDetailType - S
(0/1) |
Demographic information for the subject upon which the screening will be performed upon. Primarily the GovernmentId, DateofBirth, Race and GenderCode unless otherwise specified by the organization performing the screening. Note that DemographicDetailType is defined within DemographicDetail.xsd, a CPO schema included within ScreeningTypes.xsd. |
|
/
CreditReport/ CreditFile/ |
OrganizationName
- xsd:string - S
(1/1) |
A collection of information about a current or former employer of the person who is the subject of the credit report. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
xsd:restriction base: xsd:string [Enumerations]: Current, Prior, Spouse, Other, Unknown |
Indicates the type employment information being reported. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
- xsd:string - S (1/1) |
The name by which an organization or enterprise is known as established under the laws of a country, state, province or ruling governmental body for the purpose of conducting business transactions. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
- xsd:string - S (0/1) |
The title of the position held by the human resource. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
- CreditPostalAddressType - S (0/1) |
CPO's PostalAddress 1.2 version. Defines the mailing address of the worksite. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ PostalAddress/ |
- ReportedDateType - S (0/1) |
The date the information was added to the credit file. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
xsd:extension base: TelcomNumberType |
A telephone number. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ Telephone/ |
- xsd:string - |
The type or classification for the related component. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
- ReportedDateType - S (0/1) |
The date the information was added to the credit file. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
- FlexibleDatesType - S (0/1) |
The date on which the reported information was last verified |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
- EffectiveDateType - S (0/1) |
Dates of employment. |
|
/
CreditReport/ CreditFile/ EmploymentInformation/ |
- PositionCompensationType - S (0/*) |
Details on the compensation package offered to a human resource. |
|
/ CreditReport/
CreditFile/ EmploymentInformation/ |
xsd:restriction base: xsd:string [Enumerations]: Current, Prior, Spouse, Other, Unknown |
The type or classification for the related component. |
|
/
CreditReport/ CreditFile/ |
- CreditPersonalDataType – S (0/*) |
Any other names or aliases reported for the search subject. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ |
xsd:extension base: PersonNameType |
The name of a person. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ PersonName/ |
- PersonNameTypeType - |
The type of PersonName. Enumerated values include Subject, Alias, Other, Contact. Other values are permitted if pre-fixed with “x:”. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ |
- CreditPostalAddressType - S (0/*) |
CPO's PostalAddress 1.2 version. Defines the mailing address of the worksite. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ PostalAddress/ |
- ReportedDateType - S (0/1) |
The date the information was added to the credit file. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ |
- ContactMethodType - S (0/*) |
Contact information, such as work or home telephone number. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ |
- DemographicDetailType - S (0/1) |
A collection of government related and demographic information about the person. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ |
- ReportedDateType - S (0/1) |
The date
the information was recorded or reported. |
|
/
CreditReport/ CreditFile/ ReportedAliases/ |
- xsd:string - S (0/1) |
Entity last reporting the information. |
The credit repository bureaus can identify the type of business of the liability holder. This information is needed for an automated scoring application. This data is available for liability and inquiry records from Equifax, Experian and Trans Union.
|
/
CreditReport/ |
- CreditConsumerReferralType - S (0/*) |
Contains contact information for the credit bureau(s) and/or other organization responsible for reporting the information in the credit report. |
|
/
CreditReport/ CreditConsumerReferal/ |
- CreditBusinessTypeType - S (0/1) |
The credit repository bureaus can identify the type of business of the liability holder. This information is needed for an automated scoring application. This data is available for liability and inquiry records from Equifax, Experian and Trans Union. |
|
/
CreditReport/ CreditConsumerReferal/ CreditBusinessType/ |
- CreditBusinessTypeQualifiers - S (0/1) |
Container for the value required by the current context. |
|
/
CreditReport/ CreditConsumerReferal/ CreditBusinessType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ CreditConsumerReferal/ CreditBusinessType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
- CreditLiabilityType - S (0/*) |
A collection of information regarding a credit liability -- e.g., loan, revolving credit line, etc. -- associated with the search subject. |
|
|
/
CreditReport/ CreditLiability/ |
- xsd:boolean - S (0/1) |
A boolean indicating whether further review may be required. |
|
/
CreditReport/ CreditLiability/ |
- FlexibleDatesType - S (0/1) |
The date that the credit liability account was closed by the liability holder. |
|
/
CreditReport/ CreditLiability/ |
- xsd:string - S (0/1) |
The account number assigned to the liability account as provided by the credit repository bureau. |
|
/
CreditReport/ CreditLiability/ |
- FlexibleDatesType - S (0/1) |
The date that the credit liability account was opened by the liability holder. |
|
/
CreditReport/ CreditLiability/ |
- FlexibleDatesType - S (0/1) |
The date that the credit liability was reported paid to zero by the liability holder. |
|
/
CreditReport/ CreditLiability/ |
- FlexibleDatesType - S (0/1) |
The date that the credit liability data was reported by the liability holder. |
|
/
CreditReport/ CreditLiability/ |
- FlexibleDatesType - S (0/1) |
The AccountStatusDate is the date that the account's CurrentRating was last changed by the liability holder. If the CurrentRating status is Bankruptcy, for example, the StatusDate would be when the account first went into bankkruptcy. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
The amount charged off by a liability holder, usually for an account in collection. |
|
/
CreditReport/ CreditLiability/ |
- xsd:string - S (0/1) |
A description of any property or other collateral securing the loan. |
|
/
CreditReport/ CreditLiability/ |
- xsd:boolean - S (0/1) |
A boolean to indicate whether or not the consumer (borrower) disputes information reported for this account and has filed a FCRA dispute form. |
|
/
CreditReport/ CreditLiability/ |
- xsd:boolean - S (0/1) |
A boolean that indicates whether or not the liability account contains adverse or derogatory information. |
|
/
CreditReport/ CreditLiability/ |
xsd:extension base: xsd:string |
Terms of the deferred acount. |
|
/
CreditReport/ CreditLiability/ DeferredAccountTerms/ |
- DeferredLoanTermsType - |
Type of loan terms. Allows Experian value – “D” – or additional values if pre-fixed with “x:”. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
The highest balance recorded for the account by the liability holder. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
The highest credit limit established for the account by the liability holder. It could be higher than the current credit limit. |
|
/
CreditReport/ CreditLiability/ |
- FlexibleDatesType - S (0/1) |
Date of last activity reported. |
|
/
CreditReport/ CreditLiability/ |
- xsd:string - S (0/1) |
The current manner of payment for the liability account. |
|
/
CreditReport/ CreditLiability/ |
- LateDelinquentCountType - S (0/*) |
The number of times the liability account was reported late by the liability holder. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
The original amount of the loan. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
The monthly amount the consumer has paid or is scheduled to pay. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
The estimated monthly amount the consumer will pay or is scheduled to pay. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
The monthly amount the consumer is scheduled to pay. |
|
/
CreditReport/ CreditLiability/ |
- xsd:integer - S (0/1) |
The number of months of account history reported by the liability holder. This is the period over which Late Counts are accumulated. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
Amount past due. |
|
/
CreditReport/ CreditLiability/ |
- FlexibleDatesType - S (0/1) |
The date the account first reached the present status level. |
|
/
CreditReport/ CreditLiability/ |
- xsd:string - S (0/1) |
A text description for the loan terms (for example, 360 months at $820 per month). |
|
/
CreditReport/ CreditLiability/ |
- xsd:positiveInteger - S (0/1) |
The total number of months established as terms for repayment of a loan. |
|
/
CreditReport/ CreditLiability/ |
xsd:restriction base: xsd:string [Enumerations]: Calculated, Provided |
Indicates whether the monthly payment terms amount was provided by the repository bureau, or calculated by the credit bureau. |
|
/
CreditReport/ CreditLiability/ |
- CurrencyAmountType - S (0/1) |
The balance owed on a liability account as of the Date Reported by a repository bureau or credit bureau. |
|
/
CreditReport/ CreditLiability/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
/
CreditReport/ CreditLiability/ |
- CreditContactType - S (0/1) |
Contact information for a lender or other creditor. |
|
/
CreditReport/ CreditLiability/ Creditor/ |
- xsd:string - S (1/1) |
The name by which an organization or enterprise is known as established under the laws of a country, state, province or ruling governmental body for the purpose of conducting business transactions. |
|
/
CreditReport/ CreditLiability/ Creditor/ |
- xsd:string - S (0/1) |
When a liability account has been transferred or is being handled by a collection agency, this element indicates the name of original creditor. |
|
/
CreditReport/ CreditLiability/ Creditor/ |
- EntityIdType - S (0/1) |
An organizational identifier. |
|
/
CreditReport/ CreditLiability/ Creditor/ |
- CreditBusinessTypeType - S (0/1) |
The credit repository bureaus can identify the type of business of the liability holder. This information is needed for an automated scoring application. This data is available for liability and inquiry records from Equifax, Experian and Trans Union. |
|
/
CreditReport/ CreditLiability/ Creditor/ CreditBusinessType/ |
- CreditBusinessTypeQualifiers - S (0/1) |
Enumerated values include: “Advertising”, ”Automotive”, ”Banking”, ”Clothing”, “CollectionServices”, “Contractors”, etc. For further information, see CreditBusinessTypeQualifiers in Section 3.2.35, Global Simple Types. |
|
/
CreditReport/ CreditLiability/ Creditor/ CreditBusinessType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ CreditLiability/ Creditor/ CreditBusinessType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditLiability/ Creditor/ |
- ContactMethodType - S (0/1) |
Contact information, such as work or home telephone number. |
|
/
CreditReport/ CreditLiability/ |
- AccountOwnershipTypeType - S (0/1) |
Describes the relationship between the borrower(s) and the liability account. The following enumerations are available for "Value": AuthorizedUser; Comaker; Individual; JointContractualLiability; JointParticipating; Maker; OnBehalfOf; Terminated; and Undesignated. Additional values are allowed if prefixed with an "x:" Also contains RepositoryCode and RepositoryValue. These elements have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditLiability/ AccountOwnershipType/ |
- AccountOwnershipTypes - S (0/1) |
Container for the value required by the current context. |
|
/
CreditReport/ CreditLiability/ AccountOwnershipType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ CreditLiability/ AccountOwnershipType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditLiability/ |
- AccountStatusTypeType - S (0/1) |
Status for an account as of the AccountStatusDate. |
|
/
CreditReport/ CreditLiability/ AccountStatusType/ |
- AccountStatusTypes - S (0/1) |
Indicates the status of the account. Enumerated values are: “Closed”, “Frozen”, “Open”, “Paid”, “Refinanced”, and “Transferred”. Additional values are permitted if pre-fixed with “x:”. |
|
/
CreditReport/ CreditLiability/ AccountStatusType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ CreditLiability/ AccountStatusType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditLiability/ |
- AccountTypeType - S (0/1) |
This describes the type of account established with the liability account holder. For example, credit line, installment, mortgage, open, revolving. Enumerated values include CreditLine; Installment; Mortgage; Open; Revolving; and Unknown. Additional values are allowed if prefixed with an "x:" Also contains RepositoryCode and RepositoryValue. These elements have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditLiability/ AccountType/ |
- AccountTypeTypes - S (0/1) |
The type of account. Enumerations include “CreditLine”, “Installment”, “Mortgage”, “Open”, “Revolving”, and “Unknown”. Additional values are permitted if pre-fixed with “x:”. |
|
/
CreditReport/ CreditLiability/ AccountType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ CreditLiability/ AccountType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditLiability/ |
- CreditLoanTypeType - S (0/1) |
Contains information describing the type of loan or liability. Value under CreditLoanType can contain more than 90 enumerated values (for example, Automobile, AutoRefinance, Boat, etc.) Also contains RepositoryCode and RepositoryValue. These elements have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditLiability/ CreditLoanType/ |
- CreditLoanTypeTypes - S (0/1) |
Identifies the type of loan. More than 90 loan types are enumerated. “Agriculture”, “ChildSupport”, “Lease”, and “Mortgage” are examples of possible values. Additional values are permtted if they are pre-fixed with “x:”. |
|
/
CreditReport/ CreditLiability/ CreditLoanType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ CreditLiability/ CreditLoanType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditLiability/ |
- CreditRatingType - S (0/1) |
Contains credit bureau codes, "manner of payment" with respect to delinquencies, and dates and amounts when the borrower was late on payments. |
|
/
CreditReport/ CreditLiability/ CurrentRating/ |
- xsd:string - S (0/1) |
Code value provided by credit bureau. |
|
/
CreditReport/ CreditLiability/ CurrentRating/ |
- MOPTypeType - S (0/1) |
The type of information supplied. |
|
/
CreditReport/ CreditLiability/ CurrentRating/ |
- CurrencyAmountType - S (0/1) |
A monetary amount. |
|
/
CreditReport/ CreditLiability/ CurrentRating/ |
- FlexibleDatesType - S (0/1) |
A date. |
|
/
CreditReport/ CreditLiability/ |
- CreditRatingType - S (0/1) |
The most recent date and payment history code of the worst status beyond the current payment history element's contents. |
|
/
CreditReport/ CreditLiability/ HighestAdverseRating/ |
- xsd:string - S (0/1) |
Code value provided by credit bureau. |
|
/
CreditReport/ CreditLiability/ HighestAdverseRating/ |
- MOPTypeType - S (0/1) |
This is the account’s Manner Of Payment (MOP) type. Enumerated values include: AsAgreed, ChargeOff, Collection, Foreclosure, Late30Days, Late60Days, Late90Days, LateOver120Days, NoDataAvailable, Repossession, TooNew, WageEarnerPlan. Additional values are permitted if pre-fixed with “x:”. |
|
/
CreditReport/ CreditLiability/ HighestAdverseRating/ |
- CurrencyAmountType - S (0/1) |
A monetary amount. |
|
/
CreditReport/ CreditLiability/ HighestAdverseRating/ |
- FlexibleDatesType - S (0/1) |
A date. |
|
/
CreditReport/ CreditLiability/ |
- CreditRatingType - S (0/1) |
The most recent amount that the borrower was reported delinquent by the liability holder. |
|
/
CreditReport/ CreditLiability/ MostRecentAdverseRating/ |
- xsd:string - S (0/1) |
Code value provided by credit bureau. |
|
/ CreditReport/
CreditLiability/ MostRecentAdverseRating/ |
- MOPTypeType - S (0/1) |
This is the account’s Manner Of Payment (MOP) type. Enumerated values include: AsAgreed, ChargeOff, Collection, Foreclosure, Late30Days, Late60Days, Late90Days, LateOver120Days, NoDataAvailable, Repossession, TooNew, WageEarnerPlan. Additional values are permitted if pre-fixed with “x:”. |
|
/
CreditReport/ CreditLiability/ MostRecentAdverseRating/ |
- CurrencyAmountType - S (0/1) |
A monetary amount. |
|
/
CreditReport/ CreditLiability/ MostRecentAdverseRating/ |
- FlexibleDatesType - S (0/1) |
A date. |
|
/
CreditReport/ CreditLiability/ |
- PaymentPatternType - S (0/1) |
This is a set of previous monthly payment ratings beginning with the Payment Pattern Start Date. |
|
/
CreditReport/ CreditLiability/ PaymentPattern/ |
- xsd:string - S (1/1) |
The date of the beginning of the data in the Credit Liability Payment Pattern Data. |
|
/
CreditReport/ CreditLiability/ PaymentPattern/ |
- FlexibleDatesType - S (0/1) |
The beginning effective date for the specified supporting information. |
|
/
CreditReport/ CreditLiability/ |
- CreditRatingType - S (0/1) |
Information on prior adverse ratings. |
|
/
CreditReport/ CreditLiability/ PriorAdverseRating/ |
- xsd:string - S (0/1) |
Code value provided by credit bureau. |
|
/
CreditReport/ CreditLiability/ PriorAdverseRating/ |
- MOPTypeType - S (0/1) |
This is the account’s Manner Of Payment (MOP) type. Enumerated values include: AsAgreed, ChargeOff, Collection, Foreclosure, Late30Days, Late60Days, Late90Days, LateOver120Days, NoDataAvailable, Repossession, TooNew, WageEarnerPlan. Additional values are permitted if pre-fixed with “x:”. |
|
/
CreditReport/ CreditLiability/ PriorAdverseRating/ |
- CurrencyAmountType - S (0/1) |
A monetary amount. |
|
/
CreditReport/ CreditLiability/ PriorAdverseRating/ |
- FlexibleDatesType - S (0/1) |
A date. |
|
/
CreditReport/ CreditLiability/ |
Description
- xsd:string - S
(0/1) |
A description of the payment history of the account as of the balance date. |
|
/
CreditReport/ CreditLiability/ PaymentStatus/ |
- xsd:string - S (0/1) |
Describes any work site environment information not previously defined. For example, square footage of work area. |
|
/
CreditReport/ CreditLiability/ PaymentStatus/ |
- xsd:string - S (0/1) |
Code value provided by credit bureau. |
|
/
CreditReport/ CreditLiability/ |
- MessagesType - S (0/*) |
Informational messages provided by the organization granting the credit. |
|
/
CreditReport/ CreditLiability/ InformationalMessage/ |
- MessageType - S (0/1) |
Additional identification of the message or alert source. i.e. EquifaxSAFESCAN, Lender, RepositoryBureau, etc. |
|
/
CreditReport/ CreditLiability/ InformationalMessage/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
CreditReport/ CreditLiability/ InformationalMessage/ |
- xsd:string - S (1/*) |
Explanatory text. |
|
/
CreditReport/ CreditLiability/ InformationalMessage/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/ CreditReport/ |
- PublicRecordsType - S (0/*) |
Information on bankruptcy and similar liabilities related to court actions/records. |
|
/
CreditReport/ PublicRecord/ |
- xsd:boolean - S (0/1) |
A boolean indicating whether further review may be required. |
|
/
CreditReport/ PublicRecord/ |
- AccountOwnershipTypeType - S (0/1) |
Describes the relationship between the borrower(s) and the liability account. The following enumerations are available for "Value": AuthorizedUser; Comaker; Individual; JointContractualLiability; JointParticipating; Maker; OnBehalfOf; Terminated; and Undesignated. Additional values are allowed if prefixed with an "x:" Also contains RepositoryCode and RepositoryValue. These elements have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ PublicRecord/ AccountOwnershipType/ |
- AccountOwnershipTypes - S (0/1) |
Container for the value required by the current context. |
|
/
CreditReport/ PublicRecord/ AccountOwnershipType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ PublicRecord/ AccountOwnershipType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ PublicRecord/ |
- AgencyReferenceType - S (0/1) |
Contains the case, docket, or other identifier and associated file date assigned by the reporting agency. |
|
/
CreditReport/ PublicRecord/ |
- xsd:string - S (0/1) |
The name of the firm or person serving providing legal representation or service as an attorney. |
|
/
CreditReport/ PublicRecord/ |
- CurrencyAmountType - S (0/1) |
The amount of the defendants declared assets at the time of bankruptcy. |
|
/
CreditReport/ PublicRecord/ |
- CurrencyAmountType - S (0/1) |
The amount of the defendants declared liabilities at the time of bankruptcy. |
|
/
CreditReport/ PublicRecord/ |
- BankruptcyTypeType - S (0/1) |
Specifies the type of bankruptcy. Valid values are "Business" and "Individual". Additional values are permitted if prefixed with "x:". |
|
/
CreditReport/ PublicRecord/ |
- BankruptcyFilingMethodType - S (0/1) |
Specifies the bankruptcy filing methods. Valid values are "Individual" and "Joint". Additional values are permitted if prefixed with "x:". |
|
/
CreditReport/ PublicRecord/ |
- xsd:string - S (0/1) |
Name of court to be searched. If court and/or country is not available, then PostalCode and Municipality must be supplied. In all cases, Region and CountryCode in the parent element must be supplied. |
|
/
CreditReport/ PublicRecord/ |
- xsd:string - S (0/1) |
Number identifying a court. |
|
/
CreditReport/ PublicRecord/ |
- xsd:boolean - S (0/1) |
A boolean to indicate whether or not the consumer (borrower) disputes information reported for this account and has filed a FCRA dispute form. |
|
/
CreditReport/ PublicRecord/ |
- CreditContactType - S (0/1) |
Contact information for a lender or other creditor. |
|
/
CreditReport/ PublicRecord/ Creditor/ |
- xsd:string - S (1/1) |
The name by which an organization or enterprise is known as established under the laws of a country, state, province or ruling governmental body for the purpose of conducting business transactions. |
|
/
CreditReport/ PublicRecord/ Creditor/ |
- xsd:string - S (0/1) |
When a liability account has been transferred or is being handled by a collection agency, this element indicates the name of original creditor. |
|
/
CreditReport/ PublicRecord/ Creditor/ |
- EntityIdType - S (0/1) |
An organizational identifier. |
|
/
CreditReport/ PublicRecord/ Creditor/ |
- CreditBusinessTypeType - S (0/1) |
The credit repository bureaus can identify the type of business of the liability holder. This information is needed for an automated scoring application. This data is available for liability and inquiry records from Equifax, Experian and Trans Union. |
|
/
CreditReport/ PublicRecord/ Creditor/ CreditBusinessType/ |
- CreditBusinessTypeQualifiers - S (0/1) |
Container for the value required by the current context. |
|
/
CreditReport/ PublicRecord/ Creditor/ CreditBusinessType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ PublicRecord/ Creditor/ CreditBusinessType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ PublicRecord/ Creditor/ |
- ContactMethodType - S (0/1) |
Contact information, such as work or home telephone number. |
|
/
CreditReport/ PublicRecord/ |
- FlexibleDatesType - S (0/1) |
Date action was filed with the court. |
|
/
CreditReport/ PublicRecord/ |
- xsd:string - S (0/1) |
The name of the defendant. |
|
/
CreditReport/ PublicRecord/ |
- xsd:boolean - S (0/1) |
A boolean that indicates whether or not the liability account contains adverse or derogatory information. |
|
/
CreditReport/ PublicRecord/ |
- FlexibleDatesType - S (0/1) |
The disposition date of the bankruptcy action. |
|
/
CreditReport/ PublicRecord/ |
- CreditDispositionType - S (0/1) |
Type of bankruptcy disposition. Enumerated values include: Adjudicated; Appealed; Cancelled; Completed; Converted; Discharged; Dismissed; Distributed; Filed; Granted; InvoluntarilyDischarged; Nonadjudicated; Other; Paid; PaidNotSatisfied; Pending; RealEstateSold; Released; Rescinded; Satisfied; Settled; Unknown; Unreleased; Unsatisfied; Vacated; VoluntarilyDischarged; and Withdrawn. Additional values are permitted if prefixed with an "x:". |
|
/
CreditReport/ PublicRecord/ |
- CurrencyAmountType - S (0/1) |
This is the amount listed in the public record that the defendant is obligated to pay. |
|
/
CreditReport/ PublicRecord/ |
- xsd:boolean - S (0/1) |
This element indicates whether or not the data in the public record has been manually updated by the credit bureau based on an investigation. |
|
/
CreditReport/ PublicRecord/ |
- FlexibleDatesType - S (0/1) |
Date upon which final payment or settlement is due. |
|
/
CreditReport/ PublicRecord/ |
- FlexibleDatesType - S (0/1) |
The date that the liability or legal obligation amount was paid to zero. |
|
/
CreditReport/ PublicRecord/ |
- PaymentFrequencyTypeType - S (0/1) |
The frequency with which payments are made. For example, Monthly, Bi-Weekly, etc. |
|
/
CreditReport/ PublicRecord/ |
- xsd:string - S (0/1) |
The name of the person or other entity who is the plaintiff. |
|
/
CreditReport/ PublicRecord/ |
- PublicRecordTypeType - S (0/1) |
The type of public record from which liability arises. Enumerated values include Annulment, BankruptcyChapter11, CustodyAgreement, DivorceDecree, etc. Additional values are permitted if prefixed with an "x:" |
|
/
CreditReport/ PublicRecord/ |
- FlexibleDatesType - S (0/1) |
The date the information was added to the credit file. |
|
/
CreditReport/ PublicRecord/ |
- FlexibleDatesType - S (0/1) |
The date that the public record case was settled. |
|
/
CreditReport/ PublicRecord/ |
- FlexibleDatesType - S (0/1) |
The StatusDate is the date that the accounts Current Rating was changed to that status by the liability holder. If the current rating status is bankruptcy, for example, the StatusDate would be when the account first went into bankkruptcy. |
|
/
CreditReport/ PublicRecord/ |
- xsd:boolean - S (0/1) |
A boolean value. True if consumer voluntarily dismissed bankruptcy. |
|
/
CreditReport/ PublicRecord/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
/
CreditReport/ PublicRecord/ |
- MessagesType - S (0/*) |
Informational messages provided by the organization granting the credit. |
|
/
CreditReport/ PublicRecord/ InformationalMessage/ |
- MessageType - S (0/1) |
Additional identification of the message or alert source. i.e. EquifaxSAFESCAN, Lender, RepositoryBureau, etc. |
|
/
CreditReport/ PublicRecord/ InformationalMessage/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
CreditReport/ PublicRecord/ InformationalMessage/ |
- xsd:string - S (1/*) |
Explanatory text. |
|
/
CreditReport/ PublicRecord/ InformationalMessage/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ PublicRecord/ |
- MessagesType - S (0/*) |
Informational messages provided by the organization granting the credit. |
|
/
CreditReport/ PublicRecord/ InformationalMessage/ |
- MessageType - S (0/1) |
Additional identification of the message or alert source. i.e. EquifaxSAFESCAN, Lender, RepositoryBureau, etc. |
|
/
CreditReport/ PublicRecord/ InformationalMessage/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
CreditReport/ PublicRecord/ InformationalMessage/ |
- xsd:string - S (1/*) |
Explanatory text. |
|
/
CreditReport/ PublicRecord/ InformationalMessage/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ |
- InquiryType - S (0/*) |
A credit inquiry by a prospective creditor or other business. |
|
/
CreditReport/ CreditInquiry/ |
- FlexibleDatesType - S (0/1) |
Date of inquiry. |
|
/
CreditReport/ CreditInquiry/ |
- CreditContactType - S (1/1) |
Name and contact information for organization making the inquiry on consumer. |
|
/
CreditReport/ CreditInquiry/ InquiringOrganization/ |
- xsd:string - S (1/1) |
The name by which an organization or enterprise is known as established under the laws of a country, state, province or ruling governmental body for the purpose of conducting business transactions. |
|
/
CreditReport/ CreditInquiry/ InquiringOrganization/ |
- xsd:string - S (0/1) |
When a liability account has been transferred or is being handled by a collection agency, this element indicates the name of original creditor. |
|
/
CreditReport/ CreditInquiry/ InquiringOrganization/ |
- EntityIdType - S (0/1) |
An organizational identifier. |
|
/
CreditReport/ CreditInquiry/ InquiringOrganization/ |
- CreditBusinessTypeType - S (0/1) |
The credit repository bureaus can identify the type of business of the liability holder. This information is needed for an automated scoring application. This data is available for liability and inquiry records from Equifax, Experian and Trans Union. |
|
/
CreditReport/ CreditInquiry/ InquiringOrganization/ CreditBusinessType/ |
- CreditBusinessTypeQualifiers - S (0/1) |
Enumerated values include: “Advertising”, ”Automotive”, ”Banking”, ”Clothing”, “CollectionServices”, “Contractors”, etc. For further information, see CreditBusinessTypeQualifiers in Section 3.2.35, Global Simple Types. |
|
/
CreditReport/ CreditInquiry/ InquiringOrganization/ CreditBusinessType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ CreditInquiry/ InquiringOrganization/ CreditBusinessType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditInquiry/ InquiringOrganization/ |
- ContactMethodType - S (0/1) |
Contact information, such as work or home telephone number. |
|
/
CreditReport/ CreditInquiry/ |
- CreditLoanTypeType - S (0/1) |
Contains information describing the type of loan or liability. Value under CreditLoanType can contain more than 90 enumerated values (for example, Automobile, AutoRefinance, Boat, etc.) Also contains RepositoryCode and RepositoryValue. These elements have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditInquiry/ CreditLoanType/ |
- CreditLoanTypeTypes - S (0/1) |
Identifies the type of loan. More than 90 loan types are enumerated. “Agriculture”, “ChildSupport”, “Lease”, and “Mortgage” are examples of possible values. Additional values are permtted if they are pre-fixed with “x:”. |
|
/
CreditReport/ CreditInquiry/ CreditLoanType/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ CreditInquiry/ CreditLoanType/ |
- xsd:string - S (0/1) |
RepositoryCode and RepositoryValue have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/
CreditReport/ CreditInquiry/ |
- xsd:string - S (0/1) |
A text description for the loan terms (for example, 360 months at $820 per month). |
|
/
CreditReport/ CreditInquiry/ |
- InquiryResultTypeType - S (0/1) |
The result from a credit inquiry. Did the lender offer credit, refuse credit, etc. For complete enumerations, see InquiryResultTypeQualifiers in Section 3.2.35, Global Simple Types. |
|
/
CreditReport/ CreditInquiry/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
/
CreditReport/ CreditInquiry/ |
- MessagesType - S (0/*) |
Informational messages provided by the organization granting the credit. |
|
/ CreditReport/
CreditInquiry/ InformationalMessage/ |
- MessageType - S (0/1) |
Additional identification of the message or alert source. i.e. EquifaxSAFESCAN, Lender, RepositoryBureau, etc. |
|
/
CreditReport/ CreditInquiry/ InformationalMessage/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
CreditReport/ CreditInquiry/ InformationalMessage/ |
- xsd:string - S (1/*) |
Explanatory text. |
|
/
CreditReport/ CreditInquiry/ InformationalMessage/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/ |
- SummaryType - S (0/*) |
Contains summary information regarding the search subject's credit. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Total number of closed accounts. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Total number of collection accounts. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Total number of collection accounts transferred to third party collection agency. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
The number of employment inquiries. |
|
/
CreditSummary/ |
- xsd:boolean - S (0/1) |
A boolean that indicates whether any information has been reported from foreign bureaus. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Number of inquiries in file. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Total number of Installment accounts. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Total number of Mortgage accounts. |
|
/
CreditSummary/ |
- FlexibleDatesType - S (0/1) |
The date of the most recent trade. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Number of tradelines currently with derogatory status codes. |
|
/
CreditSummary/ |
- FlexibleDatesType - S (0/1) |
Oldest trade date. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Total number of open accounts. |
|
/ CreditSummary/ |
- xsd:integer - S (0/1) |
Total number of open accounts. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Number of inquiries during period supported by vendor of credit information. For example, Experian's reporting period is last 6 months. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
An integer indicating the number of public record items on the profile. |
|
/
CreditSummary/ |
- CurrencyAmountType - S (0/1) |
Balance of real estate liability. |
|
/ CreditSummary/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of real estate payments. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
The total number of revolving accounts. |
|
/
CreditSummary/ |
- xsd:decimal - S (0/1) |
Whole percentage amount from 0 - 100, showing the percent of revolving credit available. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Number of trades or other items in file. |
|
/
CreditSummary/ |
- xsd:integer - S (0/1) |
Number of tradelines with past derogatory status codes. |
|
/
CreditSummary/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
/
CreditSummary/ |
- CreditSummaryAmountType - S (0/1) |
Dollar amount of installment loans. |
|
/
CreditSummary/ BalanceAmount/ |
- CurrencyAmountType - S (0/1) |
A monetary total. |
|
/
CreditSummary/ BalanceAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ BalanceAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ BalanceAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of closed tradelines that still contain a balance. |
|
/
CreditSummary/ |
DelinquentCount
- LateDelinquentCountType - S (0/*) |
Contains counts of various types of delinquencies. For example, thirty days delinquent, sixty days delinquent, "current negative count," etc. |
|
/
CreditSummary/ DelinquencyCounters/ |
- LateDelinquentCountType - S (0/*) |
Contains counts of various types of delinquencies. For example, thirty days delinquent, sixty days delinquent, "current negative count," etc. |
|
/
CreditSummary/ DelinquencyCounters/ |
- xsd:integer - S (0/1) |
Number of times derogatory information has been posted. |
|
/
CreditSummary/ DelinquencyCounters/ |
- xsd:integer - S (0/1) |
Current count of negative information reported. |
|
/
CreditSummary/ DelinquencyCounters/ |
- xsd:integer - S (0/1) |
Previous count of negative information reported. |
|
/
CreditSummary/ DelinquencyCounters/ |
- xsd:integer - S (0/1) |
Previous times with a negative count. |
|
/
CreditSummary/ |
- CreditSummaryAmountType - S (0/1) |
The highest credit limit established for the account by the liability holder. It could be higher than the current credit limit. |
|
/
CreditSummary/ HighCreditAmount/ |
- CurrencyAmountType - S (0/1) |
A monetary total. |
|
/
CreditSummary/ HighCreditAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ HighCreditAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ HighCreditAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of closed tradelines that still contain a balance. |
|
/
CreditSummary/ |
- CreditSummaryAmountType - S (0/1) |
Balance past due. |
|
/
CreditSummary/ PastDueBalance/ |
- CurrencyAmountType - S (0/1) |
A monetary total. |
|
/
CreditSummary/ PastDueBalance/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ PastDueBalance/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ PastDueBalance/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of closed tradelines that still contain a balance. |
|
/
CreditSummary/ |
- CreditSummaryAmountType - S (0/1) |
Dollar amount of monthly payments. |
|
/
CreditSummary/ PaymentAmount/ |
- CurrencyAmountType - S (0/1) |
A monetary total. |
|
/
CreditSummary/ PaymentAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ PaymentAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ PaymentAmount/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of closed tradelines that still contain a balance. |
|
/
CreditSummary/ |
- CreditSummaryAmountType - S (0/1) |
Contains credit limit data, including totals for installment and revolving credit lines. |
|
/
CreditSummary/ TotalCreditLimit/ |
- CurrencyAmountType - S (0/1) |
A monetary total. |
|
/
CreditSummary/ TotalCreditLimit/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/ CreditSummary/
TotalCreditLimit/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of revolving tradelines. |
|
/
CreditSummary/ TotalCreditLimit/ |
- CurrencyAmountType - S (0/1) |
Dollar amount of closed tradelines that still contain a balance. |
|
/
CreditSummary/ |
TradeRating - xsd:positiveInteger - S (0/*) |
Trade rating. |
|
/
CreditSummary/ TradeRatings/ |
xsd:extension base: xsd:positiveInteger |
A positive integer indicating the credit bureau-assigned trade rating. Has a required attribute "ratingType", which is used to indicate the type of trade rating. |
|
/
CreditSummary/ TradeRatings/ TradeRating/ |
- xsd:string - |
A string indicating the type of credit-bureau assigned trade rating. |
|
/
CreditSummary/ |
- MessagesType - S (0/*) |
Informational messages provided by the organization granting the credit. |
|
/
CreditSummary/ InformationalMessage/ |
- MessageType - S (0/1) |
Additional identification of the message or alert source. i.e. EquifaxSAFESCAN, Lender, RepositoryBureau, etc. |
|
/
CreditSummary/ InformationalMessage/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
CreditSummary/ InformationalMessage/ |
- xsd:string - S (1/*) |
Explanatory text. |
|
/
CreditSummary/ InformationalMessage/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ |
- ScoreType - S (0/*) |
A score or rating assigned by a credit bureau based on the analysis of a search subject's credit history. Such analysis and rating is accomplished according to a designated "score model" developed by the credit bureau. |
|
/
CreditReport/ CreditScore/ |
- xsd:string - S (0/1) |
Identifies the score algorithm model name used to produce the referenced credit risk score. |
|
/
CreditReport/ CreditScore/ |
- xsd:integer - S (1/1) |
Numeric credit score resulting from credit evaluation model. |
|
/
CreditReport/ CreditScore/ |
- xsd:boolean - S (0/1) |
A boolean value. Can be generated if a negative public record or collection is present or, in the case of Trans Union, when a MOP 07 or higher condition exists. |
|
/
CreditReport/ CreditScore/ |
Code - xsd:string - S (0/1) |
Factors of the borrowers credit which give context to the referenced credit score. The factor code is normally a numeric code. |
|
/
CreditReport/ CreditScore/ Factor/ |
- xsd:string - S (0/1) |
Code value provided by credit bureau. |
|
/
CreditReport/ CreditScore/ Factor/ |
- xsd:string - S (0/1) |
Describes any work site environment information not previously defined. For example, square footage of work area. |
|
/
CreditReport/ CreditScore/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
/
CreditReport/ CreditScore/ |
- MessagesType - S (0/*) |
Informational messages provided by the organization granting the credit. |
|
/
CreditReport/ CreditScore/ InformationalMessage/ |
- MessageType - S (0/1) |
Additional identification of the message or alert source. i.e. EquifaxSAFESCAN, Lender, RepositoryBureau, etc. |
|
/
CreditReport/ CreditScore/ InformationalMessage/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
CreditReport/ CreditScore/ InformationalMessage/ |
- xsd:string - S (1/*) |
Explanatory text. |
|
/
CreditReport/ CreditScore/ InformationalMessage/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/
CreditReport/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
/
CreditReport/ |
- MessagesType - S (0/*) |
Informational messages provided by the organization granting the credit. |
|
/
CreditReport/ InformationalMessage/ |
- MessageType - S (0/1) |
Additional identification of the message or alert source. i.e. EquifaxSAFESCAN, Lender, RepositoryBureau, etc. |
|
/
CreditReport/ InformationalMessage/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
CreditReport/ InformationalMessage/ |
- xsd:string - S (1/*) |
Explanatory text. |
|
/
CreditReport/ InformationalMessage/ |
- xsd:string - S (0/1) |
A code provided by the credit bureau repository. |
|
/ |
- [Union]: AccountOwnershipTypeQualifiers, |
Enumerated account ownership types are: AuthorizedUser, Comaker Individual, JointContractualLiability, JointParticipating, Maker, OnBehalfOf, Terminated, and Undesignated. Additional values are permitted if prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: AuthorizedUser, Comaker, Individual, JointContractualLiability, JointParticipating, Maker, OnBehalfOf, Terminated, Undesignated |
Enumerated account ownership types are: AuthorizedUser, Comaker Individual, JointContractualLiability, JointParticipating, Maker, OnBehalfOf, Terminated, and Undesignated. Additional values are permitted if prefixed with “x:”. |
|
/ |
- [Union]: AccountStatusQualifiers, |
Indicates the status of the account. Enumerated values are: “Closed”, “Frozen”, “Open”, “Paid”, “Refinanced”, and “Transferred”. Additional values are permitted if prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Closed, Frozen, Open, Paid, Refinanced, Transferred |
Indicates the status of the account. Enumerated values are: “Closed”, “Frozen”, “Open”, “Paid”, “Refinanced”, and “Transferred”. Additional values are permitted if prefixed with “x:”. |
|
/ |
- [Union]: AccountTypeQualifiers, |
The type of account. Enumerations include “CreditLine”, “Installment”, “Mortgage”, “Open”, “Revolving”, and “Unknown”. Additional values are permitted if prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: CreditLine, Installment, Mortgage, Open, Revolving, Unknown |
The type of account. Enumerations include “CreditLine”, “Installment”, “Mortgage”, “Open”, “Revolving”, and “Unknown”. Additional values are permitted if prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: EquifaxSAFESCAN, EquifaxSSNVerified, ExperianFACSPlus, TransUnionHAWKAlert, TransUnionTransAlert |
Identifies the source of an alert. Enumerations include: EquifaxSAFESCAN, EquifaxSSNVerified, ExperianFACSPlus, TransUnionHAWKAlert, TransUnionTransAlert |
|
/ |
- [Union]: BankruptcyTypeQualifiers, |
Specifies the type of bankruptcy. Valid values are "Business" and "Individual". Additional values are permitted if prefixed with "x:". |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Business, Individual |
Specifies the type of bankruptcy. Valid values are "Business" and "Individual". Additional values are permitted if prefixed with "x:". |
|
/ |
- [Union]: BankruptcyFilingMethodQualifiers, |
Specifies the bankruptcy filing methods. Valid values are "Individual" and "Joint". Additional values are permitted if prefixed with "x:". |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Individual, Joint |
Specifies the bankruptcy filing methods. Valid values are "Individual" and "Joint". Additional values are permitted if prefixed with "x:". |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Borrower, CreditBureau, Equifax, Experian, Lender, RepositoryBureau, TransUnion, Unknown |
Indicates the source of a comment. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Advertising, Automotive, Banking, Clothing, CollectionServices, Contractors, CreditCard, DepartmentAndMailOrder, Employment, FarmAndGardenSupplies, Finance, Government, Grocery, HomeFurnishing, Insurance, JewelryAndCamera, LumberAndHardware, MedicalAndHealth, MiscellaneousAndPublicRecord, OilAndNationalCreditCards, PersonalServicesNotMedical, RealEstateAndPublicAccommodation, SportingGoods, UtilitiesAndFuel, Wholesale |
Type of organization extending credit. |
|
/ |
- [Union]: CreditConsumerReferralTypes, |
Identifies the credit bureau(s) and/or other organization responsible for reporting the information in the credit report. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Equifax, Experian, File, TransUnion, Vendor, Other |
Identifies the credit bureau(s) and/or other organization responsible for reporting the information in the credit report. Enumerated values include “Equifax”, “Experian”, “File”, “TransUnion”, “Vendor”, and “Other”. Additional values are permitted if prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Adjudicated, Appealed, Cancelled, Completed, Converted, Discharged, Dismissed, Distributed, Filed, Granted, InvoluntarilyDischarged, Nonadjudicated, Other, Paid, PaidNotSatisfied, Pending, RealEstateSold, Released, Rescinded, Satisfied, Settled, Unknown, Unreleased, Unsatisfied, Vacated, VoluntarilyDischarged, Withdrawn |
The current status of disposition of the liability. Enumerated values include: “Adjudicated”, “Appealed”, “Cancelled”, “Completed”, “Converted”, “Discharged”, “Withdrawn”, etc. Additional values are permitted if prefixed with an “x:”. |
|
/ |
- [Union]: CreditDispositionTypes, |
Type of bankruptcy disposition. Enumerated values include: Adjudicated; Appealed; Cancelled; Completed; Converted; Discharged; Dismissed; Distributed; Filed; Granted; InvoluntarilyDischarged; Nonadjudicated; Other; Paid; PaidNotSatisfied; Pending; RealEstateSold; Released; Rescinded; Satisfied; Settled; Unknown; Unreleased; Unsatisfied; Vacated; VoluntarilyDischarged; and Withdrawn. Additional values are permitted if prefixed with an "x:". |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Adjudicated, Appealed, Cancelled, Completed, Converted, Discharged, Dismissed, Distributed, Filed, Granted, InvoluntarilyDischarged, Nonadjudicated, Other, Paid, PaidNotSatisfied, Pending, RealEstateSold, Released, Rescinded, Satisfied, Settled, Unknown, Unreleased, Unsatisfied, Vacated, VoluntarilyDischarged, Withdrawn |
Type of bankruptcy disposition. Enumerated values include: Adjudicated; Appealed; Cancelled; Completed; Converted; Discharged; Dismissed; Distributed; Filed; Granted; InvoluntarilyDischarged; Nonadjudicated; Other; Paid; PaidNotSatisfied; Pending; RealEstateSold; Released; Rescinded; Satisfied; Settled; Unknown; Unreleased; Unsatisfied; Vacated; VoluntarilyDischarged; and Withdrawn. Additional values are permitted if prefixed with an "x:". |
|
/ |
- [Union]: CreditLoanTypeQualifiers, |
Identifies the type of loan. More than 90 loan types are enumerated. “Agriculture”, “ChildSupport”, “Lease”, and “Mortgage” are examples of possible values. Additional values are permtted if they are prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Agriculture, Airplane, ApplianceOrFurniture, AttorneyFees, AutoLease, AutoLoanEquityTransfer, Automobile, AutoRefinance, Boat, Business, BusinessCreditCard, ChargeAccount, CheckCreditOrLineOfCredit, ChildSupport, Collection, CollectionAttorney, Comaker, CombinedCreditPlan, CommercialCreditObligation, CommercialLineOfCredit, CommercialMortgage, ConditionalSalesContract, Consolidation, ConventionalRealEstateMortgage, CreditCard, CreditLineSecured, DebitCard, DebtCounselingService, DepositRelated, Educational, Employment, FactoringCompanyAccount, FamilySupport, FarmersHomeAdministrationFHMA, FederalConsolidatedLoan, FHAComakerNotBorrower, FHAHomeImprovement, FHARealEstateMortgage, FinanceStatement, GovernmentBenefit, GovernmentEmployeeAdvance, GovernmentFeeForService, GovernmentFine, GovernmentGrant, GovernmentMiscellaneousDebt, GovernmentOverpayment, GovernmentSecuredDirectLoan, GovernmentSecuredGuaranteeLoan, GovernmentUnsecuredDirectLoan, GovernmentUnsecuredGuaranteeLoan, HomeEquityLineOfCredit, HomeImprovement, HouseholdGoods, HouseholdGoodsAndOtherCollateralAuto, HouseholdGoodsSecured, InstallmentLoan, InstallmentSalesContract, InsuranceClaims, Lease, LenderPlacedInsurance, ManualMortgage, MedicalDebt, MobileHome, Mortgage, NoteLoan, NoteLoanWithComaker, Other, PartiallySecured, PersonalLoan, RealEstateJuniorLiens, RealEstateLoanEquityTransfer, RealEstateMortgageWithoutOtherCollateral, RealEstateSpecificTypeUnknown, Recreational, RecreationalVehicle, Refinance, RefundAnticipationLoan, RentalAgreement, ResidentialLoan, ReturnedCheck, RevolvingBusinessLines, Secured, SecuredByCosigner, SecuredCreditCard, SecuredHomeImprovement, SinglePaymentLoan, SpouseSupport, SummaryOfAccountsWithSameStatus, TimeSharedLoan, Title1Loan, UnknownLoanType, Unsecured, VeteransAdministrationLoan, VeteransAdministrationRealEstateMortgage |
Contains information describing the type of loan or liability. Value under CreditLoanType can contain more than 90 enumerated values (for example, Automobile, AutoRefinance, Boat, etc.) Also contains RepositoryCode and RepositoryValue. These elements have a "name-value pair" relationship. RepositoryCode is a code assigned by the repository. RepositoryValue is the corresponding descriptive field for RepositoryCode. |
|
/ |
xsd:restriction base: xsd:string |
Must conform to the three-character code designated under ISO 4217 - Representation of Currency and Funds. For example, USD for U.S. dollars. |
|
/ |
- [Union]: ExperianLoanTermsTypes, |
Type of loan terms. Allows Experian value or additional values if pre-fixed with “x:”. |
|
/ |
- [Union]: CreditDispositionQualifiers, |
The current status of disposition of the liability. Enumerated values include: “Adjudicated”, “Appealed”, “Cancelled”, “Completed”, “Converted”, “Discharged”, “Withdrawn”, etc. Additional values are permitted if prefixed with an “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: D |
Type of loan terms. Allows Experian value or additional values if prefixed with “x:”. |
|
/ |
- [Union]: InquiryResultTypeQualifiers, |
Enumerations for inquiry result. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: AccountClosed, ApplicationPending, Declined, DidNotInquire, NoOpenAccount, NotALender, OpenAccountNumberNotIssued, OpenDiscovered, OpenPrimaryAccount, ReportingAgencyInquiry, Unknown |
Enumerations for inquiry result. |
|
/ |
- [Union]: LiabilityTypes,xStringPatternExtensionType |
Enumerations identifying the type of liability. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Trade, Collection, SecuredLoan, Other |
Enumerations identifying the type of liability. Enumerations include “Trade,” “Collection,” “SecuredLoan,” and “Other”. Additional values are permitted if prefixed with “x:”. |
|
/ |
- [Union]: CommentSourceTypes,AlertSourceTypes, |
Identifies the type of credit-bureau message. Enumerated values include: “Alert”, “Comment”, “Unknown”, and “Other”. Additional values are permitted if prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Alert, Comment, Unknown, Other |
Identifies the type of credit-bureau message. Enumerated values include: “Alert”, “Comment”, “Unknown”, and “Other”. |
|
/ |
- [Union]: MOPTypes,xStringPatternExtensionType |
This is the account’s Manner Of Payment (MOP) type. Enumerated values include: AsAgreed, ChargeOff, Collection, Foreclosure, Late30Days, Late60Days, Late90Days, LateOver120Days, NoDataAvailable, Repossession, TooNew, WageEarnerPlan. Additional values are permitted if prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: AsAgreed, ChargeOff, Collection, Foreclosure, Late30Days, Late60Days, Late90Days, LateOver120Days, NoDataAvailable, Repossession, TooNew, WageEarnerPlan |
This is the account’s Manner Of Payment (MOP) type. Enumerated values include: AsAgreed, ChargeOff, Collection, Foreclosure, Late30Days, Late60Days, Late90Days, LateOver120Days, NoDataAvailable, Repossession, TooNew, WageEarnerPlan. Additional values are permitted if prefixed with “x:”. |
|
/ |
- [Union]: PaymentFrequencyQualifiers, |
Enumerated payment frequencies. For example, Lumpsum, Monthly, Weekly, Biweekly. Additional values are permitted if prefixed with “x”: |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Biweekly, LumpSum, Monthly, Weekly, SemiMonthly, Daily, TwiceWeekly, FourWeeks, Quarterly, Annually, Other, Unknown |
Enumerated payment frequencies. For example, Lumpsum, Monthly, Weekly, Biweekly. |
|
/ |
- [Union]: PublicRecordTypes,xStringPatternExtensionType |
The type of public record from which a liability arises. Enumerated values include Annulment, BankruptcyChapter11, CustodyAgreement, DivorceDecree, etc. Additional values are permitted if prefixed with an "x:" |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Annulment, Attachment, BankruptcyChapter11, BankruptcyChapter12, BankruptcyChapter13, BankruptcyChapter7, BankruptcyChapter7Involuntary, BankruptcyChapter7Voluntary, BankruptcyTypeUnknown, Collection, CustodyAgreement, DivorceDecree, FicticiousName, FinancialCounseling, FinancingStatement, ForcibleDetainer, Foreclosure, Garnishment, Judgment, LawSuit, Lien, NonResponsibility, NoticeOfDefault, Other, PublicSale, RealEstateRecording, Repossession, SupportDebt, TaxLienCity, TaxLienCounty, TaxLienFederal, TaxLienOther, TaxLienState, Trusteeship, Unknown, UnlawfulDetainer |
The type of public record from which a liability arises. Enumerated values include Annulment, BankruptcyChapter11, CustodyAgreement, DivorceDecree, etc. Additional values are permitted if prefixed with an "x:" |
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).
Implementers of the HR-XML Consortium’s Credit Report schema are advised to review applicable law in the jurisdictions in which they operate. For example, in United States, the Fair Credit Reporting Act may require third-party providers of background-check services to obtain the consent of search subjects and to advise them of results before adverse action is taken.
|
Date |
Description |
|
2002 Dec 06 |
Initial Draft |
|
2003 Jan 23 |
Incorporated TSC/CPO comments / SAP comments |
|
2003 Feb 10 |
Incorporated changes from review |
|
2003 Feb 17 |
Edits to reflect schema changes necessary to resolve ambiguous content models |
|
2003-Feb-26 |
Approved recommendation by HR-XML Consortium. The default and targetNamespaces of all HR-XML schemas have been standardized to "http://ns.hr-xml.org". This recommendation is available as part of the HR-XML 2_0 architecture. |
|
2003-Sept-01 |
EmploymentHistory 2_2 passed a vote and incorporated here. No other changes. |
|
2004-Jun-25 |
Moved CurrencyAmountType and CurrencyType to ScreeningTypes schema. |
|
2006-Feb-28 |
Approved by Consortium |


Red and Black
问题描述 :
There is a rectangular room, covered with square tiles. Each tile is colored either red or black.  From a tile, he can move to one of four adjacent tiles. But he can’t move on red tiles, he can move only on black tiles.
Write a program to count the number of black tiles which he can reach by repeating the moves described above.
输入:
The input consists of multiple data sets. A data set starts with a line containing two positive integers W and H; W and H are the numbers of tiles in the x- and y- directions, respectively. W and H are not more than 20.
There are H more lines in the data set, each of which includes W characters. Each character represents the color of a tile as follows.
‘.’ – a black tile
‘#’ – a red tile
‘@’ – a man on a black tile(appears exactly once in a data set)
输出:
For each data set, your program should output a line which contains the number of tiles he can reach from the initial tile (including itself).
样例输入:
6 9 ....#. .....#<EMAIL_ADDRESS>.#..#. 11 9 .#......... .#.#######. .#.#.....#. .#.#.###.#<EMAIL_ADDRESS>.#.#####.#. .#.......#. .#########. ........... 11 6 ..#..#..#.. ..#..#..#.. ..#..#..###<EMAIL_ADDRESS>..#..#..#.. ..#..#..#.. 7 7 ..#.#.. ..#.#.. ###.###<EMAIL_ADDRESS>###.### ..#.#.. ..#.#.. 0 0
样例输出:
45 59 6 13
#include<cstdio> #include<iostream> #include<cstring> using namespace std; char maps[25][25]; int r,c,sx,sy,res; int dx[]={-1,1,0,0}; int dy[]={0,0,-1,1}; void dfs(int a,int b) { for(int i=0;i<4;i++) { int xx=a+dx[i]; int yy=b+dy[i]; if(xx>=1&&xx<=r&&yy>=1&&yy<=c&&maps[xx][yy]=='.') { maps[xx][yy]='#'; res++; dfs(xx,yy); } } } int main() { int i,j; while(scanf("%d%d",&c,&r)&&r&&c) { memset(maps,0,sizeof(maps)); res=1; getchar(); for(i=1;i<=r;i++) { for(j=1;j<=c;j++) { scanf("%c",&maps[i][j]); if(maps[i][j]=='@') { sx=i; sy=j; maps[i][j]='#'; } } getchar(); } dfs(sx,sy); printf("%d\n",res); } return 0; }
解题报告转自：http://blog.csdn.net/u011262722/article/details/9614697
(adsbygoogle = window.adsbygoogle || []).push({});
这是研发类的题还是算法类？
很好！！
第15行代码，/n/n，应该改为\n\n
不错，赞一个！
#!/usr/bin/env python
def cou(n):
arr =
i = 1
while(i<n):
arr.append(arr[i-1]+selfcount(i))
i+=1
return arr[n-1]
def selfcount(n):
count = 0
while(n):
if n%10 == 1:
count += 1
n /= 10
return count
没错的，九度OJ也有此题
没错的，九度OJ也有此题
Thanks for using the time to examine this, I truly feel strongly about it and enjoy finding out far more on this subject matter. If achievable, as you achieve knowledge
有意思，有难度
参考 http://www.acmerblog.com/leetcode-solutions-6422.html
顶一个 赞一个
从数学角度确实是C(n,r)，能给个递推关系式吗，从分治的角度不好理解
第一个真的要比较两次吗，换成else if 不可以吗
输入样例作为一个整体输入，带回车


Your browser does not support the canvas element or JavaScript is disabled.
Please enabled Javascript to play.


A color-coded version of this document showing changes made since the previous version is also available.
This document is also available in these non-normative formats: PDF version.
Copyright © 2012 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents.
This document specifies a syntax and semantics for incorporating linear equations with rational coefficients solved in the reals in OWL 2.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
Please send any comments to<EMAIL_ADDRESS>(public archive). Although work on this document by the OWL Working Group is complete, comments may be addressed in the errata or in future revisions. Open discussion among developers is welcome at<EMAIL_ADDRESS>(public archive).
Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. The group does not expect this document to become a W3C Recommendation. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
Table of Contents |
OWL 2 has a sophisticated set of built-in numeric dataranges and rather expressive constructors for building new dataranges out of the basic dataranges. A major restriction on the sort of data ranges that can be built with existing constructors (i.e., datatype facets) is that only unary dataranges can be defined --- i.e., only datatypes may be defined. One can say that the value of a data property has to be an integer greater than 5, but one cannot say that the value of one data property is greater than that of another data property. Furthermore, one might wish to relate the values of two properties by more complex equations than mere comparisons.
This document defines an extension to OWL for defining dataranges in terms of linear (in)equalites with rational coefficients solved over the algebraic reals. These dataranges can be used in OWL axioms to, for example, define classes in terms of a constraint on the relationships between values of distinct data properties.
This extension is restricted in two respects for the sake of reasonable implementability:
These restrictions may be lifted, to various degrees, in future versions of this specification.
Consider the relation between the boiling point and the melting point of a substance. For example, for water (at 1 atmosphere) the boiling point is 100C and the melting point 0C. This can be represented in plain OWL quite easily:
ClassAssertion(DataHasValue(melting_point "0"^^xsd:decimal) water) ClassAssertion(DataHasValue(boiling_point "100"^^xsd:decimal) water)
From these assertions it follows that the boiling point of water is greater than its melting point. This is, in fact, a general principle for substances: the boiling point of a normal physical substance is greater or equal to its melting point. This physical law can be expressed with a datarange with two free variables x and y, representing the melting and boiling point, respectively.:
EquivalentClasses(NormalSubstance DataAllValuesFrom(melting_point boiling_point DataComparison(Arguments(x y) leq( x y ))))
With this definition (and given that melting_point and boiling_point are functional), one can infer:
ClassAssertion(NormalSubstance water)
When administering drugs, there are many factors that go into determining the maximum safe dose. Often, the maximum the maximum single dose of a drug is computed in terms of milligram of drug per kilogram of body weight.
EquivalentClasses(SafelyDosedPatient DataAllValuesFrom(tookDrugInAmount weight DataComparison(Arguments(totalDoseInMg weightinKg) leq(totalDoseInMg times(2, weightInKg)))))
This axiom states that the safe dose is 2 milligrams per kilogram, and thus that a safe dose (in milligrams) for a person of a given weight must be less than 2 times the weight (in kilograms) of the patient.
As safe doses vary with age and other factors, one could define a number of such classes with varying constraints on the safety of the dose.
As with built-in OWL 2 data ranges, linear (in)equations may be used to form universal, existential, and quantified restrictions on (sets of) data properties.
ComparisonRelation :=
'gt' |
'lt' |
'geq' |
'leq' |
'eq' |
'neq'
Variable := NCName
Rational := Integer / NonZeroInteger
Term := 'times' '(' [ Rational ] Variable ')' | Variable
LinearExpression:= 'plus' '(' Term { Term } ')' | Term | Variable
Arguments := 'Arguments' '(' NCName { NCName } ')'
Comparison := 'DataComparison' '(' Arguments ComparisonRelation'(' Variable Variable ')' ')'
ScaledComparison := 'DataComparison' (' Arguments ComparisonRelation '(' Term Term ')' ')'
LinearComparison := 'DataComparison' '(' Arguments ComparisonRelation '(' LinearExpression LinearExpression ')' ')'
DataComparison := Comparison | ScaledComparison | LinearComparison
The definition of a DataRange is extended with the various comparisons:
DataRange :=
Datatype |
DataComplementOf |
DataOneOf |
DatatypeRestriction |
DataComparison
It is not currently possible for user defined (in)equations to be named, though it is easy to spec a natural syntax:
In order to retain decidability with naming, there needs to be acyclicity condition akin to those for datatypes. Furthermore, since there are DataComparisons which are equivalent to datatypes, the datatype and data comparison conditions must appropriately interact.
(In)equations in RDF are expressed using MathML as below. The equations are serialized as rdf:XMLLiterals. The content of those literals must conform to the "owl-linear-comparisons-mathml.xsd".
<!DOCTYPE rdf:RDF [ <!ENTITY xsd "http://www.w3.org/2001/XMLSchema#" > ]> <rdf:RDF xmlns="http://example.org/#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:owl="http://www.w3.org/2002/07/owl#"> <owl:Ontology rdf:about="http://example.org/"/> <owl:DatatypeProperty rdf:about="#boiling_point"/> <owl:DatatypeProperty rdf:about="#melting_point"/> <owl:Class rdf:about="#NormalSubstance"> <owl:equivalentClass> <owl:Restriction> <owl:onProperties rdf:parseType="Collection"> <owl:DatatypeProperty rdf:about="#boiling_point"/> <owl:DatatypeProperty rdf:about="#melting_point"/> </owl:onProperties> <owl:allValuesFrom> <owl:DataComparison> <rdf:value rdf:parseType="Literal"> <lambda xmlns="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/1998/Math/MathML owl-linear-comparisons-mathml.xsd"> <bvar> <ci>x</ci> </bvar> <bvar> <ci>y</ci> </bvar> <apply> <leq/> <ci>x</ci> <ci>y</ci> </apply> </lambda> </rdf:value> </owl:DataComparison> </owl:allValuesFrom> </owl:Restriction> </owl:equivalentClass> </owl:Class> <rdf:Description rdf:about="#water"> <rdf:type> <owl:Restriction> <owl:onProperty rdf:resource="#boiling_point"/> <owl:hasValue rdf:datatype="&xsd;integer">100</owl:hasValue> </owl:Restriction> </rdf:type> <rdf:type> <owl:Restriction> <owl:onProperty rdf:resource="#melting_point"/> <owl:hasValue rdf:datatype="&xsd;integer">0</owl:hasValue> </owl:Restriction> </rdf:type> </rdf:Description> </rdf:RDF>
For the XML syntax, the terminals of the functional syntax are mapped into corresponding MathML elements. Consider the water example:
<Ontology xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2002/07/owl# owlxml-datarange.xsd" xmlns="http://www.w3.org/2002/07/owl#" ontologyIRI="http://example.org/"> <ClassAssertion> <DataHasValue> <DataProperty IRI="melting_point"/> <Literal datatypeIRI="xsd:decimal">0</Literal> </DataHasValue> <NamedIndividual IRI="water"/> </ClassAssertion> <ClassAssertion> <DataHasValue> <DataProperty IRI="boiling_point"/> <Literal datatypeIRI="xsd:decimal">100</Literal> </DataHasValue> <NamedIndividual IRI="water"/> </ClassAssertion> <EquivalentClasses> <Class IRI="NormalSubstance"/> <DataAllValuesFrom> <DataProperty IRI="melting_point"/> <DataProperty IRI="boiling_point"/> <DataComparison> <lambda xmlns="http://www.w3.org/1998/Math/MathML"> <bvar> <ci>x</ci> </bvar> <bvar> <ci>y</ci> </bvar> <apply> <leq/> <ci>x</ci> <ci>y</ci> </apply> </lambda> </DataComparison> </DataAllValuesFrom> </EquivalentClasses> </Ontology>
In order to validate, one must use an extended version of the XML Schema. See Appendix A for the schema.
The semantics of all constructs where data ranges can occur (DataSomeValuesFrom, DataAllValuesFrom, DataMinCardinality, DataExactCardinality, DataMaxCardinality, DataComplementOf) is defined in Section 2 of the Semantics. This section defines the meaning of DataComparisons.
As explained in the Semantics document, this is accomplished by extending the datatype interpretation function ⋅ DT to DataComparison. First some notation: for an expression exp, a variable y and a value v, exp[y -> v] is the expression obtained by replacing all occurrences of y in exp with v.
Next, on the value space of owl:real, the equality = and ordering < are defined as usual, and the operators + and * are the usual addition and multiplication operators on the real numbers.
The value of terms is then defined as follows:
Intuitively, in order to find out whether a pair (5,60) of numbers is in, say, DataComparison(Arguments(y1 y2) lt (times("4"^^owl:real y1) times("1"^^owl:real y1)))DT, one replaces all occurrences of y1 in both times(...) terms with 5, all occurrences of y2 in both terms with 60, computes the value of both times(...) terms (the first giving 20, the second giving 60), and then checks whether lt holds between them. Since this is indeed the case, the pair (5,60) is in DataComparison(...).
In what follows, y1 and y2 refer to variables, t1 and t2 to terms, and L1 and L2 to linear expressions.
There is a rich literature on implementing linear solvers. The key papers for the integration between OWL and a linear solver are:
This schema is named "owlxml-with-linear-comparisons.xsd".
<?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.w3.org/2002/07/owl#" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:m="http://www.w3.org/1998/Math/MathML"> <xsd:import namespace="http://www.w3.org/1998/Math/MathML" schemaLocation="owl-comparisons-mathml.xsd"/> <xsd:redefine schemaLocation="http://www.w3.org/2009/09/owl2-xml.xsd"> <xsd:group name="DataRange"> <xsd:choice> <xsd:group ref="owl:DataRange"/> <xsd:element ref="owl:DataComparison"/> </xsd:choice> </xsd:group> </xsd:redefine> <xsd:complexType name="DataComparison"> <xsd:complexContent> <xsd:extension base="owl:DataRange"> <xsd:sequence> <xsd:element ref="m:lambda" minOccurs="1" maxOccurs="1"/> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="DataComparison" type="owl:DataComparison"/> </xsd:schema>
This schema is named "owl-linear-comparisons-mathml.xsd".
<?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.w3.org/1998/Math/MathML" xmlns="http://www.w3.org/1998/Math/MathML" xmlns:m="http://www.w3.org/1998/Math/MathML" elementFormDefault="qualified"> <xsd:element name="gt"/> <xsd:element name="lt"/> <xsd:element name="geq"/> <xsd:element name="leq"/> <xsd:element name="eq"/> <xsd:element name="neq"/> <xsd:element name="ci" type="xsd:NCName"/> <xsd:element name="sep"/> <xsd:element name="cn"> <xsd:complexType mixed="true"> <xsd:sequence> <xsd:element ref="sep" maxOccurs="1"/> </xsd:sequence> <xsd:attribute name="type"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:pattern value="real|rational"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:complexType> </xsd:element> <xsd:element name="bvar"> <xsd:complexType> <xsd:sequence> <xsd:element ref="m:ci" minOccurs="1" maxOccurs="1"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="times"> <xsd:complexType> <xsd:sequence> <xsd:element ref="m:cn"/> <xsd:element ref="m:ci" maxOccurs="1" minOccurs="1"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="plus"> <xsd:complexType> <xsd:sequence> <xsd:element ref="m:times" minOccurs="1"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="apply"> <xsd:complexType> <xsd:sequence> <xsd:choice minOccurs="1" maxOccurs="1"> <xsd:element ref="m:gt"/> <xsd:element ref="m:lt"/> <xsd:element ref="m:geq"/> <xsd:element ref="m:leq"/> <xsd:element ref="m:eq"/> <xsd:element ref="m:neq"/> </xsd:choice> <xsd:choice minOccurs="2" maxOccurs="2"> <xsd:element ref="m:ci"/> <xsd:element ref="m:times"/> <xsd:element ref="m:plus"/> </xsd:choice> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="lambda"> <xsd:complexType> <xsd:sequence> <xsd:element ref="m:bvar" minOccurs="1" maxOccurs="unbounded"/> <xsd:element ref="m:apply"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema>
This section summarizes the changes to this document since the Working Group Note of 27 October, 2009.


Spoilers: Secret turmoil for Ava in Home and Away
Justin’s (James Stewart) daughter Ava (Alice Roberts) has been staying in Summer Bay while Nina (Zoe Naylor) and Brian (Tom O’Sullivan) navigate a messy divorce, but Ava’s turbulent mood has left Justin and Leah (Ada Nicodemou) worried that something more could be going on than his daughter is telling them.
In the morning, Ava’s phone rings, and Justin sees it’s Brian. He encourages her to talk to her stepdad, but she brushes it off, saying she’ll call him later.
However, Leah approaches Justin later on, Ava’s phone in hand. She says she found it in the dog kennel, with 15 missed calls from Brian on the screen. Justin questions her about the phone, but she says she put the phone away as she was sick of it ringing all the time.
Justin calls Brian to work out why Ava has been ignoring him and finds out that Brian didn’t even know Ava was with him. Nina hasn’t been keeping him in the loop, and he had shown up to pick her up from practise only to find she wasn’t there.
While Brian has been trying to find out from Ava what’s going on, Nina tells Justin on the phone later on that she simply forgot to tell him his stepdaughter was in the Bay. Leah and Justin are suspicious, but then they overhear Ava clearly getting grilled by her mother on the phone.
Advertisement Advertisement
Justin finds out Nina has been telling Ava to avoid Brian’s calls, and swiftly steps in to intercept the call. He tells Nina that she needs to be protecting their daughter from her marriage drama, not dragging her into them.
He hangs up and tells Ava none of the situation is her fault. Then he decides he will do whatever it takes to make his daughter feel safe and secure – once he’s worked out how…


Redirects to the URL derived from the specified path
, with
specified status
, a positive integer that corresponds to an
HTTP status code
. If not specified, status
defaults to “302”Found".
res.redirect('/foo/bar')
res.redirect('http://example.com')
res.redirect(301, 'http://example.com')
res.redirect('../login')
Redirects can be a fully-qualified URL for redirecting to a different site:
Redirects can be relative to the root of the host name. For example, if
the application is on http://example.com/admin/post/new
, the
following would redirect to the URL http://example.com/admin
:
Redirects can be relative to the current URL. For example, from
http://example.com/blog/admin/
(notice the trailing slash),
the following would redirect to the URL
http://example.com/blog/admin/post/new
.
Redirecting to post/new
from
http://example.com/blog/admin
(no trailing slash), will
redirect to http://example.com/blog/post/new
.
If you found the above behavior confusing, think of path segments as directories (with trailing slashes) and files, it will start to make sense.
Path-relative redirects are also possible. If you were on
http://example.com/admin/post/new
, the following would
redirect to http://example.com/admin/post
:
A back
redirection redirects the request back to the
referer,
defaulting to /
when the referer is missing.


A problem solver by heart!
Self-motivated and hardworking
fresher seeking for an
opportunity
to work a challenging
environment
to prove my skills and utilize
my knowledge and intelligence
Intermediate (2015-2017)
PMS
Software Engineer (2017-Present)
Capital University of Science and Technology (CUST)
Internship July-September 2019 Internee (Software)
At Commission
on Science and Technology for Sustainable Development in
Mardan software House
2017 – Present Volunteer
At Capital University of Science and Technology (CUST), Islamabad
A problem solver by heart!
Self-motivated and hardworking
fresher seeking for an
opportunity
to work a challenging
environment
to prove my skills and utilize
my knowledge and intelligence
Intermediate (2015-2017)
Punjab Group of Colleges
Software Engineer (2017-Present)
Capital University of Science and Technology (CUST)
Internship July-September 2019 Internee (Software)
At Commission
on Science and Technology for Sustainable Development in
the South (COMSATS), Islamabad
2017 – Present Volunteer
At Capital University of Science and Technology (CUST), Islamabad
A problem solver by heart!
Self-motivated and hardworking
fresher seeking for an
opportunity
to work a challenging
environment
to prove my skills and utilize
my knowledge and intelligence
Intermediate (2015-2017)
Punjab Group of Colleges
Software Engineer (2017-Present)
Capital University of Science and Technology (CUST)
Internship July-September 2019 Internee (Software)
At Commission
on Science and Technology for Sustainable Development in
the South (COMSATS), Islamabad
2017 – Present Volunteer
At Capital University of Science and Technology (CUST), Islamabad


Demo WebApp
How high is carbon footprint of your city?
Green
Air quality is considered satisfactory, and air pollution poses little or no risk.
Yellow
Air quality is acceptable; however may be a moderate health concern for a very small number of people who are unusually sensitive to air pollution.
Orange
Members of sensitive groups may experience health effects. The general public is not likely to be affected.
Red
Everyone may begin to experience health effects; members of sensitive groups may experience more serious health effects.
Purple
Health alert: everyone may experience more serious health effects.
Maroon
Health warnings of emergency conditions. The entire population is more likely to be affected.
Your browser does not support HTML5 Canvas.


The Inn of the Sixth Happiness (1958)
Grade: 65
Ingrid Bergman's career was nearly destroyed by her affair with an Italian director, but by 1958 her image had recovered sufficiently for her to be cast as a saintly missionary. In "The Inn of the Sixth Happiness" (the title refers to a Chinese saying) her character can do no wrong, and her halo grows brighter and stronger as the film progresses.
Set in northern China, the production was to be filmed in nearby Formosa (modern-day Taiwan). When the Nationalist Chinese government tried to meddle with the storyline, the film's location was changed to the British island of Wales. There, local residents of Chinese ancestry were cast in supporting roles but were given no lines due to their un-Chinese Welsh accents.
The plot was based on the Alan Burgess biography of Gladys Aylward (Bergman). She was an ambitious English servant who in 1930, against all advice and without money, took a hazardous journey to China to work as a missionary. There, she runs an inn with the intention of converting travellers through Christian storytelling. She also becomes a paid Chinese government official, working to end the custom of foot-binding among young women.
As Aylward's do-gooding finds increasing success, she wins the respect of the local Mandarin official (Robert Donat) and Dutch-Chinese patriot Colonel Lin (Curt Jurgens). There is also an inevitable romance between Lin and Aylward, which can't really go anywhere due to the need to keep Bergman's character pure. Aylward's character begins performing heroic actions whose favorable resolutions seem implausible and simplistic. She stops a prison riot and effects reforms, and later leads a herd of children through territory threatened by ruthless Japanese invaders.
While Bergman's character is ageless and immortal, her supporting cast is not as fortunate. Among the martyred are elderly missionary Mrs.Lawson (Athene Seyler), genial assistant Yang (Peter Chong), and prison spokesman Li (Burt Kwouk).
Director Mark Robson received an Oscar nomination for work on "The Inn of Sixth Happiness".
This was Donat's final film. He died prior to the film's release. He gives a hammy but charming performance.
<EMAIL_ADDRESS>http://members.tripod.com/~Brian_Koller/movies.html
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


Markelov to make full-time F2 return as HWA's first driver for 2020
by Jack BenyonArtem Markelov will compete in Formula 2 for a seventh season as the ex-Renault Formula 1 junior joins the new HWA team for 2020.
Markelov first contested the series in 2014 when it was known as GP2. His best finish came in the first year of the F2 era in 2017 when he was runner-up to Charles Leclerc but, after concluding his stint with the Russian Time squad, he joined Super Formula in '19.
However, he replaced the Indy 500-bound Jordan King at the MP Motorsport team for this year's Monaco round, and is contesting the final two F2 events of 2019 with Arden - which will be replaced by HWA next year - after a troublesome period in Japan.
"I am really looking forward to racing for HWA RACELAB in Formula 2 next season," said Markelov, who failed to score a point in in Super Formula and was 21st overall.
"I think we will gel quickly.
"HWA has a vast wealth of motorsport experience, from which I am sure I will benefit."
Formula E and DTM company HWA branched out into junior single-seaters for the first time when it fielded a three-car team in FIA Formula 3 this year, finishing fifth in the teams' standings with Jake Hughes its highest-placed driver in the points in seventh.
HWA has purchased Arden's F2 entry, cars and equipment for 2020.
The two outfits signed an engineering deal for 2019, with the team's regular drivers - the late Anthoine Hubert and Tatiana Calderon - both receiving support from HWA engineers.
Ulrich Fritz, HWA's CEO, said Markelov's experience would prove helpful as the team becomes a separate entity.
"Artem is the ideal driver for us in our first season as an independent team in Formula 2," said Fritz.
"He has lots of experience at this level. His tally of eight race wins speaks for itself.
"His expertise as a driver will help make our introduction to the series easier. I am pleased that we were able to acquire his services."
HWA is yet to reveal its second driver for the 2020 season.


--- title: DS18B20 Temperature Sensors keywords: fastai sidebar: home_sidebar summary: "Classes and methods to handle DS18B20 temperature sensors arrached to a raspberry pi." description: "Classes and methods to handle DS18B20 temperature sensors arrached to a raspberry pi." nb_path: "index.ipynb" ---
This file will become your README and also the index of your documentation.
pip install ds18b20
Fill me in please! Don't forget code examples:
device = Device(base_dir='resources/')
# values from calibration
raw_low = -1.563
raw_high = 97.75
ref_low = 0.01
ref_high = 98.7
# set calibration
device.set_calibration('28-03219779d857', raw_low, raw_high, ref_low, ref_high)
temps = device.get_temps()
for dp in temps:
print(dp.get_device_sn(), dp.get_date_time(), format(dp.get_temp_C(), '.3f'))


Material examined
Search GBIF for a specimen code. Source code on
GitHub
.
Enter specimen code
Find
Status


| Name | Description |
|---|---|
| Example Name |
This is the description of Example Name. This is the description of Example Name.
This is the description of Example Name. This is the description of Example Name.
This is the description of Example Name. This is the description of Example Name.
|
| Example Name |
This is the description of Example Name. This is the description of Example Name.
This is the description of Example Name. This is the description of Example Name.
This is the description of Example Name. This is the description of Example Name.
|