STFDOC1-2.html
INITIAL STRUCTURE OF THE ISTF DOCUMENTATION SERIES
Date: 6 Mar 2000
CONTACT:David Norfors, David@Nordfors.se
PARTICIPANTS:
David Norfors, Editor - ISTF Documentation
Series
email: David@Nordfors.se
tel: +46-708-371441
http://istf-docs.norrnod.se
http://docs.istf.org
Christine Maxwell
email: maxwell@isoc.org
Vinton G. Cerf, Chairman - ISTF
email: vcerf@mci.net
ABSTRACT
The structure of the ISTF Documentation
Series contains 1) a Series of temporary documents - TPD - including proposals
and drafts, 2) one ISTF archival series - STFDOC, and 3) one academic publishing
series - Journal of the ISTF (JIST). The archival series STFDOC includes
all official documents of the ISTF. It also documents the organisational
structure and workflow of the ISTF through "folders" - a folder document
is created for each work grou &, each task, including a short presentation
of the work and links to all archival documents created in the task or
work group.
The ISTF documentation series supports the
following publications:
* Proposals and Drafts
(TPD)
Temporary precursor stages of ISTF work
DRAFTS are
documents intended for publication in the STFDOC archival series
Proposals may be of several types, e.g.
The ISTF archival series
Task Proposals and Drafts. (TPD)
TPD is not an archival series - it consists
of temporary publications which can *not* be referred to in archival documents
(the links will go dead when the documents are removed). They can be referred
to in other temporary documents.
The drafts are working documents, in the
style of "Internet-drafts" of the IETF (you can see them here: http://www.ietf.org/ID.html
)
The ISTF task proposal is an addition to
this model. A proposal declares an intention of creating and performing
a task and a wish for feedback directly to the author. It is meant as a
tool to make it easier for the ISTF participants to build a critical mass
around an idea for a task. Some proposals will generate tasks, other might
not.
A proposal should be short - maximum 4000
characters. It should be written in a clear and concise style:
This is who we are (or I am), This is how
to contact us, This is what we want to do, This is why we are posting this
proposal, This is how far we have come today, etc....
Proposals and drafts have an expiration date
after which they are removed unless the authors prolong it. We should find
a mailbot that can see to that notifications are sent automatically to
the authors a week before deletion.
The draft/proposal is a text file (in text
or html format) with the name "<short title - revision no -workgroup
abbr>.txt"
Format
of a DRAFT:
DRAFT <short title - revision no -workgroup
abbr>-draft.txt
TITLE OF THE DRAFT
Version <version number>. Submitted
<date>. Will be removed <date>.
CONTACT: <Name & modes of contact
(email/telephone/address)>
PARTICIPANTS:
<Name/s & contact information (+
affiliation/s)>
ABSTRACT: Max 400 characters summing up the
draft
<BODY>
Format
of a TASK PROPOSAL:
TASK PROPOSAL <short title - revision
no -workgroup abbr>-tap.txt
TITLE OF TASK PROPOSAL
Date:
Version:
Will be removed:
Contact: <name, email, telephone>
Author/s (the lines below repeated for
each author):
Name
Title: (voluntary info.)
Affiliation/s: (voluntary info.)
Email:
DIRECTED TO:(Write who the proposal is
directed to - for example all the participants in the ISTF, people with
certain interests or qualifications, the ISSG, etc.)
ABSTRACT: Max 200 characters summing up the
proposal
BODY:
Motivation: Layout in 4000 words why you
are making this proposal, and
other pertinent information ( include here
the information you already have
under "Body of Proposal".....
Next Steps: Clearly state what
you think should be the next steps
Format
of a WORK GROUP PROPOSAL
WORK GROUP PROPOSAL <short title - revision
no - workgroup abbr>-wgp.txt
PROPOSAL TO ESTABLISH AN ISTF WORK GROUP
<workgroup name>
Date: <date>
Version: <version number>
Will be removed: on approval of the WG,
but latest <date> by <name>
Contact: <name, email, telephone>
Author/s (the lines below repeated for each author):
Name
Title: (voluntary info.)
Affiliation/s: (voluntary info.)
Email:
INTRODUCTION:
why we propose this WG
relevance
relation to other WGs
etc
OBJECTIVES OF THE WORK GROUP:
over-all objective
objectives
Societal Task Force Documents - STFDOC
This is the archival series of the ISTF.
It contains all official documents of the ISTF. For example:
- Work group folders and task folders
- ISTF Reports - the official report from
an ISTF task
- Minutes from ISSG meetings
- Minutes from work group meetings
ISTF Work Groups and ISTF Tasks
Registring a work group or a task is like
opening a folder. It should be supported by the ISSG. A task is submitted
to the editor by the chief investigator. It should be
supported by a work group or the ISSG.
The
Work Group "folder" contains a header:
NAME OF THE WORK GROUP
Registered <date>. Completed <date>
(if succesfully completed).
Closed <date> (if closed). Co-ordinator:
<name, email>
Participants: <names, emails, roles>
Objects of the Work Group: (text)
Tasks of the Work Group: (links to tasks)
Temporary documents of the Work Group:
(link to folder outside the STFDOC archive)
The
TASK "folder" contains a header:
<WORK GROUP> (or ISSG) TASK <task
number>
TITLE OF THE TASK
Registered <date>. Completed <date>
(if succesfully completed).
Closed <date> (if closed).
Chief investigator: <name, email>
Participants: <names, emails, roles>
Milestones: <MILESTONES> (including
planned or actual dates for completion) (there could be something here
about the information strategy of the work)
Then a folder containing links to STFDOCs,
links to peer reviewed publications (Journal of the ISTF or others) + any
other relevant links or documents
Links to drafts are kept in a separate
folder "Drafts and other temporary working documents".
Journal
of the ISTF
A peer reviewed academic journal for publishing
articles building on task work. This will permit researchers to participate
in ISTF tasks as a part of their payed work.
Earlier versions of STFDOC1, replaced
by this version:
STFDOC1-1