Valid

Valid

We have 12300 GBP in total from the project. Split 3 ways:

• Daniel: 4100 GBP
• Darren: 4100 GBP
• Neil: 4100 GBP

For project management purposes that's 41 days (at 300 GBP per day):

• Outreach = 5
• Research = 3
• Management = 3
• Streaming player = 10
• VALID = 16
• Events = 2
• Server = 2

Or 82 days at a low rate (at 150 GBP per day):

• Outreach = 10
• Research = 6
• Management = 6
• Streaming player = 20
• VALID = 32
• Events = 4
• Server = 4

For VALID system Kendra have 32 days (at low rate - so 16 days high rate):

• Create wireframes = 3 (N = 3)
• Research define metadata = 8 (N = 4 / K = 4)
• License / legal structure = 8 (N = 4 / lawyer = 4)
• Brand & interface = 8 (N = 8 / Y = 8)
• Site build / assembly = 14 (N = 8 / K = 6)
• Integrate front end / Ajax = 10 (Y = 4 / N = 1 / K = 4 / 3 = )
  • Query Builder - nested data structure: add/modify nodes
  • http://plugins.jquery.com/project/SQL_QUERY_BUILDER
  • http://www.kendra.org.uk/wiki/wiki.pl?KendraBaseQueryBuilderScreenshots
• Output data in machine readable = 14 (N = 2 / K = 12)
• Getting test data =8 (N = 2 / K = 4 / Y = 2)
• Testing & debugging = 6 = (N =2 / K = 2 / Y = 2)

Neil previously said for Valid Database:

• 5 day - define rules language and notation
• 3 day write parser / generator / xml parser / xml generator - basic tools
• 4 day - write command line quart engine
• 3 day license on prototype.

Notes:

• Limit users over development period - invited content owners only.
• Many videos can use same license.

Modules:

• Build license
• Calculate price - license builds questionnaire form - conditional pricing calculated from license and status of consumer
• Search video database - faceted

---

The licence query engine is in three parts:

• a Drupal widget that launches a javascript, with optional parameters sourced from Drupal's own tables and can accept a form entry back from that script

• A javascript that can run through a questionnaire, at each stage either asking a new question of the user, or doing a form entry when the job is done

• A web service which is called back by the Javascript, that determines what questions are to be asked, or gives the final OK

• The questions will be HTML FORMS, so they can ask more than one question at a time.

• Answers to be stored in the Drupal database

• Each time we invoke the query engine, it will be provided with the full license, and all the answers to all the questions answered so far; this means the query engine will be stateless

• Interface to the query engine will be JSON web service

• As far as Drupal is concerned, the license is just a string, and the questions are just name/value pairs stored in a standard Drupal table

• Note that Drupal will perform a final LOCAL reverifiction of the token

---

NH:

• designs license data structures, parser, generator
• works with Darren and Daniel to design Drupal schemas, which interlock with license schema
• builds license query engine (the hard bit of the whole system)
• builds authentication system (license query engine outputs auth token at the end of the process)
• all of the above are available as web services to the rest of the system
• documents interfaces to all of the above, as they are written
• does not do any Drupal or Javascript programming, but does liase with the authors of those parts to ensure that all code works together
• will write microformat scraper that can extract license statements from web pages
• will allow for valid validator to be launched from another web page, will then scrape license from referrer...