Basic XML Questions

This site is best viewed in a modern browser with JavaScript enabled.

brendandonhue

This summer I will be doing web design for a jeweler.
I was thinking of using XML to keep track of the products/prices/info. Say the XML file looked like this. (I don't know the XML syntax yet, this is just a sample!).
<item>
<productid>001</productid>
<name>Product Name</name>
<price>Price</price>
</item>
Do you think XML would be work well for this project? If I don't use XML, I would just be using HTML and doing a page for each product, as I dont need a full blown database.
And how would I take that XML file, and transform it into this?
Product ID:001
Name: Product Name
Price: Price
Would I use XSL to parse/display the data?
BTW I don't need like, exact code on how to do this, just someone to point me in the right direction so I can learn this.
I have already started looking at the W3Schools tutorials on XML.
Thx in advance

khalidali63

I wrote an extermely flexible solution for this member,take a look at this thread..

http://forums.webdeveloper.com/showthread.php?threadid=9363

Works both on IE and NS,and you don't have to worry about learning any other language ,such as xsl and stuff,just plain old JavaScript and DOM will do.

brendandonhue

Thanks, Sounds great from that thread, but your site seems to be down
I have gone to other pages hosted on your server (im guessing that the IP is you running it yourself).
Ill try again a little later.

Charles

Originally posted by khalidali63
[J]ust plain old JavaScript and DOM will do.

[font=georgia]Yes, but one in ten users do not use "plain old JavaScript and DOM" and that one in ten users includes persons with disabilities who cannot use "plain old JavaScript and DOM". As such that solution could cause the page to violate accessibility laws and certainly wouldn't be very nice. As this is to keep track of "products/prices/info" if this is in the US then Title III of the Americans with Disabilities Act would definitely apply and possible Title I as well. Just go ahead and learn XSLT. It's a pretty quick learn and rather useful.[/font]

khalidali63

yes,the web page is up...sowwy..

brendandonhue

Ok thanks! Looks pretty neat khalidali.
Although I read some tuts on XSLT and that may be the way to go if Charles is correct about those laws.

Charles-I have seen you post maybe a dozen times that something will not work for 1 in 10 users. I was wondering what exactly it was your referring to when you say that 1 in 10. Is it text only/aural browsers, or disabled javascript or something?

khalidali63

Originally posted by brendandonhue
Ok thanks! Looks pretty neat khalidali.
........

As we all know,there are a tonnes of options out there when you look for coding,it all comes to the final point that what exactly suites your requirements.
XML/XSL an ultimate option without getting worried about any browser compliance problems...
JavaScript/XML is only an additional option for users,if charles has something against it why don't he sue MS,who to begin with created the XML data island idea and created a proprietery tag.
The solution I provided is only intended for people who deem this appropriate for them,for the others all the rest of the options are open for chosing.

Charles

[font=georgia]Currently about one in ten users do not use JavaScript (http://www.thecounter.com/stats/2003/May/javas.php). And because some of those users are disabled and cannot use JavaScript you are not supposed to rely upon it (http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-scripts) And because of the Americans with Disabilities Act (http://www.usdoj.gov/crt/ada/pubs/ada.txt) if you are in the US you might be facing a lawsuit if your web site does rely upon it (http://www.usdoj.gov/crt/foia/tal712.txt). Other countries have other accessibility laws that apply so be careful.[/font]

khalidali63

As we all know,there are a tonnes of options out there when you look for coding,it all comes to the final point that what exactly suites your requirements.
XML/XSL an ultimate option without getting worried about any browser compliance problems...
JavaScript/XML is only an additional option for users,if charles has something against it why don't he sue MS,who to begin with created the XML data island idea and created a proprietery tag.I thought I did a great job in creating a NS compatible code that works in IE as well,for those who like to use DOM methods to manipulate the xml with javascript.
The solution I provided is only intended for people who deem this appropriate for them,for the others all the rest of the options are open for chosing.

Charles

[font=georgia]When you post some code or a method that is hurtful to people (and inaccessible pages do hurt the disabled) or that might expose the web author to lawsuits you at least have an obligation to warn them. "Do no harm" as it were. And perhaps you have an obligation to not post harmful code or methods at all but to promote better web practices.

And see http://www.evolt.org/article/Accessibility_Laws_In_Canada/4090/28074/ for a review of the state of Internet accessibility law in Canada.[/font]

brendandonhue

Ok thanks.
I think it would just be best to use XSL, don't want any legal problems, as I don't think I am even of legal age to be working :rolleyes:

AdamGundry

I don't think I am even of legal age to be working

Which country are you in? In the UK, you have to be 14 to work part time, for limited hours. I probably sometimes break the law, but I am working for myself, and as I'm under 18 I can't be sued. Isn't the law great.

I agree with Charles, you should not use Javascript for page content because it limits your audience, and is unfair (legal or not). Use JS for added interactivity, but the content should be available to everyone.

Adam

brendandonhue

US, and just turned 13.
I know I can legally work part time at 14.

Hester

If you follow the W3C Accessibility Guidelines I believe they say that if you do use Javascript, then make sure an identical page made without it is available.

I have two pages on my work site that use drop down menus and Javascript to make them link to other documents. It's the best solution in terms of space and presentation, what the client wanted. But I also have a message that comes up when Javascript isn't used offering a link to the same page, but with the menus turned into simple links.

I've just made the pages run from XML so I don't have to manually update two pages at once.

Jona

[font=arial]He guys, I've followed this thread, and I'd like to know what XSLT is, and how it provides a way to, not using Javascript (?), read and process XML documents and print them as HTML markup (am I right?). If I'm not mistaken, XSLT is XML "stylesheets," that provide a way for XML to be parsed... But the question is, how would I go about using it?

I hope to get into XML, because not only does it look really cool and interesting, but it also provides an efficient way for me to store, extract, and process data.[/font]

Jona

Jona

[font=arial]Okay, I've read up a whole bunch on XSLT and found a great link to some XSLT tutorials. Pretty clever...

So I come to find out that XSLT is the "stylesheet" language of XML, and it basically sets the structure in which the data in the XML document is output...

Now, Charles posted a link on the SAXON XSLT Parser... I wanted to know what this parser is needed for? I've created XML and XSLT documents on my local computer, so I know that it's "basically" client-side--but it has no compatibility issues! It's almost like creating your own template for a programming language! That's neat. No wonder it's called the eXtensible Markup Language.

All right, so that's basically all I have to say for now... Give me your input, guys! I need it. [/font]

Jona

Khalid_Ali

XSLT parsers read the xml and apply the xsl/xslt file format to it and produce the desired results.
I think all of the XSL processors take to the most 3 parameters( at least the ones I worked with do)

XSML file XSL file and OTPUT file

All generation 6+ browsers(NS6+ and IE6+) have their built in xsl processor that transforms the xml document according to the xslt file.

Be specific about your quetion..to get more insight on these issues..

Jona

[font=arial]Well, ok, it makes sense now why I can use XSLT on IE6 and NS6. Are the two browsers' XSLT processors basically the same or is it like Javascript and back to compatibility issues? Also, for older browsers to support XML, I'd have to use an external XSLT processor like SAXON, right? So finally all I really have to do is use an XSLT processor (SAXON) for all browsers so that I don't have to worry about compatibility, right? I think I'm getting the general idea here... (Right? )[/font]

Jona

Charles

[font=georgia]You can run XSLT three ways:

1) at the browser

2) at the server

3) before you upload to the server.

I use method three, using Saxon to generate a HTML version and often to generate a printer friendly Formatting Objects version which is then processed into PDF.[/font]

Jona

[font=arial]So then the question would be, is there any "best method"? What are the advantages and disadvantages of each method? Am I right in saying that the "at the browser," method has compatibility issues, the "at the server" method is the dynamic method and the "before uploaded" method is the static method? Are there any other advantages or disadvantages I'm missing?

Thanks for helping guys, I've come across a few things and done a lot with at the browser XML (using IE, I haven't tested anything in NN or Moz yet). As much as creating my own DTD that reads the data and sets up a table with that data, and even adds up the sums. Very interesting how XML/XSLT works. I like it. [/font]

Jona