Talk:XML - Managing Data Exchange/A single entity

From Wikibooks, the open-content textbooks collection

Jump to: navigation, search
  • add some HTML tags to the stylesheet section so they know what the basic HTML means
    • alternatively link the reader to a basic coverage of HTML and suggest reading this before proceeding
  • include short definition of XML document, schema, and stylesheet in introduction
    • good idea and maybe add a diagram showing how they interrelate
  • include some thoughts on organizing data into a data model - content analysis (what does content analysis mean?)
  • explain sequence tag in complex type
  • edit the netbeans link

thanks, viji

rtw 01:20, 2 Feb 2006 (UTC)

  • This chapter needs an introduction to explain the data modeling driven approach to the first few chapters.

Contents

[edit] post revision comments

viji

so, I did not do the explanation of the data model driven approach, YET. I will, I might ask you for direction. Do you think it should go more in the introduction than in this chapter?

[edit] It appears spaces ARE allowed in attribute values...

In the Rules to follow the book states:

attribute values should have quotation marks around them and no spaces

Yet in the section on default and fixed values for schemas which are supposedly a well-formed XML documents, we see:

<xsd:element name="description" type="xsd:string" 
    default="really cool place to visit!" />

and

<xsd:element name="description" type="xsd:string" 
    fixed="you must visit this place - it is awesome!" />

Are not default and fixed attributes? Do their values not contain spaces?

KJC 02:05, 11 October 2006 (UTC)

[edit] Exhibit 2 - No "standalone" element

In Exhibits 2 and 3 the prologue (XML declaration) does not appear to have the standalone="yes" element which the text description under exhibit 3 suggests should be present.

But the text does indicate that this is an optional element so perhaps that is fine.

[edit] Formatting...

The formatting of this page is vary confusing at times. For example, under DTD section, subheading "Grouping Attributes for an Element"...

Shouldn't this line: <!ATTLIST car horn CDATA #REQUIRED

Be grouped in the box with these lines:

                    seats CDATA #REQUIRED
                    steeringwheel CDATA #REQUIRED
                    price CDATA #IMPLIED>

This sort of thing seems to be all over the page, which makes it hard to read. Unfortunately, I don't know anything about XML (why I'm here) so I'm worried if I try to fix it up I will make a mistake.

[edit] DTD (Document Type Definition) Validation - Simple Example

This section makes NO SENSE. There is no coherent description of what DTD is or why it's useful or when it should be used. Just throwing out an example like that is practically useless.