NSI Web-Based Retailer Application 1.0
Conformance Requirements

NAME

NSI Web-Based Retailer Application

LABEL

CORE RETAILER WEB-BASED APPLICATIONS

When the NASPL Certification Logo, along with this label, is used on, or in relation to, a technology registered as conformant to this Conformance Requirements Document, it must be accompanied by an attribution in the form defined in Schedule 4 of the North American Association of State and Provincial Lotteries Certification Trademark License Agreement.

DESCRIPTION

This Conformance Requirements Document is for a web-based application intended for use by one or more lotteries for a retailer-focused website that provides financial and other information to retailers. Certification applies to the application itself, which may be installed at multiple lotteries with minimal configuration.

Certification applies to the application and supporting infrastructure, including support for the requirements defined in the Best Practice for data (such as format and availability), but not to the actual data present on the retailer-focused website.

CONFORMANCE REQUIREMENTS

The Conformance Requirements are derived from the following Best Practice:

• Core Retailer Web-Based Applications, Version 1, Document Number BP0601, October 2006, and any Corrigenda issued against such Best Practice, supplemented by any Interpretations applicable to this particular version and revision of the Best Practice.

A conformant Web-Based Retailer Application must:

• Implement all the mandatory "Must" requirements of the Best Practice for which "Web-based Technology Vendor" is identified as the Practitioner in the Requirements Checklist (Appendix A) of the Best Practice.
• Implement all the recommended "Should" requirements for which "Web-based Technology Vendor" is identified as the Practitioner in the Requirements Checklist (Appendix A) of the Best Practice, or provide a rationale in the Conformance Statement for why the recommendation is not followed.

Appendix A of the Best Practice provides a checklist of the mandatory, recommended, and optional requirements. This Appendix should be considered normative with respect to the assigned Practitioner for each requirement, but in the case of any conflict between the content of the checklist and the main body of the Best Practice, the Best Practice shall take precedence.

OVERRIDING STANDARDS

• Americans with Disabilities Act (ADA) requirements outlined in Section 508 of the Rehabilitation Act, US Department of Justice (www.usdoj.gov/crt/ada/adahom1.htm).
• Extensible Markup Language (XML) 1.0 (Third Edition), World Wide Web Consortium (W3C) (www.w3.org/TR/REC-xml).
• Extensible Stylesheet Language (XSL) Version 1.0, World Wide Web Consortium (W3C) (www.w3.org/TR/xsl).
• LDAP Version 3, as defined by the following series of Request for Comments documents:
  • IETF RFC 2251: Lightweight Directory Access Protocol (v3) (December 1997)
  • IETF RFC 2252: Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions (December 1997)
  • IETF RFC 2252: Lightweight Directory Access Protocol (v3): UTF-8 String Representations of Distinguished Names (December 1997)
  • IETF RFC 2253: Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names (December 1997)
  • IETF RFC 2254: Lightweight Directory Access Protocol (v3): The String Representation of LDAP Search Filters (December 1997)
  • IETF RFC 2255: Lightweight Directory Access Protocol (v3): The LDAP URL Format (December 1997)
  • IETF RFC 2256: Lightweight Directory Access Protocol (v3): A Summary of the X.500 User Schema for use with LDAPv3 (December 1997)
  • IETF RFC 2829: Lightweight Directory Access Protocol (v3): Authentication Models for LDAP (May 2000)
  • IETF RFC 2830: Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security (May 2000)
  • IETF RFC 3377: Lightweight Directory Access Protocol (v3): Technical Specification (September 2002)
• The Jabber Protocol, as defined by the following series of Request for Comments documents:
  • IETF RFC 3920: Extensible Messaging and Presence Protocol (XMPP): Core (Jabber Software Foundation, October 2004)
  • IETF RFC 3921: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence (Jabber Software Foundation, October 2004)
• NSI Technical Standard, XML Retail Accounting Reports in the Lottery Industry, TS0402, June 2005.
• XHTML 1.0: Extensible HyperText Markup Language (Second Edition), World Wide Web Consortium (W3C) (www.w3.org/TR/xhtml1).
• XML-RPC 1.0 (www.xmlrpc.com/spec).

INDICATORS OF CONFORMANCE

• A completed Validation Report, as specified in the NSI Core Retailer Web-Based Applications Validation Specification, which includes the results of running the validation tool on the website hosting the web-based application, along with the completed self-validation questionnaire.
• A Certificate showing the entity's certification against the NSI XML Retail Accounting Report Producing Applications 1.0 Conformance Requirements.

MIGRATION

As this is the first version of the NSI Web-Based Retailer Application Conformance Requirements, there are no migration issues.