All they had to do was type in the URL. The best analogy is: Someone tells you they don't send the letters out until March, but if you ask the clerk he will show you your letter now. The clerk and the letters in this case were automated. They did not steal, they did not cheat, they went around the process. They queried a system legally and it told them the answer when it shouldn't have.
Have you really tried? With small business server you can do this for under $1300 and have Exchange, SQL Server, IIS, Sharepoint and more. It is easy to set up for a trained admin (pay one for a day).
The fact is that in order for any data interchange to work, the parties must first agree on what data will be exchanged -- semantics -- and once they do that, there is no need to repeat the tags in each and every record/document being transmitted. Any agreed-upon delimited format will do, and the criterion here is efficiency,
WRONG!!!
The point of al those repeated tags is that machine time and bandwidth is very cheap now, but human time is not. The beauty of XML is "agreed-upon" is optional now. We can understand the data without a formal meeting to come to an agreement.
As a guy who has spent a significant portion of his life in meetings about data mapping between systems, I love XML because of how easy it is to read, understand, communicate about and map to the structures I need the data for.
Nor, in fact, should anyone buy the notion that filtering software protects children. It doesn't. Statistically kids are in no danger on the Net. Their greatest source of harm comes from physical abuse from family members and people they know,
This is an invalid argument.
Physical assualt is not the only form of danger to children. The reasons for filtering are not limited to fear they will meet someone that will exploit them.
Slashdot Mirror
All they had to do was type in the URL. The best analogy is: Someone tells you they don't send the letters out until March, but if you ask the clerk he will show you your letter now. The clerk and the letters in this case were automated. They did not steal, they did not cheat, they went around the process. They queried a system legally and it told them the answer when it shouldn't have.
Have you really tried? With small business server you can do this for under $1300 and have Exchange, SQL Server, IIS, Sharepoint and more. It is easy to set up for a trained admin (pay one for a day).
When feel like I am getting twice the performance as my current machine for the same price. I usally will upgrade.
The fact is that in order for any data interchange to work, the parties must first agree on what data will be exchanged -- semantics -- and once they do that, there is no need to repeat the tags in each and every record/document being transmitted. Any agreed-upon delimited format will do, and the criterion here is efficiency,
WRONG!!!
The point of al those repeated tags is that machine time and bandwidth is very cheap now, but human time is not. The beauty of XML is "agreed-upon" is optional now. We can understand the data without a formal meeting to come to an agreement.
As a guy who has spent a significant portion of his life in meetings about data mapping between systems, I love XML because of how easy it is to read, understand, communicate about and map to the structures I need the data for.
This is an invalid argument.
Physical assualt is not the only form of danger to children. The reasons for filtering are not limited to fear they will meet someone that will exploit them.