Talk:XML - Managing Data Exchange/Recursive relationships

From Wikibooks, the open-content textbooks collection

• Isn't the Many to Many recursive diagram incorrect? Surely one set of crows feet should be on the package and another on the activity. - Peter Johnson - peter.johnson@screechlaboratories.co.uk

• Use a similar example throughout the chapter for the 1:1, 1:M, and M:M sections. Perhaps one that relates to business.

• Bold key words and start with clear definition after each.

• Follow author guidelines to revise chapter.

---

XML: Managing Data Exchange/Recursive relationships - Editorial Board revisions - Viji

• remove the XSL items from the Learning Objectives

Introduction

"... such as a one-to-one, one-to-many, and many-to-many" - those are the only relationships that we have studied so far, therefore using "such as" does not really make sense.

• Where (and if) appropriate change the headings that read "one to one model" to "one to one recursive model" etc.

a look at new elements - change to New schema elements

• bold the element tags just to highlight them and set them apart

• also follow the tag with its definition then set a break before the rest of the explanation / examples

• what does "On {32}... " mean? Does it mean line 32? Since there are no line numbers and we are not using line numbers because they really don't match up, find another way of referencing the code line (if infact that is what is going on here). you can even copy and paste the code refered to here

--- that same sentence should probably read "only one" instead of "one only"

• "Experiment with changing the predecessor value on of the XML file above to “1”, and you will see that the file will not validate!" - include where in the XML document, which variable must be changed to "1".

• xpath is introduced for the first time here, please give a brief definition or description - it does not have to be exacting, it can be general - also do this before the <xsd:unique> element, mentioning that it will come later in the paragraph

change examples to fit with the tourguide model

(one to one recursive: perhaps use changes in the names of cities (like Istanbul was Constantinopal) but you would need at least three names; or from the previous 1:1 chapter example you could say that the top destination changes every year and make a recursive relationship from that)

(one to many recursive: perhaps use a state and cities and a city that is the state capital - ignore the bit about some countries somewhere with two capitals - you can make it smaller, perhaps 2 states with 4 cities one of which is the capital)

(many to many recursive: perhaps use a tourist package with air flights, hotel nights, museum trips, sightseeing, etc. which can be bought separately or in various packages)

• once again I think line numbers are being used ({41} and {18 - 21}), refer to the code in another way - you can even copy and paste the code refered to here

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

Thank you!

[edit] Professor's comments

The examples in this chapter need to be redone using ID and IDREF to make them simpler. Some of the prior comments (e.g., defining Xpath) will not be appropriate as a result. The tour examples are a good idea to keep with the tourism theme.

rtw 17:20, 5 Feb 2006 (UTC)

[edit] post revision comments

viji this revision looks like it addressed most of the comments