Search Results

H. Peter Alesso Portfolio Past, Present, and Future. " Oh, why is love so complicated?" asked Henry. ​ Alaina said, "It's not so complicated. You just have to love the other person more than yourself." Not everyone who fights is a warrior. ​ A warrior knows what's worth fighting for.

My Story I love words, but that wasn't always the case. ​ I grew up with a talent for numbers, leading me to follow a different path. I went to Annapolis and MIT and became a nuclear physicist at Lawrence Livermore National Laboratory. Only after retiring was my desire to tell stories reawakened. ​ In recent years, I have immersed myself in the world of words, drawing on my scientific knowledge and personal experience to shape my writing. As a scientist, I explored physics and technology, which enabled me to create informative and insightful books, sharing my knowledge with readers who sought to expand their understanding in these areas—contributing to their intellectual growth while satisfying my own passion. But it was my time as a naval officer, that genuinely ignited my imagination and propelled me into science fiction. After graduating from the United States Naval Academy and serving on nuclear submarines during both hot and cold wars, I witnessed firsthand the complexities and challenges of military operations that seamen face daily. This allowed me a unique perspective, which I channeled into creating Henry Gallant and a 22nd-century world where a space officer fought against invading aliens. Through this narrative, I explored the depths of human resilience, the mysteries of space, and the intricacies of military conflict. ​ My stories let me share the highlights of my journey with you. ​ I hope you enjoy the ride. 1/9

Captain Henry Gallant AMAZON Chapter 1 Streak Across the Sky ​ Cold night air smacked Rob Ryan in the face as he stepped out of the Liftoff bar—a favorite haunt of pilots. He was still weaving his way through the parking terminal looking for his single-seat jet-flyer when a familiar face appeared at his elbow. ​ Grabbing his arm, his friend said, “You shouldn’t fly. Let me give you a ride.” ​ Ryan straightened to his full six-two height and shrugged off his friend’s hand. ​ “I’m fine,” he said, swiping a lock of unkempt brown hair out of his eyes. ​ “Don’t be pigheaded. There’s a difference between self-reliance and foolishness.” ​ He pushed past his friend. “Nonsense. I fly better when I’m . . . mellow.” ​ As he left his buddy behind, he noticed a young woman who had come out of the bar after him. He had spent the past hour eyeing this smokin’ hot redhead, but she had been with somebody. Now she was heading out on her own. She glanced at him and quickened her pace. ​ A thought penetrated the fog in his mind. ​ I’ll show her. ​ At his Cobra 777 jet-flyer, he zipped up his pressure suit, buckled into the cockpit, and pulled on his AI neural interface—all the while imagining a wild take-off that would wow the redhead. ​ He jockeyed his jet along the taxiway onto the runway. When the turbo launch kicked in, the black-and-chrome jet spewed a cloud of exhaust and dust across the strip. He jammed the throttle all the way in and gave a whoop of pure joy at the roar and explosive thrust of the machine. The exhilaration—a primitive, visceral feeling—increased by the second, along with his altitude and speed. His love of speed was only matched by his almost unhealthy fascination with flying machines—too fast was never fast enough. ​ For a few seconds, his mind flashed back to his very first flight. The thrill only lasted a few minutes before the mini flyer spun out and crashed. Without a word, his father picked him up and sat him back down in the seat, restarting the engine with a wink and a grin. Clearest of all was the memory of his father’s approval as he took off again and soared higher and faster than before. ​ Now he sliced through the crisp night air in a military jet that had his name engraved on the side. He ignited an extra thruster to drive the engine even hotter. Riding the rush of adrenaline, he pulled back on the stick to pull the nose up. Atmospheric flying was different than being in space, and for him, it had a sensual rhythm all its own. As he reached altitude, he pulled a tight loop and snapped the jet inverted, giving himself a bird’s-eye view of the ground below. ​ But instead of reveling in admiration as expected, he found himself fighting for control against a powerful shockwave as a Scorpion 699 jet blew past him. The blast of its fuel exhaust was nothing compared to the indignation and shame that burned his face. ​ It was the redhead. ​ Damn. She’s good. ​ His pulse raced as he became fully alert. Determined to pursue her, he angled the ship across air traffic lanes, breaking every safety regulation in the book. Instinctively his eyes scanned the horizon and the edges around him, watching for threats or other machines that might interfere with his trajectory. Pinwheeling in a high-G turn, he felt the crush of gravity against his chest, yet still, his hand on the throttle urged ever more speed from the machine. ​ He lost track of the Scorpion in the clouds, and in mere seconds she maneuvered behind him. He tried to shake her using every evasive maneuver he had learned in his fighter training but couldn’t do it. His eyes roamed the sky, watching for potential dangers. The night sky was dark, but several landmarks lit up the ground below him. Earth’s capital, Melbourne, glowed with activity to the north; a mountain range stretched across the horizon 50 km to the west, and an airport lay to the south at the edge of the ocean. As he scanned the skyline, he noticed a radio-telescope antenna. Impulsively he dove toward it, the Scorpion on his tail. ​ At the last moment, the redhead broke pursuit to avoid the antenna, but in a moment of reckless folly, Ryan crashed through the flimsy wire mesh, no more substantial to his Cobra than a wisp of cloud. “That’ll need a patch,” he chuckled. ​ But once more, the Scorpion blew by him. He watched it roar away as if he were in slow motion. As the redhead curved back toward him for another pass, he gritted his teeth in frustration. With thrusters already at max burn, he punched the afterburner to create his own shock wave and turned head-on into her path. “Damn!” he screamed as the other ship twisted away. ​ His golden rule for staying alive while flying was “never yield but always leave yourself an out.” Folly had made him reckless, and he knew his reflexes were sluggish, but he was pissed at himself for letting this pilot provoke him. ​ Recovering his reason, he leveled off and threw down the skid flaps to reach a more reasonable speed. The jet took the torque and inertia strain, and the flashing red lights on his display turned yellow and then green. Despite his irritation, he allowed himself a faint smile when his AI read the Scorpion’s registration: Lorelei Steward. ​ Good sense advised that he throttle back, but pride won out. Spotting the Scorpion silhouetted against a cloud, he jammed the throttle forward yet again. ​ Finally, behind her, his smile broadened. She wouldn’t slip away this time. She pulled her jet into a violent oblique pop, rolled inverted until the nose pointed to the ground then returned to upright. ​ He stuck with her, move for move. ​ Abruptly she angled for the nearby mountain range. He chased her, low and fast, through a pass and down into a twisting canyon, rolling and pitching in a dizzying display of aerobatic skill. He kept close on her six until they blew out of the ravine. ​ In a desperate ploy to shake him, she turned back toward Melbourne’s airspace and headed straight into a crowded flying highway. ​ Ryan was so close behind that it took a few seconds before he realized her blunder. She had turned into an oncoming traffic lane. ​ The cockpit warning lights lit up the cabin as Ryan dodged a stream of oncoming vehicles. Up ahead, Lorelei ducked under a passenger liner that swerved directly into his path. ​ Time slowed to a crawl as he foresaw his fate—he could escape by pulling up—but that would force the crowded passenger liner to dive and crash into the ground. ​ “Damn it all!” he yelled and dove—leaving the liner a clear path to safety. Through the neural interface, his AI shrieked, ​ TOO LOW! PULL UP! TOO LOW! PULL UP! ​ He used every bit of expertise he could muster to twist, turn, and wrestle his jet into a controlled descent. His vision narrowed as the lights of city and ships gave way to a line of unyielding rocks zooming toward him. In a blink, he ran out of time—and altitude. ​ BRACE FOR IMPACT! ​ The Cobra plowed a trough a hundred meters long across the desert floor. Ryan sat in the cockpit, stunned and disoriented amid the flames and wreckage until his lungs convulsed from the dense smoke. An acidic stench and the taste of jet fuel assailed his nose and throat, rousing him from his stupor. Fumbling to unbuckle the safety harness, he held his breath until he could release the hatch and climb out of his ruined machine. Shaking hands searched his body for broken bones. To his relief, he was intact . . . if he didn’t count the ringing in his ears and the blood that coursed down his face. ​ The maxim from flight school ran through his mind: “Any landing you walk away from . . .” But as he limped away, his beloved Cobra burned into a twisted mound of molten metal, its nose buried in the dusty red ground. He shook his head at the wreck. “Captain Gallant is going to have my ass.”

