I think it's a good idea, keeps it simple. Basically an EntityLinker that knows how to parse date spans. I think this would be a good first approach, and we can iterate from there. Later on I do see utility in a regex approach that can be used to produce training annotations from user data to generate the date model, but what you propose is a logical first step; we would need a result parser anyway. Thanks
On Fri, Mar 7, 2014 at 12:08 PM, Jörn Kottmann <[email protected]> wrote: > On 03/07/2014 05:45 PM, Mark G wrote: > >> This addon I propose would take text, and return a real java.util.Date, >> with a precision, likely stored in an extended Span object. Initially, I >> would like it to deal with year, seasonal, month, and day level >> references, >> and return a real Date and a precision. Don't care so much about days of >> week mentions and such, this is geared more towards supporting search and >> other datetime related analytics. >> > > What do you think about using the existing name finder interface to > identify spans that > contain a date. A second component, maybe based on the entity linker > interface, could > be used to parse the actual date for the detected spans. > > Jörn >
