It would help me think about this if there was a short write-up /
documentation describing,
for newbies, what the purposes / goals of this tool are. e.g., a short
"users manual". Is there
such a thing? I'd be happy to help convert it to our docbook format :-)
-Marshall
Jörn Kottmann wrote:
Hello,
here is a little introduction about the cas project structure.
Each cas project has a central typesystem, this typesystem must
be compatible with the stored cas files and also with the cas processor
descriptors.
The cas files of a project are stored in special corpus folders,
which must be defined by the user. Inside this folder
the cas files are organized in a flat structure, it is not possible
to place them in a subfolder of the corpus folder.
There is another special folder for the cas processor descriptors.
These contain the
xml descriptor itself and all needed resources. It is also possible to
write files to this
folder e.g cas consumer which create something and want to save it.
These special descriptor folders all contained in a base folder, so
the user
only needs to define this base folder and all subfolder are automatically
descriptor folders. But I do not like this anymore, I think it is
easier for
a user if he just define a folder to be a descriptor folder like it must
be done for a corpus folder, I will change this.
The locations of the typesystem and the special folders are saved in
the .corpus file. This is an xml based project config file.
One major problem I encountered is, that it is not possible to change the
typesystem, e.g. if a type is removed its not possible to load the cas
files which contain a FS of this type.
Tell me what you think.
Thanks,
Jörn