Midshipman Henry Gallant in Space AMAZON Joining the Fleet 1 A massive solar flare roared across the sun, crackling every display console in the tiny spacecraft. “No need to worry, young man. We’re almost there,” said the aged pilot. ​ “I’m not concerned about the storm,” said newly commissioned Midshipman Henry Gallant. Eagerly, he shifted in his seat to get a better view of the massive battlecruiser Repulse that would be his home for the next two years. She was a magnificent fighting machine, a powerful beast in orbit around Jupiter. ​ The pilot maneuvered to minimize the effects of the x-ray and gamma radiation until the craft slid into the cold black shadow of the Repulse. Gallant could hardly contain his delight as the tiny ship quivered in the grip of the warship’s tractors. ​ By the time the docking hatch finally slid open, Gallant was waiting impatiently for his first glimpse inside the warship. ​ He hurried to the bridge. The officer of the watch stood next to the empty captain’s chair, surrounded by a dizzying array of displays and virtual readouts. The officer rested his hand on the panel that concealed the Artificial Intelligence (AI) tactical analyzer. ​ “Midshipman Henry Gallant, reporting aboard, sir.” Drawing his gangly seventeen-year-old figure to its full height, he gave a snappy salute. He tugged at his uniform jacket to pull the buttons into proper alignment. ​ “Welcome aboard, Mr. Gallant. I’m Lieutenant Mather.” Mather was of average height, barrel-chested with angular facial features and a stoic look. Beyond a glance, he showed little interest in the new arrival. “Give me your comm pin.” ​ Gallant handed over his pin, Mather made several quick selections on a touch screen, then swiped it past the chip reader. ​ While his ID loaded into the ship’s computer, Gallant took the opportunity to look around. The semicircular compartment, though spacious, bristled with displays, control panels, and analysis stations. ​ From his academy training, he could guess most of the functions. There were communications, radar, weapons, and astrogation, plus a few he couldn’t identify. Several of the positions were vacant operating automatically. Gallant’s fingers twitched, eager to be a part of the bridge’s efficient operation. A huge view screen dominating the compartment displayed Jupiter. An orbiting space station was visible against the vastness of the gas giant. He marveled at the spectacle. ​ “Junior officer authorization verified. The ID pin has been updated with Repulse’s access codes,” a computer’s voice announced from a nearby speaker. Its neutral, disinterested tone reminded Gallant of a rather cold and distant teacher he had had in basic math years ago. ​ ”Did you bring your gear aboard?” asked Mather. ​ “My duffle bag is at the docking port, sir.” ​ The aged pilot had helped Gallant carry his gear from the shuttlecraft onto Repulse. Then, after a cheery smile and a friendly, “Good luck,” he climbed back in his shuttle and left. Having no family of his own, Gallant had found some faint comfort in the good wishes. ​ ”I’ll have your gear sent to your quarters. But, for now, you had better see the captain,” said Mather, raising an eyebrow at Gallant. ​ “Aye aye, sir,” said Gallant. ​ Mather turned to one of the bridge’s junior officers, a young woman. She wore a single thin gold stripe on her blouse sleeve, indicating her rank as Midshipman First Class, one-year senior to Gallant. He ordered, “Midshipman Mitchel, take Mr. Gallant to the captain’s cabin.” ​ As they left the bridge, Mitchel said, “Henry Gallant . . . I remember you from the academy. I’m surprised you’re still in uniform.” ​ Gallant gritted his teeth, as he had done many times before when confronted with what he perceived as overt disapproval. He didn’t recognize her, but he couldn’t help but observe that she was an attractive brunette with a trim figure. ​ “Will you be training as a fighter pilot or missile weapons officer?” she asked. ​ “I had basic fighter training on Mars and will be taking advanced pilot training with Repulse’s Squadron 111.” ​ “I’m a qualified second-seat astrogator in 111. Most likely, we’ll wind up flying together at some point.” ​ Because her demeanor revealed nothing about whether that idea repelled or appealed to her, Gallant nodded. ​ When they reached the captain’s cabin, she said, “I’m Kelsey, by the way.” Then, as she turned to leave, she added as an afterthought, “Good luck.” ​ Gallant watched her walk away. He wondered if her remark was sincere. ​ *** Gallant stood like a statue inside the open hatch. ​ Captain Kenneth Caine was seated with his back to him, reviewing Gallant’s military record, which was displayed on a computer screen. Clean-shaven with close-cropped graying hair, Caine was solidly built with square shoulders and a craggy face. His well-tailored uniform hugged his robust frame, accentuating his military bearing. ​ From his brief time onboard, Gallant had already realized that Repulse was an orderly ship, and that Kenneth Caine was an orderly captain. Precision and discipline were expected. He was suddenly conscious that his tangled brown hair was longer than regulations allowed. ​ The cabin was sparsely furnished in a traditional, starkly military fashion. A desk in one well-lit corner held the single personal item in the room: a photo of an attractive, mature woman with a pleasant smile. The sadness in her eyes hinted at the difficult bargain she had made as the lonely wife of a dedicated space officer. ​ While the captain flipped through the personnel folder, Gallant’s gaze wandered to the compartment’s viewscreen. The solar flare had subsided, leaving gigantic colorful Jupiter filling most of the view. ​ “At ease, Mr. Gallant,” said Caine, finally turning to face the newcomer. “Welcome aboard the Repulse.” ​ Gallant relaxed his stance and said in a strong, clear voice, “Thank you, sir.” ​ Caine looked him up and down and scrunched his face before asking, “What do you know of this ship’s mission, Mr. Gallant?” ​ “As the flagship of the Jupiter Fleet, Repulse must prevent alien encroachment along the frontier, sir,” ventured Gallant. ​ “Quite right, as far as that goes. But you’ll find, Mr. Gallant, that this task is more nuanced and layered than may be apparent. As a United Planets officer, you must find shades of meaning that can affect your performance. What would you surmise is behind this frontier watch?” The captain’s brisk voice demanded a resolute answer. ​ Gallant spoke guardedly at first, but as his confidence grew, his voice gained assurance. “Well, sir, UP knows little about the aliens’ origins or intentions. They appear to have bases on the satellites of the outer planets. Clashes with their scout ships have proven troublesome, and Fleet Command wants to gather more intelligence. With so little known about alien technology, it isn’t easy to assess the best way to repel it. Still, this fleet must forestall an invasion of Earth by preventing the aliens from gaining a foothold in this sector.” ​ ”And what would you say will be essential in achieving victory in battle?” ​ Leaning forward with his hands behind him to balance out his jutting jaw, Gallant said with fierce intensity, “Surprise, sir! I assume that is why you’ve dispersed most of the fleet. So you can search the widest possible region of space for the first signs of significant alien activity.” ​ Caine examined the young man again as if seeing him for the first time. “Good. We will not be the ones surprised. We will be prepared. You can appreciate how important it is that Repulse performs well.” Then, he added, “And I will allow nothing, and no one, to interfere with our mission.” ​ “Yes, sir,” said Gallant, feeling the sting from the pointed comment. ​ “Tell me, Mr. Gallant,” said the captain, shifting in his chair to find a more comfortable position, “why did you apply to the academy?” ​ Gallant’s voice swelled with passion. “For as long as I can remember, I’ve wanted to pilot spaceships and explore the unknown, sir.” ​ ”You are undoubtedly aware that many people wanted your hide raised up the flagpole.” Caine’s eyebrow twitched. “Although your progress for two academic years at the academy was respectable, many doubt that a Natural can compete in the fleet. Today, your real qualification for advancement is your double helix.” ​ Caine continued, “Frankly, I’m astonished you have gotten this far without the advantages of genetic engineering. You’re a bit of a mystery that has yet to unfold.” ​ Gallant didn’t like being referred to as a mystery, but he had his own uncertainty about how his future might evolve. ​ Caine said, “Now that you are commissioned, you must serve a two-year deployment on Repulse. Then, if you complete all your qualifications and receive strong ranking marks, you may be recommended for promotion to ensign.” ​ He gave a weak smile and added. “Learn your duties, obey orders, and you will have nothing to fear.” Caine searched Gallant’s face. “Well, nothing to say for yourself?” ​ Gallant thrust his chin out and said, “I am prepared to do my duty to the best of my ability, sir!” ​ “It is exactly ‘the best of your ability’ that is in question, young man,” responded Caine.

Rear Admiral Henry Gallant AMAZON Chapter 1 Far Away ​ Captain Henry Gallant was still far away, but he could already make out the bright blue marble of Earth floating in the black velvet ocean of space. ​ His day was flat and dreary. Since entering the solar system, he had been unable to sleep. Instead, he found himself wandering around the bridge like a marble rattling in a jar. His mind had seemingly abandoned his body to meander on its own, leaving his empty shell to limp through his routine. He hoped tomorrow would bring something better. ​ I’ll be home soon, he thought. ​ A welcoming image of Alaina flashed into his mind, but it was instantly shattered by the memory of their last bitter argument. The quarrel had occurred the day he was deployed to the Ross star system and had haunted him throughout the mission. Now that incident loomed like a glaring threat to his homecoming. ​ As he stared at the main viewscreen of the Constellation, he listened to the bridge crew’s chatter. “The sensor sweep is clear, sir,” reported an operator. ​ Gallant was tempted to put a finger to his lips and hiss, “shh,” so he could resume his brooding silence. But that would be unfair to his crew. They were as exhausted and drained from the long demanding deployment as he was. They deserved better. ​ He plopped down into his command chair and said, “Coffee.” ​ The auto-server delivered a steaming cup to the armrest portal. After a few gulps, the coffee woke him from his zombie state. He checked the condition of his ship on a viewscreen. ​ The Constellation was among the largest machines ever built by human beings. She was the queen of the task force, and her crew appreciated her sheer size and strength. She carried them through space with breathtaking majesty, possessing power and might and stealth that established her as the quintessential pride of human ingenuity. They knew every centimeter of her from the forward viewport to the aft exhaust port. Her dull grey titanium hull didn’t glitter or sparkle, but every craggy plate on her exterior was tingling with lethal purpose. She could fly conventionally at a blistering three-tenths the speed of light between planets. And between stars, she warped at faster than the speed of light. Even now, returning from the Ross star system with her depleted starfighters, battle damage, and exhausted crew, she could face any enemy by spitting out starfighters, missiles, lasers, and plasma death. ​ After a moment, he switched the readout to scan the other ships in the task force. Without taking special notice, he considered the material state of one ship after another. Several were in a sorrowful dysfunctional condition, begging for a dockyard’s attention. He congratulated himself for having prepared a detailed refit schedule for when they reached the Moon’s shipyards. He hoped it would speed along the repair process. ​ Earth’s moon would offer the beleaguered Task Force 34, the rest and restoration it deserved after its grueling operation. The Moon was the main hub of the United Planets’ fleet activities. The Luna bases were the most elaborate of all the space facilities in the Solar System. They performed ship overhauls and refits, as well as hundreds of new constructions. Luna’s main military base was named Armstrong Luna and was the home port of the 1st Fleet, fondly called the Home Fleet. ​ Captain Julie Ann McCall caught Gallant’s eye as she rushed from the Combat Information Center onto the bridge. There was a troubled look on her face. ​ Is she anxious to get home too? ​ Was there someone special waiting for her? Or would she, once more, disappear into the recesses of the Solar Intelligence Agency? ​ After all these years, she’s still a mystery to me. ​ McCall approached him and leaned close to his face. ​ In a hushed throaty voice, she whispered, “Captain, we’ve received an action message. You must read it immediately.” ​ Her tight self-control usually obscured her emotions, but now something extraordinary appeared in her translucent blue eyes—fear! ​ He placed his thumb over his command console ID recognition pad. A few swipes over the screen, and he saw the latest action message icon flashing red. He tapped the symbol, and it opened. TOP SECRET: ULTRA - WAR WARNING Date-time stamp: 06.11.2176.12:00 Authentication code: Alpha-Gamma 1916 To: All Solar System Commands From: Solar Intelligence Agency Subject: War Warning Diplomatic peace negotiations with the Titans have broken down. Repeat: Diplomatic peace negotiations with the Titans have broken down. What this portends is unknown, but all commands are to be on the highest alert in anticipation of the resumption of hostilities. Russell Rissa Director SIA TOP SECRET: ULTRA - WAR WARNING He reread the terse communication. ​ As if emerging from a cocoon, Gallant brushed off his preoccupation over his forthcoming liberty. He considered the possibilities. Last month, he sent the sample Halo detection devices to Earth. He hoped that the SIA had analyzed the technology and distributed it to the fleet, though knowing government bureaucracy, he guessed that effort would need his prodding before the technology came into widespread use. Still, there should be time before it becomes urgent. The SIA had predicted that the Titans would need at least two years to rebuild their forces before they could become a threat again. Could he rely on that? ​ Even though he was getting closer to Earth with every passing second, the light from the inner planets was several days old. Something could have already transpired. There was one immutable lesson in war: never underestimate your opponent. ​ A shiver ran down his spine. ​ This is bad. Very bad! ​ Gone was the malaise that had haunted him earlier. Now, he emerged as a disciplined military strategist, intent on facing a major new challenge. ​ Looking expectantly, he examined McCall’s face for an assessment. ​ Shaking her head, she hesitated. “The picture is incomplete. I have little to offer.” ​ Gallant needed her to be completely open and honest with him, but he was unsure how to win that kind of support. ​ He rubbed his chin and spoke softly, “I’d like to tell you a story about a relationship I’ve had with a trusted colleague. And I’d like you to pretend that you were that colleague.” ​ McCall furrowed her brow, but a curious gleam grew in her eyes. ​ He said, “I’ve known this colleague long enough to know her character even though she has been secretive about her personal life and loyalties.” ​ McCall inhaled and visibly relaxed as she exhaled. Her eyes focused their sharp acumen on Gallant. ​ “She is bright enough to be helpful and wise enough not to be demanding,” continued Gallant. “She has offered insights into critical issues and made informed suggestions that have influenced me. She is astute and might know me better than I know myself because of the tests she has conducted. When I’ve strayed into the sensitive topic of genetic engineering, she has soothed my bumpy relationship with politicians.” ​ He hesitated. Then added, “Yet, she has responsibilities and professional constraints on her candidness. She might be reluctant to speak openly on sensitive issues, particularly to me.” ​ McCall’s face was a blank mask, revealing no trace of her inner response to his enticing words. He said, “If you can relate to this, I want you to consider that we are at a perilous moment. It is essential that you speak frankly to me about any insights you might have about this situation.” She swallowed and took a step closer to Gallant. Their faces were mere centimeters apart. ​ “Very well,” she said. “The Chameleon are a spent force. After the loss of their last Great Ship, they are defenseless. They agreed to an unconditional surrender. They might even beg for our help from the Titans. Their moral system is like ours and should not be a concern in any forthcoming action. However, the Titans have an amoral empathy with other species.” ​ He gave an encouraging nod. ​ She added, “Despite the defeat of Admiral Zzey’s fleet in Ross, the Titans remain a considerable threat. They opened peace negotiations ostensibly to seek a treaty with a neutral zone between our two empires. But we can’t trust them. They are too aggressive and self-interested to keep any peace for long. One option they might try is to eliminate the Chameleon while they have the opportunity. Another is to rebuild their fleet for a future strike against us. However, the most alarming possibility would be an immediate attack against us with everything they currently have. They might even leave their home world exposed. But that would only make sense if they could achieve an immediate and overwhelming strategic victory.” ​ Gallant grimaced as he absorbed her analysis. ​ She concluded, “This dramatic rejection of diplomacy can only mean that they are ready to reignite the war—with a vengeance. They will strike us with swift and ruthless abandon.” ​ Gallant turned his gaze toward the bright blue marble—still far away.

