Request for Change

A Request for Change (RFC) is applicable to the TIPSTER concept, design and architecture.

Generally, RFCs are the result of needed changes to the Architecture Design, but they can be initiated by any new requirement which is applicable to the TIPSTER Program. RFCs are reviewed and approved/disapproved by the Architecture Committee.

Preparation and Submission of RFCs

Content and form must follow the Change Request Form. Form Instructions are available. The completed form is submitted to the TIPSTER SECM via e-mail. Direct acceptance of RFCs via the Web is not yet available, but may be available in the future.

Current RFC Status

(The full text of each RFC can be obtained by clicking on its name.)

Name	Date Submitted	Submitted by	Status
Add RemoveAttribute operation	29 March1996	NYU	Approved by AC, 8 May 1996
Add CreateAttributeValue operation	29 March 1996	NYU	Approved by AC, 8 May 1996
Highlighting	3 April 1996	Univ. of Mass.	Replaced by RFC3a
Highlighting (revised)	17 June 1996	Univ. of Mass.	Approved by AC, 19 July 1996
Thresholds for Detection	3 April 1996	Univ. of Mass.	Replaced by RFC4a
Thresholds for Detection (revised)	17 June 1996	Univ. of Mass.	Approved by AC, 19 August 1996
Monitoring RetrieveDocuments	3 April 1996	Univ. of Mass.	Approved by AC, 8 May 1996
Generate new InternalId on Document copy operations	30 April 1996	Logicon	Approved by AC, 7 Jan 1997
Return Results from RetrieveDocuments [Lightweight Documents & BaseDocument pointers]	30 April 1996	Logicon	Approved by AC, 19 July1996
Close Should Not Call Sync	8 Dec 1997	Univ. of Sheffeld	Reviewed by AC, sent to Chief Architect
Standard Annotations	17 Feb 1998	TWG	Under review by AC
Pattern Specification Language	16 March 1998	DRAFT	Under review by AC
Document Detection	16 March 1998	DRAFT	Under review by AC
Document Lists	9 March 1998	DRAFT	Under review by AC
Class Document	21 Feb 1998	DRAFT	Under review by AC

Note: AC = TIPSTER Architecture Committee