Explore BrainMass
Share

Expanding XML, DTD, CSS files

This content was STOLEN from BrainMass.com - View the original, and get the already-completed solution here!

Expand the XML file a little bit by making sure that it is valid as well as well-formed.

"Create a DTD file that defines the format of the XML file. Also submit an updated version of the XML file that is linked to the DTD file.

To clarify :
? You will need to turn in three files for this project:
o Your DTD file. (The DTD needs to be contained in a separate file. (suggestion getting your DTD working as an internal DTD first and then once it is correct, work toward moving it outside of the XML file).
o A new version of the XML file you submitted last week renamed appropriately and updated to be linked to your DTD file.
o A new version of the CSS file you submitted last week renamed appropriately and updated for any changes you may have made to your XML file. (Note: changes to the XML file are not required, but are allowed if you would like to tweak it a little. But, if you make changes to your file, the changes must not make your file less complex or remove elements from the file you submitted last week.)
? There are no requirements for your DTD file other than it must validate the XML file
? Your XML file needs to contain at least one attribute.

Since I have to use Netbeans to create this XML file can you also using attach a Word document that clearly explain the assignment with screen shots.

© BrainMass Inc. brainmass.com October 25, 2018, 12:30 am ad1c9bdddf
https://brainmass.com/computer-science/files/expanding-xml-dtd-css-file-230095

Attachments

Solution Preview

I have created the DTD file for your books.xml and checked that it passes the validation. Slightly adjusted the Books.css so that ...

Solution Summary

The expert expands a XML file a little bit by making sure that it is valid as well as well-formed.

$2.19
See Also This Related BrainMass Solution

Individual website help

Individual Web Page 1 Assignment: Design, code, document and test one Web page which includes:
• Multiple data types (incl. Numeric, Boolean, String and Array)
• Multiple operators
• write methods which display variables assigned values and operators results
• All this in scripts and at least one external .js JavaScript source file
• Enclose script code within a <script> element within a CDATA section and hide from incompatible browsers.
• Some presentation/display/formatting (style, color, font, etc.) using each of the following:
 Inline CSS
 Internal CSS
 An external CSS file.

Note: No global variables.
CODING STANDARD FOR WEB PAGES

The following Coding Standards will be used in all your web pages.
• Well formed and Valid template
• Minimum Required Documentation
• Test Data and Expected Results
• Coding Style
Well formed and valid template
To aid in insuring that your web pages are "well formed and valid", I am requiring that you use the following template.
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">

<!-- required "top comments" -->

<head>
<title>your document title</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
</head>
<body>
</body>
</html>
Minimum Required Documentation

For each file, please add these required comments directly above the <head> tag for each HTML document/file and at the very top for all other related text documents/files. Replace the <!-- required "top comments" --> from the template above with the information request below.
• AUTHOR
• DATE
• FILENAME
• REVISION HISTORY (at a minimum note the version number - better to provide a summary of changes since the last submission)
• What EDITOR you USED to create the page/program.
• A LIST OF ALL MY REQUIREMENTS for each program. Indicate any of them not implemented. PROVIDE (Also provide an accompanying INLINE COMMENT WHICH FLAGS EACH OF THESE REQUIREMENT IMPLEMENTATIONS (it is often difficult to find your implementation).
Test Data and Expected Results
• A web page can produce output but it needs to be the "expected results". Where the code in your Web page is not "self-documenting", include comments in the Web page, or in a separate "readme" text file, which provide reasonable test data and expected results.
Coding Style
• Be CONSISTENT.
• Name the initial web page index.htm and give any other pages meaningful names.
• Use meaningful VARIABLE names -- NOT x, y, a, etc.
• Limit all lines in code to less than 80 character (screen width).
• Use BLANK LINES to separate sections of the page/program and improve readability.
• Arrange BRACES for ease of seeing matching pairs (JavaScript).
• CAPITALIZE the names of CONSTANTS (JavaScript).
• INDENT subordinate statements, much like an outline (and don't indent if a statement is not subordinate) (JavaScript).
• Essentially follow the coding style in the texts.
Individual Web page 2, Expanded Web Site: Design, code, document and test a Web page with:

• Functions which include:
 An array of two elements and a loop that displays the array values
 An if..else
 A switch with break statements and default statement
 A for loop
 A while loop
 A window.alert() method
• At least one function which uses an argument and returns a value.
• All functions in scripts.

View Full Posting Details