René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Define parsers outside of TAG for use within it","articleBody":"It would be convenient to define parsers _outside_ of TAG for use within it.  This would allow users to easily adjust the behavior of a parser for an evolving format (ex. https://github.com/lum-ai/odinson).\r\n\r\n\r\n### Plan\r\n- To support this we'd need to discuss how a custom parser should be registered with TAG.  Perhaps it should be passed in the config object (ex. `{\"odin\": mycustomParseFunction}`, where `mycustomParseFunction` returns `data`.)\r\n\r\n- The `Parser` constructor and helper functions in `parse/parse.js` will also need to be modified to work over a dynamic set of parsers instead of (or in addition to) the statically-defined ones TAG currently supports.\r\n\r\nThe parser system as currently written is based on classes, and `Parser` reads directly from each parser object's `.data` (e.g., from `this.odin.data` in the `parseOdin()` function) property.  We may want to consider switching to a purely functional approach to support custom parsers.","author":{"url":"https://github.com/myedibleenso","@type":"Person","name":"myedibleenso"},"datePublished":"2019-04-03T17:39:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/41/TextAnnotationGraphs/issues/41"}