Talk:XML - Managing Data Exchange/The one-to-one relationship

Revisions to One-to-One Relationship Dustin K. Pitts January 28, 2006

The following things are suggestions for the revision of my chapter over one-to-one relationships.


 * 1) Have a brief overview of what XML is.  Define the XML Schema, XML Style Sheet, and the XML Document.
 * 2) Have a better definition of the one-to-one relationship.  Relate it to the data model that is given.
 * 3) Reword the introduction so that the goals of the chapter a little more clear.
 * 4) In the new elements and attributes part of the Schema the third bullet should be its not it’s.
 * 5) Have a separate category for the restrictions in the XML Schema.  It will set them apart more and allow for more organization.  Maybe a label or something would help this.
 * 6) Bold the titles of the restrictions so you can easily find them.
 * 7) Have a separate category for the If Statement.  Make it stand out.
 * 8) Have a more in depth summary so that someone skimming the chapter can get a more general idea of what is going on.

Editorial Board Suggestions
MIST 5730 Advanced Data Management, University of Georgia, in response to Dustin


 * 1) The overview of XML is covered in a previous chapter. You could link to this information at the beginning of the chapter.
 * 2) It may be helpful to include a new section header entitled "Prerequisites" (or something similar) at the beginning of the chapter and link to chapters that the learner should have already read. This resource also could have answered some of Mr. McCreary's questions (below).
 * 3) Focus on the one-to-one relationship and how this relationship is represented in the schema.
 * 4) Cut advanced topic information and paste within your chapter link on the "Chapter XSL" page that Viji created (accessible from the main table of contents). This would address your suggestions concerning the "if statements" and "restrictions." The editorial board will need to discuss whether "Chapter XSL" is the correct descriptor for the chapter link Viji created. Not all advanced topics are related to XSL; some are related to Java.
 * 5) To address your suggestions to reword and go more in depth with some of the content, I agree. If you didn't really understand the chapter, add and reword content in the way that you think makes the most sense.
 * 6) And, of course, please make the changes specified by the author guidelines.

Christina Serrano, 2/1/06

Excellent Start
Hi Dustin,

First of all. Great Job! Keep up the good work.

Yes, I agree that we need to start out with some basics of XML Schema. I got very confused by the title. Creating one-to-one relationships is not the right topic.

I think that restrictions are an advanced topic. I don't even teach it in my beginning classes.

Here are the key concepts I introduce in one-day (8 hour class) on XML Schemas:
 * 1) History of XML and XML Schema
 * 2) XML Schema as compared to a DTD?  Why are Schemas better?
 * 3) What is it used for? (Validation of structure and data type checking)
 * 4) What is the structure of an XML Schema file?
 * 5) How do you add elements and attributes?
 * 6) How do you assign simple data types (string, boolean, integer and date)
 * 7) Adding enumerations
 * 8) Adding a pattern to validate a zip code
 * 9) How do you use an XML schema to validate an XML file (need a lab)
 * 10) What else are schemas used for (e.g. data mapping)

At the end of the class students feel they can create a simple XML Schema to validate some simple data.

I am looking forward to working with you on this. Let me know if you want me to make any changes. Collaborative writing is a challenge.

- Dan Feb. 2nd 2006 User:dmccreary

Professor's comments
rtw 01:20, 2 Feb 2006 (UTC)

We need to make clear to the reader that the schema is mapping only a portion of the model (the 1:1 aspect). Maybe the model should be redrawn with a color box around country and destination. If you want, I can do this, as all the models need to be maintained by one person. The prerequisites section should go in the first chapter and include topics such as knowledge of HTML and data modeling. It can be assumed that the preceding chapter is a prerequisite for the current chapter. Section summaries are useful and there is an author guideline on how to make these standout in the text.

Editorial Board Comments - Christina
2/21/06

Dustin, thanks for making all of the changes that we suggested. I also like Dr. Watson's suggestion to highlight the 1:1 relationship in the data model presented in this chapter. And perhaps the data model could be truncated. For example, I don't know that it's necessary to include the "hotel" entity--if this were removed, the schema and document could also be simplified.

I removed references in the chapter in regards to style sheets and Java parsing because there is no longer content in the chapter to explain these topics.