About: Subspace eddy

Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: Subspace eddy Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

A subspace eddy was a potentially disruptive spatial phenomenon. In 2152, the Vulcan starship Seleya became caught in a subspace eddy while attempting to chart the thermobaric clouds at the perimeter of the Delphic Expanse. As a result, the Seleya was pulled into the Expanse, and all contact with the ship was lost. (ENT: "Impulse")

Attributes	Values
rdfs:label	Subspace eddy
rdfs:comment	A subspace eddy was a potentially disruptive spatial phenomenon. In 2152, the Vulcan starship Seleya became caught in a subspace eddy while attempting to chart the thermobaric clouds at the perimeter of the Delphic Expanse. As a result, the Seleya was pulled into the Expanse, and all contact with the ship was lost. (ENT: "Impulse")
dcterms:subject	Subspace phenomena
dbkwik:memory-alph...iPageUsesTemplate	dbkwik:resource/4CGJk_wgLQKYXAPvXhmMyw== dbkwik:resource/ET5bAQzBxKKt-crQ8UWh8w==
abstract	A subspace eddy was a potentially disruptive spatial phenomenon. In 2152, the Vulcan starship Seleya became caught in a subspace eddy while attempting to chart the thermobaric clouds at the perimeter of the Delphic Expanse. As a result, the Seleya was pulled into the Expanse, and all contact with the ship was lost. (ENT: "Impulse") In 2378, the Delta Flyer II passed through a subspace eddy. Captain Kathryn Janeway suspected it was the wake of another ship. The Doctor dismissed it as probably just the gravimetric shear from a nearby Mutara class nebula. The eddy turned out to be the wake of a Hierarchy survey vessel. (VOY: "Renaissance Man")

OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software