Timebase Pty Ltd v. Thomson Corporation, The

Filing 247

Declaration of Jenna J. Bayer in Support of 246 Memorandum in Support of Motion filed by Timebase Pty Ltd. (Attachments: # 1 Exhibit(s) A - Part 1, # 2 Exhibit(s) A - Part 2, # 3 Exhibit(s) B, # 4 Exhibit(s) C, # 5 Exhibit(s) D - Part 1, # 6 Exhibit(s) D - Part 2, # 7 Placeholder for Exhibit E, # 8 Exhibit(s) F, # 9 Exhibit(s) G, # 10 Exhibit(s) H, # 11 Exhibit(s) I, # 12 Exhibit(s) J, # 13 Exhibit(s) K, # 14 Exhibit(s) L, # 15 Appendix A, # 16 Appendix B, # 17 Appendix C, # 18 Appendix D - Part 1, # 19 Appendix D - Part 2, # 20 Appendix D - Part 3, # 21 Appendix E - Part 1, # 22 Appendix E - Part 2, # 23 Appendix F - Part 1, # 24 Appendix F - Part 2, # 25 Appendix F - Part 3, # 26 Appendix F - Part 4, # 27 Appendix F - Part 5, # 28 Appendix F - Part 6, # 29 Appendix F - Part 7, # 30 Appendix F - Part 8, # 31 Appendix F - Part 9, # 32 Appendix F - Part 10, # 33 Appendix F - Part 11, # 34 Appendix F - Part 12, # 35 Appendix F - Part 13, # 36 Appendix F - Part 14, # 37 Appendix F - Part 15, # 38 Appendix F - Part 16, # 39 Appendix G - Part 1, # 40 Appendix G - Part 2)(Hosteny, Joseph)

Exhibit A ‐ Part 2

(TimeBase’s United States Patent No. 6,233,592 B1,
“System for Electronic Publishing”)

to

TimeBase’s Memorandum in Support of Its Motion
for Summary Judgment of No Invalidity

US 6,233,592 Bl

69

70

-46Sunset provision
207.

This

Part

ceases

to be

in

force

at

the

(j)end of

5

years

after the Parliamentary Joint Committee is first appointed.
Examples of expiry of a portion of a REGULATION

FEDERAL COURT RULES
Updated as at 22 March 1996

10

ORDER 75 NATIVE TITLE RULES
NATIVE TITLE ACT 1993

ORDER 75
RULE 21
15

Sunset provision
21. Order 75 ceases to be in force on 1 March 1997.
MIGRATION (1993) REGULATIONS - Updated as at 25 July 1994

20

REG 2A
lOA
Sunset provision
2A.10A.

No

application may

be

made

under

this

Division

on

or

after 1 July 1993.
25

[8 06jType Field
This Field provides more specific information about the type of legislation.
It is different to the ID Field described above which gives the legislation a unique 10.
30

This Field uses three single character codes to describe the legislation.
These are as follows:

P = Principal ACTS or REGULATIONS.
It indicates that this is the main or Principal ACT or REGULATION.
35

OR In other words the ACT or REGULATION which gets amended.

Principal ACTS or REGULATIONS can be either in existence (enacted in previous years) or newly
enacted (created in the current year).

366274US

IN; III BCCjO 1 206 US. DOC: lAD

US 6,233,592 Bl
71

72

-47-

There is nothing specifically unique or different in a principal ACT or REGULATION that makes it
easy to identify. By elimination it is however, possible to say what is not a Principal ACT or
REGULATION. This is done by looking at the ACT or REGULATION'S title information. Amending
Acts or Regulations (which are dealt with next) usually contain the word's "Amending",
"Amendment", "Repeal" or "Statute Law Revision" in their Short Title. Another indicator in the case
of ACTS is that the Long Title will also contain the word's "Amending", "Amendment", "Repeal" or
"Statute Law Revision" (REGULATIONS however, do not have a Long Title).

10

The example marked (K) and (J) below shows the Long and Short Titles for a Principal Act
known as the Trade Practices Act. (Compare these examples with the ones marked (L) and (M)
below).

LONG TITLE(K)
15

An Act relating to certain Trade Practices
PART I-PRELIMINARY

SECT 1
20

Short title(J)
1. This Act may be cited as the Trade Practices Act 1974.*1*

SEE NOTES TO FIRST ARTICLE OF THIS CHAPTER .
Note: A principal ACT or REGULATION can contain amendments to other ACTS or
25

REGULATIONS. It therefore, still needs to be considered for its effect on other ACTS.
A" Amending ACTS or REGULATIONS.
It indicates that this is a changing or Amending ACT or REGULATION.
OR In other words the ACT or REGULATION which does the amending.

30

Amending ACTS or REGULATIONS will not generally exist in their own right in the consolidated
information for which we are creating the data base. The changes they effect will nearly always
become part of the Principal ACT or REGULATION

There are some rare exceptions to the above point however, which will need to be identified - (the
35

way to do this most effectively will be to identify them in Australia and provide a list or table of what
these ACTS and REGULATIONS are).

As already stated the best ways to identify an Amending ACT or REGULATION are:

3662.74US

[N :\llBCC10 1 206US. DOC: lAD

US 6,233,592 Bl

74

73

-48-

Amending ACTS or REGULATIONS will nearly always contain the word's "Amending",
"Amendment", "Repeal" or "Statute Law Revision" in their Short Title.

For Acts (but not Regulations) there is also a Long Title at the very beginning of the Act (usually
before Section 1) which will also contain the word's "Amending" "Amendment", "Repeal" or
"Statute Law Revision".
The example marked (L) and (M) below shows the Long and Short Titles for the Amending ACT
10

known as the Trade Practices(Secondary Boycotts) Amendment Act 1979.

LONG TITLE(L)
An

Act

to

amend

the

Trade

Practices

Act

1974

with

respect

Secondary Boycotts and other industrial practices.
15

PART I-PRELIMINARY
SECT 1
Short tit 1 e(M)
20

1.

This

Act

may

be

cited

as

the

Trade

Practices

(Secondary

Boycotts) Amendment Act 1979.*1*
SEE NOTES TO FIRST ARTICLE OF THIS CHAPTER .
Note: An Amending ACT or REGULATION can be amended itself by a further amending
25

ACT or REGULATION.
More Examples of Amending ACTS and REGULATIONS
Following are some more examples of Amending ACTS and REGULATIONS and what
to look for.

30

Statute Law Revision Acts
Below are two examples of these. Usually, this is clean up legislation which makes many
changes and often effects a larger number of ACTS, They can be specific as in the case
of the Decimal Currency example or they can be general as in the case of the 1973
35

example,
They

can

both

change

(amend

Parts,

Divisions and

Sections of ACTS

and

REGULATIONS) and/or delete (repeal) whole ACTS and REGULATION or Parts,
Divisions and Sections,

366274US

[N:\ L1BCCIO 1206 us. DO

c

IA D

US 6,233,592 Bl
75

76

-49-

St a t u t e Law Revision (Decimal Currency) Act 1966

I

Statute Law Revision Act 1973

There are other form of Amending ACT similar to the Statute Law Revision Acts as follows:

A.C.T.

Self-Government

(Consequential

Provisions)

Regulations

1989 NO.3
Defence Legislation Amendment Act 1984
10

Fringe Benefits Tax (Miscellaneous Provisions) Act 1986
Statute Law (Miscellaneous provisions) Act (No.1) 1986
Taxation Laws Amendment Act (No.3) 1986
The above can usually be spotted by the use of words such as "Consequential

15

Provisions" "Laws Amendment", "Legislation Amendment", "Miscellaneous Provisions" in
their Short Titles.

Repeal Acts

Below are two examples of these. One where the term Legislation is used in the title
20

indicating that more many ACTS are being repealed. Again this is often clean up
legislation which repeals many ACTS whose purpose or reason for being has lapsed.
Alternatively, as the second example indicates Repeal ACTS can be specific, effecting
the repeal of only one ACT.

25

Eg g Export Legislation Repeal Act 1984

I

National Welfare Fund Repeal Act
N= Not known

Indicates that the type of the ACT or REGULATION is not known or cannot be deterimined. These
30

records will the be handled in Australia.

[B 07] Reprint No Field

The information required for this field does not appear in the Commonwealth Data as presently
supplied to/held by us. It will need initially to be obtained in the form of a list of existing reprints and
35

their numbers and be added to both the Commonwealth data and the data base as a once only
job. It will then need to be maintained on a monthly basis using the two AGPS Pamphlet
Publications known as ACTS TABLES for Acts and STATUTORY RULES TABLES for
Regulations, the last page in each contains this information for the current year. Note: where the

366274US

IN: \L I Bee io 1 206U S. DOC: lAD

US 6,233,592 Bl
77

78

-50Pamphlets are not available or the reprint number is not known or unavailable then the number
999 should be used to indicate this.

Each of the two tables from the Pamphlets contains the name of the Reprinted ACT or
REGULATION in alphabetical order (but see Statutory Rules example below) followed by the date
of reprint, then followed by the words "Reprint No." and a number. It is this last number that needs
to be entered.

ACTS TABLE entry example
10

INational Health Act 1935 (20 September 1996) Reprint NO.5
STATUTORY RULES TABLE entry example
Note: Statutory Rules are listed by their parent Act (the Act under which the are made appearing
15

in Italic as shown in the example below).

Banks (Shareholdings) Act 1972--

I
20

Banks (Shareholdings) Regulations (2 August 1995) Reprint NO.2

[6 OBJReprint Date Field

Like the Reprint Number discussed in [6 07J above the information required for this field does not
appear in the Commonwealth Data as presently supplied to/held by us. It too will need initially to
be obtained in the form of a list of existing reprints and be added to both the Commonwealth data
and the data base as a once only job. It will then need to be maintained on a monthly basis using
25

the two AGPS Pamphlet Publications known as ACTS TABLES for ACTS and STATUTORY
RULES TABLES for Regulations, the last page in each contains this information for the current
year.

Each of the two tables contains the name of the Reprinted ACT or REGULATION in alphabetical
30

order (but see Statutory Rules example below) followed by the date of reprint, then followed by the
words "Reprint No." and a number.

For this field it is the Date preceding the Reprint Number that needs to be entered.
For examples see the examples at [6 07J above.
35

Note: Again where the Pamphlets are not available or the reprint date is not known or unavailable
then the date 00/00/00 should be used to indicate this.

366274US

[N: IlIBCC)O' 206US. 0 DC: I A D

US 6,233,592 Bl

80

79

-51-

[C] TEXTBLOCK TABLE
[C 01] When the should it be used?
TEXTBLOCK entries will not normally be required for ACTS or REGULATIONS which are either
Principal or Reprinted ACTS or REGULATIONS. But note that in the case of Principal ACTS there
are exceptions, namely; where the Principal ACT or REGULATION also amends or repeals other
ACTS or REGULATIONS.

[C 02]10 FIELD
10

This field simply repeats the information obtained in [6 01] above. Its purpose is to link this Table
with the MASTER TABLE by way of the same 10. For the example, in [B 01] for the Social
Security Act the 10 was Act-19910046. This 10 would be repeated in this field.

[C 03]Textblock 101
15

This field is for the 10 of the specific Part, Section or regulation in an Amending ACT or
REGULATION that causes a change (amendment) to happen.
Textblock 102 (see [C 04] below) on the other hand records the 10 of the specific Part, Section or
regulation in an Amending Act or Regulation that is changed (amended).

20

EXAMPLE 1
Following is an example of an amendment to the Social Security Act which shows how the
information required for this field is obtained.

25

Please note there are several ways in which Amending ACTS and REGULATIONS are presented.

However, the information required for this 10 field is present in all cases. This first example shows
the things to look for and the next example show some of the variations possible.

(N)

The first thing required is an indication as to type. The example is an Amending Act.

(0)

The second thing required is the relevant year. In the example this is ~.

(P)

The third thing required is the Act or Reg Number. In this example this is 104.

(Q)

30

The fourth thing required is the specific Part. Section or regulation doing the amending. In

this example this is SCH1 (ie: Schedule 1).

35

The 10 entry for this example would then be as follows:
ACT-19950104-SCH-1

I~OCIAL

366274US

SECURITY LEGISLATION (N)AMENDMENT I,CT

INa.

1)

(0)1995 No.

(P)104 of 1995

[N :\lIBCC JO 1206 US, DO C: I AD

US 6,233,592 Bl

82

81

-52-

(Q)SCHEDULE 1

Section 4<

AMENDMENT OF THE SOCIAL SECURITY ACT 1991 RELATING TO<
THE DEFINITION OF INCOME<
1. After Paragraph 8 (81 (zfl:<

Insert:<
II

(zfa)

a payment of financial supplement made to the person<

under the Student Financial Supplement Sc h erne

10

j

II

•

<

EXAMPLE 2
This example shows a different style of amendment to Example 1.
The 10 entry for this example would be as follows: ACT-19950105-SEC-4

It would be made up of the following:

(R)

Indication of Amending Act. (This would be Reg if we were dealing with a Regulation).

(5)

Year of Act is 1995.

(T)

Act or Reg Number is 105.

(U)

15

Specific Part, Section or regulation doing the amending is SEC4. Note: there is no

reference to a Schedule (SCH) because Section 4 is doing the amending.
20
SOCIAL SECURITY

(NON-BUDGET MEASURES)

LEGISLATION

(R)AMENDMENT ACT

(5}1995 No.

(T}105 of 1995

$$NSECT

25

(U)4.

Section 198 of the Principal Act is amended by inserting after subsection

(lA) :
$$P

n(lB) Subject to subsection (lC),
30

(a)

a

person

(the

I

carer ')

is

if:<
personally

providing

constant

care

for

a

severely handicapped person; and<
(bl

the handicapped person is temporarily absent from Australia for a period

of not more than 3 months; and<
(c)

35

the carer accompanies

the handicapped person on his or her absence

from

Australia;<
the carer does not cease to be qualified for a carer pension merely because of
that absence from Australia.
$$P

366274US

l N ;\LI BCC10 1206 US. DO C: lAD

US 6,233,592 Bl

83

84

-53-

11

(lC)

person

If,

during a

outside

calendar year,

Australia

on

more

the

than

carer has accompanied the
one

occasion,

qualified for carer pension under subsection (lB)
or she has,

during that calendar year,

the

carer

handicapped

ceases

to

be

in that calendar year after he

qualified for carer pension under that

subsection for periods that together add up to 3 months.

II.

$$A

[C 04]Textblock 102
10

This field is for the 10 of the specific Part, Section or regulation in an Amending ACT or
REGULATION that is changed (amended).

Textblock 101 (see IC 03] above) on the other hand records the 10 of the specific Part, Section or
regulation in an Amending ACT or REGULATION that causes a change (amendment) to happen.
15

EXAMPLE 1
Following is an example of an amendment to the Social Security Act which shows how the
information required for this field is obtained.

20

Please note, as with Textblock 101, there are several ways in which Amending ACTS and
REGULATIONS are presented. However, the information required for this 10 field is present in all
cases. This first example shows the things to look for and the next example shows some of the
variations possible.

25

(V)

Again the first thing is an indication as to type. The example is an Amending Act.

(W) The second thing required is the relevant year. In the example this is iaill..
(X)

The third thing required is the Act or Reg Number. In this example this is 46.

(Y)

The fourth thing required is the specific Part, Section or Regulation that is being amended.

In this example this is SEeS.
30

The 10 entry for this example would then be as follows:
ACT -1991 0046-SEC-8

SOCIAL SECURITY LEGISLATION AMENDMENT ACT (No.1) 1995 No. 104 of 1995 35
SCHEDULE 1

Section 4<
AMENDMENT OF THE SOCIAL SECURITY (V)ACT (W)1991

366274US

IN:\ II Bee 10 1 206U S. DOC: lAD

US 6,233,592 Bl

85

86

-54(X) [if not available/reproduced in the Amendment text can be obtained from the main ID field in
MASTER TABLE]
RELATING TO<
THE DEFINITION OF INCOME<
1. After Paragraph (Y)S (S) (zf) : <

Insert:.::

II

(zfa)

a payment of financial supplement made to the person<

under the Student Financial Supplement Schemeill.<
10

EXAMPLE 2
This example shows a different style of amendment to Example 1.
The ID entry for this example would be as follows: ACT-19950105-SEC-198

15

It would be made up of the following:

(Z)

Indication of Amending ACT. (This would be Reg if we were dealing with a REGULATION).

(AA) Year of ACT is 1991
(88) The third thing required is the ACT or REGULATION Number.
In this example this is 46.
20

(CC) Specific Part, Section or regulation being amended is SEC198.
SOCIAL SECURITY

(NON-BUDGET MEASURES) LEGISLATION AMENDMENT ACT 1995 No.

105 of

1995

(Z) (AA) (88)
25

[if not available/reproduced in the Amendment text can be obtained from the main

ID field in MASTER TABLE]
$$NSECT

4.

Section

subsection

(C:C)198

of

the

Principal

Act

is

amended

by

inserting

after

(lA):

$$P
30
11

(lB) Subject to subsection (Ie),

(a)

a

person

(the

'carer')

is

if:<

personally

providing

constant

care

for

a

severely handicapped person; and<
(bl
35

the handicapped person is temporarily absent from Australia for a period

of not more than 3 months; and<

(c)

the carer accompanies the handicapped person on his or her absence from

Australiai<

366274US

[N :\LI BCCIO 1 206US. DOC: IA D

US 6,233,592 Bl

87

88

-55the carer does not cease to be qualified for a

carer pension merely because of

that absence from Australia.

$$P

II

(IC)

person

If,

during a

outside

calendar year,

Australia

on

more

the

than

carer has accompanied the

one

occe s a on ,

the

carer

handicapped

ceases

to

be

qualified for carer pension under subsection (lB) in that calendar year after he
or she has,

during that

calendar year,

qualified for carer pension under that

subsection for periods that together add up to 3 months.".

10

$$A

[C 05]Oate of Commencement Field
This field is for the date an amendment or repeal of a specific Part, Section or regulation
commenced. See also [B 04] for information on commencement.
15

EXAMPLE
Below is an example of a commencement provision from an amending ACT. Note how various
sections of the amending ACT are allocated a date of commencement. Using the Section
identified in TEXTBLOCK 101 the date of commencement can be identified and entered in this
20

field.

Thus if the TEXTBLOCK ID1 field were ACT-19950105-SEC-8 then the date information required
for this field would be 1 July 1995. See (DO) below.

25

SOCIAL SECURITY (NON-BUDGET MEASURES) LEGISLATION AMENDMENT ACT 1995 No.

105 of

1995 - SECT 2<
Commencement<

$$T
30

$$NSECT
2. (1)

Subject

to

this

s ec t t on ,

this

Act

commences

on

the

day

on

which

it

receives the Royal Assent.

$$P
35
(2)

Subdivision A of Division 2 of Part 2 is taken to have commenced on 1 July

1993.

$$P

366274US

1N :\ll Bee ro 1 206US. DO C: lAD

US 6,233,592 Bl

89

90

-56-

(3)

Sections 8 and 9 are taken to have commenced on

(00)1

July 1995.

$$P

(4)

Section 10 is taken to have commenced on 1 April 1993.

$$p

[C 06] Date of Expiry Field
This field provides for amendments that are enacted for a period of time, for example; during a
10

special event such as the Olympics.

Note: Expiry provisions are rare and should only be added if clearly specified in the data as in the
example below.

15

EXAMPLE
See (EE) below.

OLYMPIC SECURITY (NON-BUDGET MEASURES) LEGISLATION AMENDMENT ACT 1997 No. 109 of
1995
20
$$NSECT
4.

Section

midnight

298

after subsection

25

of

the

Principal

Act

is

amended

on 1 July 1997 and ending on midnight

for

the

(EE)25

period

commencing at

July 1997 by inserting

(2A):

$$P

II

(2B)

(a)

Subject to subsection

a

person

(the

(2C)

'carer')

I

is

if; c

personally

providing

constant

care

for

a

severely handicapped personi and<
30

(b)

the handicapped person is temporarily absent from Australia for a

period

of not more than 3 months; and<
(c)

the carer accompanies the handicapped person on his or her absence

from

Australia;<
the carer does not cease to be qualified for a carer pension merely because of

35

that absence from Australia.
$$P

366274US

[N :\lIBCC 10 1206 US. DOC: I A D

US 6,233,592 Bl
92

91

-57II

(2C)

person

If,

during a

outside

calendar year,

Australia

on

more

the

than

carer has
one

accompanied the handicapped

occe s aon ,

the

carer

ceases

to

be

qualified for carer pension under subsection (lB) in that calendar year after he
or she has,

during that calendar year/

qualified for carer pension under that

subsection for periods that together add up to 3 months.

fl.

$$A

366274US

{N :\LI Bee 10 1 206US. DO c : IA D

US 6,233,592 Bl

93

94

-58AePENf)fX

D

Keying Guide for Australian
Legislation Documents
General

Validation
All files produced must be parsed against the relevant DTD and each table should be
viewed using a suitable Table renderer to make sure that they have been coded
10

correctly.

DTD modifications
No local modifications must be made to the supplied DTD's. If there are any situations in
which it is thought that a change to a DTD is required then the requested change and
the reasons for it must be submitted to SGMLSE. If a change is deemed necessary, then
15

the DTD will be changed in the UK and resupplied. This is necessary to maintain
consistency in the DTD's being used at both ends in the process.

Files
The SGML files that will be supplied have already been partially processed but will be
invalid according to the DTD (especially the tables).
20

Each file should omit the document type declaration and begin directly with the root
element.

Carriage return characters
Carriage return characters must not appear in any element which has #PCDATA within
its content model. If it is wished to use carriage return characters to shorten line lengths,
25

then they must be placed in positions where they will be ignored by an SGML parser e.g.
in places where #PCDATA is not allowed, or within start and end tags in places where
separator characters are allowed.
Case
Element and attribute names are case-insensitive. They may be entered in either

30

uppercase, lowercase or a mixture.
Attribute values are usually case-insensitive. The only time that they are case-sensitive
is when they have a declared type of CDATA, in which case the string values should be
entered directly as they appear in the text.

366274US

[N :\LI BCCjO 1 206US. DO C: r A D

US 6,233,592 Bl

95

96

-59Markup minimisation
No non-empty elements have omissible start or end tags, but the empty end tag

</ >

can

be used to end the currently open element. A carriage return character can not occur
within an empty end tag.

OTD structure
There are four DTDs and a common element declaration that are used to define the
structure of the legislation.

REGS.DTD
This DTD has the public identifier "-//SGMLSE//DTD 1.0 Regulations//EN" and contains
10

the declaration for the regulations. It has two parameter entity references which include
"-//SGMLSE//DTD 1.0 Act//EN" and "-//SGMLSE//DTD 1.0 Regulation//EN".
The file regs.sgm produced by the Perl script regs. pI conforms to regs.dtd and calls in all
acts as parameter entities.

ACTS.DTD
15

This DTD has the public identifier "-//SGMLSE//DTD 1.0 Acts//EN" and contains the
declaration for the acts. It has a parameter entity references which includes
"-//SGMLSE/IDTD 10 Act/lEN".
The file acts.sgm produced by the Perl script acts.pl conforms to acts.dtd and calls in all
acts as parameter entities.

20

ACT.DTD
This DTD has the public identifier "-//SGMLSE/IDTD 1.0 Act//EN" and contains the
declaration of an act.

REG.DTD
This DTD has the public identifier "-//SGMLSE//DTD 1.0 Regulation//EN" and contains
25

the declaration of a regulation.

COMMON.ELT
This list of elements has the public identifier "-//SGMLSE//ELEMENTS 1.0 Common
Elements//EN" and includes element and entity definitions common to all document
types.
30

Character entities
The character entities allowed have been selected from the ISO public sets isogrk1,
isogrk3, isolat1, isonum, isopub and isotech.

I

These characters are translated one-to-one to the equivalent character in the Times New

Roman True Typefont.

35

The <quote> or <blockquote> elements should be used instead to surround any quoted

text.

IUse Quotes (") at the beginning and at the end ofthese elements.

366274US

1N: \LI Bee JO 1 206 US. DOC: lAD

US 6,233,592 Bl

98

97

-60-

Labels and identifiers
The major structural elements - act, reg, part, schedule, section, sub, s-sub, ss-sub, ...
all have a required label attribute (Ibl). Unique identifiers should be generated for these
elements. The label for these elements is the preceding number or letter WITHOUT any
punctuation or parentheses. For example:
1979 No. 141 The charge to income tax - REG 1
Income Tax
1. Fred ...
10

1.(1)Thisis.
<section

type~"reg" lbl~"l"

ID~"CWACT-19790141-SEC-l">

<title>Income Tax<l>
<list>
-c Li,
15

Ibl~"l"><p>Fred

...<1>

<list>
<Ii

Ibl~"I"><p>This

is ...<1>

</list>
<IIi>
</list>
20

</section>

Convert list and li items back to the original look in Folio Views, ie to
1. Fred ...
1. (1) This is ...

Cross references
25

All cross references point directly to a target by providing the id of the target as the value
of an attribute of the xref element. For details of the format of cross reference identifier
strings, see the description of the xref element below.

All JD's are marked unchanged as Jump Destinations (.ID's).
<SECTION W="CWACT-19950104-SEC-1" LBL="l">
30

becomes:
<.JD:"

=

"CWACT-19950104-SEC-1 ">

REGS OTO ELEMENT
REGS
35

This is the root element of the Regulations. Its definition is :
<!ELEMENT

regs- -

(title, header?,

reg+)

>

That is, it contains a required title element, followed by an optional header element
followed by 1 or more act element.

366274US

IN: \1I BCCJO 1 206US. DO C: IA D

US 6,233,592 Bl
99

100

-61INot translated

ACTS DTD ELEMENT
ACTS
This is the root element of the Acts. Its definition is :
<!ELEMENT

acts - -

(title, header?, a ct r ) >

That is, it contains a required title element, followed by an optional header element
followed by 1 or more act element.

INot translated
10

REG DTD ELEMENTS
REG
This is the root element of the dtd for a Regulation. Its definition is :
<!ELEMENT reg

-

(title,

notes?,

provisions?,

(preamble I long-

title)?,
15

((order+1 (sectionl schedule) + Ichapter+ Ipart+) ,schedule*))>

<!ATTLIST

reg id ID #REQUIRED

CDATA

lbl
insert-date

NUMBER

repeal-date

NUMBER
NUMBER

amend-leg

#IMPLIED

#IMPLIED

IDREF

repeal-leg
amend-date

#IMPLIED

IDREF

insert-leg
20

#REQUIRED

#IMPLIED

#IMPLIED

IDREF

#IMPLIED

>
25

The insert-date attribute should be used to insert the date YYYYMMOO that the REG
was inserted. The insert-leg should be used to insert the 10 of the legislation that
inserted the REG.
The repeal-date attribute should be used to insert the date YYYYMMOO that the REG
was repealed. The repeal-leg should be used to insert the 10 of the legislation that

30

repealed the REG.
The amend-date attribute should be used to insert the date YYYYMMOO that the REG
was amended. The amend-leg should be used to insert the 10 of the legislation that
amended the REG.

The title gets marked up as Level "Heading Level I ". The period between the insert-date
35

and the repeal-date or amend-date (that is the period during which the above element
was in force) gets marked up as/allows:
The Folio Views markup used is Groups. See the manual for explanations. We will use
three kinds of groups: Inforce-yyyy, Inforce-yyyy-mm and Inforce-yyyy-mm-dd (yyyy can

366274US

IN :\LI Bee 10 1 206US. DO C: IA 0

US 6,233,592 Bl
101

102

-62be any year, mm can be any monthfrom I - 12 and dd can be any dayfrom I - 31).

If the

element was valid throughout a year yyyy, the element becomes a member of the Inforceyyyy group. If the element was valid only for some months within a year, it becomes a
member of the relevant Inforce-yyyy-mm groups.

if the element was only valid for some

days within a month, the element becomes a member of the relevant Inforce-yyyy-mm-dd
groups. Example:

If the element was validfrom 1/7/94 to 7/4/96, then the element belongs to the following
groups:
Inforce-v-t-Or. Inforce-v-t-Us, Inforce-94-09, Inforce-v-i-LO, Inforce-v-i-I I, Inforce-94-I2,
10

Inforce-vS, Inforce-96-0I, Inj(Jrce-96-02, Inforce-96-03, Inforce-96-04-0I, Inforce-96-0402, Injorce-96-04-03, Inforce-96-04-04, Inforce-96-04-05, Injorce-96-04-06 and Inforce96-04-07.
Note that the element is not part of the lnforce-v-t group because the element wasn't in
force throughout of 1994. Nor is the element part of the Injorce-96-04 group because the

15

element wasn't in force throughout April 1996.

If the enduser wants to search for all elements that are valid as ofa particular date then
the enduser can enter that date in a Query Template in the form DD/MM/YYYY. The
Query Template then searches the Folio Views infobase for all elements that belong to the
groups Inforce-yyyy, Inforce-yyyy-mm and Inforce-yyyy-mm-dd.
20

ACT DTD ELEMENTS
ACT
This is the root element of the dtd for an Act. Its definition is :
< ! ELEMENT
25

title)?,
<!ATTLIST

act

-

(title,

notes?,

provisions?,

(preamble I long-

(section+lchapter+lpart+lsub+)*, s chedu Lev )
act id ID #REQUIRED
date CDATA #IMPLIED
insert-date
insert-leg
repeal-date

30

repeal-leg
amend-date
amend-leg

NUMBER

#IMPLIED

IDREF
NUMBER

#IMPLIED

IDREF
NUMBER

#IMPLIED
#IMPLIED

#IMPLIED

IDREF

#IMPLIED

>
35

That is, it contains a required title element, followed by optional notes, provisions, and
preamble and either one or more reg, order, rule, section, chapter or part elements. It
has a required id attribute and implied date attribute

366274US

[N :\lIBC C 10 1206 US, DO C: lAD

US 6,233,592 Bl
104

103

-63The insert-date attribute should be used to insert the date YYYYMMDD that the ACT
was inserted. The insert-leg should be used to insert the ID of the legislation that
inserted the ACT.
The repeal-date attribute should be used to insert the date YYYYMMDD that the ACT
was repealed. The repeal-leg should be used to insert the 10 of the legislation that
repealed the ACT.
The amend-date attribute should be used to insert the date YYYYMMOO that the ACT
was amended. The amend-leg should be used to insert the 10 of the legislation that
amended the ACT.
10

Examples
1979 No. 141 The charge to income tax
<act lbl="141" ID="CWACT-19790141-TXT-O">
<title>1979 No. 141 The charge to income tax</>

1979 No. 141 The charge to income tax*1*
15

<act lbl="141" ID="CWACT-19790141-TXT-O">
<title>1979 No.

141 The charge to income t ax-cnot eref ref="CWACT-

19790141-note-1"></>

I

The noterefgets marked up as a popup link. The text ofthe note becomes the text within

the popup link.

20

ITreated the same as Reg DTD Elements. See therefor details.
COMMON ELEMENTS

PART
<!ELEMENT part - 25

(title,

(%plevel;)*,

(chapter+ldivision+lsection+)*, notes?)
<!ATTLIST

partid ID #REQUIRED
lbl CDATA #IMPLIED
insert-date

IDREF

#IMPLIED

repeal-date

30

NUMBER

insert-leg

#IMPLIED

NUMBER

#IMPLIED

repeal-leg

IDREF

#IMPLIED

amend-date

NUMBER

#IMPLIED

amend-leg

IDREF

#IMPLIED

>
35

The insert-date attribute should be used to insert the date YYYYMMOO that the PART
was inserted. The insert-leg should be used to insert the 10 of the legislation that
inserted the PART.

366274US

IN: \L I Be C]O 1 206U S. 0 OC: I AD

US 6,233,592 Bl
106

105

-64The repeal-date attribute should be used to insert the date YYYYMMOO that the PART
was repealed. The repeal-leg should be used to insert the 10 of the legislation that
repealed the PART.
The amend-date attribute should be used to insert the date YYYYMMOO that the PART
was amended. The amend-leg should be used to insert the 10 of the legislation that
amended the PART.
Example

<PART lbl="l" ID="CWACT-19790141-PT-l">
<title></title>
10

<r»

I

The title gets marked up as Level "Heading Level 2". Dales gel treated the same way as

in Regs DTD Elements. See therefor details.

ORDER
<!ELEMENT order - -

15

(title,

(divisionlsectionlpart I scheduleJ+)
< ! ATTLIST

order

>

id ID #REQUIRED

lbl CDATA #IMPLIED
insert-date

NUMBER

#IMPLIED

insert-leg

IDREF

#IMPLIED
#IMPLIED

repeal-date

NUMBER

repeal-leg

IDREF

#IMPLIED

amend-date

NUMBER

#IMPLIED

amend-leg

20

IDREF

#IMPLIED

>
25

The insert-date attribute should be used to insert the date YYYYMMDD that the ORDER
was inserted. The insert-leg should be used to insert the 10 of the legislation that
inserted the ORDER
The repeal-date attribute should be used to insert the date YYYYMMDD that the
ORDER was repealed. The repeal-leg should be used to insert the 10 of the legislation

30

that repealed the ORDER
The amend-date attribute should be used to insert the date YYYYMMOO that the
ORDER was amended. The amend-leg should be used to insert the 10 of the legislation
that amended the ORDER
Example

35

1979 No. 140 FEDERAL COURT RULES - ORDER 3<
ORDER 3<
TIME<

$$T

366274US

[N :\lIBC C 10 1206 us, DO C; I AD

US 6,233,592 Bl
107

108

-65$$A
$$T
1979 No. 140 FEDERAL COURT RULES - RULE 1<
<ORDER lbl="3" ID="CWACT-19790140-0RD-3">
<title>TIME</title>
<section type="rule" lbl="l" ID="CWACT-19790140-0RD-3.1">

I

The title gets marked up as Level "Heading Level 2 ". Dales get treated the same way as

in Regs DTD Elements. See therefor details.

DIVISION
<!ELEMENT

division - -

<!ATTLIST

10

division id ID #REQUIRED

(title,

(sub-division+

I section+) ) >

lbl CDATA #IMPLIED
insert-date

IDREF

#IMPLIED

repeal-date

NUMBER

#IMPLIED

repeal-leg

IDREF

#IMPLIED

amend-date

NUMBER

#IMPLIED

amend-leg

15

NUMBER

insert-leg

#IMPLIED

IDREF

#IMPLIED

>
20

The insert-date attribute should be used to insert the date YYYYMMDD that the
DIVISION was inserted. The insert-leg should be used to insert the 10 of the legislation
that inserted the DIVISION.
The repeal-date attribute should be used to insert the date YYYYMMDD that the
DIVISION was repealed. The repeal-leg should be used to insert the ID of the legislation

25

that repealed the DIVISION.
The amend-date attribute should be used to insert the date YYYYMMDD that the
DIVISION was amended. The amend-leg should be used to insert the ID of the
legislation that amended the DIVISION.
Example

30

1979 No. 140 FEDERAL COURT RULES - DIVISION 1<
Division 1-General<
$$T

$$A
$$T
35

1979 No. 140 FEDERAL COURT RULES - RULE 1<
Cases for service of originating process<
<DIVISION Ibl="1" ID="CWACT-19790140-DIV-1>
<title>General</title>

366274US

IN :\lIBCCjO 1206 US, DOC: lAD

US 6,233,592 Bl
110

109

-66<RULE Ibl="1" ID="CWACT-19790140-DIV-1.1">

<title> Cases for service of originating process </title>

I

The title gets marked up as Level "Heading Level 3". Dates get treated the same way as
in Regs DTD Elements. See there for details.

SUB-DIVISION
<!ELEMENT

sub-division

<!ATTLIST

sub-division id ID #REQUIRED

(title, section+)

>

lbl CDATA #IMPLIED
insert-date

NUMBER

insert-leg

IDREF

#IMPLIED

repeal-date

10

NUMBER

#IMPLIED

#IMPLIED

repeal-leg

#IMPLIED

NUMBER

#IMPLIED

amend-leg
15

IDREF

amend-date

IDREF

#IMPLIED

>

The insert-date attribute should be used to insert the date YYYYMMDD that the SUBDIVISION was inserted. The insert-leg should be used to insert the ID of the legislation
that inserted the SUB-DIVISION.
The repeal-date attribute should be used to insert the date YYYYMMDD that the SUB20

DIVISION was repealed. The repeal-leg should be used to insert the 10 of the legislation
that repealed the SUB-DIVISION.
The amend-date attribute should be used to insert the date YYYYMMDD that the SUBDIVISION was amended. The amend-leg should be used to insert the ID of the
legislation that amended the SUB-DIVISION.

25

The title gets marked up with a Paragraph Style (see Folio Views In/abase Production Kit
Manual jar details) 'Subdivision '. Dates get treated the same way as in Regs DTD
Elements. See there jar details.

PROVISIONS
<!ELEMENT
30

provisions

- -

(title, tblblk)

>

Example
$$NTABLE
TABLE

OF

PROVISIONS<

$$P
Order<
35

$$P
Preliminary<

1.

$$P
2.

Sittings and Vacation<

366274US

[N: \L I Be c ] 0 1206 US. DOC: I AD

US 6,233,592 Bl

111

112

-67 <PROVISIONS>
<TITLE>TABLE OF PROVISIONS>
<TBLBLK>
</TBLBLK>
</PROVISIONS>

Provisions get ignored. The Table of Provisions gets generated by the conversion
program from the following Elements: Part, Chapter, Order, Division, Subdivision and
Section. The generated Table of Provision is stored just before the first Part, Chapter,
10

Order, Division, Subdivision and Section.

CHAPTER
<!ELEMENT chapter - -

(title,

(%'plevel;)*,

(part+lsection+larticle+)?»
< !ATTLIST

chapter

id ID #REQUIRED

lbl CDATA # IMPLIED

15

insert-date

NUMBER

#IMPLIED

insert-leg

#IMPLIED

NUMBER

#IMPLIED

repeal-leg

IDREF

#IMPLIED

amend-date

NUMBER

#IMPLIED

amend-leg

20

IDREF

repeal-date

IDREF

#IMPLIED

>
The insert-date attribute should be used to insert the date YYYYMMOO that the
CHAPTER was inserted. The insert-leg should be used to insert the 10 of the legislation
25

that inserted the CHAPTER
The repeal-date attribute should be used to insert the date YYYYMMOO that the
CHAPTER was repealed. The repeal-leg should be used to insert the 10 of the
legislation that repealed the CHAPTER.
The amend-date attribute should be used to insert the date YYYYMMOO that the

30

CHAPTER was amended. The amend-leg should be used to insert the 10 of the
legislation that amended the CHAPTER.

The title gets marked up as Level ~'Heading Level 2 ". Dates get treated the same way as

I

in Regs DTD Elements. See there jor details.

35

SECTION
This is a sub element of a Regulation. Its definition is :
<!ELEMENT section - <!ATTLIST

366274US

section

(title,

(%unstruct-cont;))>

id ID #REQUIRED

r N: \LI Bee 10 1206U S. 0 DC: lAD

US 6,233,592 Bl
113

114

-68lbl CDATA #IMPLIED
insert-date

NUMBER

#IMPLIED

insert-leg

IDREF

#IMPLIED

repeal-date

NUMBER

#IMPLIED

repeal-leg

IDREF

#IMPLIED

amend-date

NUMBER

#IMPLIED

amend-leg

IDREF

#IMPLIED

>

That is, it contains a required title element, followed by unstructured content. It has a
10

required Ibl attribute and a required id attribute.
The insert-date attribute should be used to insert the date YYYYMMOO that the
SECTION was inserted. The insert-leg should be used to insert the 10 of the legislation
that inserted the SECTION.
The repeal-date attribute should be used to insert the date YYYYMMOD that the

15

SECTION was repealed, The repeal-leg should be used to insert the 10 of the legislation
that repealed the SECTION,
The amend-date attribute should be used to insert the date YYYYMMOO that the
SECTION was amended. The amend-leg should be used to insert the 10 of the
legislation that amended the SECTION,

20

Examples
1979 No. 141 The charge to income tax - SECT. 1
Income Tax
1979 No. 141 The charge to income tax - REG 2
Tax

25

3, Income tax shall be charqed.;
<section lbl="l" id="CWACT-1979141-SEC-l">
<title>Income tax</>
<section type="reg" lbl="2" id="CWACT-1979141-SEC1.2"><title>Tax</title>

30

<p>Income tax shall be charged ... </>

I

The title gets marked up as Level "Heading Level 4 ", Dates get treated the same way as

in Regs DTD Elements, See therefor details,

SCHEDULE
This is a sub element of a Regulation. Its definition is :

35

<!ELEMENT schedule
<!ATTLIST

(title?,

(%unstruct-cont;))>

schedule id ID #REQUIRED
lbl CDATA #IMPLIED
insert-date

366274US

NUMBER

#IMPLIED

IN:\LIBCCI01206US.OOC:IAD

US 6,233,592 Bl
115

116

-69insert-leg

IDREF

repeal-date

NUMBER

#IMPLIED

repeal-leg

IDREF

#IMPLIED

amend-date

NUMBER

#IMPLIED

amend-leg

IDREF

#IMPLIED

#IMPLIED

>

That is, it contains a required title element, followed by unstructured content. It has a
required Ibl attribute and a required id attribute.
The insert-date attribute should be used to insert the date YYYYMMDD that the
10

SCHEDULE was inserted. The insert-leg should be used to insert the 10 of the
legislation that inserted the SCHEDULE.
The repeal-date attribute should be used to insert the date YYYYMMDD that the
SCHEDULE was repealed. The repeal-leg should be used to insert the 10 of the
legislation that repealed the SCHEDULE.

15

The amend-date attribute should be used to insert the date YYYYMMDD that the
SCHEDULE was amended. The amend-leg should be used to insert the 10 of the
legislation that amended the SCHEDULE.
Examples
1979 No. 141 The charge to income tax - SCHEDULE 1

20

Income Tax
1. Income tax shall be charged ...
<schedule

lbl~"l"

id~"CWACT-1979141-SCH-l">

<title>Income tax</>
<p>Income tax shall be charged ... </>
25

The ti.tle gets marked up as Level"Headi~g Level 2". Dates get treated the same way as
in Regs DTD Elements. See therefor detazls.

I

FORM
<!ELEMENT

form- -

<!ATTLIST

form%reqlbl;

(title, formreg,

front, back?)

>

%reqid;>

30

Each form has a title, regulation, a front and an optional back. Each has a required Ibl
attribute and a required 10.
Example
FORM A<
Regulation 7<

35

(Front of Form)<
COMMONWEALTH OF AUSTRALlA<
Trade Practices Act 1974-Sub-section 88 (1)<

366274US

IN :\LI Bee JQ1 206US. DO C; IA D

US 6,233,592 Bl

117

118

-70EXCLUSIONARY PROVISIONS:<
APPLICATION FOR AUTHORIZATION<
To the Trade Practices Commission: Application is hereby made under sub-section 88
(1) of the Trade
(Back of Form)<
DIRECTIONS<
1. Where there is insufficient space on this form to furnish the required information, the
information is to be shown on separate sheets, numbered consecutively and signed by
or on behalf of the applicant.
10

<FORM Ibl="a" ID="CWACT-19790141-FORM-A">
<FORMREG>Regulation 7</FORMREG>
<FRONT>
<ASIS>
COMMONWEALTH OF AUSTRALlA<

Trade Practices Act 1974-Sub-section 88 (1)<

15

EXCLUSIONARY PROVISIONS:<
APPLICATION FOR AUTHORIZATION<
To the Trade Practices Commission: Application is hereby made under sub-section 88
(1) of the Trade
20

</ASIS>
</FRONT>
<BACK>
<ASIS>
DIRECTIONS<

25

1. Where there is insufficient space on this form to furnish the required information, the
information is to be shown on separate sheets, numbered consecutively and signed by
or on behalf of the applicant.
</ASIS>
</BACK>

30

</FORM>

Forms get marked up with a Paragraph Style 'Forms '. The markup of 'Front' and 'Back'
gets inserted as hidden text (hidden text is visible

011

the screen but doesn 't show when the

Form gets printed.

FORM ELEMENTS
35

FORM REG
<!ELEMENT

formreg

- -

(#PCDATA)

>

see above example

366274US

IN :\ll Bee 10'206 US. DOC: lAD

US 6,233,592 Bl
119

120

-71-

FRONT
<!ELEMENT

front

- -

(asis)

>

see above example

BACK
<!ELEMENT

back - -

(asis) >

see above example

ASIS
<!ELEMENT

asis - -

(#PCDATA) >

date is displayed as-is
10

see above example

HEADER ELEMENTS
HEADER
<!ELEMENT

header

(scope? , updated?) >

scope

(%text; ) >

SCOPE
15

<!ELEMENT

UPDATED
<!ELEMENT

updated

-

-

(%text; ) >

-

0

(not.e e )

NOTE ELEMENTS
NOTES
20

< ! ELEMENT

notes

>

List of notes at the start of an act

NOTE
< ! ELEMENT

note - -

(%plevel;) >

<!ATTLIST note id ID #REQUIRED>
25

A single note

Forms get marked up with a Paragraph Style 'Forms '. The markup of 'Front' and 'Back'
gets inserted as hidden text (hidden text is visible on the screen but doesn't show when the
Form gets printed.

STRUCTURAL ELEMENTS
30

TITLE
A generic title, which may occur in several different contexts.

ICovered in Acts DTD Elements, Regs DTD Elements and so on.
INLINE ELEMENTS
35

BOLD
Used to mark any inline text which is set in a bold face other than a title or a label. It may
contain text or any inline elements other than <bold>.
It has no attributes.

366274US

[N:\LIBCC 101 206US. DOC: lAD

US 6,233,592 Bl
121

122

-72-

ILEQN
An inline equation. This is a mathematical equation which is embedded in a line of text
characters or other inline elements. See the attached description of equations for further
details.

ITAL
Used to mark any inline text which is set in a italic face other than a title or a label. It
may contain text or any inline elements other than <italic>.
It has no attributes.

QUOTE
l o A sequence of text characters or inline elements surrounded by single or double paired
quotation marks. The quotation mark characters must not be entered as text characters
or entity references as they will be generated automatically.

SUSSCR
A Subscript (inferior).
15

SUPER
A superscript (superior).

IBrought over from SGML to Folio Views with no changes.
CROSS REFERENCES
NOTEREF
20

A reference to a NOTE element normally used in a TITLE element

IImplemented as a popup link.
TEMPREF

A reference to a piece of legislation where the 10 is not known. The tempref element will
converted to an XREF element at a later date (when the 10 is known).

25

INot converted.
RNGREF

A cross reference to a sequential range of targets, e.g. see Sections 3 to 7.
It has two required attributes, startref and endref. Startref is the id of the first of the
targets referenced and endref is the id of the last target referenced. For a description of
30

id strings, see the description of the xref element.

IConverted as a Query Link.
XREF

A cross reference to a single target. It has a single attribute, ref, which must contain the
id string of the target of the reference. Ids are not being entered on elements during
35

keying, but will be generated automatically from the Ibl attribute of elements. However,
for xrefs it is necessary to work out what the id string of the target will be. The format of
id strings is described below:

IConverted as a jumplink.
366274US

l N :\ll Bee] 0 1206 US, DO C: I A D

US 6,233,592 Bl
123

124

-73-

ID Strings
Cross references to sections of Acts and Act Schedules should be marked up using the
xref element as described above.
******************************************************

Id strings are made up of four sequential fields separated by a "-" (dash) character as
follows:
fieldl-field2-field3-field4

field 1 is the type of document which is being referenced. The current valid value is ACT.
field2 is an abbreviated form of the year and number of the Act, e.g. 19880001 is 1988
10

NO.1.

field3 identifies the type of object being referenced. Valid values are:
ORD
DIV

order
division

SCH schedule in an Act
15

SEC section in an Act
CH

chapter in an Act

PT

part in an Act

NOTE

a note

field4 is the identifier of the element being referenced, which is formed by concatenating
20

the values of the Ibl attributes of the referenced element and its ancestor elements,
separated by a "." (point) character. e.g. 1 or 1.1 or 1.1.a or 1.1.a.iv
Examples
csection Ibl="l">c!-- id is ACT-19790141-SEC-l -->
ctitle>The charge to income tax.c/>

25

clist>
eli Ibl="l">
cp>Income tax shall be charged ... c/>

IImplemented asjumpdestination.
30

BLOCK LEVEL ELEMENTS
DPEQN
A display equation. This is a mathematical equation which is set on one or more lines by
itself. See the attached description of equations for further details.
It has no attributes.

35

It has no attributes.

LIST
A list of related lines of text which are not sub, s-sub or ss-sub elements.

366274US

{N :\LIBCCI01206US .DOC: lAD

US 6,233,592 Bl

125

126

-74-

LI
An item in a list. This is a single line of text within a list.
It has a single attribute, marker, which has allowed values of bullet, dash or none, with a
default of none. If a marker character precedes the list item then the relevant value
should be entered for the attribute. The marker character should not be entered as text.
If any marker character other than a bullet or dash is found, contact SGMLSE for a
change to the DTD.

p
A single line of text.
10

BLOCKQUOTE
A non-inline quote. The quotation mark characters must not be entered as text
characters or entity references as they will be generated automatically

TBLBLK
A container element for a table which has a title. It contains a required title element
15

followed by a single table.
It has no attributes.

IThe above elements get implemented either without conversion or using paragraph styles.
TABLE ELEMENTS
General
20

Arbortext tables expressed in tagged ASCII form must follow this basic structure:
<table>
<rowrule>
for each row

25

« t ao Le row»

<cellrule>
for each column
<tablecell>text</tablecell>
<cellrule>

30

</tablerow>
<rowrule>

35

</table>

366274US

[N: III s c c I0 1206 us. DOC: lAD

US 6,233,592 Bl
127

128

-75-

TABLE
The <table> tag has three required attributes. They must be specified correctly or the
table will not be handled properly.
ncols=NUMBER The number of columns in the table. This value MUST agree with the
number of columns expressed by the required cwl attribute.
wdm=(251501751100)

The numbers indicate the width of the table as a percentage of

the page width.
cwl=L1ST

where LIST is a list of integers each separated by a colon. Each integer

represents the relative width of a column.
10

Example
A four column table which is the full width of the page. The second and third columns are
twice the width of the first column, and the fourth column is three times the width of the
first:

<table ncols="4" wdm="lOO" cwl="1:2:2:3">
15

or, equivalently,

<table ncols="4" wdm="lOO" cwl="5:10:10:15">

CELLRULE
Empty element. Specifies a vertical rule. It has a single attribute, rty, which specifies the
type of rule. Valid values for rty are:
(point)

20

for a blank rule,

" "(dash)

for a single rule,

"-,,

(equals)

for a double rule,

"+"

(plus)

for a bold rule.

Example
25

<cellrule rty=".">
for a blank rule, or

<cellrule rty="-">
for a single rule.

ROWRULE
30

Empty element. Specifies a sequence of horizontal rules, one per cell in the row. It has a
single attribute, rtl, which is a colon-delimited list of rule type specifiers. There must be
one rule type specifier for each cell in the row. The valid specifiers are as for cellrule
above.

Example
35

For a four-column table
<rowrule rtl=,r-:.:. :-">

would draw a horizontal rule above cells one and four.

366274US

[N:\.LIBCC 101 206US. DOC: lAD

US 6,233,592 Bl
129

130

-76-

TABLEROW
Specifies a row in the table. It has a single attribute, hdr, which specifies whether or not
the row is a header row in a table which will be repeated over page breaks. The only
valid value is "1" (one), which indicates that the row is a header row. An omitted value
for hdr indicates that the row is not a header row. A value is only valid on the first
<tablerow> in the table.
Example
<tablerow hdr="l">

indicates that the row is a header row (iff the <tablerow> is the first in the table, else it
10

will generate an error).
<tablerow>

indicates that the row is not a header row if the <tablerow> is the first in the table.

TABLECELL
Indicates a cell in a row in a table. It has four optional attributes:
15

chj = (b III ric)

Horizontal justification for that cell.

b
1

for flush left,

r

for flush right,

c
20

for both right and left justified,

for centred.

Default: left justified
cvj = (t I c I b)

Vertical justification for that cell.

t

25

for top justified,

c

for centred, or

b

for bottom justified.

Default: top justified
spn=INTEGER
For horizontally

spanned

columns.

VAL

is a whole

number

representing how many columns are spanned. Note that for horizontal spans, the text
appears in the LEFTMOST cell in the span, and all other cells in the span should be void
30

of text.
Default: 1
vspn=INTEGER

For vertically spanned rows. VAL is a whole number representing how

many rows are spanned. Note that for vertical spans, the text appears in the LOWEST
cell in the span, and all other cells in the span should be void of text.
35

Default: 1

Arbortext table example
Ifoo

366274US

fum

! N: \L I Bee 10 1 206US. DO C; I AD

US 6,233,592 Bl
131

132

-77feel
spanned

ugh

<tbl>
<table wdm="1 00" cwl="3:4:3">
<rowrule rtl="-:-:-">
<tablerow hdr="1 ">
10

<cellrule rty="-">
<tablecell>foo</tablecell>
<cellrule rty="-">
<tablecell chj="c">fum</tablecell>
<cellrule rty="-">

15

<tablecell chj="r" cvj="b">fee</tablecell>
<cellrule rty="-">
</tablerow>
<rowrule rtl="-:-:-">
<tablerow>

20

<cellrule rty="-">
<tablecell spn="2" chj="c">spanned</tablecell>
<cellrule rty="-">
<tablecell chj="c">ugh</tablecell>
<cellrule rty="-">

25

</tablerow>
<rowrule rtl="-:-:-">
</table>
</tbl>

30

ITables get converted to Microsoft Word tables and then converted into Folio Views.
EQUATION ELEMENTS
General
This maths DTD is a subset of the Arbortext maths DTD, which itself is derived from the
AAP maths DTD.

35

In maths mode, all spaces are ignored (except in a <phr> element as described below).
Correct spacing is handled automatically.
All alphabetical characters and symbols are treated as variables and set in italic face,
unless they occur within <phr>, <rm> or <rf> elements.

366274US

{N :\ll Bee 10 1 206U S. DOC: lAD

US 6,233,592 Bl
134

133

-78All numeric characters and operators are set in roman face, unless they occur within an
<it> element.
Greek symbols should be entered using the <g> element rather than entity references.
E.g. <g>a</g> produces alpha, <g>b</g> beta, etc. Any entity references for Greek
characters which appear in equations will be flagged as errors by the parsing program.

B
Bold text in an equation.

DE
Denominator of a fraction.
10

F
Inline equation.

FD
Display equation.

FEN
15

Fence. A pair of bracketed delimiters. The attribute Ip (left post) defines the type of the
left delimiter as below, and the following element rp (right post) defines the type of the
right delimiter.

<!ATTLIST fen

lp

(parjsqblcublangjvb)

par

left square bracket

vb

(

sqb

20

left parenthesis

[

cub

left curly brace

{

ang

left angle bracket

<

vb

left vertical bar

-->
25

FR
Fraction.

G
Greek character or characters. Valid characters are:
char

equivalent entity

a

alpha

b

30

beta

c

delta

D

Delta

e

epsilon

3

epsiv

4

35

chi

d

phiv

f

366274US

phis

(N: \.L IBeC] 0'206 US. DOC: lAD

US 6,233,592 Bl
136

135

-79F

Phi

g

gamma

G

Gamma

h

eta
iota

j

thetav

k

kappa

I

lambda

L

Lambda

m

mu

n

nu

p

10

pi

2

piv

P

Pi

q

thetas

Q

Theta

s

15

sigma

rho

S

Sigma

9

rhov

t

tau

u

20

upsilon

U

Upsilon

v

sigmav

w

Omega

x

xi

X

Xi

Y
y

psi

z

30

omega

W

25

zeta

Psi

INF
Inferior. Subscript in an equation.

IT
35

Italic text in an equation.

NU
Numerator of a fraction.

366274US

IN: \LJ B CC)O 1 20BUS. DOC: I A 0

US 6,233,592 Bl
138

137

-80-

OVL
Overline.

PHR
Phrase. In a phrase all characters are set in roman face and keyed space characters are
preserved. A phrase is essentially a temporary escape out of maths mode back into
normal text mode.

RAD
Radical or root. Contains a radicand (xrcd»), which is the constructs which appear
beneath the top horizontal bar, and an optional radix (rdx), which is the power of the root
10

(e.g. square, cube, 4, etc.).

ReD
Radicand, The content of a root construct.

RDX
Radix. The power of a root.
15

RF
Roman Function. A function name set in roman face, such as log, sin, cos, lim, arg, etc.
It differs from the <rm> element in that preceding and following space characters are
generated to separate it from surrounding characters.

RM
20

Roman face. Used to force an alpha character to be displayed in normal face rather than
be treated as a variable and displayed in italic face.

RP
Right delimiter of a fence. It has a single attribute, post, which defines the type of the
delimiter. Valid values are the same as for the Ip attribute of the <fen> element, except
25

that they specify the right hand match for the relevant left post.

SUP
Superior, A superscript in an equation,

UNL
Underline.
30

Arbortext equation examples
... by multiplying by the fraction -

6
B

where 35

<P> ... by multiplying by the fraction -<I>
<dpeqn><fr><nu><rm>A</></><de><rm>B</></></></>
<p>where -</P>

366274US

IN: \ LI BCCjO 1 206US. DO C: I A D

US 6,233,592 Bl
140

139

-81by the formula gross taxable income
net assets

<p> ... by the formula -<I>
<dpeqn><fr><nu><phr>gross taxable income</></><de><phr>net
assets</></></></>

Equations get converted to Microsoft Word equations and then converted into Folio
Views. Alternatively equations get converted to images and added to Folio Views as
10

images.

366274US

[N :\lIBCC JO1206 US, DO C: IA D

US 6,233,592 Bl
141

142

-82... ~)lC

APPENDIX E

<!SGML "ISO 8879:1986"
ArborText's default SGML declaration, modified to allow
longer id/idref's, and to use a number of special characters
within them.

10

15

20

25

30

35

CHARSET
BASESET "ISO 646-198311CHARSET
International Reference Version (IRV)IIESC 2/54/0"
DESCSET
o 9 UNUSED
929
11
2 UNUSED
13
1 13
14
18 UNUSED
32
95 32
127 1 UNUSED
128 128 "High-order characters"
CAPACITY SGMLREF
TOTALCAP
ENTCAP
ENTCHCAP
ELEMCAP
GRPCAP
EXGRPCAP
EXNMCAP
ATTCAP
ATTCHCAP
AVGRPCAP
NOTCAP
NOTCH CAP
IDCAP
IDREFCAP
MAPCAP
LKSETCAP
LKNMCAP

200000
35000
35000
35000
150000
35000
35000
50000
35000
35000
35000
35000
35000
35000
35000
35000
35000

40

SCOPE

45

DOCUMENT

SYNTAX
SHUNCHAR 012345678910 11 1213 1415 1617
18 192021 22232425262728293031 127
BASESET "ISO 646-19831ICHARSET
International Reference Version (IRV)IIESC 2/5 4/0"
DESCSET 0
128 0

366274US

fN :\LI Bee 10 1206 US. DO C: lAD

US 6,233,592 Bl
143

144

-83-

10

15

20

25

30

35

40

128 128 "High-order characters"
FUNCTION RE 13
RS 10
SPACE 32
TAB SEPCHAR 9
NAMING LCNMSTRT ""
UCNMSTRT ""
LCNMCHAR "-.l[]"
UCNMCHAR "-.l[] "
NAMECASE GENERAL YES
ENTITY NO
DELIM
GENERAL SGMLREF
SHORTREF SGMLREF
SGMLREF
NAMES
QUANTITY SGMLREF
ATTCNT
100
ATTSPLEN
960
960
BSEQLEN
DTAGLEN
16
16
DTEMPLEN
ENTLVL
16
GRPCNT
100
96
GRPGTCNT
GRPLVL
16
800
LITLEN
64
NAMELEN
NORMSEP
2
1024
PILEN
960
TAGLEN
24
TAGLVL
FEATURES
MINIMIZE DATATAG NO
OMITTAG YES
RANK
NO
YES
LINK
SIMPLE NO
IMPLICIT NO
EXPLICIT NO
OTHER CONCUR NO
SUBDOC NO
FORMAL YES
APPINFO NONE>

SHORTTAG

< iDOCTYPE legislation
[

< !-DTD for ScantextlAbha Legislation - (C) Turn-Key Systems 1997
45

History:
1997-10-13: fix hist at beginning of regs

366274US

[N:\LIBCC 101 206US. DOC: lAD

US 6,233,592 Bl
145

146

-841997-10-07: restore < target> tag
1997-10-02: enhanced support for regulations (hist, unconv etc)

-->
< !-- useful characters such as &mdash; -- >
< !ENTITY % ISOpub public "ISO 8879-1986//ENTITIES Publishing//EN" >
%ISOpub;
10

< !-- PARAMETER ENTITIES USED TO SIMPLIFY DTD MARKUP -->
< !entity % major

15

"schedule Iintcon Iarticle Iannex Iclause Ichapter Ipart Idivision Isubdivn Isection Isubsec I
reg Isubreg"
-- major levels -- >

< !entity % minor" defn Ipara Isubpar 11 subparz ]subpar.I] subpara ]point"
-- minor levels -- >
20

< !entity % secreg "section I reg"
-- used where either sections or regs are appropriate -- >

< !entity % level "%major; I %minor;"
-- all levels -- >
25

< !entity % refs "term II. ref Ih.ref"
-- references which can be found in normal text -- >

< !entity % raw "(rawtext Irawtable Iunconverted) *"
30

--

material such as forms which remains as raw text -- >

< !entity % effect "sc"
-- typographical effects (more to be added later) -- >
35

< !entity % text "(%refs; I %effect; I#PCDATA)*"
-- normal text (including refs defined above) -- >

< !entity % hnote "hist I note"
-- hist and note are temporarily interchangeable -- >
40

< !entity % body "(p + Irepealed), (%hnote;)*"
-- body of a legislative element -- >

< !entity % lev.id "((label, desc?) I (desc, label?»"
45

--

reversible level id -- >

< !-- MASTER ELEMENT -- >

366274US

j

N :\LI Bee 10' 206US. DO C: IA D

US 6,233,592 Bl
147

148

-85-

< 'element legislation - - (act I regulations) +
-- Acts and Regs are currently supported -- >

< '-- DEFINITIONS OF ACTS AND CONSTITUENT ELEMENTS -- >
< !element act
- - (desc, (%hnote; I %raw;)*.

10

longtitle, preamble?
(chapter+ I part+ I section+),
schedule *, hist*) >
< !element longtitle - - (#PCDATA)>
< !element preamble - - (p+) + (para) >

< !element regulations - - (desc, (%hnote;
(chapter+ I part+ I reg+),

%raw;)*,

schedule *, hist*) >

15

< !-- MAJOR LEVELS -->
< !element chapter - - (label, desc, (%hnote;)*,
20

25

30

35

I article + »)>
«(%secreg;)*, part*)
- - (label?, desc, hist*,
«(%secreg;)*, division*) I (article+ I clause-t-Il)
< !element division - - (label", desc, (p I %hnote;)*,
«(%secreg;)*, subdivn*) I clause + )) >
< !element subdivn - - (label?, desc, (%hnote;)*,
«%secreg;)+ I clause + » >
< !element section - - (%lev.id;,
«subsec + , (modules I module + )'1) I repealed» >
< !element subsec - - (%lev.id;,
«p, (p I note)*, hist*) I (repealed, note*, hist*») >
< !element modules - - (%lev.id;,
module+)>
< !element module - - (%lev.id;.
(submod + I repealed» >
< !element submod - - (%lev.id;,
(tp, (p I %hnote; I method I tabloid)*) I (repealed, (%hnote;)*))) >
< !element reg
- - (label?, desc, hist?
(subreg + I repealed» >
< !element subreg - - (label, desc?, hist?,
(tp, (p I note)*, hist*) I (repealed, note.", hist*»)>

< !element part

40

< !-- SCHEDULES, CONVENTIONS etc -- >
< !element schedule - - (label?, desc?, hist*,

45

(chapter + I part + I section + I item + I p + I tabloid +
%raw;) >
< !element intcon - - (desc, preamble,
(part+ I division+ I subdivn+ I article+), annex*)>
< !element annex - - (label", desc, p*,
(part* I division* I clause* I para") >

366274US

I intcon)?,

IN: \ L I ec c I 0 1 ZOBUS. DOC: I AD

US 6,233,592 Bl
149

150

-86-

< !element article - - (label, dcsc, p*,
(division*

I clause* I para")

>

< !element clause - - «((label, desc?) I (desc, label», p+) >
< !element item - - (label?, desc?, %body;) >

10

15

20

< !-- DEFINITIONS AND MINOR LEVELS -- >
< !element defn - - (%body;»
< !element note - - (label?. p +) >
< !element hist - - (label", (p+ I %raw;»>
< !element point - - (p + ) >
< 'element para - - (label", %body;) >
< !element subpar! - - (label?, %body;»
< !element subpar2 - - (label?, %body;»
< !element subpar3 - - (label?, %body;»
< !element subpar4 - - (label?, %body;»

< !element method - - (%lev.id;, (p I %hnote; I step) + ) >
< !element step - - (label, %body;) >
< r., COMMON CONSTITUENT ELEMENTS -- >
< !element label - - (%text;)

25

chapter number, section number, etc. -- >
- - (%text;)
-- chapter name, section name, etc. -- >
< !element term - - (%text;)
-- defined term -- >
< !element repealed - 0 EMPTY
-- indicates that the enclosing level has been repealed -- >
< !element p
- - (%minorl %refs; I %effect I tabloid Iamend I target I#PCDATA)*
-- textual paragraph at any level -- >
--

< 'element desc

30

35

< !-- UNCONVERTED MATERIAL -- >
< !element unconverted - - CDATA
-- yet to be converted (eg. complex schedules) -- >
- - CDATA
-- unconverted text (eg. forms) -- >
< !element rawtable - - CDATA
-- unconverted tables (eg. amended provisions) -- >

< !element rawtext
40

45

< 1_- CROSS-REFERENCES -->
< !element I.ref - - (%text;) -- legislation ref -- >
< !element h.ref

366274US

- - (%text;)

-- history ref -->

r N :\L I sc c J 0 1 2D6U S. 0 DC:

lAD

US 6,233,592 Bl
151

152

-87 -

< !-- AMENDMENT MARKUP -->
< !element amend - - (%refs I %effect Iquote I#PCDATA)*
-- amendment = action + text -- >
< !element target - - (#PCDATA)
-- target of amendment -- >
- - (label Idesc Ip I %levell %refs I %effect I#PCDATA)*
-- quoted material -- >

< !element quote

10

< !-- PSEUDO-TABLES -->
< 'element tabloid - - (label?, desc?, (head I row)+»
< !element head - - (cell +) >
< !element row - - (cell +) >
< !element cell - - (#PCDATAlp)*>

15

< !-- EFFECTS -->
< !element sc
- - (#PCDATA) -- small caps -- >
20

< !-- ATTRIBUTE LISTS -->
< !attlist act
juris (cth Insw Ivic Iqld Isa Iwa Itas Iact Int limp)

25

< !attlist
30

35

< !attlist
40

< !attlist
< !attlist
< !attlist

45

< !attlist

< !attlist

366274US

#REQUIRED -- jurisdiction
year CDATA #REQUIRED -- year assented
number CDATA #REQUIRED -- act number
reps CDATA #IMPLIED -- 2nd reading (RR) -senate CDATA #IMPLIED -- 2nd reading (Sen)-assent CDATA #IMPLIED -- assent date
cdate CDAT A #IMPLIED -- commencement
-- >
regulations juris (cth Insw Ivic Iqld Isa Iwa Itas Iact Int limp)
#REQUIRED -- jurisdiction
year CDATA #REQUIRED -- year assented
number CDATA #REQUIRED -- act number
reps CDATA #IMPLIED -- 2nd reading (RR)
senate CDAT A #IMPLIED -- 2nd reading (Sen) -notified CDATA #IMPLIED -- notification date --- >
cdate CDAT A #IMPLIED -- commencement
schedule id
ID
#IMPLIED -- legislation id
cdate CDATA #IMPLIED -- commencement
refsec CDAT A #IMPLIED -- referring section -- >
chapter id
ID
#IMPLIED -- legislation id
cdate CDATA #IMPLIED -- commencement
-->
part
id
ID
#IMPLIED -- legislation id
-->
cdate CDATA #IMPLIED -- commencement
division id
ID
#IMPLIED -- legislation id
cdate CDATA #IMPLIED -- commencement
-->
subdivn id
ID
#IMPLIED -- legislation id
cdate CDAT A #IMPLIED -- commencement
-- >
section id
ID
#IMPLIED -- legislation id

[N: 'ILl Be C)O 1 206U s. DOC; I A D

US 6,233,592 Bl
153

154

-88cdate CDATA #IMPLIED -- commencement
-- >
ID
#IMPLIED -- legislation id
cdate CDATA #IMPLIED -- commencement
-- >
reg
id
ID
#IMPLIED -- legislation id
-->
cdate CDATA #IMPLIED -- commencement
subreg id
ID
#IMPLIED -- legislation id
cdate CDAT A #IMPLIED -- commencement
-- >
l.ref ref IDREF #IMPLIED -- legislation idref -- >
term
id
ID
#IMPLIED -- term id
-- >

< !attlist subsec id
< !attlist

< !attiist
< !attiist
< !attiist
10

]>

366274US

(N: \LI

ac c 10 1 206US. DOC: IA

D

US 6,233,592 Bl

155

156

We claim:
1. A computer-implemented system for publishing an
electronic publication using text-based data, comprising:
a plurality of predefined portions of text-based data with
each predefined portion being stored;
at least one predefined portion being modified and stored;
a plurality of linking means of a markup language, each
predefined portion of said text-based data and said at
least one modified predefined portion of text-based data
being encoded with at least one linking means; and
a plurality of attributes, each attribute being a point on an
axis of a multidimensional space for organising said
plurality of predefined portions and said at least one
modified predefined portion of said text-based data.
2. The system according to claim 1, comprising means for
searching within the system.
3. The system according to claim 2, wherein said searching means uses one or more attributes.
4. The system according to claim 2, wherein said searching means uses any predefined portion, any modification of
a predefined portion, or any word or phrase within such
predefined portion or such modification.
5. The system according to claim 1, further comprising
means for searching at least one of said text-based predefined portions of said data using said plurality of
attributes, wherein said plurality of attributes are coupled to
each of said predefined portions by said respective linking
means, and for retrieving one or more of said predefined
portions using said plurality of attributes to define a point in
said multidimensional space.
6. The system according to claim 1, wherein said markup
language is Standard Generalised Markup Language
(SGML) or eXtensible Markup Language (XML).
7. The system according to claim 6, wherein said textbased data is encoded using one or more Document Type
Definitions (DTD) or Style Sheet Mechanisms (SSM).
8. The system according to claim 1, wherein said linking
means comprises any piece of information additional to the
body of the text-based data.
9. The system according to claim 8, wherein said linking
means is a code or markup that allows departure and
destination points to be created between portions of said
text-based data.
10. The system according to claim 1, wherein said at least
one linking means comprises an identification code for said
respective predefined portion.
11. The system according to claim 1, wherein a first
database comprises said plurality of predefined portions of
text-based data.
12. The system according to claim 11, wherein a second
database comprises said plurality of attributes for managing
said first database.
13. The system according to claim 1, wherein said predefined portions are encoded with one or more attributes.
14. The system according to claim 1, wherein said respective predefined portion is changed by performing one of the
group consisting of adding at least one attribute to said
respective predefined portion, deleting at least one attribute
from said respective predefined portion, and modifying at
least one of the attributes of said respective predefined
portion.
15. The system according to claim 1, wherein said respective predefined portion is changed by performing one of the
group consisting of adding data to said respective predefined
portion, deleting data from said respective predefined
portion, and modifying data of said respective predefined
portion.

16. The system according to claim 1, wherein said textbased data comprises legislation.
17. The system according to claim 16, wherein each of
said plurality of predefined portions of said text-based data
is a respective provision of said legislation.
18. The system according to claim 17, wherein said
provision is a section or schedule of an Act, or a regulation
or schedule of a Regulation(s).
19. The system according to claim 1, wherein each
predefined portion is a block of said text-based data, said
block being larger than a single word and less than an entire
document of said text-based data.
20. A computer readable recording medium for publishing
an electronic publication using text-based data, comprising:
a plurality of predefined portions of text-based data with
each predefined portion being stored;
at least one predefined portion being modified and stored;
and
a plurality of linking means of a markup language, each
predefined portion of said text-based data and said at
least one modified predefined portion of text-based data
being encoded with at least one linking means; and
a plurality of attributes, each attribute being a point on an
axis of a multidimensional space for organising said
plurality of predefined portions and said at least one
modified predefined portion of said text-based data.
21. The recording medium according to claim 20, wherein
means for searching can be used to search the recording
medium.
22. The recording medium according to claim 21, wherein
said searching means uses one or more attributes.
23. The recording medium according to claim 21, wherein
said searching means uses any predefined portion, any
modification of a predefined portion, or any word or phrase
within such predefined portion or such modification.
24. The recording medium according to claim 20, further
comprising means for searching at least one of said predefined portions of said text-based data uses said plurality of
attributes, wherein said plurality of attributes are coupled to
each of said predefined portions by said respective linking
means, and for retrieving one or more of said predefined
portions using said plurality of attributes to define a point in
said multidimensional space.
25. The recording medium according to claim 20, wherein
said markup language is Standard Generalised Markup
Language (SGML) or eXtensible Markup Language (XML).
26. The recording medium according to claim 25, wherein
said text-based data is encoded using one or more Document
Type Definitions (DTD) or Style Sheet Mechanisms (SSM).
27. The recording medium according to claim 20, wherein
said linking means comprises any piece of information
additional to the body of the text-based data.
28. The recording medium according to claim 27, wherein
said linking means is a code or markup that allows departure
and destination points to be created between portions of said
text-based data.
29. The recording medium according to claim 20, wherein
said at least one linking means comprises an identification
code for said respective predefined portion.
30. The recording medium according to claim 20, wherein
a first database comprises said plurality of predefined portions of said text-based data.
31. The recording medium according to claim 30, wherein
a second database comprises said plurality of attributes for
managing said first database.
32. The recording medium according to claim 20, wherein
said predefined portions are encoded with one or more
attributes.

5

10

15

20

25

30

35

40

45

50

55

60

65

US 6,233,592 Bl
157

158

said predefined portions by said respective linking means,
33. The recording medium according to claim 20, wherein
said respective predefined portion is changed by performing
and for retrieving one or more of said predefined portions
one of the group consisting of adding at least one attribute
using said plurality of attributes to define a point in said
to said respective predefined portion, deleting at least one
multidimensional space.
attribute from said respective predefined portion, and modi- 5
45. The method according to claim 40, wherein said
fying at least one of the attributes of said respective premarkup language is Standard Generalised Markup Language
defined portion.
(SGML) or eXtensible Markup Language (XML).
34. The recording medium according to claim 20, wherein
46. The method according to claim 45, wherein said
said respective predefined portion is changed by performing
text-based data is encoded using one or more Document
one of the group consisting of adding data to said respective
10 Type Definitions (DTD) or Style Sheet Mechanisms (SSM).
predefined portion, deleting data from said respective pre47. The method according to claim 40, wherein said
defined portion, and modifying data of said respective
linking means comprises any piece of information additional
predefined portion.
to the body of the text-based data.
35. The recording medium according to claim 20, wherein
48. The method according to claim 47 wherein said
15
said text-based data comprises legislation.
linking means is a code or markup that allows departure and
36. The recording medium according to claim 35, wherein
destination points to be created between portions of said
each of said plurality of predefined portions of said texttext-based data.
based data is a respective provision of said legislation.
49. The method according to claim 40, wherein said at
37. The recording medium according to claim 36, wherein
said provision is a section or schedule of an Act, or a 20 least one linking means comprises an identification code for
said respective predefined portion.
regulation or schedule of a Regulation(s).
50. The method according to claim 40, wherein a first
38. The recording medium according to claim 20, wherein
database comprises said plurality of predefined portions of
said recording medium is made from one of the group
said text-based data.
consisting of magnetic media, optical media, and magneto51. The method according to claim 50, wherein a second
25
optical media.
database comprises said plurality of attributes for managing
39. The recording medium according to claim 20, wherein
said first database.
each predefined portion is a block of said text-based data,
52. The method according to claim 40, wherein said
said block being larger than a single word and less than an
predefined portions are encoded with one or more attributes.
entire document of said text-based data.
53. The method according to claim 40, wherein said
40. A computer-implemented method for publishing an 30
respective predefined portion is changed by performing one
electronic publication using text-based data, comprising the
of the group consisting of adding at least one attribute to said
steps of:
respective predefined portion, deleting at least one attribute
providing a plurality of predefined portions of text-based
from said respective predefined portion, and modifying at
data with each predefined portion being stored;
35 least one of the attributes of said respective predefined
encoding each predefined portion of said text-based data
portion.
with at least one linking means of a markup language;
54. The method according to claim 40, wherein said
providing at least one predefined portion being modified
respective predefined portion is changed by performing one
and stored;
of the group consisting of adding data to said respective
providing a plurality of attributes, each attribute being a 40 predefined portion, deleting data from said respective predefined portion, and modifying data of said respective
point on an axis of a multidimensional space for
predefined portion.
organising said plurality of predefined portions and said
55. The method according to claim 40, wherein said
at least one modified predefined portion of said texttext-based data comprises legislation.
based data.
56. The method according to claim 55, wherein each of
41. The method according to claim 40, comprising the 45
step of searching said text-based data.
said plurality of predefined portions of text-based data is a
42. The method according to claim 41, wherein said
respective provision of said legislation.
searching step uses one or more attributes.
57. The method according to claim 56, wherein said
43. The method according to claim 41, wherein said
provision is a section or schedule of an Act, or a regulation
searching step uses any predefined portion, any modification 50 or schedule of a Regulation(s).
58. The method according to claim 40, wherein each
of a predefined portion, or any word or phrase within such
predefined portion is a block of said text-based data, said
predefined portion or such modification.
block being larger than a single word and less than an entire
44. The method according to claim 40, further comprising
document of said text-based data.
the step of searching at least one of said predefined portions
of said text-based data using said plurality of attributes,
wherein said plurality of attributes are coupled to each of
* * * * *