Semantic Web Services AMAZON Chapter 6.0 ​ The Semantic Web ​ In this chapter, we provide an introduction to the Semantic Web and discuss its background and potential. By laying out a road map for its likely development, we describe the essential stepping stones including: knowledge representation, inference, ontology, search and search engines. We also discuss several supporting semantic layers of the Markup Language Pyramid Resource Description Framework (RDF) a nd Web Ontology Language (OWL). ​ In addition, we discuss using RDF and OWL for supporting software agents, Semantic Web Services, and semantic searches. ​ Background ​ Tim Berners-Lee invented the World Wide Web in 1989 and built the World Wide Web Consortium (W3C ) team in 1992 to develop, extend, and standardize the Web. But he didn’t stop there. He continued his research at MIT through Project Oxygen[1] and began conceptual development of the Semantic Web. The Semantic Web is intended to be a paradigm shift just as powerful as the original Web. ​ The goal of the Semantic Web is to provide a machine-readable intelligence that would come from hyperlinked vocabularies that Web authors would use to explicitly define their words and concepts. The idea allows software agents to analyze the Web on our behalf, making smart inferences that go beyond the simple linguistic analyses performed by today's search engines. ​ Why do we need such a system? Today, the data available within HTML Web pages is difficult to use on a large scale because there is no global schema. As a result, there is no system for publishing data in such a way to make it easily processed by machines. For example, just think of the data available on airplane schedules, baseball statistics, and consumer products. This information is presently available at numerous sites, but it is all in HTML format which means that using it has significant limitations. ​ The Semantic Web will bring structure and defined content to the Web, creating an environment where software agents can carry out sophisticated tasks for users. The first steps in weaving the Semantic Web on top of the existing Web are already underway. In the near future, these developments will provide new functionality as machines become better able to "understand" and process the data. ​ This presumes, however, that developers will annotate their Web data in advanced markup languages. To this point, the language-development process isn't finished. There is also ongoing debate about the logic and rules that will govern the complex syntax. The W3C is attempting to set new standards while leading a collaborative effort among scientists around the world. Berners-Lee has stated his vision that today’s Web Services in conjunction with developing the Semantic Web, should become interoperable. ​ Skeptics, however, have called the Semantic Web a Utopian vision of academia. Some doubt it will take root within the commercial community. Despite these doubts, research and development projects are burgeoning throughout the world. And even though Semantic Web technologies are still developing, they have already shown tremendous potential in the areas of semantic groupware (see Chapter 13) and semantic search (see Chapter 15). Enough so, that the future of both the Semantic Web and Semantic Web Services (see Chapter 11) appears technically attractive. ​ The Semantic Web The current Web is built on HTML, which describes how information is to be displayed and laid out on a Web page for humans to read. In effect, the Web has developed as a medium for humans without a focus on data that could be processed automatically. In addition, HTML is not capable of being directly exploited by information retrieval techniques. As a result, the Web is restricted to manual keyword searches. For example, if we want to buy a product over the Internet, we must sit at a computer and search for most popular online stores containing appropriate categories of products. We recognize that while computers are able to adeptly parse Web pages for layout and routine processing, they are unable to process the meaning of their content. XML may have enabled the exchange of data across the Web, but it says nothing about the meaning of that data. The Semantic Web will bring structure to the meaningful content of Web pages, where software agents roaming from page-to-page can readily carry out automated tasks. We can say that the Semantic Web will become the abstract representation of data on the Web. And that it will be constructed over the Resource Description Framework (RDF) (see Chapter 7) and Web Ontology Language (OWL) (see Chapter 8). These languages are being developed by the W3C, with participations from academic researchers and industrial partners. Data can be defined and linked using RDF and OWL so that there is more effective discovery, automation, integration, and reuse across different applications. These languages are conceptually richer than HTML and allow representation of the meaning and structure of content (interrelationships between concepts). This makes Web content understandable by software agents, opening the way to a whole new generation of technologies for information processing, retrieval, and analysis. Two important technologies for developing the Semantic Web are already in place: XML and RDF. XML lets everyone create their own tags. Scripts, or programs, can make use of these tags in sophisticated ways, but the script writer has to know how the page writer uses each tag. In short, XML allows users to add arbitrary structure to their documents, but says nothing about what the structure means. ​ If a developer publishes data in XML on the Web, it doesn’t require much more effort to take the extra step and publish the data in RDF. By creating ontologies to describe data, intelligent applications won’t have to spend time translating various XML schemas. In a closed environment, Semantic Web specifications have already been used to accomplish many tasks, such as data interoperability for business-to-business (B2B) transactions. Many companies have expended resources to translate their internal data syntax for their partners. As everyone migrates towards RDF and ontologies, interoperability will become more flexible to new demands. Another example of applicability is that of digital asset management. Photography archives, digital music, and video are all applications that are looking to rely to a greater degree on metadata. The ability to see relationships between separate media resources as well as the composition of individual media resources is well served by increased metadata descriptions and enhanced vocabularies. The concept of metadata has been around for years and has been employed in many software applications. The push to adopt a common specification will be widely welcomed. ​ For the Semantic Web to function, computers must have access to structured collections of information and sets of inference rules that they can use to conduct automated reasoning. AI researchers have studied such systems and produced today’s Knowledge Representation (KR). KR is currently in a state comparable to that of hypertext before the advent of the Web. Knowledge representation contains the seeds of important applications, but to fully realize its potential, it must be linked into a comprehensive global system. ​ The objective of the Semantic Web, therefore, is to provide a language that expresses both data and rules for reasoning as a Web-based knowledge representation. ​ Adding logic to the Web means using rules to make inferences and choosing a course of action. A combination of mathematical and engineering issues complicates this task (see Chapter 9). The logic must be powerful enough to describe complex properties of objects, but not so powerful that agents can be tricked by a paradox. Intelligence Concepts The concept of Machine Intelligence (MI) is fundamental to the Semantic Web. Machine Intelligence is often referred to in conjunction with the terms Machine Learning, Computational Intelligence, Soft-Computing, and Artificial Intelligence. Although these terms are often used interchangeably, they are different branches of study. For example, Artificial Intelligence involves symbolic computation while Soft-Computing involves intensive numeric computation. We can identify the following sub-branches of Machine Intelligence that relate to the Semantic Web: Knowledge Acquisition and Representation. Agent Systems. Ontology. Although symbolic Artificial Intelligence is currently built and developed into Semantic Web data representation, there is no doubt that software tool vendors and software developers will incorporate the Soft-Computing paradigm as well. The benefit is creating adaptive software applications. This means that Soft-Computing applications may adapt to unforeseen input. Knowledge Acquisition is the extraction of knowledge from various sources, while Knowledge Representation is the expression of knowledge in computer-tractable form that is used to help software-agents perform. A Knowledge Representation language includes Language Syntax (describes configurations that can constitute sentences) and Semantics (determines the facts and meaning based upon the sentences). For the Semantic Web to function, computers must have access to structured collections of information. But, traditional knowledge-representation systems typically have been centralized, requiring everyone to share exactly the same definition of common concepts. As a result, central control is stifling, and increasing the size and scope of such a system rapidly becomes unmanageable. In an attempt to avoid problems, traditional knowledge-representation systems narrow their focus and use a limited set of rules for making inferences. These system limitations restrict the questions that can be asked reliably. XML and the RDF are important technologies for developing the Semantic Web; they provide languages that express both data and rules for reasoning about the data from a knowledge-representation system. The meaning is expressed by RDF, which encodes it in sets of triples, each triple acting as a sentence with a subject, predicate, and object. These triples can be written using XML tags. As a result, an RDF document makes assertions about specific things. Subject and object are each identified by a Universal Resource Identifier (URI), just as those used in a link on a Web page. The predicate is also identified by URIs, which enables anyone to define a new concept just by defining a URI for it somewhere on the Web. The triples of RDF form webs of information about related things. Because RDF uses URIs to encode this information in a document, the URIs ensure that concepts are not just words in a document, but are tied to a unique definition that everyone can find on the Web. Search Algorithms The basic technique of search (or state space search) refers to a broad class of methods that are encountered in many different AI applications; the technique is sometimes considered a universal problem-solving mechanism in AI. To solve a search problem, it is necessary to prescribe a set of possible or allowable states, a set of operators to change from one state to another, an initial state, a set of goal states, and additional information to help distinguish states according to their likeliness to lead to a target or goal state. The problem then becomes one of finding a sequence of operators leading from the initial state to one of the goal states. Search algorithms can range from brute force methods (which use no prior knowledge of the problem domain, and are sometimes referred to as blind searches) to knowledge-intensive heuristic searches that use knowledge to guide the search toward a more efficient path to the goal state (see Chapters 9 and 15). Search techniques include: Brute force Breadth-first Depth-first Depth-first iterative-deepening Bi-directional Heuristic Hill-climbing Best-first A* Beam Iterative-deepening-A* Brute force searches entail the systematic and complete search of the state space to identify and evaluate all possible paths from the initial state to the goal states. These searches can be breadth-first or depth-first. In a breadth-first search, each branch at each node in a search tree is evaluated, and the search works its way from the initial state to the final state considering all possibilities at each branch, a level at a time. In the depth-first search, a particular branch is followed all the way to a dead end (or to a successful goal state). Upon reaching the end of a path, the algorithm backs up and tries the next alternative path in a process called backtracking. The depth-first iterative-deepening algorithm is a variation of the depth-first technique in which the depth-first method is implemented with a gradually increasing limit on the depth. This allows a search to be completed with a reduced memory requirement, and improves the performance where the objective is to find the shortest path to the target state. The bi-directional search starts from both the initial and target states and performs a breadth-first search in both directions until a common state is found in the middle. The solution is found by combining the path from the initial state with the inverse of the path from the target state. These brute force methods are useful for relatively simple problems, but as the complexity of the problem rises, the number of states to be considered can become prohibitive. For this reason, heuristic approaches are more appropriate to complex search problems where prior knowledge can be used to direct the search. Heuristic approaches use knowledge of the domain to guide the choice of which nodes to expand next and thus avoid the need for a blind search of all possible states. ​ The hill-climbing approach is the simplest heuristic search; this method works by always moving in the direction of the locally steepest ascent toward the goal state. The biggest drawback of this approach is that the local maximum is not always the global maximum and the algorithm can get stuck at a local maximum thus failing to achieve the best results. To overcome this drawback, the best-first approach maintains an open list of nodes that have been identified but not expanded. If a local maximum is encountered, the algorithm moves to the next best node from the open list for expansion. This approach, however, evaluates the next best node purely on the basis of its evaluation of ascent toward the goal without regard to the distance it lies from the initial state. The A* technique goes one step further by evaluating the overall path from the initial state to the goal using the path to the present node combined with the ascent rates to the potential successor nodes. This technique tries to find the optimal path to the goal. A variation on this approach is the beam search in which the open list of nodes is limited to retain only the best nodes, and thereby reduce the memory requirement for the search. The iterative-deepening-A* approach is a further variation in which depth-first searches are completed, a branch at a time, until some threshold measure is exceeded for the branch, at which time it is truncated and the search backtracks to the most recently generated node. A classic example of an AI-search application is computer chess. Over the years, computer chess-playing software has received considerable attention, and such programs are a commercial success for home PCs. In addition, most are aware of the highly visible contest between IBM’s Deep Blue Supercomputer and the reigning World Chess Champion, Garry Kasparov in May 1997. Millions of chess and computing fans observed this event in real-time where, in a dramatic sixth game victory, Deep Blue beat Kasparov. This was the first time a computer has won a match with a current world champion under tournament conditions. Computer chess programs generally make use of standardized opening sequences, and end game databases as a knowledge base to simplify these phases of the game. For the middle game, they examine large trees and perform deep searches with pruning to eliminate branches that are evaluated as clearly inferior and to select the most highly evaluated move. We will explore semantic search in more detail in Chapter 15. Thinking The goal of the Semantic Web is to provide a machine-readable intelligence. But, whether AI programs actually think is a relatively unimportant question, because whether or not "smart" programs "think," they are already becoming useful. Consider, for example, IBM’s Deep Blue. In May 1997, IBM's Deep Blue Supercomputer played a defining match with the reigning World Chess Champion, Garry Kasparov. This was the first time a computer had won a complete match against the world’s best human chess player. For almost 50 years, researchers in the field of AI had pursued just this milestone. Playing chess has long been considered an intellectual activity, requiring skill and intelligence of a specialized form. As a result, chess attracted AI researchers. The basic mechanism of Deep Blue is that the computer decides on a chess move by assessing all possible moves and responses. It can identify up to a depth of about 14 moves and value-rank the resulting game positions using an algorithm prepared in advance by a team of grand masters. Did Deep Blue demonstrate intelligence or was it merely an example of computational brute force? Our understanding of how the mind of a brilliant player like Kasparov works is limited. But indubitably, his "thought" process was something very different than Deep Blue’s. Arguably, Kasparov’s brain works through the operation of each of its billions of neurons carrying out hundreds of tiny operations per second, none of which, in isolation, demonstrates intelligence. One approach to AI is to implement methods using ideas of computer science and logic algebras. The algebra would establish the rules between functional relationships and sets of data structures. A fundamental set of instructions would allow operations including sequencing, branching and recursion within an accepted hierarchy. The preference of computer science has been to develop hierarchies that resolve recursive looping through logical methods. One of the great computer science controversies of the past five decades has been the role of GOTO-like statements. This has risen again in the context of Hyperlinking. Hyperlinking, like GOTO statements, can lead to unresolved conflict loops (see Chapter 12). Nevertheless, logic structures have always appealed to AI researchers as a natural entry point to demonstrate machine intelligence. An alternative to logic methods is to use introspection methods, which observe and mimic human brains and behavior. In particular, pattern recognition seems intimately related to a sequence of unique images with a special linkage relationship. While Introspection, or heuristics, is an unreliable way of determining how humans think, when they work, Introspective methods can form effective and useful AI. The success of Deep Blue and chess programming is important because it employs both logic and introspection AI methods. When the opinion is expressed that human grandmasters do not examine 200,000,000 move sequences per second, we should ask, “How do they know?'' The answer is usually that human grandmasters are not aware of searching this number of positions, or that they are aware of searching a smaller number of sequences. But then again, as individuals, we are generally unaware of what actually does go on in our minds. Much of the mental computation done by a chess player is invisible to both the player and to outside observers. Patterns in the position suggest what lines of play to look at, and the pattern recognition processes in the human mind seem to be invisible to that mind. However, the parts of the move tree that are examined are consciously accessible. Suppose most of the chess player’s skill actually comes from an ability to compare the current position against images of 10,000 positions already studied. (There is some evidence that this is at least partly true.) We would call selecting the best position (or image) among the 10,000, insightful. Still, if the unconscious human version yields intelligent results, and the explicit algorithmic Deep Blue version yields essentially the same results, then couldn’t the computer and its programming be called intelligent too? For now, the Web consists primarily of huge number of data nodes (containing texts, pictures, movies, sounds). The data nodes are connected through hyperlinks to form `hyper-networks' can collectively represent complex ideas and concepts above the level of the individual data. However, the Web does not currently perform many sophisticated tasks with this data. The Web merely stores and retrieves information even after considering some of the “intelligent applications” in use today (including intelligent agents, EIP, and Web Services). So far, the Web does not have some of the vital ingredients it needs, such as a global database scheme, a global error-correcting feedback mechanism, a logic layer protocol, or universally accepted knowledge bases with inference engines. As a result, we may say that the Web continues to grow and evolve, but it does not learn. If the jury is still out on defining the Web as intelligent, (and may be for some time) we can still consider ways to change the Web to give it the capabilities to improve and become more useful (see Chapter 9). Knowledge Representation and Inference An important element of AI is the principle that intelligent behavior can be achieved through processing of symbol structures representing increments of knowledge. This has given rise to the development of knowledge-representation languages that permit the representation and manipulation of knowledge to deduce new facts. Thus, knowledge-representation languages must have a well-defined syntax and semantics system, while supporting inference. First let’s define the fundamental terms “data,” “information,” and “knowledge.” An item of data is a fundamental element of an application. Data can be represented by population and labels. Information is an explicit association between data things. Associations are often functional in that they represent a function relating one set of things to another set of things. A rule is an explicit functional association from a set of information things to a resultant information thing. So, in this sense, a rule is knowledge. Knowledge-based systems contain knowledge as well as information and data. The information and data can be modeled and implemented in a database. Knowledge-engineering methodologies address design and maintenance knowledge, as well as the data and information. Logic is used as the formalism for programming languages and databases. It can also be used as a formalism to implement knowledge methodology. Any formalism that admits a declarative semantics and can be interpreted both as a programming language and database language is a knowledge language. Three well-established techniques have been used for knowledge representation and inference: frames and semantic networks, logic based approaches, and rule based systems. Frames and semantic networks also referred to as slot and filler structures, capture declarative information about related objects and concepts where there is a clear class hierarchy and where the principle of inheritance can be used to infer the characteristics of members of a subclass from those of the higher level class. The two forms of reasoning in this technique are matching (i.e., identification of objects having common properties), and property inheritance in which properties are inferred for a subclass. Because of limitations, frames and semantic networks are generally limited to representation and inference of relatively simple systems. Logic-based approaches use logical formulas to represent more complex relationships among objects and attributes. Such approaches have well-defined syntax, semantics and proof theory. When knowledge is represented with logic formulas, the formal power of a logical theorem proof can be applied to derive new knowledge. However, the approach is inflexible and requires great precision in stating the logical relationships. In some cases, common-sense inferences and conclusions cannot be derived, and the approach may be inefficient, especially when dealing with issues that result in large combinations of objects or concepts. Rule-based approaches are more flexible. They allow the representation of knowledge using sets of IF-THEN or other condition action rules. This approach is more procedural and less formal in its logic and as a result, reasoning can be controlled in a forward or backward chaining interpreter. In each of these approaches, the knowledge-representation component (i.e., problem-specific rules and facts) is separate from the problem-solving and inference procedures. Resource Description Framework (RDF) The Semantic Web is built on syntaxes which use the Universal Resource Identifier (URI) to represent data in triples-based structures using Resource Description Framework (RDF) (see Chapter 7). A URI is a Web identifier, such as "http:" or "ftp:.” The syntax of URIs is governed by the IETF, publishers of the general URI specification the W3C maintains a list of URI schemes . In an RDF document, assertions are made about particular things having properties with certain values. This structure turns out to be a natural way to describe the vast majority of the data processed by machines. Subject, predicate, and object are each identified by a URI. The RDF triplets form webs of information about related things. Because RDF uses URIs to encode this information in a document the URIs ensure that concepts are not just words in a document, but are tied to a unique definition. All the triples result in a directed graph whose nodes and arcs are all labeled with qualified URIs. The RDF model is very simple and uniform. The only vocabulary is URIs which allow the use of the same URI as a node and as an arc label. This makes self-reference and reification possible, just as in natural languages. This is appreciable in a user-oriented context (like the Web), but is difficult to cope with in knowledge-based systems and inference engines. ​ Once information is in RDF form, data becomes easier to process. We illustrate an RDF document in Example 6-1. This piece of RDF basically says that a book has the title "e-Video: Producing Internet Video," and was written by "H. Peter Alesso." Example 6-1 ​ Listing 6-1 Sample RDF /XML H. Peter Alesso e-Video: Producing Internet Video The benefit of RDF is that the information maps directly and unambiguously to a decentralized model that differentiates the semantics of the application from any additional syntax. In addition, XML Schema restricts the syntax of XML applications and using it in conjunction with RDF may be useful for creating some datatypes. The goal of RDF is to define a mechanism for describing resources that makes no assumptions about a particular application domain, nor defines the semantics of any application. RDF models may be used to address and reuse components (software engineering), to handle problems of schema evolution (database), and to represent knowledge (Artificial Intelligence). However, modeling metadata in a completely domain independent fashion is difficult to handle. How successful RDF will be in automating activities over the Web is an open question. However, if RDF could provide a standardized framework for most major Web sites and applications, it could bring significant improvements in automating Web-related activities and services (see Chapter 11). If some of the major sites on the Web incorporate semantic modeling through RDF, it could provide more sophisticated searching capabilities over these sites (see Chapter 15). We will return to a detailed presentation of RDF in Chapter 7. RDF Schema ​ The first "layer" of the Semantic Web is the simple data-typing model called a schema. A schema is simply a document that defines another document. It is a master checklist or grammar definition. The RDF Schema was designed to be a simple data-typing model for RDF. Using RDF Schema, we can say that "Desktop" is a type of "Computer," and that "Computer" is a sub class of “Machine”. We can also create properties and classes, as well as, creating ranges and domains for properties. ​ All of the terms for RDF Schema start with namespace http://www.w3.org/2000/01/rdf-schema# . The three most important RDF concepts are "Resource" (rdfs:Resource), "Class" (rdfs:Class), and "Property" (rdf:Property). These are all "classes," in that terms may belong to these classes. For example, all terms in RDF are types of resource. To declare that something is a "type" of something else, we just use the rdf:type property: rdfs:Resource rdf:type rdfs:Class . rdfs:Class rdf:type rdfs:Class . rdf:Property rdf:type rdfs:Class . rdf:type rdf:type rdf:Property . ​ This means "Resource is a type of Class, Class is a type of Class, Property is a type of Class, and type is a type of Property." ​ We will return to a detailed presentation of RDF Schema in Chapter 7. Ontology A program that wants to compare information across two databases has to know that two terms are being used to mean the same thing. Ideally, the program must have a way to discover common meanings for whatever databases it encounters. A solution to this problem is provided by the Semantic Web in the form of collections of information called ontologies. Artificial-intelligence and Web researchers use the term ontology for a document that defines the relations among terms. A typical ontology for the Web includes a taxonomy with a set of inference rules. Ontology and Taxonomy We can express an Ontology as: Ontology = < taxonomy, inference rules> And we can express a taxonomy as: Taxonomy = < {classes}, {relations}> The taxonomy defines classes of objects and relations among them. For example, an address may be defined as a type of location, and city codes may be defined to apply only to locations, and so on. Classes, subclasses, and relations among entities are important tools. We can express a large number of relations among entities by assigning properties to classes and allowing subclasses to inherit such properties. Inference rules in ontologies supply further power. An ontology may express the rule "If a city code is associated with a state code, and an address uses that city code, then that address has the associated state code." A program could then readily deduce, for instance, that an MIT address, being in Cambridge, must be in Massachusetts, which is in the U.S., and therefore should be formatted to U.S. standards. The computer doesn't actually "understand" this, but it can manipulate the terms in a meaningful way. The real power of the Semantic Web will be realized when people create many programs that collect Web content from diverse sources, process the information and exchange the results. The effectiveness of software agents will increase exponentially as more machine-readable Web content and automated services become available. The Semantic Web promotes this synergy — even agents that were not expressly designed to work together can transfer semantic data. The Semantic Web will provide the foundations and the framework to make such technologies more feasible. Web Ontology Language (OWL) In 2003, the W3C began final unification of the disparate ontology efforts into a standardizing ontology called the Web Ontology Language (OWL). OWL is a vocabulary extension of RDF. OWL is currently evolving into the semantic markup language for publishing and sharing ontologies on the World Wide Web. OWL facilitates greater machine readability of Web content than that supported by XML, RDF, and RDFS by providing additional vocabulary along with formal semantics. ​ OWL comes in several flavors as three increasingly-expressive sublanguages: OWL Lite, OWL DL, and OWL Full. By offering three flavors, OWL hopes to attract a broad following. ​ We will return to detailed presentation of OWL in Chapter 8. ​ Inference ​ A rule may describe a conclusion that one draws from a premise. A rule can be a statement processed by an engine or a machine that can make an inference from a given generic rule. The principle of "inference" derives new knowledge from knowledge that we already know. In a mathematical sense, querying is a form of inference and inference is one of the supporting principles of the Semantic Web. ​ For two applications to talk together and process XML data, they require that the two parties must first agree on a common syntax for their documents. After reengineering their documents with new syntax, the exchange can happen. However, using the RDF/XML model, two parties may communicate with different syntax using the concept of equivalencies. For example, in RDF/XML we could say “car” and specify that it is equivalent to “automobile.” ​ We can see how the system could scale. Merging databases becomes recording in RDF that "car" in one database is equivalent to "automobile" in a second database. ​ Indeed, this is already possible with Semantic Web tools, such as a Python program called "Closed World Machine” or CWM. Unfortunately, great levels of inference can only be provided using "First Order Predicate Logic," FOPL languages, and OWL is not entirely a FOPL language. ​ First-order Logic (FOL) is defined as a general-purpose representation language that is based on an ontological commitment to the existence of objects and relations. FOL makes it easy to state facts about categories, either by relating objects to the categories or by quantifying. ​ For FOPL languages, a predicate is a feature of the language which can make a statement about something, or to attribute a property to that thing. ​ Unlike propositional logics, in which specific propositional operators are identified and treated, predicate logic uses arbitrary names for predicates and relations which have no specific meaning until the logic is applied. Though predicates are one of the features which distinguish first-order predicate logic from propositional logic, these are really the extra structure necessary to permit the study of quantifiers. The two important features of natural languages whose logic is captured in the predicate calculus are the terms "every" and "some" and their synonyms. Analogues in formal logic are referred to as the universal and existential quantifiers. These features of language refer to one or more individuals or things, which are not propositions and therefore force some kind of analysis of the structure of "atomic" propositions. ​ The simplest logic is classical or boolean, first-order logic. The "classical" or "boolean" signifies that propositions are either true or false. ​ First-order logic permits reasoning about the propositional and also about quantification ("all" or "some"). An elementary example of the inference is as follows: ​ A ll men are mortal. John is a man. ​ ​ The conclusion: ​ John is mortal. ​ Application of inference rules provides powerful logical deductions. With ontology pages on the Web, solutions to terminology problems begin to emerge. The definitions of terms and vocabularies or XML codes used on a Web page can be defined by pointers from a page to an ontology. Different ontologies need to provide equivalence relations (defining the same meaning for all vocabularies), otherwise there would be a conflict and confusion. Software Agents Many automated Web Services already exist without semantics, but other programs, such as agents have no way to locate one that will perform a specific function. This process, called service discovery, can happen only when there is a common language to describe a service in a way that lets other agents understand both the function offered and the way to take advantage of it. Services and agents can advertise their function by depositing descriptions in directories similar to the Yellow Pages. There are some low-level, service-discovery schemes which are currently available. The Semantic Web is more flexible by comparison. The consumer and producer agents can reach a shared understanding by exchanging ontologies which provide the vocabulary needed for discussion. Agents can even bootstrap new reasoning capabilities when they discover new ontologies. Semantics also make it easier to take advantage of a service that only partially matches a request. An intelligent agent is a computer system that is situated in some environment, that is capable of autonomous action and learning in its environment in order to meet its design objectives. Intelligent agents can have the following characteristics: reactivity — they perceive their environment, and respond, pro-active — they exhibit goal-directed behavior and social — they interact with other agents. Real-time intelligent agent technology offers a powerful Web tool. Agents are able to act without the intervention of humans or other systems: they have control both over their own internal state and over their behavior. In complexity domains, agents must be prepared for the possibility of failure. This situation is called non-deterministic. Normally, an agent will have a repertoire of actions available to it. This set of possible actions represents the agent’s capability to modify its environments. Similarly, the action "purchase a house" will fail if insufficient funds are available to do so. Actions therefore have pre-conditions associated with them, which define the possible situations in which they can be applied. The key problem facing an agent is that of deciding which of its actions it should perform to satisfy its design objectives. Agent architectures are really software architectures for decision-making systems that are embedded in an environment. The complexity of the decision-making process can be affected by a number of different environmental properties, such as: Accessible vs inaccessible. Deterministic vs non- deterministic. Episodic vs non-episodic. Static vs dynamic. Discrete vs continuous. The most complex general class of environment is inaccessible, non-deterministic, non-episodic, dynamic, and continuous. ​ Trust and Proof ​ The next step in the architecture of the Semantic Web is trust and proof. If one person says that x is blue, and another says that x is not blue, will the Semantic Web face logical contradiction? ​ The answer is no, because applications on the Semantic Web generally depend upon context, and applications in the future will contain proof-checking mechanisms and digital signatures. Semantic Web Capabilities and Limitations The Semantic Web promises to make Web content machine understandable, allowing agents and applications to access a variety of heterogeneous resources, processing and integrating the content, and producing added value for the user. The Semantic Web aims to provide an extra machine understandable layer, which will considerably simplify programming and maintenance effort for knowledge-based Web Services. Current technology at research centers allow many of the functionalities the Semantic Web promises: software agents accessing and integrating content from distributed heterogeneous Web resources. However, these applications are really ad-hoc solutions using wrapper technology. A wrapper is a program that accesses an existing Website and extracts the needed information. Wrappers are screen scrapers in the sense that they parse the HTML source of a page, using heuristics to localize and extract the relevant information. Not surprisingly, wrappers have high construction and maintenance costs since much testing is needed to guarantee robust extraction and each time the Website changes, the wrapper has to be updated accordingly. ​ The main power of Semantic Web languages is that anyone can create one, simply by publishing RDF triplets with URIs. We have already seen that RDF Schema and OWL are very powerful languages. ​ One of the main challenges the Semantic Web community faces for the construction of innovative and knowledge-based Web Services is to reduce the programming effort while keeping the Web preparation task as small as possible. The Semantic Web’s success or failure will be determined by solving the following: • The availability of content. • Ontology availability, development, and evolution. • Scalability – Semantic Web content, storage, and search are scalable. • Multilinguality – information in several languages. • Visualization – Intuitive visualization of Semantic Web content. • Stability of Semantic Web languages. Conclusion ​ In this chapter, we provided an introduction to the Semantic Web and discussed its background and potential. By laying out a roadmap for its likely development, we described the essential stepping stones including: knowledge representation, inference, ontology, and search. We also discussed several supporting semantic layers of the Markup Language Pyramid Resource Description Framework (RDF) and Web Ontology Language (OWL). ​ In addition, we discussed using RDF and OWL for supporting software agents, Semantic Web Services, and semantic search. [1] MIT's Project Oxygen is developing technologies to enable pervasive, human-centered computing and information-technology services. Oxygen's user technologies include speech and vision technologies to enable communication with Oxygen as if interacting directly with another person, saving much time and effort. Automaton, individualized knowledge access, and collaboration technologies will be used to perform a wide variety of automated, cutting-edge tasks.

