Create a Wordpress Template

<?xml version="1.0" encoding="UTF-8"?> <!-- list element if required --> <!ELEMENT recipe_list (recipe*)> <!-- top level recipe element --> <!ELEMENT recipe (name, description, course, servings, suitability?, ingredients, method)> <!-- container elements --> <!ELEMENT suitability (diet*)> <!ELEMENT ingredients (ingredient+)> <!ELEMENT method (step+)> <!-- basic elelements --> <!ELEMENT name (#PCDATA)> <!ELEMENT description (#PCDATA)> <!ELEMENT course (#PCDATA)> <!ELEMENT servings (#PCDATA)> <!ELEMENT diet (#PCDATA)> <!ELEMENT step (#PCDATA)> <!-- complex elelement --> <!ELEMENT ingredient (#PCDATA)> <!ATTLIST ingredient quantity CDATA #REQUIRED unit_of_measure (item | g | kg | ml | l ) #REQUIRED > With the above DTD complete the following task Recipes are requested by eatFast users by specifying: • Any dietary requirements they have in terms of the type of diet they need to eat, e.g. low fat • Dietary requirements may also include particular cuisines they might prefer, e.g. Indian • Any ingredients they would prefer the dish to contain, e.g. yogurt • The type of course the dish would be suitable for, e.g. a main dish or starter The user requests are passed to publishers who return lists of recipes for dishes that match the user requirements. The recipe information supplied by publishers will typically include: • The name of the dish • A short description of the dish • The course, i.e. when the dish is normally served/eaten • Any special diets for which the dish may be suitable • The number of people the dish would normally feed, i.e. the servings, given the specified quantities of ingredients • A description of the method used to make the dish, including details of the individual steps involved in the process Tasks 1. Using the supplied DTD ([login to view URL]), create an XML file for a sample recipe to be used by eatFast. You should include at least three ingredients and four steps in the method of preparation. You should name this document ‘[login to view URL]’. 2. Create an XSD/Schema file based on the supplied DTD file and your sample XML file from task 1. Your schema should ensure that; • the ‘course’ is restricted to the values ‘starter’, ‘main’, ‘drink’ or ‘dessert’. • the number of servings is between 1 and 6. • the (optional) suitability information is limited to at most three particular diets • the diets initially being catered for include ‘vegetarian’, ‘low fat’, and ‘diabetic’ You should name this document ‘[login to view URL]’. 3. Create an XSD/Schema and a sample XML file to show how a recipe request should be structured, based on the information contained in the briefing above. You should name theses document ‘[login to view URL]’ and ‘[login to view URL]’ 4. Extend both the initial recipe XML document that you created in task 1, and the XSD/Schema that you constructed in task 2, to include more nutritional details of ingredients. These details should include: • the number of calories contained in a specified quantity e.g. 100g • substitute ingredients for particular diets, e.g. using quorn instead of pork for vegetarians An ingredient may have up to 3 substitute ingredients. The substitute ingredient should contain the same information as a regular ingredient with the exception that substitutes cannot themselves have substitutes. You should name your documents ‘[login to view URL]’ and ‘[login to view URL]’. 5. Create an XLST file to display the initial recipe from task 1 as HTML in a web browser. The resulting output should be simple and clear to view. You should name the XSLT file ‘[login to view URL]’. Write a short (500 words, +/-10%) report, describing how you chose to structure the extended recipe and recipe request documents. As part of that report, you should consider how you have/could make use of namespaces in the system to define your data and the role of id attributes