Talk:XML - Managing Data Exchange/XSLT and Style Sheets

Revisions suggested by Benjamin Trice

 * The name of this chapter is Stylesheets from the main chapter list, but it is listed as XSL at the top of the page upon entering the chapter. Making hese items the same would help avoid confusion over which chapter a user is currently reading.


 * When discussing line numbers from lines of code, the line numbers need to be listed to the left of the code.


 * Under the XML to XML section, the sentence, "These are copya nd copy-of," needs to be fixed.


 * In the Templates section, the sentence, "This allows you to process a node more once," nees to be fixed.


 * Under the sorting section, the separation of those lines of code is confusing to look at. It should be represented like the other lines of code and include its sample output after the code.


 * Under Parameters and Values, fix the separated code into one solid section.

'''No Answers are given for the Exercises. Future classes should answer them and add them to the wiki book'''

--- Editorial Board Revisions - Viji

some minor changes:

(2) what does XSLFO stand for

(3) "one for a Unix man page" probably should be 'main'
 * Actually, it refers to Unix man pages. I changed it to "manual page" to be less ambiguous. --Jarkko Piiroinen 06:37, 19 August 2006 (UTC)

(4) eliminate the references to the code using line numbers - do not put line numbers in the code they dont match up or if incorporated directly they dont allow the user to copy and paste into an editor easily - you can copy and paste the code refered to here or just make it clear what you are refering to, by now people should be accustomed to finding tags

(5) "This means that all elements must have a start-tag" - I think it means to say "an end tag"

(7) the headline "i the numeric value to be formatted", is the " i " extraneous? and what is going on with * numbers hanging out there by itself and * patterns under this heading (something seems awry here)

(8) change examples to fit with the tourguide model - especially the CD collection example is straight from W3Schools, even that weird green color

(9) after fixing the parameter section code into one solid code, then describe each part - reference the code in the explanation (can use the code frags to reference)

Remember to move the exercises to another link and link to answers - refer to the single entity chapter for the format.

major changes

Part 1: XML Fundamentals
 * sections:

Relational Data Models

Introduction to XML

A single entity

The one-to-many relationship

The one-to-one relationship

The many-to-many relationship

Recursive relationships

Data schemas

Namespace

Stylesheets

Introduction to Stylesheets

XHTML

CSS

XSL - will be organized into sections

XPath

XLink

XSL Reference tables


 * the XSL chapter can be organized into sections and we can coordinate the division of sections.


 * you can use the resources of your interface architect group to help you


 * you should consider joining the editorial board in charge of the stylesheet section

be a lot of rearranging, consolidating, organizing, and especially reformatting code.
 * you can give your presentation on the date you are scheduled to present, but, you and your interface team will have until April 15th to completely edit the Stylesheet section --- I think there will


 * We can work on the new stylesheet section at: contents page => chapter stylesheets => stylesheet section, so that students have the original material in its unedited form to refer to.

Thank You Ben! I look forward to working with you on the Editorial Board!

post revision comments
viji


 * I don't like using line numbers to refer to parts of code examples - it just forces the reader to count lines; I would rather see the code copied and pasted then commented on. what do you think

!=, &lt;, etc.) - could we check to make sure that these are incorporated?
 * the XSL material removed from chapters 3 thru 6 were not all incorporated such as: regex, operator (=,