Henry Gallant and the Warrior AMAZON Going Up 1 Lieutenant Henry Gallant plodded along the cobblestone streets of New Annapolis—head down, mind racing . . . ​ My orders say take command of the Warrior immediately . . . but no promotion . . . Why not? He pondered the possibilities, but he already knew the answer. Though he had steely gray eyes, a square jaw, and was taller than nearly everyone around him, what distinguished him most was not visible to the naked eye—he was a Natural—born without genetic engineering. Is this my last chance to prove myself? ​ By the time he reached the space elevator, the welcoming breeze of the clear brisk morning had brightened his mood and he fell into line behind the shipyard personnel without complaint. Looking up, he marveled: That cable climbs into the clouds like an Indian rope trick. When it was his turn at last, the guard scanned his comm pin against the access manifest. The portal light blinked red. “Pardon, sir. Access denied,” said the grim-faced sentry. ​ “Call the officer of the guard,” demanded Gallant. ​ The officer of the guard appeared but was no more inclined to pass Gallant through than the sentry was. The guard touched the interface panel and made several more entries, but the portal continued to blink red. ​ “There’s a hold on your access, sir.” ​ Trouble already? Gallant thought. Then he asked, “A hold?” ​ “Yes, sir. Your clearance and authorization are in order, but SIA has placed a hold on your travel. They want you to report to SIA headquarters, A.S.A.P.” ​ “I need to go to the shipyard and attend to important business before going to the Solar Intelligence Agency,” clarified Gallant, but even as he said it, he knew it wouldn’t help. “Sorry, sir. Orders.” ​ Gallant noticed the four gold stripes of a captain’s sleeve. The officer was waiting to take the next elevator. ​ “Captain?” he said, hailing the man before he recognized him. ​ Captain Kenneth Caine of the Repulse marched to the guard post, frowning. “What can I do for you, Gallant?” ​ Of all the luck, he thought. Caine was the last person he wanted to impose upon, but it was too late now. ​ Several uncomfortable moments passed with the three of them standing there—Caine, Gallant, and the officer of the guard—staring at each other, waiting for someone to break the silence. ​ Finally, Gallant addressed Caine: “Well, sir, I’ve received orders to take command of the Warrior, but apparently all the T’s haven’t been crossed and my shipyard access has a hold from SIA.” ​ Caine’s frown deepened. ​ Gallant turned to the officer of the guard and said, “Is it possible to allow me go to my ship and complete my business? I’ll report to SIA immediately afterward.” ​ The officer of the guard fidgeted and squirmed. He understandably did not like being placed in such a position while under the scrutiny of a full captain. ​ Caine shrugged. ​ Gallant was puzzled for a moment, wondering how to win Caine’s support. ​ He tried the officer of the guard again, “Perhaps, you could send a message to SIA headquarters stating that you informed me of my requirement to report and that I agreed to attend this afternoon after I assume command of my ship. I’ll initial it.” ​ Caine nodded. ​ The guard brightened visibly. “That should be acceptable, sir.” He made a few entries into his interface panel and the portal finally blinked green. ​ Gallant stepped through the gate and joined Caine. Together they walked to the elevator doors and mingled with the group waiting for the next available car. ​ “Thank you for your help, captain,” said Gallant. “I’m sorry to have troubled you.” Caine merely nodded. ​ Unwilling to miss the opportunity to reconnect with his former commanding officer, Gallant asked, “How’ve you been, sir?” ​ Caine’s frown returned. “Well, personally, it’s been quite a trial . . .” ​ Gallant resisted the temptation to coax him onward. ​ After a minute, Caine revealed, “I lost a lot of shipmates during the last action.” He sighed and took a moment to silently mourn their passing. ​ “I’m sorry, sir,” said Gallant, who was sensitive to the prickling pain in Caine’s voice. Gallant then took a long look at the senior officer. He recalled a mental image of his former commanding officer—solidly built and squared shouldered with a crew-cut and a craggy face. In contrast, the man before him now was balding and flabby, with a puffy face and deep frown lines. ​ “Humph,” grumbled Caine, recognizing Gallant’s critical stare. “You’ve changed too. You’re no longer the lanky callow midshipman who reported aboard the Repulse nearly five years ago.” “Thank you, sir,” said Gallant, breaking into an appreciative smile. ​ Caine returned the smile and, warming to the conversation, he said, “We had a few good times back then—and a few victories as well—a good ship, a good crew.” ​ A minute passed before Caine added, “As for the Repulse—she’s suffered along with her crew . . . perhaps more than her fair share. As you know, she’s has been in the forefront of battle since the beginning of the war, but when the Titans attacked Jupiter Station earlier this year, we took a terrible beating—along with the rest of the fleet.” Caine’s face went blank for a few seconds as he relived the event. “ The Titans used nuclear weapons to bombard the colonies. The loss of life was staggering. Jupiter’s moons are now lifeless, scorched rocks. The colonists fled on whatever transport they could find and they’re now in the refugee camp on the outskirts of this city,” said Caine. Then, trying to sound optimistic but unable to hide his concern, he added, “We gave the Titans some lumps as well. It’ll be some time before they can trouble us on this side of the asteroid belt.” “So I understand, sir.” ​ SWOOSH! BAM! ​ The elevator car doors opened with a loud bang. ​ Caine stepped inside. Gallant grabbed the strap and buckled himself into the adjacent acceleration couch. ​ A powerful engine pulled the glass-encased car along a ribbon cable anchored to the planet’s surface and extended to the Mars space station in geostationary orbit. A balance of forces kept the cable under tension while the elevator ascended—gravity at the lower end and the centripetal force of the station at the upper end. The tiny vehicle accelerated swiftly to seven g’s and reached orbit in less than ten minutes before braking to docking speed. ​ Gallant enjoyed a spectacular view as the car sped through the clouds. Below him was the receding raw red and brown landscape of Mars spread over the planet’s curvature; above him was one of man’s most ambitious modern structures; —a space station, replete with a shipyard that housed the newest space vessels under construction including Gallant’s new command, the Warrior, as well as ships in need of repair, including the Repulse. ​ Gallant tried to pick out his minute ship against the much larger battle cruisers nested near it, but the rotation of the station hid it from view. ​ “Repulse is completing extensive repairs. She’ll be back in action before long. I have a fierce loyalty to my ship and I know she’ll acquit herself well, no matter what comes,” said Caine. “I’m sure she will, sir,” said Gallant. ​ “I haven’t congratulated you on your first command, yet” Caine said, extending his hand. “You’ve earned it.” ​ “Thank you, sir,” said Gallant, shaking hands, while a thought flashed through his mind, If I earned command, why wasn’t I promoted? ​ “Do you have any idea of your first assignment, yet?” ​ “No, sir. It could be almost anything,” said Gallant, but he was thinking, ​ Probably involves the Warrior’s special capabilities. ​ Caine said, “At least you’ll get a chance to strike the enemy.” ​ Gallant said, “We still know so little about the aliens’ origins or intentions. Since they’ve taken Jupiter, they’ve expanded their bases from the satellites of the outer planets. They’ve also penetrated into the asteroids. That puts them in a position to launch raids here.” ​ Caine said, “I once asked you, ‘What’s the single most important element in achieving victory in battle?’” ​ “Yes, sir, and my answer is the same: surprise.” ​ “Yes,” Caine said, “but to achieve surprise, it’s essential for us to gather more intelligence.” “I agree, sir.” ​ “Tell me, Gallant,” Caine said, as he shifted position, “are you aware there are many people who hold you in contempt? They still doubt that a Natural can serve in the fleet.” ​ Gallant grimaced. “I’ve always done my duty to the best of my ability, sir.” ​ “And you have done admirably, from what I know of your actions, but that hasn’t fazed some. I’ve heard little about your last mission.” ​ “I can’t discuss that mission, sir. It’s been classified as need-to-know under a special compartment classification,” said Gallant, as he thought, I wish I could tell you about the AI berserker machine. I can only imagine what’s in store for the Warrior. “Nevertheless, I’ve heard that Anton Neumann was much praised for that mission. He was promoted to full commander and given the cruiser Achilles, though, I wouldn’t be surprised if his father’s influence played a role in that.” ​ Gallant said nothing, but stared down at his shoes, Neumann always wins. ​ Caine grunted and then said, “Neither of us is in good standing with Anton’s father.” ​ Caine and Gallant had previously run afoul of Gerome Neumann, President of NNR, Shipping and Mining Inc., and an industrial and government powerbroker. ​ Gallant nodded. Upon arriving at the space station platform, the elevator car doors opened automatically and once again banged loudly. ​ SWOOSH! BAM! ​ A long, enclosed tunnel formed the central core of the station with twenty-four perpendicular arms that served as docking piers. The tunnel featured many windows and access ports to reach the twenty-four ships that extended from the docking arms. ​ The two men chatted about the war news while they rode a tram along the tunnel causeway. Finally, Gallant left Caine at the Repulse and continued to his new command. ​ A swarm of workmen buzzed along the Warrior’s scaffolding, cranes hauled machinery to and fro, and miscellaneous gear lay haphazardly about. An infinite amount of preparation was under way, servicing the ship in anticipation of her departure. ​ Gallant gaped . . . There she is. ​ He leaned forward to take in every line and aspect of the ship. Despite the distractions, he saw the ship as a thing of exquisite beauty. ​ The Warrior featured a smooth rocket shaped hull and while she was smaller than her battle cruiser neighbors, she weighed thirty-thousand tons with an overall length of one hundred and twenty meters and a beam of forty meters. She was designed with stealth capability, so she emitted no detectable signals and remained invisible until her power supply required recharging. Her armament included a FASER cannon, several short-range plasma weapons, and several laser cannons. She was equipped with an armor belt and force shield plus electronic warfare decoys and sensors. The ship’s communications, navigation, FTL propulsion, and AI computer were all state-of-the-art. The crew of 126 officers and men, was highly trained and already on board. When the Warrior traveled through the unrelenting and unforgiving medium of space it would serve as the crew’s heartfelt home. ​ The brief, relaxed sense of freedom that Gallant had enjoyed between deployments was coming to an end; his shoulders tightened in anticipation. He stepped onto the enclosed gangplank and saluted the flag that was displayed on the bow. Then he saluted the officer of the watch and asked, “Request permission to come aboard, sir?” ​ “Permission granted, sir,” said Midshipman Gabriel in a gravelly voice that was totally at odds with his huge grin, dimpled cheeks, and boyish freckled face. ​ Was I ever that young? thought Gallant before he recalled he was only a few years older. Boarding the ship, Gallant’s eyes widened as he sought to drink everything in. He was impressed by the innovative technologies that had been freshly installed. The novelty of his role on this ship was not lost on him. Upon reaching the bridge, he ordered Gabriel to use the ship’s intercom to call the crew to attention. ​ “All officers, report to the bridge!” Gabriel ordered. When the officers had gathered around him a minute later, he said, “All hands, attention!” ​ Drawn together on every deck, the crew stopped their work, came to attention, and listened. Gallant recited his orders, “Pursuant to fleet orders, I, Lieutenant Henry Gallant, assume command of the United Planet ship, Warrior, on this date at the Mars’ Space Station.” He continued reciting several more official paragraphs, but from that moment forward, the Warrior was a member of the United Planets’ fleet and Gallant was officially her commanding officer. With the formal requirements concluded, Gallant spoke over the address system: “At ease. Officers and crew of the Warrior, I’m proud to serve with you. I look forward to getting to know each one of you. For now, we must outfit this ship and prepare to do our job as part of the fleet. There are battles to be fought, a war to win, and the Warrior has a key role to play.” ​ Satisfied with his brief statement, Gallant nodded to Gabriel. ​ Over the address system Gabriel announced, “Attention! All hands dismissed! Return to your regular duties.” ​ Gallant stood before the officers on the bridge, addressed each by name and shook their hands, starting with the executive officer and then the department heads; operations, engineering, and weapons; followed by the junior officers. His first impression was that they were an enthusiastic and professional group. ​ “I will provide prioritized work items for each of you to address in the next few days as we prepare for our upcoming shakedown cruise. For now, you can return to your duties. Thank you.” Gallant entered the Combat Information Center and pulled on a neural interface to the ship’s AI. The dozens of delicate silicon probes touched his scalp at key points. It sensitively picked up wave patterns emanating from his thoughts and allowed him to communicate with the AI directly. Gallant formed a mental image of the Warrior's interior. While Gallant could use the interface for evaluating the ship’s condition, the controls remained under manual control. He hashed out his priorities for his department heads to work on and sent them messages. He ordered them to address the myriad of items he had been mentally considering for hours. While he would have liked to have had a discussion with each officer individually, that would simply have to wait. It was time to get back to the space elevator. Gallant frowned in frustration at being pulled away by his appointment: ​ I’d better hustle to SIA.

