Data Queries
============
1. What format are the printers files?
At present, the printers files are held in Ventura tagged ASCII or Quark
Xpress. At present, the Institute is arranging to have a standard
Ventura tagging system put in place across all publications, and to have
books which are typeset in Quark Xpress re-typeset in Ventura publisher
to attempt to ensure some standard of uniformity. It can be taken that
the standardised versions are the ones which will be used as the basis
for the CD-ROM publication.
2. On what platforms are the printers files held?
Presently they are held predominantly on IBM PC format, with some text
being held on Macintosh format. This position will also be regularised
such that all text files are held on IBM PC formats.
3. What are the field requirements?
We wish to avoid if at all possible the complexities of detailed
fielding in the manipulation of the text. The fundamental unit of each
publication is the chapter section. This section comprises one or more
paragraphs, and may include tables and mathematical layouts. We propose
that the chapter section be the only distinguished field in the book.
4. What logic will dictate a hypertext link, and where should this jump
to?
The optimal system for hypertext linking will be as follows:
Table of Contents to chapter section
Index to chapter section
Table of cases to case reference within a chapter section
Table of legislation (Statutes) to legislative reference within a chapter section
Legislative reference to next occurrence of legislative reference
The latter hypertext link is the only link where it is envisaged that
the query will span individual publications. Both the source and
destination of the hypertext links can be defined either
a) by the Ventura tag characteristic or
b) by the structure of the reference.
For instance, a legislative reference occurring in one section of a book
will be identical to its hypertext destination in another section of the
book. Hypertext linking as described at bullet points three and four
are the less critical.
5. Can a sample of the data be supplied?
Yes, immediately if required, or optimally when the standardisation
process has commenced.
Software Development Queries
1. What functionality should the application have?
The user should be in a position to:
1) select a text or a number of texts to be the subject of a search
2) carry out a full text search on the entire contents of the text
3) carry out a full text search on any or all of the following components of the text
The Index
The Table of Contents
The Table of Statutes
The Table of Cases
The search facilities should be capable with dealing with simple Boolean
logic, using standard operators. It should be possible to retain a
listing of searches carried out in an individual session for saving to
file or for printing. This listing must include reference to the text
or texts which were researched. The user should be able to browse the
records with hits in the context of their position within the text: for
instance if a hit is returned in a particular chapter section, the
chapter sections preceding and following the chapter section containing
the hit should also be visible on screen.
More advanced text management facilities, such as text file shadowing,
highlighting, bookmarking and annotation are not per se a requirement.
However, if the text management software supports such facilities, this
should not be a reason to preclude it.
2. What are the security requirements and considerations?
The electronic text contains valuable proprietary information. In this
regard, the following levels of security are vital:
a) The text itself should not be installed on the computer which manages the CD-ROM.
b) Reasonable precautions should be in place to render difficult the duplication of the CD-ROM itself.
c) It is envisaged that all of the text will be supplied on the same CD-ROM. However, individual users may have different licences for various publications on the CD-ROM. Accordingly each individual publication must be security locked.
d) It is not proposed to disable text copying at the GUI level (using copy and paste) or to limit the number of chapter sections which can be printed. However, printing controls should be limited to the selection
of one individual chapter section at a time for printing: we wish to
avoid the possibility of batch printing or the facilitation of the
printing of the entire body of text.
e) We propose to produce only one version of the CD-ROM: in networked environments, we will require companies to purchase multiple copies of the CD-ROM for distribution to individual users machines should they so require.
Should the application be 16 bit (i.e. Win 3.11) compatible?
============================================================
Yes.
Updating Queries
================
1. How often will the publication be updated?
Annually.
2. Are all the publications reprinted each year?
Generally yes, with perhaps three or four exceptions, depending on the
extent of changes in tax law.
General Publishing Queries
==========================
1. Can a breakdown of distribution of publications and costs of
individual publications be provided?
The publications are distributed evenly, except for one publication
whose distribution totals that of all of the other publications
combined. The individual publications vary in price from A310 to A375
depending on how specialised their content is.
2. Will there be further publications in the future?
Yes.
3. Will a higher fiscal value be placed on the CD-ROM publication than
the hard copy?
This marketing decision has yet to be finalised.
Schedule
========
1. What is the required schedule for completion of project?
We wish to be in a position to publish the CD-ROM product in June of
1998.
2. What is the schedule for publishing the database on the Web?
We would aspire to be in a position to do so within six months of the
initial publication of the CD-ROM.
3. Would the required functionality for a CD-ROM product be the same as
the required Web functionality?
Broadly, yes. However, it is likely that the CD-ROM product on the Web
would be priced along a pay per view model or along an access licence
model.
Hardware
========
1. What is the required minimum specification the finished application
should run on?
486/66 mhz, Intel or Intel compatible processor, 4X CD-ROM drive, 8 MB
RAM, Windows 3.1, Windows 95 or Window NT OS. We do not propose to
produce a Macintosh compatible version.
Miscellaneous
=============
1. Will this project be put to tender?
The Institute of Taxation is speaking to a number of companies in
connection with this project. All interested parties are being offered
the same level of information, and we are dealing with any further
requests for information such as your own as they arise. We do not
propose to put the project through a formal tendering process.
Furthermore, should it transpire that certain interested parties should
demonstrate competence in individual aspects of the project, we would
consider fragmenting the project and as signing phases of it to the
companies whose expertise seems strongest in the relevant areas.