but since RSS feeds are supplying all that formated data, why don't we all agree on a field that says what the recommended and absolute minimum refresh periods are for each feed? (With a default if it's not present.)
All agree to something - you're new to this RSS specification thing right?;-)
Seriously, there are three elements specified in RSS2.0 which may be of use - skipHours, skipDays and ttl. ttl sounds in the right direction to your original requirements.
(but it also has flaws, it uses HTTP methods besides simple GET/POST, which means it is a huge PITA to implement
Hardly. Its trivial to implement a script that supports PUT and DELETE, not to mention HEAD, OPTIONS and TRACE. Trying to implement XML-RPC - now _that's_ pain.
The bad news is that the onus of work will shift onto site authors. Anyone maintaining a site using embedded objects will have to either re-code or suffer a changed "user experience".
Ahhh - that's useful. Since they are recoding, they now have the chance it make it accessible too. That would be beneficial for users.
Seeing as how there's nothing preventing this action from being taken against Mozilla or Opera, I'd side with MS on this one.
It would be much better for Microsoft either to conceed defeat, or to lose on appeal. That way it sends a nice clear signal that money doesn't win patent battles. Microsoft losing this patent challenge is probably another step toward revoking these ridiculous software patents.
Microsoft overturning this verdict will leave Open Source developers in a great degree of risk. Any company can launch a frivilous patent suit against an open source product - even when there's clear prior art. When its Microsoft doing the attacking - who can keep up with the financial burden of defending an open source product?
Software patents is going to be the way Microsoft competes against Open Source products.
Screen readers make web developers cry. If I'm a web designer, my well-paid job is to make a great-looking page. I can't do this if my creativity is restricted such that Mama Joe Bob from Arkansas has to be able to view my page with Netscape 2.02 on her Macintosh.
Netscape 2.02 on a Macintosh is not a screen reader. IBM Homepage Reader, Jaws and Window-Eyes are examples of a screen reader.
How many architects complain about building safety regulations as a restriction of their creativity? The ones that do aren't worth hiring - the same for these web designers who do likewise.
If you can't design a website using web standards, consider hiring someone who can.
[In response to a refutation of his argument]:
So, are you a true moron, or just a lying creep?
An ad hominem, a false dichotomy and a fallacy of interrogative presupposition. Now _that's_ a weak argument. Presumably for the sake of continuing an argument that's been refuted? You do yourself no favours acting in this way.
Re:/ Because providers always tell the truth... /
on
Practical RDF
·
· Score: 1
I find it odd to note that it is never discussed how RDF will be kept from rapidly degenerating into Meta-tag style abuse.
This is one of the questions I had in mind during Tim Berners-Lee's lecture at the Royal Society earlier this week (There's a streaming media of the lecture itself - and this question was raised - I think it was the first one in the Q&A session). The answer lies in much the same solution used by the web and its visitors today.
What happens when you visit a website that contains false and blatantly wrong information? You don't go back there. So you'd only use sources you trust. (Face it, you don't trust _everything_ on the World Wide Web right? Yet the web works as a medium despite this "flaw").
Its the web's way of routing around the damage - the damage of false information.
Listing a series of dates does nothing a simple perl script can extract.
I can't imagine why you'd say this. If I'm interested in WW2 I ought to be able to specify a date-range 1939-1945 in my searches.
Events within the above date range would include the birth of Stephen Hawking and Al Pacino - not something related to WW2. Elementary evidence that a list of dates by itself without any related data is useless.
The gigantic propaganda campaign about the "wonderful new things" that semantic markup would make possible was always just a masturbatory fantasy by people who'd never implemented anything,
So, what have you implemented that's being used by thousands of businesses across the world? Pot. Kettle. Black, Mr failed AI expert.
So the real outcome of the XML-scam is that the effort to add metadata to webpages has been set back at least five years.
Adding metadata to webpages is deceased. It has been for over half a decade (Yes it is 2003 this year). Its a dead donkey, no need to flog it any more.
What should have been emphasized was META headers for: Yahoo topic-category, DMoz topic-category, list of persons, list of places, list of companies, list of things, dates discussed, document type (eg timeline, image gallery, biography, etc).
Utterly useless. Listing a series of dates does nothing a simple perl script can extract. Now linking a date to an actual place - now that's something useful. And your above example fails that simple relationship. Screenscraping ain't gonna save you - its far too brittle for practical real world use.
Actually pure flash pages like Homestar could get around it pretty easily. Most the animations a full page and the minimal HTML is only a wrapper. All they have to do is change the linking a bit so the.swf file is called directly and not embedded in HTML
Sod that. Ditch the HTML entirely. Then add the flash file to the DirectoryIndex of your webserver. Then http://www.example.com/ can return a.swf file instead of an html file.
Guilty of ignoring abuse complaints - yep. The evidence is already there. If you are not going to look after your mailserver, its probably best that its blacklisted until you have a change of opinion.
So you are right and everybody else is wrong. Way to make friends net-nazi.
As long as it is his mailserver - it is his rules. If you don't like it - tough. Unless you have a contract with him that documents that he will accept email from you, you have nothing except his good will. Calling him a net-nazi isn't the most optimal way of getting his good will.
However, if they do, they will typically be rejecting email as SPEWS sees fit.
An admin decides what is best for his organisation. If he decides to automatically reject email based on a SPEWS query - that is his choice. Also, if he decides not to reject an email based on a SPEWS query, he can chose do that. The use of SPEWS does not force either.
Why else would he be using SPEWs?
For any number of reasons. No-one is forced to use SPEWS, and no-one is forced to reject mail based on a SPEWS query - the admin choses what is best for his network.
He doesn't require this knowledge.
Sure he believes he does, otherwise his system wouldn't be quering SPEWS at all.
He simply requires an assurance that measures are taken to ensure that the number of false positives is kept to a minimum.
Spews offers multiple lists - use the right one like Level 1, which lists netblocks owned by spammers and spam support operations. Its not terribly difficult, is it?
[Spews] It doesn't allow admins to refuse email as they see fit. It allows them to reject email as SPEWS sees fit. While you could argue that the admin has the right to unblock any site he wants, this ability is worthless without the knowledge of which sites are wrongfully blocked.
That is complete and utter tripe. Admins do not have to use Spews, and the don't have to use only Spews. They can use as many and varied collection of blacklists as they wish. Spews only returns a result of a query, and does no actual blocking. An administrator does not have to reject all email that querys as spam positive - it is his choice on how he deals with Spews query results on the incoming mail. If an admin requires the knowledge of which sites are blocked, then he can get that information when he needs it by configuring his mail servers accordingly.
to be a pedant, the problem WOULD be solved if EVERYONE hit the "D" key.
How does hitting the "D" key prevent mail servers from being clogged up with spam to the point that proper email cannot be delivered? That to me is sufficient reason to that "just hit delete" is no solution at all.
Hmmm.. I've always preferred javascript faqts, run by Martin Honnen. It is a little difficult to search, a bit unintuitive, but there's stacks of excellent and up-to-date scripting info there.
the scribes messed about with red ink, trying different things,
The citation you provide makes no mention of this assertion. It even provides a passage that indicates the presence of structure - a reusable structure:
"The earliest type of text commonly used in private tombs was the 'offering given by the king' (hetep-di-nisut) formula. It was a short prayer..."
prayer - structure.
And again in the very next paragraph:
"In the Fifty Dynasty [2465-2322 BC] autobiographical texts developed further to include episodes illustrating the tomb-owner's character and describe his memorable achievements"
Episodes - that is a structure.
And going even further back, before your first reference of 2500B.C.
"
The Pyramid Texts were a collection of Egyptian mortuary prayers, hymns, and spells intended to protect a dead king or queen and ensure life and sustenance in the hereafter. The texts, inscribed on the walls of the inner chambers of the pyramids [from c. 2686-c. 2160 BC]... The texts constitute the oldest surviving body of Egyptian religious and funerary writings available to modern scholars."
Prayers, hymns, and spells, what a structured collection of writings! They were used as part of a ritual - yet another organised structure.
The more I read from this website the more evidence of structured text I see.
I have a longterm project to solve this, generally: [theory]
No need. Its already done. Its called RSS. Its a way of syndicating new items on a website. When you use an RSS aggregator it periodically requests an update from the website, bringing new items to your attention within one update cycle.
Major news sites and web logs are already using this technology. Recently the BBC and Rolling Stone added RSS feeds to their websites. The New York Times has been using RSS feeds for quite some time already.
All agree to something - you're new to this RSS specification thing right? ;-)
Seriously, there are three elements specified in RSS2.0 which may be of use - skipHours, skipDays and ttl. ttl sounds in the right direction to your original requirements.
Hardly. Its trivial to implement a script that supports PUT and DELETE, not to mention HEAD, OPTIONS and TRACE. Trying to implement XML-RPC - now _that's_ pain.
General etiquette is once an hour at the most.
Ahhh - that's useful. Since they are recoding, they now have the chance it make it accessible too. That would be beneficial for users.
It would be much better for Microsoft either to conceed defeat, or to lose on appeal. That way it sends a nice clear signal that money doesn't win patent battles. Microsoft losing this patent challenge is probably another step toward revoking these ridiculous software patents.
Microsoft overturning this verdict will leave Open Source developers in a great degree of risk. Any company can launch a frivilous patent suit against an open source product - even when there's clear prior art. When its Microsoft doing the attacking - who can keep up with the financial burden of defending an open source product?
Software patents is going to be the way Microsoft competes against Open Source products.
1999 shortly after the patent was granted.
Netscape 2.02 on a Macintosh is not a screen reader. IBM Homepage Reader, Jaws and Window-Eyes are examples of a screen reader.
How many architects complain about building safety regulations as a restriction of their creativity? The ones that do aren't worth hiring - the same for these web designers who do likewise.
If you can't design a website using web standards, consider hiring someone who can.
Elrond's two sons show up along with Aragorn's rangers after they visit Isengard. They accompany Aragorn down the Paths of the Dead.
Those vowels were stolen early on in Welsh history by native Havaiians. (So we were left with a lanugage we could spit and talk at the same time).
An ad hominem, a false dichotomy and a fallacy of interrogative presupposition. Now _that's_ a weak argument. Presumably for the sake of continuing an argument that's been refuted? You do yourself no favours acting in this way.
This is one of the questions I had in mind during Tim Berners-Lee's lecture at the Royal Society earlier this week (There's a streaming media of the lecture itself - and this question was raised - I think it was the first one in the Q&A session). The answer lies in much the same solution used by the web and its visitors today.
What happens when you visit a website that contains false and blatantly wrong information? You don't go back there. So you'd only use sources you trust. (Face it, you don't trust _everything_ on the World Wide Web right? Yet the web works as a medium despite this "flaw").
Its the web's way of routing around the damage - the damage of false information.
Events within the above date range would include the birth of Stephen Hawking and Al Pacino - not something related to WW2. Elementary evidence that a list of dates by itself without any related data is useless.
So, what have you implemented that's being used by thousands of businesses across the world? Pot. Kettle. Black, Mr failed AI expert.
Adding metadata to webpages is deceased. It has been for over half a decade (Yes it is 2003 this year). Its a dead donkey, no need to flog it any more.
Utterly useless. Listing a series of dates does nothing a simple perl script can extract. Now linking a date to an actual place - now that's something useful. And your above example fails that simple relationship. Screenscraping ain't gonna save you - its far too brittle for practical real world use.
Sod that. Ditch the HTML entirely. Then add the flash file to the DirectoryIndex of your webserver. Then http://www.example.com/ can return a .swf file instead of an html file.
Guilty of ignoring abuse complaints - yep. The evidence is already there. If you are not going to look after your mailserver, its probably best that its blacklisted until you have a change of opinion.
As long as it is his mailserver - it is his rules. If you don't like it - tough. Unless you have a contract with him that documents that he will accept email from you, you have nothing except his good will. Calling him a net-nazi isn't the most optimal way of getting his good will.
An admin decides what is best for his organisation. If he decides to automatically reject email based on a SPEWS query - that is his choice. Also, if he decides not to reject an email based on a SPEWS query, he can chose do that. The use of SPEWS does not force either.
For any number of reasons. No-one is forced to use SPEWS, and no-one is forced to reject mail based on a SPEWS query - the admin choses what is best for his network.
Sure he believes he does, otherwise his system wouldn't be quering SPEWS at all.
Spews offers multiple lists - use the right one like Level 1, which lists netblocks owned by spammers and spam support operations. Its not terribly difficult, is it?
Including the four thousand duplicates of the sobig email - the one that opens your machine as a spam relay.
That is complete and utter tripe. Admins do not have to use Spews, and the don't have to use only Spews. They can use as many and varied collection of blacklists as they wish. Spews only returns a result of a query, and does no actual blocking. An administrator does not have to reject all email that querys as spam positive - it is his choice on how he deals with Spews query results on the incoming mail. If an admin requires the knowledge of which sites are blocked, then he can get that information when he needs it by configuring his mail servers accordingly.
How does hitting the "D" key prevent mail servers from being clogged up with spam to the point that proper email cannot be delivered? That to me is sufficient reason to that "just hit delete" is no solution at all.
Hmmm.. I've always preferred javascript faqts, run by Martin Honnen. It is a little difficult to search, a bit unintuitive, but there's stacks of excellent and up-to-date scripting info there.
The citation you provide makes no mention of this assertion. It even provides a passage that indicates the presence of structure - a reusable structure:
prayer - structure.
And again in the very next paragraph:
Episodes - that is a structure.
And going even further back, before your first reference of 2500B.C.
Prayers, hymns, and spells, what a structured collection of writings! They were used as part of a ritual - yet another organised structure.
The more I read from this website the more evidence of structured text I see.
There you go. Style (red ink) layered on top of a structure (headings). Structure first, style later.
No need. Its already done. Its called RSS. Its a way of syndicating new items on a website. When you use an RSS aggregator it periodically requests an update from the website, bringing new items to your attention within one update cycle.
Major news sites and web logs are already using this technology. Recently the BBC and Rolling Stone added RSS feeds to their websites. The New York Times has been using RSS feeds for quite some time already.