Excerpts Writing Porfolio Finding Inspiration in Every Turn ​ The Henry Gallant Saga Midshipman Henry Gallant in Space Lieutenant Henry Gallant Henry Gallant and the Warrior Commander Gallant Captain Henry Gallant Commandor Henry Gallant Henry Gallant and the Great Ship Rear Admiral Henry Gallant Midshipman Henry Gallant at the Academy Dramatic Novels Youngblood Dark Genius Captain Hawkins Short Stories All Androids Lie Computer Books Connections Thinking on the Web The Semantic Web The Intelligent Wireless Web E-Video Computer Apps Graphic Novels Screenp lay

Henry Gallant and the Great Ship AMAZON Chapter 1 An Unfortunate Turn of Events As soon as the morning watch settled in, Captain Henry Gallant walked onto the Constellation’s bridge. The Officer-of-the-Deck rose and vacated the command chair without speaking. The voyage had lasted long enough for the crew to become accustomed to his routine. Habitually, during the first minutes of the day, he examined the ship’s vital operational parameters from his bedside monitor before going into CIC for a detailed task force sitrep. Blips from the combat space patrol (CSP) were visible on the main viewer. The speakers broadcast communication traffic from distant Hawkeyes. Once he had satisfied himself that all was as it should be, he appeared on the bridge and assessed the more mundane needs for the day. The OOD handed him a list of completed tasks and those that demanded his approval. During this activity, he was lost in contemplation, and no one dared interrupt his train of thought. ​ Only after dictating his orders for the day did he relax and give a word of encouragement to the OOD. Then he disappeared below decks for his daily walkabout, where he gauged the temperament of the crew. The hour exercise through the spacecraft carrier allowed him to maintain his fitness. This ritual was the most efficient use of his time since it also allowed him to observe ongoing maintenance and repair activities. On the one hand, the number of administrative duties clamoring for his attention limited his time; on the other, keeping in sync with his ship’s pulse was vital to making good decisions. It brought a faint smile to his lips when he resolved to shift more of the clerical burden onto his XO. Margret Fletcher had a talent for paperwork and was known for her no-nonsense adherence to the regs. Even though he overloaded her of late, she had responded with her usual zeal. ​ As he passed through compartment after compartment, he dictated audio notes into his comm pin about items that needed attention. He marched along the corridors and stepped through the open hatches, ever mindful of the crew’s attention. Although immersed in his process, the crew discerned that his military instincts were on full alert. He would notice the slightest failure of attention to detail as the men and women went about their jobs. Occasionally, he heard a laugh or good-natured ribbing. That was well. A crew that could laugh while working would faithfully execute their duties. He enjoyed the sameness of each day; it reassured him that his world remained rational. It had been two days since the Constellation had poked her nose into the Ross star system. Gallant congratulated himself on making the deployment from Earth so rapidly. It had been a long and arduous two-month grind, but Task Force 34 was finally ready to relieve Task Force 31 as guardian of this system. ​ He shifted his mind back to the disturbing initial surveillance reports that had perplexed him for the last twenty-four hours. Task Force 31 was not visible, which by itself, wasn’t alarming. A planetary body might block their light, though they weren’t responding to radio signals either. Again, they might be on the other side of the star, and the speed of light wasn’t being accommodating. Another calculation percolated into his consciousness. He had sent Hawkeyes out on a sweep of the system. So far, nothing was amiss, but there was confusing radio chatter from the planets indicating that some horrific event had occurred recently. Gallant returned to the bridge in time to review the latest recon update. None of the information was reassuring. He noticed an anomaly in the data that prickled the hairs on the back of his neck. Though the statistics were mysteriously thin and precariously riddled with contaminated inconsistencies, they were coaxing him toward a disturbing conclusion. He worried his premonition might be correct and ordered the CIC to conduct an AI simulation analysis. It wasn’t long before Commander Fletcher stepped onto the bridge. ​ “Good morning, Captain,” she said. Then with a frown, she added, “I have the results.” Gallant spun in his command chair and cast a concerned eye on her. ​ She held a tablet by two fingers out in front of her as if she had found it in a vat of something vile. “Morning XO,” said Gallant, taking the device. Swiping through the screens, he absorbed the information while his heartbeat rose. He wanted to remain calm to reinforce his reputation as imperturbable. He didn’t want Fletcher or anyone else to suspect that he could lose his composure. But he was bursting to rush into CIC. He wanted to review the raw data to verify that it was accurate, but he knew that the analysts would have been meticulous in developing this report. She interrupted his concentration. “You were right, sir.” ​ “Ha—h’m,” he said, clearing his throat. He took a deep breath and forced himself to appear relaxed. ​ Fletcher shook her head and prodded, “Looks like an enormous debris field—possibly with escape pods.” ​ She pointed to the area spread deep throughout the star system’s heart, halfway between planets Bravo and Charlie. The OOD and the chief of the watch inched closer, craning their necks to get a peek at the tablet. ​ Gallant recalled the disturbing image of the original data. Understanding flooded over him. He visualized what must have taken place, and it took an enormous effort to suppress his emotions. ​ She scowled. “No sign of Task Force 31.” ​ Still, he didn’t respond. ​ She muttered, “That doesn’t necessarily mean . . .” ​ Everyone on the bridge gazed expectantly at him. ​ Like a father who returns home to find his front door smashed open, he ordered, “OOD, open a channel to all ships.” ​ A moment later, the OOD reported, “Channel open to all ships, Commodore.” ​ “To all ships, this is Commodore Gallant; set general quarters, assume formation diamond 4.4.” ​ “Aye aye, sir,” came the response from each ship. ​ The task force split into four strike forces. Captain Jackson of the Courageous led the first strike force designated 34.1. It was followed one light hour behind by 34.2 and 34.3, led by Captain Hernandez of the Indefatigable and Captain Chu of the Inflexible, respectively. They kept a light-hour separation from each other. Finally, Gallant led Constellation and Invincible in 34.4, another light hour behind the rest. The cruisers and destroyers were split amongst the strike forces. The dispersed strike forces looked like a baseball diamond with the Constellation at home plate. ​ It took several hours to complete the maneuver. Satisfied that the ships were sufficiently far apart for the majority to survive a blast from the Great Ship’s super-laser, he ordered, “Task Force change course to 030 Mark 2, all ahead full.” ​ Gallant waited anxiously on the bridge for the entire twenty-four hours it took for the task force to crawl across the Ross star system. Some telltale blips appeared on the scope interspersed within a belt of asteroids. When they were finally close enough, they saw the remains of many half-dead ships. They began picking up distress signals of countless escape pods. Officers and watch-standers on the bridge stared at the viewscreen, trying to glimpse the wreckage. ​ Gallant’s eye estimated the number of blips. They could only be the remnants of Task Force 31. It was worse than he imagined—a terrible loss of life. ​ “OOD, prepare med-techs. Send the search and rescue teams to recover the escape pod survivors.” The initial action report was sent by the senior surviving officer, Captain Raymond. It was sketchy. It couldn’t be called a ‘battle’ report since not a single ship of the task force had fired a shot. ​ After a brief visit to Constellation’s sickbay, the officer reported to Gallant’s stateroom. ​ Raymond was not quite fifty, but his balding head, sunken eyes, and beaked nose made him appear older. His long black mustache with grey flecks drooped, making him appear to frown. His uniform was in tatters, and he had several bandaged injuries that had been tended to by the ship’s surgeon. His thickset body was powerful, but he stood slumped over, pain etched across his face. ​ “That’s the scorched wreck of my ship, the Dauntless,” said Captain Raymond, pointing to the viewscreen. The broken battlecruiser, along with the crippled remnants of four cruisers and a dozen destroyers, were all that was left of Commodore Pearson’s Task Force 31. ​ “Commodore Pearson orders were to hold the system at all costs. Admiral Graves had assured him that the Great Ship would not appear. He was told that it would have to protect the Chameleon home planet in the Cygni star system against the Titans. At least that was President Neumann’s thinking after he found out that the Chameleon had only the one Great Ship left.” ​ “The United Planets has been in negotiation with the aliens for over a year,” said Gallant. “Was there no progress?” ​ There was anguish in Raymond’s voice. “None. And the Chameleon were angry.” He paused, dropping his gaze. “The governor told them to shove off, no deal was possible. After that ultimatum, things turned ugly.” ​ Gallant frowned. “Take your time and start from the beginning.” ​ Raymond’s words were clipped. “Task Force 31 had one carrier, four battlecruisers, and two cruiser-destroyer squadrons between planets Charlie and Bravo when the Great Ship appeared. They demanded that the United Planets evacuate the star system. Well, you know Pearson, no way that was happening. He sounded battle stations and ordered his ships to disperse to present a minimal target for the Chameleons.” ​ When Raymond hesitated, Gallant prompted, “What happened next?” ​ “The action was a disaster—a complete shock. The Chameleon looked at the dispersion as a threat and warned him to stand-down, withdraw, or surrender. After a few minutes, they fired.” ​ He cast his eyes down. ​ “The single blast was so devastating that it destroyed nearly all our ships. The blinding light and searing heat crippled my Dauntless and disintegrated most of the task force. The crippled remainders launched escape pods and waited for a follow-up salvo that, mercifully, never came. We hobbled out of the way. I sent a message to the governor on Charlie.” Raymond swallowed hard and furrowed his brow. “The governor’s response was to call it ‘an unfortunate turn of events.’” “I learned later that the Chameleon had threatened to make peace with the Titans if we didn’t yield the system. They must have since it gave them the freedom of action to leave their home world unprotected and deal with us.” He handed Gallant a flash drive. “This contains a plot of the action and the recordings of the communications between our ships and the governor. I’ve stuck my neck out to get this information on the record. You should collect and check the wreckage along with my observations.” ​ “I understand. Some powerful men in the admiralty will be worried. I will describe the action in a detailed report to be sent to Earth,” said Gallant. He worried about how to keep Task Force 34 from suffering the same fate as their predecessor.

