7272
7373Example CAS XMI and types system files can be found under :code: `tests\t est_files `.
7474
75- .. _reading_a_cas_file :
76-
7775Reading a CAS file
7876~~~~~~~~~~~~~~~~~~
7977
@@ -100,8 +98,6 @@ Most UIMA JSON CAS files come with an embedded typesystem, so it is not necessar
10098 with open (' cas.json' , ' rb' ) as f:
10199 cas = load_cas_from_json(f)
102100
103- .. _writing_a_cas_file :
104-
105101 Writing a CAS file
106102~~~~~~~~~~~~~~~~~~
107103
@@ -130,16 +126,14 @@ returned as a string using :code:`cas.to_xmi()`.
130126 # Written to file
131127 cas.to_json(" my_cas.json" )
132128
133- .. _creating_a_cas :
134-
135129 Creating a CAS
136130~~~~~~~~~~~~~~
137131
138132A CAS (Common Analysis System) object typically represents a (text) document. When using cassis,
139- you will likely most often :ref: ` reading < reading_a_cas_file >` existing CAS files, modify them and then
140- :ref: ` writing < writing_a_cas_file >` them out again. But you can also create CAS objects from scratch,
133+ you will likely most often reading existing CAS files, modify them and then
134+ writing them out again. But you can also create CAS objects from scratch,
141135e.g. if you want to convert some data into a CAS object in order to create a pre-annotated text.
142- If you do not have a pre-defined typesystem to work with, you will have to :ref: ` define one < creating_a_typesystem >` .
136+ If you do not have a pre-defined typesystem to work with, you will have to define one.
143137
144138.. code :: python
145139
@@ -265,8 +259,6 @@ The same goes for setting:
265259 assert lst[" tail.tail.head" ] == " newer_baz"
266260
267261
268- .. _creating_a_typesystem :
269-
270262 Creating types and adding features
271263~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
272264
0 commit comments