codeaudit / dkpro-core-asl

Automatically exported from code.google.com/p/dkpro-core-asl
0 stars 0 forks source link

Rename "api.srl" to "api.semantics" #187

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
We have a tendency to use "linguistic layers" as one way to organize our api 
modules.

api.segmentation
api.phonetics
api.lexmorph (ya... badly chosen)
api.syntax

It seems attractive to have also a "api.semantics" and possible use "api.srl" 
as a starting point (and add the SemanticField suggested elsewhere)

However, we also have

api.ner
api.coref

which I would tend to leave like they are, i.e. not merge them into semantics. 
I have a feeling regarding these as "semantics" makes the scope a bit too broad.

Original issue reported on code.google.com by richard.eckart on 2 Aug 2013 at 4:54

GoogleCodeExporter commented 9 years ago
I recently re-discovered the Manning/Schütze book Found. of Stat. NLP and 
found that the introductory chapters provide an excellent overview of some 
topics.

In Chap. 3 (Linguistic Essentials) p. 112, discourse analysis (in particular 
anaphoric relations, i.e. coreference, but also modelling of speech acts) is 
considered as part of pragmatics.

(Manning/Schütze: "Linguistics is traditionally subdivided into phonetics, 
phonology, morphology, syntax, semantics and pragmatics")

So this view would support to add the api.coref to a new api.pragmatics.

In Manning/Schütze, semantics covers among many other aspects WSD. Since both 
NER and SRL require some kind of disambiguation (as do other kinds of semantic 
tagging), I think both api.ner and api.srl would nicely fit into a 
api.semantics.

Original comment by eckle.kohler on 2 Aug 2013 at 5:32

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 16 Aug 2013 at 1:54

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r1782.

Original comment by richard.eckart on 16 Aug 2013 at 1:54