Common use of Generic Requirements Clause in Contracts

Generic Requirements.  All feeds should be in JSON format  Each feed should have a [unique URL], which can accept parameters Required screens and feeds from Kew CMS:  Dashboard screen and feed. Configuration items: AR load radius (metres) Special message title Special message body Homescreen image identifier Names of Flickr collections to be used in Collections section. There will not be a fixed number of collections, but there will be at least 1. Price and opening time details on support screen Map/filter categories (e.g. „Off the beaten track‟), subcategories (e.g. „hidden gems‟) and default items (e.g. „Duke‟s Garden‟) Section and sub-section intro, where not pulled from Flickr Define default order for items in See Today section.  News feed - feed of all [news and blog articles] marked with „for mobile‟. Feed should include [image URL, title, caption and description] Fields are slightly different between news and blog items – to be finalised by Kew and supplier.  Attractions feed. Fields to be finalised by Kew and supplier.  Species page feed. Fields to be finalised by Kew and supplier.  Tree profile feed. Fields to be finalised by Kew and supplier.  AR screen and feed. Fields to be finalised by Kew and supplier.  Plant code feed – short URLs for Flickr sets and video URLs  Content hard-coded into app  Loader image  Section intro text – for each section and sub-section  Intro blurb on all other screens  Map base layer – and if possible all tiles  All screen graphics