Commodore Henry Gallant AMAZON Chapter 1 Unidentified Flying Object Lieutenant Rob Ryan was bored. ​ He hated the mundane tasks of being a squadron leader. He liked ‘fast’—the faster, the better. But that wasn’t happening today as he cruised over Earth in his Viper. ​ He was stuck with the tedious job of training his new wingman, Glenn Holman, in strafing maneuvers against the Antarctic target range. ​ As he executed a simple wingover in his starfighter, he wa s about to comment on the poor performance of his novice companion when out of nowhere, the world changed, shifting with shocking suddenness. ​ That’s not possible! ​ He instinctively flung an arm across his face to ward off the seemingly endless wall of steel that had materialized in front of him. ​ I must be hallucinating! ​ Heart-throbbing fear gripped him. ​ But there is something delicious about fear. It starts with bitter panic and grows into sour excitement—until, at last, comes sweet courage. ​ Ryan pulled his arm down, tightened his grip on the thruster, and yelled, “Hard to port! Max thrust! Flip gyros!” ​ Over the next several seconds, he concentrated on avoiding a collision with the mountain of metal. ​ In the first second, he felt the chest-crushing weight of 14 g’s as his Viper began the pivot. ​ In the next second, he fought down the blackness of his vision, narrowing into a tunnel as 20 g’s tested the limitations of his pressure suit. ​ By the third second, he felt as if he was being squashed like a ripe tomato—right before he blacked out. ​ Several seconds later, he came to, blinking against the glare of the sun. Even as he aimed his ship toward it, he heard Holman gasp, “I can’t . . . make it . . .” ​ Almost immediately, Ryan saw the brilliant red-white explosion of Holman’s Viper as it went splat against the steel wall. ​ He sighed with relief when he saw an escape pod spiral toward Earth. ​ *** ​ The July blizzard howled across the high plateau of the Amundsen–Scott South Pole Antarctic Station, leaving a record snowfall of crystalline ice in its wake, and blustering so hard that the Earth defense sensor arrays were blanketed under the full fury of the whiteout. So powerful was the blizzard that sharp flecks of ice pierced the multilayered protective gear of the technician sent to investigate some minor static interference. As the man crawled toward the besieged sensors, his hands lost feeling despite the well-insulated flex-gloves. A large scavenger Skuas bird dive-bombed him, causing him to grab hold of the lifeline tether to keep from falling off the sheer rock cliff. ​ “Damn!” ​ “What’s wrong?” ​ Against the howling of the wind, he could barely hear the question. During the six-month southern hemisphere ‘night,’ the wind blew at 160 km/h, and the temperature dropped to minus 89 °C. Despite the harsh conditions, the dry atmosphere and extended darkness made the station the Earth’s best location for astronomical observations. It had every conceivable type of sensor from microwave telescopes to neutrino detectors. The sensors were so accurate and dependable that the people of Earth rested reassured of their absolute safety. ​ The man gripped the taut cable as he spoke into the mic, “Why do I always get the crap jobs?” “Just do it. And better hurry. Something big is brewing.” ​ Inside the station’s geodesic dome, a sensor operator screamed, “Contact! Contact over Melbourne. It’s massive!” ​ The duty officer came over to the operator’s station. “What’s the problem?” ​ The operator pointed, his finger trembling in shock at the image that filled his screen. ​ Flabbergasted, the duty officer asked, “Where did that come from? No unidentified contacts have been reported!” ​ “It just popped up out of nowhere.” ​ “That’s impossible.” ​ “I’m telling you. Everything was normal, nothing but standard traffic patterns, and then WHAM! There it was.” ​ “Have you run a diagnostic on your equipment?” ​ “Look at the other sensors. They all show the same thing. We have a man outside checking some minor glitches, but nothing that would explain this.” ​ “It isn’t a colossal malfunction? Do you think this is a bona fide contact?” ​ “Yes, sir!” ​ In the stunned silence, the senior chief operator said, “Designate contact as Tango 101, in geosynchronous orbit over Melbourne.” ​ Still unable to grasp the situation, the duty officer asked again, “Why didn’t you spot this earlier?” ​ “I’m telling you; it wasn’t there before. It came out of nowhere. As if it dropped out of cloak.” The dark eyes of the duty officer met the senior chief’s gaze. “That’s impossible. Even in a blizzard, our active sensors can penetrate any cloaking device within a million kilometers of Earth.” ​ As he shook his head, the chief’s white hair fell across his grizzled face, but his eyes stayed steady. “Until now.” ​ The officer asked, “What type of craft is it?” ​ “Nothing in our databases even comes close. Visual images are starting to come in now. Man, it’s the strangest thing I’ve ever seen.” ​ The officer’s eyes bugged out. “Oh, my Gawd! That’s incredible. It’s enormous. What the hell is it?” ​ His hand smacked the red alert button, and his voice echoed over the base-wide intercom. ​ “Activate planet defenses. Scramble standby fighters.” ​ A second later, he said into the emergency radio, “Put me through to Admiral Devens, immediately.” ​ When Admiral Devens responded, the duty officer said, “We have an unidentified flying object over the capital.” ​ “Notify all missile and laser batteries to target the contact, but hold fire until further notice,” said the admiral, unruffled. “Have fighter command scramble all fighters and intercept the UFO.” ​ *** ​ “Fighter command, this is Lieutenant Ryan flying Constellation’s Viper 607. I have Tango 101 in sight.” ​ Like a minnow swimming next to a blue whale, Ryan flew alongside the alien craft examining its features. ​ He said, “Tango 101 is a monster ship that looks like a giant squid. It has an ellipsoid body thirty kilometers in diameter with protruding spikes seventy kilometers long. This Great Ship is beyond the combined resources of all the planets.” ​ “Is it broadcasting?” asked the command center. ​ “Negative, according to my sensors. It has not responded to radio communications, and I can detect no emissions at all, hostile or otherwise.” ​ “Shadow it, but do not engage.” ​ *** Twelve hours later, President Kent addressed the nation. “My fellow citizens, what you have heard is true. We have detected an alien vessel over Earth, but there is no immediate cause for alarm. Planetary defenses are on full alert. Our space fleet and fighters have surrounded the unknown spaceship. We do not know who these beings are, but they are not our Titan enemy. ​ And though victory against that enemy may still seem a long way off, we are prepared to face any challenge they set against us. This new arrival has so far taken no hostile action, and our hope is that they will prove to be a benefactor rather than an adversary. ​ “So, we must be patient until our visitor decides to speak. Until then, I am certain that you will all remain as brave and resolute as our proud space navy that stands guard protecting us at this moment.” ​ Over the next several hours, news stations maintained uninterrupted coverage around the world. Opinions were divided over accepting the president’s optimism. Some listened to the vitriolic counterargument made by presidential candidate Gerome Neumann. He advised swift and total annihilation of the aliens who had violated Earth’s space. ​ When it seemed that the tension couldn’t get any greater, an astounding event occurred. A shuttlecraft departed the Great Ship and landed at the Melbourne spaceport.

