A DTD is a BNF description of a language. In the XML world it is used by a type of parser known as a validating parser. What this means is that the parser uses the DTD as a reference sheet so that it can verify the correctness of a particular XML document. (If you take a look at a typical XML document it normally specifies a URL pointing to a DTD in the header).
Yes, I agree. Make the push for standardized adoption of your DTD.
However, being the best implementors is a very risky strategy and I would say probably next to impossible unless you have the resources i.e, a team of shit hot programmers. Personally, I prefer to see innovation and unique application rather than bullet proof code. Try and get first-mover on this as it is critical if your standard is to be adopted and you want to steal a march on your competitors.
I can see how the fear of your work being stolen would give you pause for thought. There is every chance that a competitor will rip off your work and even more worrying are those that would employ the E3 approach against you (Embrace, Extend, Extinguish).
A while ago I gave a considerable amount of thought to protecting myself from competitors and I gradually came to realize that a reasonably effective defense is a release programme. Basically, you use software life cycle development techniques to control the release of your DTDs into the public domain. Unfortunately this does mean a lot of extra work in the steup but it will pay dividends over the long term.
Hope this helps and good luck with the project.
Hey 1.4Ghz means that the buttons on Java GUIs will go up and down almost in *real-time*. Wow. those wierdos in the Java development camp will be dancing in the air!
Yeah. I'm taking issue with your judgmental approach. Kids have a hard enough time already with authority without more constraints being heaped upon them. Freedom is a precious thing and those that would seek to curtail it are universally hated.
'the underlying reasons why "a kid" can do such things in the first place.'
Are you so old that you cannot remember that as a kid your number one priority was to attract the attention of your peers? The Internet gives the kids an oppurtunity to aquire peer recognition through spectacular technical stunts. Admittedly DoS attacks aren't particularly original, they rank somewhere between knocking on doors and fire-starting, but they do benefit from the fact that they GET PEOPLE'S ATTENTION. And that is all any kid wants to do.
"Hello, is that the fire brigade... yes? Okay, there's a fire at The Wookey Hollow Club" - standard reaction of a sixteen year old that has just been refused entry to a nightclub.
Slashdot Mirror
Hard cheese old boy. Instead of relying on cron you could take this job execution utility for a spin if it is super important that you achieve FP.
A DTD is a BNF description of a language. In the XML world it is used by a type of parser known as a validating parser. What this means is that the parser uses the DTD as a reference sheet so that it can verify the correctness of a particular XML document. (If you take a look at a typical XML document it normally specifies a URL pointing to a DTD in the header).
Yes, I agree. Make the push for standardized adoption of your DTD. However, being the best implementors is a very risky strategy and I would say probably next to impossible unless you have the resources i.e, a team of shit hot programmers. Personally, I prefer to see innovation and unique application rather than bullet proof code. Try and get first-mover on this as it is critical if your standard is to be adopted and you want to steal a march on your competitors.
I can see how the fear of your work being stolen would give you pause for thought. There is every chance that a competitor will rip off your work and even more worrying are those that would employ the E3 approach against you (Embrace, Extend, Extinguish). A while ago I gave a considerable amount of thought to protecting myself from competitors and I gradually came to realize that a reasonably effective defense is a release programme. Basically, you use software life cycle development techniques to control the release of your DTDs into the public domain. Unfortunately this does mean a lot of extra work in the steup but it will pay dividends over the long term. Hope this helps and good luck with the project.
Hey 1.4Ghz means that the buttons on Java GUIs will go up and down almost in *real-time*. Wow. those wierdos in the Java development camp will be dancing in the air!
I don't think you lack talent, just discipline.
What?? You mean you actually, really, honestly do sit there monitoring the page with the refresh button? Wow. Your index finger must be exhausted.
Yeah. I'm taking issue with your judgmental approach. Kids have a hard enough time already with authority without more constraints being heaped upon them. Freedom is a precious thing and those that would seek to curtail it are universally hated.
Bollox! You've probably got a script monitoring the page.
'the underlying reasons why "a kid" can do such things in the first place.' Are you so old that you cannot remember that as a kid your number one priority was to attract the attention of your peers? The Internet gives the kids an oppurtunity to aquire peer recognition through spectacular technical stunts. Admittedly DoS attacks aren't particularly original, they rank somewhere between knocking on doors and fire-starting, but they do benefit from the fact that they GET PEOPLE'S ATTENTION. And that is all any kid wants to do.
Presumably you would also advocate the immediate machine gunning of any script kiddie caught with DoS tools?
"Hello, is that the fire brigade... yes? Okay, there's a fire at The Wookey Hollow Club" - standard reaction of a sixteen year old that has just been refused entry to a nightclub.