Quark noted in DS9: "The Maquis, Part I" that his bottle of Vulcan port was "three centuries old." At this point in the timeline it was the year 2370 and given the amount of dust accumulated on the bottle one would gather he'd had it sitting on the shelf for quite a while. Calculating three-hundred Earth years (for lack of a Vulcan timetable reference) prior to 2370 places the wine's origination year at 2070. Now given that Quark had owned it for some time before meeting Sakonna, I'd safely place this particular sample of Vulcan port as being produced around the 2060s if not earlier. This is therefore reflected in my edit of the main article; I just wanted to explain my reasoning for the benefit of others. - anonymous (as always), October 7, 2011 (UTC)


This was added this morning:

Technically, for a wine to be Port, it must be a fortified wine from the Douro Valley in the northern provinces of Portugal (see Port wine at Wikipedia). While many other areas, such as Australia, South Africa, India, and the United States, produce wines like Port, they are imitations and not genuine Port. The term "Vulcan port" is therefore a colloquialism, suggesting that the production of Vulcan port, conceivably the production of Vulcan alcoholic beverages in general, is possibly an imported practice not native to Vulcan culture; thus alcoholic beverages produced on Vulcan may be intended primarily for exportation. Then again, the Vulcans' cultural aversion to alcohol may have dissolved by the events of Deep Space Nine given that in DS9: "The Maquis, Part I" Sakonna drank a glass of Ferengi red wine, and a few years later in VOY: "Repression" Tuvok drinks from a glass of Vulcan brandy.

Most of this is not relevant to this particular article, other parts are speculation. -- sulfur 11:26, October 7, 2011 (UTC)

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.