hi stut, thank you for your advices. - Screentexts are texts shown as link texts or descriptions in forms and other page elements which remain static in one language area. The screentexts are getting replaced by they' re coresponding translations as the user selects a different language. - The Google standard, of websites describes, that Query URL's like ?param1=XYZ¶m2=123 or as in $_SERVER['QUERY_STRING'] are not human readable, which makes them not acceptable as valid content links. But as I am pretty familar with search engine optimisation, my system is creating metatags for every page, h1 tags are used for headlines, h2 tags for subheads and so on. If you are a professional in search engine optimisation, you will not find any weakness in my application anymore. Its happending absolutely automatically the authors don't have to do anything, for make it happen. Stopword lists like in my- sql are removing useless keywords and so on. - Yes, my system is the only application framework worldwide with its capabilities. I added a neural networking functionality which makes it possible to autodecide which contents are inte- resting for the viewers on a page. Fx: If a user is allergic, no products containing large amounts of the alergen are shown in the shop anymore. As well it is possi- ble to create psychological profiles from the users of the system during the runtime of the application. I have read a paper from the department of defence, from year 2004. I first read it in the early beginning of this year. I figured out, that my application framework is the perfect psynet application for performing psychological operations over the internet. I guess I developed one of the biggest weapon systems available now a days. - As a blogging standard I would describe websites which contain a linklist to the left or the right of the blogs content as well as a calender and a search field. I guess this makes a blog. - The shop system is widely using ajax for performing fast shopping actions, its possible to use videos or audiofiles as product descip- tion media, as well as soon you change product parameters these me- dias are getting replaced by different color media or size images as what ever you could think of. And as well my system is using XLinks, which means, you add a link to a document, you are able to select the target document from one of the content modules, automatically the headline of the target document is used as link description and as well the link is shown as a nonquery url, like: http://www.domain.com/en/magazin/something-new/while-i-wrote-it-here.html Done without mod_rewrite. I hope I answered all your questions. Best Regards, Sascha Am Montag, den 10.09.2007, 16:39 +0100 schrieb Stut: > Things to do before spamming a public English mailing list... > > 1) Make sure your email actually says what the product is > 2) Make sure you have a relevant subject line > 3) Make sure it's in English > 4) Run it through a spelling checker, preferably an English one > 5) Stop and think whether the people you're spamming are really gonna care! > 6) This one is really important. Make sure you include a URL to the > product's website. Oh, and make sure that website actually works, > especially when it says it's powered by your product! > > Some additional questions and notes that you may find useful... > > * What the heck are "Kategories"? Maybe you mean categories? > * What the heck are "Screentexts"? > * As far as I know Google have never published any standards regarding > URLs. Do you have a reference? > * Claiming that your product is the only one in the whole wide world to > do something is very dangerous. Would you bet the farm on it? Because > what with the numerous highly litigious patent owners out there you > could well be! > * "blogging standards"?? Another reference needed please. > * "The shop system is not containing query urls anymore, without use of > mod_rewrite." What the heck does that mean? You had SQL in your URLs? > * It's the best is it? On what do you base that claim? > > -Stut > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
