ResolvedTopicclass | action.t[5710] |
Superclass Tree | Subclass Tree | Global Objects | Property Summary | Method Summary | Property Details | Method Details |
class
ResolvedTopic : object
(none)
ResolvedTopic
object
resolvedTopicNothing
canMatchLiterally
inScopeList
likelyList
otherList
topicProd
construct
getBestMatch
getTopicText
getTopicTokens
getTopicWords
wrapActionObject
wrapObject
canMatchLiterally | action.t[5829] |
By default, we simply return true. Note that the base library never has any reason of its own to disallow literal matching of topic text; this property is purely for the use of language modules, to handle language-specific input that parses at a high level as a topic phrase but which has some idiomatic or grammatical function that makes it in appropriate to try to extract the meaning of the resolved topic from the literal text of the topic phrase in isolation. This case doesn't seem to arise in English, but does occur in other languages: Michel Nizette cites "parlez-en a Bob" as an example in French, where "en" is essentially a particle modifying the verb, not a full-fledged phrase that we can interpret separately as a topic.
inScopeList | action.t[5853] |
likelyList | action.t[5854] |
otherList | action.t[5855] |
topicProd | action.t[5862] |
construct (inScope, likely, others, prod) | action.t[5711] |
getBestMatch ( ) | action.t[5783] |
getTopicText ( ) | action.t[5805] |
getTopicTokens ( ) | action.t[5835] |
getTopicWords ( ) | action.t[5843] |
wrapActionObject (role) | action.t[5738] |
wrapObject (obj) | action.t[5759] |