STIDS 2010 Home
Venue & Local info
Agenda & Papers
Call for Papers
In addition to the common information provided on the STIDS 2010 website (http://stids.c4i.gmu.edu/), the theme
of the TS/SCI Workshop Oct 29th will be "Improving STIDS technology transfer into fielded, high value, end-user
applications." (STIDS here refers to all semantic technology and ontology R&D and not just the presentations in
the STIDS Conference & Workshop).
Attendance to the main conference is a pre-requisite,
and each attendee of the STIDS Classified Workshop will be
expected to participate by presenting related semantic technology or ontology research and development,
plans and ideas, or by contributing to the overall discussion. Attendance is limited to 40, at present, and those
with the most to contribute will have priority. The goal is to make real progress towards this theme this coming
year, and to report that progress at the STIDS 2011 TS/SCI Workshop (a very hard task in a poor economy with many
difficult DoD, IC, national, and international problems, but badly needed).
There is a STIDS 2010 TS/SCI Workshop website on JWICS Intelink and a STIDS 2010 announcement in the "Events Schedule"
banner that everyone can see when logging into the high-side (TS/SCI) Intelink. This notice will appear on the Intelink
29 October 2010
Institute for Defense Analyses (IDA) SCIF
4850 Mark Center Drive, Alexandria, VA 22311
You will be notified of your acceptance and you will receive driving
directions and meeting times after your Certs have been sent to IDA
(see below) and you have been approved for the STIDS TS/SCI workshop.
Clearances & Visit Requests:
Clearances and visit requests may be sent through JPAS - SCI SMO
code is 7A2932. Identify Brian Haugh as IDA POC for STIDS 2010 TS/SCI.
Or FAX to 703-671-4708 (U) or 703-671-4707 (S). To verify receipt,
please call 703-671-4700.
Program Security Specialist
Institute for Defense Analyses
For additional information on the STIDS Classified Workshop, please
contact Terry Janssen at firstname.lastname@example.org.