New Release Sometimes, the right man in the wrong uniform can make all the difference. Ethan, a lowly recruit with an oil-stained uniform and a spirit worn down by disappointment, finds his life forever changed by a twist of fate. Squinting at his reflection, he sees the sleeves of his borrowed jacket bore captain’s stripes. A grotesque emblem is embossed over the jacket's breast pocket—a roaring lion's head surrounded by a cluster of jagged broken bones—the symbol of the Special Operations Service. There is no way out. The ship is taking off because they think an elite SOS captain is on board to take command—him. His choices were brutally simple . . . act like the officer everyone thought he was or be found out as a fraud. One was survival, the other . . . The consequences sent a wave of panic through him. He was a mouse in a lion's skin. He had to become that lion until he found a way out of his cage. Ethan's path intersects with Kate Haliday, the leader of the dark matter project in the Cygni star system. A subtle dance of glances and half-spoken truths begins. But the threads of connection are fragile as they are tangled with the ambitions of Commander Varek, a skeptical officer. The emergence of an unknown alien race casts a long shadow that shifts the cosmic chessboard of a space fleet and a galactic empire. Their interest in dark matter and Earth's colonies weaves a layer of mystery and suspense. In this hard science fiction dance, Ethan must navigate the intricacies of love, rivalry, and alien invasion. The possibility of being unveiled darkens his every step. With each move, the line between the man he is and the officer he pretended to be . . . blurs. Once a misfit dropout, Mike now controls the fate of man versus machine In a world where the boundaries between man and machine blur, your thoughts, emotions, and yearnings are no longer private. The confluence of biotech and infotech has given birth to the Algorithm—a force that predicts your every move and has the power to shape your deepest desire. But when the Algorithm starts undermining human worth, many find themselves obsolete. Grappling with their waning relevance, they find solace in a new realm. They master the skills of a surreal virtual world that requires neither gravity nor light. As technology's grip tightens, a haunting question emerges: Does anyone hold the reins of the omnipotent Algorithm? Enter an unlikely hero—an aimless dropout who unwittingly finds himself at the nexus of power. Tall and lean, Mike has deep-set blue eyes that often reflect his internal conflicts and dilemmas. His past is riddled with disappointment and insecurity. Assuming another student’s ID in a crowded exam room, Mike's journey takes an unexpected turn when a stern figure declares, "I am Jacob Winters. Welcome to the AI career placement test. Today, we will discover which of you represents the pinnacle of human genius." Delve into Keeper of the Algorithm to discover a future where destiny is written in code and domination is the ultimate prize. For serious AI enthusiasts only!

