Forum Moderators: coopster
I have visited and searched numerous sites, tutorials on this and I would like to know if anyone here have tried it for their site?
is there any parser (php much appreciated) that uses the DTD of the xml file?
how about a forum here that would discuss xml and related x stuff?
<added>I think Brett mentioned once that you need enough individual threads to warrant a new forum, it seems to come up in regards to specific scripting languages right now, might not quite be ready yet.
here is one of my wildest idea about xml and dtd.
for example you would create a form that would ask for some data ... instead of php or javascript to filter data input on the form (example strip html tags, etc..) DTD would do this for us ... or my imagination is a litle bit wild about xml and dtd?
anyway its a mark-up language and programmers are the one create a program or script that would use this markup language.
how about a corroborative site project?
just thinking. =)
[devshed.com...]
{love the nickname, BTW)
Hold the boat. You're telling me that you used PHP to render the XML for the browser?
aaaaaa - a light bulb just went off. Is it true that only certain browsers will let you see the XML?
I think for the time being, that's the solution most people use - you build xml pages and then process it on the server side (PHP being one obvious way) and then you send XHTML to the browser.
You get al the data management advantages of xml
Visitors get all the compatibility advantages of whatever flavor of x/html you choose.
Search engines don't understand the DTDs anyway, so you don't lose anything (i.e there's no search engine that can look at a DTD and know that your "foot" site is about appendages not measurements).
Tom
Ergophobe, thanks for the post. But if the SEs don't understand the DTDs why bother with XML? Without the DTD how will the SEs parse my pages?
I'm in the planning stages for a collaborative project that involves XML, an RDF model, RSS feeds and even RPC. Why not just use a PHP/MySQL site instead? What's the advantage - other than RSS & RPC?
BOL XML - [xml.com...]
XHTML - [w3.org...]
Here is where to go for PHP XML questions, [php.net...]
Think of XML as an instruction media stream with built-in commands that trigger events. You can define handlers for different XML events, when expat see an even occur then it will execute a function.
Here is a good article on the expat that PHP uses [xml.com...]
I still don't understand - sorry to be so dense - what the advantage is of going with XML VS just building a PHP/MySQL application aside from the ability to implement RSS and RPC?
The whole appeal of XML to me is that it allowed me to define data in a DTD which I could allow others creating documents of the same subject matter as mine to use for their web sites. This would set us up for the beginnings of what XML was designed for - structured data, IE: data with a descriptor which tells you what the data is. The DTD would lead us to the bigger picture items like Metadata and SEs that return search results that are dead-on the subject you searched for. If the SEs don't understand the DTD then the whole scheme falls apart. So what's the point of using XML?
I feel like I'm missing the obvious. If your patience hasn't worn thin I'd welcome getting set straight! :)
let us not forget that xml is a markup language and it is mainly designed for exchange of data like RSS.
Lorax, this is why others uses RSS instead of simply using mysql/php (but some do get data in mysql, convert it to xml, den use php) i may simply feed ur article or data into my site by simply getting your xml. i think there are other sites that do this. try this one
[wired.com ]
Like DOM which is also a recommendation which could be use for scripting language.
it does not intend to replace html/xhtml and you would need a program (back-end)or scipting language to convert xml to x/html.
Most of program or scripting language available only parse xml but not validate it, where dtd comes into the picture. Anyway, i think that dtd is 1 of the power of xml that programs, script languages have overlooked, or they are still cooking this for us?!?
all i can say is exploring xml would let us dig more farther and further, with all the X's such as xsl, xslt, xpath, etc ... or should i say "excetera" =)
i really need a gud book on this one.
<marcia, thanks for the comment. />
If you introduce xml you could first let them log in to their account then extract their account details to an xml document. They can then work just with that xml document - which will be much smaller (and quicker) than the actual database.
That should give a bit of a performance improvement.
