...in the NIST SP-800 series of publications. Federal (US) agencies are already expected to abide by the standards described in that series, as well as other NIST/FIPS publications, e.g.FIPS 140-2 for cryptographic modules,or FIPS 200 for establishing minimum security requirements for specific systems.
Having had to study several of those publications for work-related tasks, I don't see where there should be any level of pushback from the corporate IT world, since a great many of them already have security measures in place that meet or exceed the requirements described in the NIST and FIPS publications. Individuals' systems, or SOHO systems and networks, would be a bit more problematic; a retailer throwing together an office network of four or five off-the-shelf boxes from (picking a name at random) Dell would likely have no idea where to start in trying to meet all the various technical specifications described just in NIST 800-59, if they even know that publication exists.
Bottom line...there's a great deal of education that will be required, not only with individuals and small-shop operators, but with network designers and custom-system builders. The days of ordering up a laundry list of parts from (again, grabbing names out of midair) NewEgg, throwing them together and delivering a completed machine to a customer with a pat on the back and a "have fun" are gone. Especially if the customer falls into one of the more ticklish areas of electronic security, such as a doctor's office or a law firm.
Want to stem the flood of HFT software into the Wall Street environment? Pass a law that requires any such software to be written in Ada. Think that one through...
If the Texas School Board Association had its way, school pupils in Texas would never hear of Jefferson. Instead, they'd learn how great a contributor to America was (wait for it...) Phyllis Schlafly.
1. It would require a very large and dynamic database, and that database would require updating almost every minute, as transmitters change "signatures", are switched on or off, or are interfered with by atmospheric phenomena. The storage and computational power required to do so would keep a midrange desktop machine busy almost 100% of the time.
2. Significant events that disrupt the power grid, such as the derecho in the eastern US over the weekend, would render the system useless within the affected area.
3. Propagation conditions would affect such a system even more than GPS is affected. One big CME would knock out at least half the transmitters the concept relies on, if not more.
Falcone thinks he can sue TWO government entities at the same time? File this under the heading of "more money than brains". Especially since one of his targets is the DoD, which has the first, last and only word on GPS operation.
I'd LOVE to see your sling-shot. I've never seen one with a three-hundred-meter vertical, two-kilometer horizontal range with enough accuracy to hit a fast-moving R/C airplanecarrying a camera.
Total cost for that little gem is less than $300US. Granted, no live video feed back to the operator for that particular example, but it has been done, and it adds about $300US to the above price tag.
A shotgun? Good luck with that. You might want to review some of the videos posted here. Many of those planes operate at altitudes well outside the nominal range of a shotgun.
Let's not forget that there are TWO carriers out there that sell iPhones: AT&T and Verizon. I happen to be a customer of the latter.
Guess what. While AT&T is going to be getting iOS 4.3.3, my iPhone4 is still plodding along on iOS 4.2.7, and iTunes reports I have the latest software update! When do Verizon users get to catch up with the rest of the world?
Sounds like the school is kangaroo-court convicting the kids of libel. Unfortunately for the school, there's an absolute defense for libel: truth. A bit of poking around should determine whether or not the kids were telling the truth in short order.
Meanwhile, why is the school acting as the Internet Police? They have better things to spend their time and money on...for example, teaching kids.
There's a deletion-review discussion ongoing, with a large number of long-established editors pushing to overturn the deletion. Somebody really jumped the gun on this one.
Indeed, the laws of the United States are quite clear. If something occurs in a public place (and a public street definitely qualifies), it may be photographed or videographed by any person with clear line of sight to that event. The exception would be if the event took place inside a vehicle, which most jurisdictions consider an extension of a person's home or corporation's property, in which case the implied right of "privacy in the home" applies.
The charge of "unlawful wiretapping" is nothing more than an attempt at an end run around Graber's rights. I hope the judge can see this.
If someone's looking for a small, low-power CW-only unit, I humbly suggest the Elecraft KX1.
Pluses: about the size of a paperback, runs on 6 AA batteries, claimed battery life at 1-2W is 20 to 30 hours of "casual operation", base model operates 20M and 40M, has an optional internal antenna tuner so a random-wire antenna will provide good results, and by all reports is a very reliable unit. Minuses: it's a kit, so if you're not comfortable with a soldering iron it's probably not for you, and doesn't have its own key unless you buy the optional plug-in paddles.
Were it me, I'd plop down the bucks on the kit, add the tuner option and maybe the 30M and 80M modules as well, spend a few evenings putting it together, and stash it and a couple of fifty-foot rolls of hookup wire in my pack, along with some extra batteries "just in case". I may not need it, but added to whatever other personal-safety equipment I have along, it's one more possible avenue of communication.
DISCLAIMER: I am in no way affiliated with Elecraft.
It's an option, yes, but likely not a viable one unless the admins are looking at the very simplest of tasks, e.g. warm-booting servers.
Here's a question that might prove relevant. How does NASA handle very similar requirements for their interplanetary missions? This might be a good time to open some dialog with the good people at Goddard or JPL and see what sort of ideas they might have.
I can't think of any. The other major CRS out there all look a great deal like SABRE. Some of the smaller airlines may have built some coprocessing systems on RDBMS which use the CRS as a back-end, just to make it a bit easier on the reservations and ticketing people, but since I don't work in the travel field any more I don't know who that might be or what they're using.
Now yeah, you can build a faster single-purpose db. But you better have a god damn'd lot of dev hours allocated to the task. My bet is that you'll probably come our way ahead in cash & time to market with Oracle, a good data architect and a good DBA. Any time you want to put your money on the line, you let me know.
Seems to me this describes AA perfectly...SABRE has been around since what, the mid- to late-70s? And it's still actively developed and maintained. At a fairly hefty annual price tag. And yeah, the user interface is antiquated and arcane, but no one's come up with anything better yet.
Now, I don't know what they're using to get it to play nice with the Internet (since Travelocity is tied directly into SABRE), but that must have been an interesting exercise in programming on its own. That, however, is a discussion topic for another time and place.
Sheesh...and it took someone from MIT to point this out? Look at a prime example of a high-end, heavily-scaled, specialized database: American Airlines' SABRE. The reservations and ticket-sales database system alone is arguably one of the most complex databases ever devised, is constantly (and I do mean constantly) being updated, is routinely accessed by hundreds of thousands of separate clients a day...and in its purest form, is completely command-line driven. (Ever see a command line for SABRE? People just THINK the APL symbol set looked arcane!) And yet this one system is expected to maintain carrier-grade uptime or better, and respond to any command or request within eight seconds of input. I've seen desktop (read: non-networked) Oracle databases that couldn't accomplish that!
As another VE (volunteer examiner), as well as one who had to learn the code to obtain the Technician-class license some time back, here's my two cents' worth (save up the change for a root beer or something).
The Morse Code isn't dead. Groups such as FISTS will make sure it sticks around on the ham bands for quite some time. Even non-members will continue to operate it, if for no other reason than the maintenance and improvement of a traditional skill. I prefer to operate digital modes -- SSTV and PSK31 are my favorites -- but I still want to improve my CW skills to the point that I can do some contesting using the code.
There's still another area where the Morse is not going away yet...that of maritime radio service. An applicant for licensure as a ship's Radio Officer must possess at least a 2nd-class Radiotelegraph License, which requires both a sending and receiving test at 20 words per minute (300 characters/min using the Paris standard). Granted, with the deployment of GMRSS the Radio Officer is becoming less and less a fixture on many transoceanic vessels, but they're still there. Not just them, either...applicants for both Master and Mate licenses still have to be able to copy light signals, which are sent by Morse Code.
I realize I'm probably beating a dead horse here, but I'm feeling compelled to contribute my two cents' worth. (Save up the change for a root beer or something.)
You could teach C, C++, Java, Perl, Smalltalk, Fortran, or any number of other programming languages, either structured or object-oriented. But if the students don't get some of the basic concepts of building algorithms and flows, all they're going to come out with is the ability to recognize a given language based on the syntax...three out of five times.
Better to start with giving the students a foundation in the thought processes that go into program development: defining the problem thoroughly, choosing the best framework for a solution, seeing if there's already a solution available, deciding if what's available is better or worse than something "home-brewed", and only then sitting down with pen and paper and starting the actual design. If you want to use C as a foundation language for demonstrating the process, well and good. But, IMO, problem-solving should be stressed over the mechanics of any given language.
As to the selection of language...again, IMO, C or C++ isn't the best first choice, even though they're de facto industry standards at this point. If they can write good, clean, tight Java code, it's a fairly short step up to C++. If they can write good, clean, tight Smalltalk routines, learning a SQL variant will be a comparative snap. Tossing them into the mix at the C or C++ level, especially as neophyte coders, will send at least half of them screaming for the nearest AOL chat room, and give at least a third of the remainder migraines. Teach them to walk first, then to run marathons.
...in the NIST SP-800 series of publications. Federal (US) agencies are already expected to abide by the standards described in that series, as well as other NIST/FIPS publications, e.g.FIPS 140-2 for cryptographic modules,or FIPS 200 for establishing minimum security requirements for specific systems.
Having had to study several of those publications for work-related tasks, I don't see where there should be any level of pushback from the corporate IT world, since a great many of them already have security measures in place that meet or exceed the requirements described in the NIST and FIPS publications. Individuals' systems, or SOHO systems and networks, would be a bit more problematic; a retailer throwing together an office network of four or five off-the-shelf boxes from (picking a name at random) Dell would likely have no idea where to start in trying to meet all the various technical specifications described just in NIST 800-59, if they even know that publication exists.
Bottom line...there's a great deal of education that will be required, not only with individuals and small-shop operators, but with network designers and custom-system builders. The days of ordering up a laundry list of parts from (again, grabbing names out of midair) NewEgg, throwing them together and delivering a completed machine to a customer with a pat on the back and a "have fun" are gone. Especially if the customer falls into one of the more ticklish areas of electronic security, such as a doctor's office or a law firm.
Just my 2p worth.
This is going to be a fantastic sales point...
...for Apple. It may also be what drives several former Windows-centric corporations into Linux.
Why do you think I mentioned it? Apparently, my sarcasm didn't translate...
Want to stem the flood of HFT software into the Wall Street environment? Pass a law that requires any such software to be written in Ada. Think that one through...
If the Texas School Board Association had its way, school pupils in Texas would never hear of Jefferson. Instead, they'd learn how great a contributor to America was (wait for it...) Phyllis Schlafly.
It is truly a strange world in which we live.
The downsides to the concept, as I see them:
1. It would require a very large and dynamic database, and that database would require updating almost every minute, as transmitters change "signatures", are switched on or off, or are interfered with by atmospheric phenomena. The storage and computational power required to do so would keep a midrange desktop machine busy almost 100% of the time.
2. Significant events that disrupt the power grid, such as the derecho in the eastern US over the weekend, would render the system useless within the affected area.
3. Propagation conditions would affect such a system even more than GPS is affected. One big CME would knock out at least half the transmitters the concept relies on, if not more.
Falcone thinks he can sue TWO government entities at the same time? File this under the heading of "more money than brains". Especially since one of his targets is the DoD, which has the first, last and only word on GPS operation.
I'd LOVE to see your sling-shot. I've never seen one with a three-hundred-meter vertical, two-kilometer horizontal range with enough accuracy to hit a fast-moving R/C airplane carrying a camera.
Total cost for that little gem is less than $300US. Granted, no live video feed back to the operator for that particular example, but it has been done, and it adds about $300US to the above price tag.
Things to make you go "hmmm...."
A shotgun? Good luck with that. You might want to review some of the videos posted here. Many of those planes operate at altitudes well outside the nominal range of a shotgun.
Let's not forget that there are TWO carriers out there that sell iPhones: AT&T and Verizon. I happen to be a customer of the latter.
Guess what. While AT&T is going to be getting iOS 4.3.3, my iPhone4 is still plodding along on iOS 4.2.7, and iTunes reports I have the latest software update! When do Verizon users get to catch up with the rest of the world?
Sounds like the school is kangaroo-court convicting the kids of libel. Unfortunately for the school, there's an absolute defense for libel: truth. A bit of poking around should determine whether or not the kids were telling the truth in short order.
Meanwhile, why is the school acting as the Internet Police? They have better things to spend their time and money on...for example, teaching kids.
Just my two cents' worth.
The article's been restored. Looks like the Deletion Review process did what it was supposed to do.
There's a deletion-review discussion ongoing, with a large number of long-established editors pushing to overturn the deletion. Somebody really jumped the gun on this one.
Indeed, the laws of the United States are quite clear. If something occurs in a public place (and a public street definitely qualifies), it may be photographed or videographed by any person with clear line of sight to that event. The exception would be if the event took place inside a vehicle, which most jurisdictions consider an extension of a person's home or corporation's property, in which case the implied right of "privacy in the home" applies.
The charge of "unlawful wiretapping" is nothing more than an attempt at an end run around Graber's rights. I hope the judge can see this.
DISCLAIMER: IANAL. I am, however, a photographer.
If someone's looking for a small, low-power CW-only unit, I humbly suggest the Elecraft KX1. Pluses: about the size of a paperback, runs on 6 AA batteries, claimed battery life at 1-2W is 20 to 30 hours of "casual operation", base model operates 20M and 40M, has an optional internal antenna tuner so a random-wire antenna will provide good results, and by all reports is a very reliable unit. Minuses: it's a kit, so if you're not comfortable with a soldering iron it's probably not for you, and doesn't have its own key unless you buy the optional plug-in paddles.
Were it me, I'd plop down the bucks on the kit, add the tuner option and maybe the 30M and 80M modules as well, spend a few evenings putting it together, and stash it and a couple of fifty-foot rolls of hookup wire in my pack, along with some extra batteries "just in case". I may not need it, but added to whatever other personal-safety equipment I have along, it's one more possible avenue of communication.
DISCLAIMER: I am in no way affiliated with Elecraft.
...that in the Chinese, "bing" means poison?
Do a bit of research. What aerospace firms are in Alabama and Utah?
It is ALWAYS about the money. 'Nuff said.
It's simple, really...they're seeing a goose that lays golden eggs, and deciding it's better to roast the goose.
It's an option, yes, but likely not a viable one unless the admins are looking at the very simplest of tasks, e.g. warm-booting servers.
Here's a question that might prove relevant. How does NASA handle very similar requirements for their interplanetary missions? This might be a good time to open some dialog with the good people at Goddard or JPL and see what sort of ideas they might have.
Disclaimer: IANAL.
That said...wouldn't this be a place where the SLAPP statutes come into play?
Enquiring minds, etc....
I can't think of any. The other major CRS out there all look a great deal like SABRE. Some of the smaller airlines may have built some coprocessing systems on RDBMS which use the CRS as a back-end, just to make it a bit easier on the reservations and ticketing people, but since I don't work in the travel field any more I don't know who that might be or what they're using.
Seems to me this describes AA perfectly...SABRE has been around since what, the mid- to late-70s? And it's still actively developed and maintained. At a fairly hefty annual price tag. And yeah, the user interface is antiquated and arcane, but no one's come up with anything better yet.
Now, I don't know what they're using to get it to play nice with the Internet (since Travelocity is tied directly into SABRE), but that must have been an interesting exercise in programming on its own. That, however, is a discussion topic for another time and place.
Sheesh...and it took someone from MIT to point this out? Look at a prime example of a high-end, heavily-scaled, specialized database: American Airlines' SABRE. The reservations and ticket-sales database system alone is arguably one of the most complex databases ever devised, is constantly (and I do mean constantly) being updated, is routinely accessed by hundreds of thousands of separate clients a day...and in its purest form, is completely command-line driven. (Ever see a command line for SABRE? People just THINK the APL symbol set looked arcane!) And yet this one system is expected to maintain carrier-grade uptime or better, and respond to any command or request within eight seconds of input. I've seen desktop (read: non-networked) Oracle databases that couldn't accomplish that!
As another VE (volunteer examiner), as well as one who had to learn the code to obtain the Technician-class license some time back, here's my two cents' worth (save up the change for a root beer or something).
The Morse Code isn't dead. Groups such as FISTS will make sure it sticks around on the ham bands for quite some time. Even non-members will continue to operate it, if for no other reason than the maintenance and improvement of a traditional skill. I prefer to operate digital modes -- SSTV and PSK31 are my favorites -- but I still want to improve my CW skills to the point that I can do some contesting using the code.
There's still another area where the Morse is not going away yet...that of maritime radio service. An applicant for licensure as a ship's Radio Officer must possess at least a 2nd-class Radiotelegraph License, which requires both a sending and receiving test at 20 words per minute (300 characters/min using the Paris standard). Granted, with the deployment of GMRSS the Radio Officer is becoming less and less a fixture on many transoceanic vessels, but they're still there. Not just them, either...applicants for both Master and Mate licenses still have to be able to copy light signals, which are sent by Morse Code.
I realize I'm probably beating a dead horse here, but I'm feeling compelled to contribute my two cents' worth. (Save up the change for a root beer or something.)
You could teach C, C++, Java, Perl, Smalltalk, Fortran, or any number of other programming languages, either structured or object-oriented. But if the students don't get some of the basic concepts of building algorithms and flows, all they're going to come out with is the ability to recognize a given language based on the syntax...three out of five times.
Better to start with giving the students a foundation in the thought processes that go into program development: defining the problem thoroughly, choosing the best framework for a solution, seeing if there's already a solution available, deciding if what's available is better or worse than something "home-brewed", and only then sitting down with pen and paper and starting the actual design. If you want to use C as a foundation language for demonstrating the process, well and good. But, IMO, problem-solving should be stressed over the mechanics of any given language.
As to the selection of language...again, IMO, C or C++ isn't the best first choice, even though they're de facto industry standards at this point. If they can write good, clean, tight Java code, it's a fairly short step up to C++. If they can write good, clean, tight Smalltalk routines, learning a SQL variant will be a comparative snap. Tossing them into the mix at the C or C++ level, especially as neophyte coders, will send at least half of them screaming for the nearest AOL chat room, and give at least a third of the remainder migraines. Teach them to walk first, then to run marathons.