opla-v2
opla-v2 copied to clipboard
Builder : entities are coming !
We need to add entities to the builder:
- Systems : display all system entities and we could activate them (any, email, date, number, ...)
- A non system entity is a list of terms and each terms are associated to synonyms
Entities Data type / pattern entities @system list all read only entities. Pattern types:
- @system.any (@any / any) : pattern wildcards that match any words
- @system.zero_or_more (@zero_or_more / zero_or_more) : pattern wildcards that match zero or more words
Data types:
- @system.number (@number) : number pattern
- @system.date (@date) : date pattern to extract a date
- @system.email (@email) : email pattern
- @system.url (@url) : email pattern
- @system.address (@address) : address pattern
- @system.color (@color) : color pattern
@entity.xxx are user's defined entities. This entity is defined by a list of words associated to synonyms. Example @entity.city (shorthand : @city) You define a list [ New York, Paris, London ] And for New York you add synonyms : [ NY, NYC, Big Apple ]
Properties
A property (prop) is a key/value entry stored permanently in system/agent/user's context. A context is a database.
@context : list all defined properties. 2 types of entry:
- read only system entries, created by the system/agent.
- read/write items created during conversation System properties: @context.userprofile (user, read): .username / .firstname / .lastname / .gender / .age / .country / .avatar / .anonymous / .lastConnection @context.date (system, read): .date.year / .date.month / .date.day / .date.hour / .date.minute / .date.second @context.platform (user, read): could be (webchat, facebook messenger, ...) @context.agent (agent, read): .agent.name / .agent.version