Youngblood AMAZON Death’s Dream Kingdom* ​ “I can’t breathe!” ​ Youngblood’s lungs strained to inhale the last of the thin air but drew in only an empty breath. His heart pounded against his hollow lungs. His fingers stretched wide and then clenched. ​ The last faint echoes of whining machinery died away as the fading glow of emergency lights sputtered out. ​ He opened his eyes wide trying to make sense of the dark confined space. ​ Where am I? ​ Lying on his back in pitch black, he reached up and touched a smooth encapsulating surface without seams or latches. ​ A coffin? Banging against the case, a raspy cry escaped his mouth, “Helppp.” ​ He scratched with fingers until they bled; he smashed with fists until they bruised. ​ “AUUGGH!” ​ His face was a bulging purple mask with a protruding red tongue. Gory hands wiped away oozing goo dripping from his nose. Each passing second was a countdown toward imploding lungs. Coma and death were fast approaching—causing a spasm of raw cold fear—a deep primal terror like the first great scare a child experienced when his nightmare turned ‘real’ and the claws of a hideous monster squeezed his throat. ​ “Air! I’ve got to have air,” he begged in a whisper. ​ He balled his fist and punched him. He kicked. Again, and again. ​ CRACK! ​ A small fissure created a loud hiss as air trickled into the confined space. ​ Finally able to inhale, Youngblood’s chest rose and fell with each precious breath. ​ The visceral threat of suffocation lessened, but the injuries continued to throb. ​ He pulled out some of the needles that feathered his body. ​ It’s a hibernation chamber. ​ They were supposed to revive him when they found a cure. ​ Did they find a cure? ​ For a moment, he opened his mouth and raised his eyebrows, then . . . ​ Stupid! Stupid! ​ This wasn’t a normal recovery. There were countless things wrong with this. Was this a random system failure? Someone should have been monitoring. ​ His brain screamed. ​ Why isn’t there an alarm and an attendant? ​ They might all be dead. ​ He tried to break out of the case. The straining structure moaned as he pressed against it, but his debilitated joints and impaired muscles lacked the strength to free him. ​ As he continued to welcome the incessant wheezing of cool air filtering into the cocoon, he waited, but no one came. ​ The only sounds of activity were the sparks of electrical wires far off in the distance. With stiff fingers, he massaged his sore arms and legs, but all his efforts to break out of the coffin-like container failed. ​ He dug his fingernails into his palms to escape the deadness that gnawed inside him. Dark destructive thoughts flooded in. The future that was supposed to augur health had turned into a nightmare. His mind stretched back to something very painful, a filament-thin memory, I was eighteen when the debilitating effects of the illness began. Father said hibernation was the only solution. I trusted him. Lies! All his words were lies . . . he just wanted to be rid of me. Lingering on the ghost-like memory as it waxed and waned, it was the end of hope. At that moment, everything came crashing down inside of him. ​ The chamber grew claustrophobic. ​ I’m done. ​ He closed his eyes. ​ It’s over. ​ He let the minutes pass, hoping the pain would end, wishing he would end . . . but neither did. Finally, he opened his eyes and took a deep breath. Focusing his thoughts, he pushed back against the black despair. ​ No! I won’t give up. I’m going to survive . . . somehow. ​ But it was undeniable, he needed immediate medical aid, or this chamber would become a coffin. He screamed when he yanked out the rest of the needles. He cast away the trailing tubes that had sustained his life for . . . ​ How long? ​ No way of telling. ​ You can do this. You must. ​ He pressed against the case once more. It creaked and groaned like a living thing and it took many more tries before, at last, it broke open enough to allow him to squeeze out. Leaning over the edge, he shifted his weight to let it carry him over the side. Hitting the floor with a thump, he began to crawl. It took an hour to reach the wall a mere twenty yards away. There were other chambers along the way, but none appeared operational. ​ “Is anyone there?” he called out—repeatedly. ​ There was never a reply. ​ In a moment of raw honesty, he understood: ​ No one else escaped. ​ Moving along the wall until he reached a door, he wobbled to his feet and managed to stand and press a button. It slid open. ​ He tried to walk, but his legs were unwilling. Leaning against the wall, he let his body slide down to the floor like a sack of sand. ​ There was a dim glow of light at the end of the hall, but crawling took an interminable effort. The light was coming from a control console inside a small room. The dark surroundings offered little information about the devices inside. Exhausted, he hoisted himself into a chair and listened to the rhythmic sound of blood drops smacking onto the floor like a drum beating Taps. ​ As his face blanched, he trembled with dizziness and nausea, his tunnel vision narrowed, the room blackened and spun . . . and then . . . nothingness . . . ​ *** Youngblood woke in a cold sweat. His head throbbed but the room had stopped spinning. He was still sitting at the dysfunctional control panel though only a few dials remained lit. As a computer science major, he thought he should make sense of them, but they were as foreign as a Gödel puzzle. Damn! ​ His fist smashed into the console. ​ HUMMM. ​ He heard the distinct sound but couldn’t pinpoint its location. ​ With every sense alert, he sat waiting . . . ​ “Hello? Is anyone there?” ​ The cold dark concrete walls and poured concrete floor echoed his words but offered no response. ​ There were a couple of doors further down the hall. ​ He stood up. Simply stretching his body took all his effort. His entire body hurt, but slowly he managed to shuffle toward the doors. ​ The first door was locked. ​ The next one was too. ​ He twisted around a corner, but a misstep caused him to fight his own momentum to forestall crashing headfirst into the unyielding wall. The impact to his shoulder knocked him back and whirled him around. Reaching out, he grasped a handle and yanked it to steady himself. ​ The door opened. ​ A storage closet? ​ Catching his breath, he strained his eyes against the dark shadows to identify several large cardboard boxes and a few wooden crates. The largest box was next to a cabinet with symbols he didn’t recognize. Yet, a Red Cross sign was visible on the furthest crate. He stretched his hands toward the old dirt covered wooden crate and pried open the thick heavy lid with his fingers. ​ “Argh.” ​ The cry of anguish was from his own mouth. He placed his suffering hands under his armpits and squeezed until the strained fingers returned to normal. ​ After several minutes, he pulled the lid away and let dirt rattle down into the container. He reached inside to grab a medical package. ​ Thanks. ​ He used the meager emergency rations to stop the bleeding and applied analgesic wherever he could reach. The medication flowed through his veins, stifling the shock and blood loss. He started to relax but his parched throat cried . . . water. ​ He was unable to make out the markings on the other boxes, but he opened the nearest one and groped inside for something familiar. ​ No. ​ Next. ​ No. The last cardboard box . . . ​ Yes. A bottle of water. ​ Taking great gulps, he guzzled what seemed a treasure from an extinct world. He looked for more. There was only one. ​ He tackled another wooden crate. Inside was a flashlight, but it didn’t work. There were batteries on the bottom, but they leaked acid goop. Yet, a few seemed OK. He tried them and felt like a rich man when the flashlight lit and offer the first real peek at his surroundings. ​ There was a nearby room with more defunct hibernation chambers. Another room had medical equipment for reviving patients. ​ But there were no windows anywhere. ​ It’s a bunker. ​ But why put hibernation chambers underground? ​ Putting the puzzle aside, he dug deeper into the storage containers. There were useful items; a butane lighter, a compass, nylon line, a hatchet, a shovel, a hacksaw and lots of basic tools for repairing electrical and computer equipment. ​ He found a workman’s jumpsuit coveralls hanging from a hook on the closet wall and a pair of large black boots. ​ These will come in handy. ​ He moved on and found another closet full of boxes. These were sealed with a plastic wrap, but there was no auxiliary power system visible. ​ There’s got to be a communication device somewhere. ​ He returned to the console and found a diagram framed on the nearby wall. It appeared to be a network of underground tunnels connecting bunkers. An annotated alphanumerical system designated this bunker HB11. Several others had similar designations, but there were also two unique identifiers, YO and SP. The HB might be for hibernation, but he had no clue what YO or SP might represent, nor could he guess how to access the network of tunnels. ​ As he stared at the tunnel map, memorizing the layout, he imagined all the places he could travel to and the places he might visit. What kind of facilities were at each stop along the way? Maybe someday he will find out. ​ He examined some instruments on the console which still had power. The computer system seemed functional, but there wasn’t any written material or operable viewscreen that could offer him instructions. The instruments were as complicated as a spaceship’s and when he attempted to patch into the AI system, he heard a noise. ​ He held his breath. ​ Is someone coming? ​ A humming sound continued from a device in the next room. He must have activated it with his random actions. The machine was marked with English letters and symbols that indicated it was a medical treatment apparatus. He could read several tags on the valves and dials and guessed it was a rejuvenation machine. It took several minutes to surmise how it would work. ​ I’ve got to try this. ​ He climbed naked into the rejuvenation tub and opened a faucet. Synth-fluid and hot medicated elixirs filled the vat. Setting the timer for two hours, he lingered while the potions treated his many superficial ailments. ​ A shame this can’t cure my disease. ​ He relaxed during the treatment while it invigorated his frail body. ​ What’s next? ​ He dragged his body about and toured the bunker, returning to the original room. The flashlight shone on dozens of forsaken hibernation chambers. There was a twin room across the hall, but it too had become a graveyard. ​ A tragedy. I should commemorate them . . . later. ​ He considered revisiting the closets and the locked doors, but that could wait. ​ He looked for more water. ​ No water. ​ The next decision would be critical for his survival. He wanted to use the rejuvenation machine while he restored the power and computer systems, but how long would that take? He had no food or water. Besides, even though he had been a computer whiz, this equipment was far beyond his expertise. Questions exploded in his head like a string of fireworks. ​ Should I stay here? Should I go exploring? ​ Running his fingers through his long shaggy hair, he concluded there was no choice. Putting on the coveralls and boots, he stuffed computer instruments and tools into his cargo pockets. He filled a backpack with survival items and even though it was heavy, he was chafing to get started. Where are the people? ​ *** “I’ve never seen a sky like this,” said Youngblood, as he climbed out of the bunker’s hatch. His eyes took a moment to adjust to the bright sun peeking between a few windswept clouds. “Noon,” he mused and let the hatch drop down. ​ Birds flew overhead, and a glimpse of motion alerted him to a nearby rodent, but there were no roads or worn paths visible. ​ “There’s life, but where are the people?” ​ Originally, he had been placed in hibernation in California’s Stanford Hospital. He had no idea where he was now, but it stood to reason he shouldn’t be too very far away. ​ He surveyed the landscape around him. To the east, he saw a prominent hill rising about a mile away. It was surrounded by scrub brush poking out between a few scattered pine trees. ​ “Hmm . . . a good vantage point.” ​ He swung around and noticed similar regions to the north and south. ​ But things were far different to the west. ​ Where the sky kissed the horizon, blue turned into a mosaic of red, brown, and purple swirls, and the silhouette of a city’s barebone skeleton rose in the distance like a faraway mirage. An acidic stench of smoke and ash invaded his nostrils forcing him to cover his mouth to suppress a spasmodic cough. A brownish yellow haze floated on the hot dry air and dark soot settled on his coveralls. ​ His mouth could barely speak the words, “I can’t believe they actually did it.” ​ A single tear ran down his cheek as he brushed the barren residual ash off his clothes. Anyway, it’s better to die in a flash . . . than suffocate. ​ He licked his lips and swallowed to relieve his parched throat. ​ His fear . . . Where are the people? ​ Became . . . Are there people? ​ Swinging the backpack over his shoulder, he faced east and started forward. A slight cooling breeze sent him on his way as he marched toward the hill. He walked only a few hundred yards before he had to stop and rest. The process repeated itself until his muscles cramped and screamed. He wiped the perspiration off his forehead with his sleeve as he passed areas of dead trees and fall branches. He remained alert for a flash of color, or movement, or any sign of smoke.