# <!-- METAHEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml"
# <!-- HEADER
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"base:title": "0oo - Text classifier into Goal/Idea/Plan from Introduction/Body/Conclusion."
"og:title": "Text classifier into Goal/Idea/Plan from Introduction/Body/Conclusion."
"og:description": "When we read text, we often expect to understand the problem, and solution suggested, and conflate that into one text, like described here in [this video](https://wiki.mindey.com/shared/shots/52111eac9a8fe7c81172d397a-problem-idea-split.mp4), which makes text more consumable and practical right away, because there is a natural introduction, body and conclusion. So, in order to fill up Infinity with topics, we could simply implement a parser, that, given text, is able to identify the &quot;problem specification&quot;, &quot;solution suggested&quot;, and &quot;implementation steps&quot; from a traditional &quot;introduction-body-conclusion&quot; type of publications. For making reading more straightforward, we could even join them up, providing a single document with a line at …"
"og:image": "https://avatars0.githubusercontent.com/u/28134655"
"og:url": "/method/816/"
"base:css": "/static/css/bootstrap.min.9c25540d6272.css"
"base:extra-css": "/static/css/base.57997aeac1df.css"
"base:favicon": "/static/favicon.acaa334f0136.ico"
"base:body_class": ""
"layout:logo": "/static/0oo.8d2a8bbef612.svg"
"layout:index": "/"
"layout:menu": "/menu/"
"layout:categories": "/intents/"
"layout:ideas": "/methods/"
"layout:projects": "/projects/"
"layout:users": "/users/"
"layout:about": "/about/"
"layout:help": "/help/"
"layout:bug_report": "https://github.com/wefindx/0oo"
"layout:login": "/accounts/login/"
"layout:light-off": "/darken/?darken=true"
"layout:set-multilingual": "/mulang/?mulang=true"
"layout:lang": "Kalba"
"layout:set-language-post-action": "/i18n/setlang/"
"layout:csrf-token": "Zr2CkCTtwcvPoXC8cSChodPSKBdV7iV3qSNumdSQ6geVDY0llfXoxZjNRNE8txaU"
"layout:input-next": "/method/816/"
"layout:languages": [{"code": "ja", "is-active": "false", "name": "日本語"}, {"code": "lt", "is-active": "true", "name": "Lietuviškai"}, {"code": "zh-hans", "is-active": "false", "name": "简体中文"}, {"code": "en", "is-active": "false", "name": "English"}, {"code": "ru", "is-active": "false", "name": "Русский"}, {"code": "oo", "is-active": "false", "name": "O;o,"}]
# <!-- TOPIC
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:parent:intents": [{"url": "/intent/964/", "title": "Dirbtinis intelektas (AI) ir sistemos mokymasis (ML)"}, {"url": "/intent/1366/", "title": "Kibernetinė erdvė"}]
"item:title": ".:en:Text classifier into Goal/Idea/Plan from Introduction/Body/Conclusion."
"item:summary": "None"
"item:voting": +1
"item:voting:add": "/admin/hlog/voting/add/?method=816"
"item:voting:csrf_token": "Zr2CkCTtwcvPoXC8cSChodPSKBdV7iV3qSNumdSQ6geVDY0llfXoxZjNRNE8txaU"
"item:voting:submit-value-option": {"selected": "[-]", "value": "-"}
"item:base-administration": false
"item:body": |
    .:en
    When we read text, we often expect to understand the problem, and solution suggested, and conflate that into one text, like described here in [this video](https://wiki.mindey.com/shared/shots/52111eac9a8fe7c81172d397a-problem-idea-split.mp4), which makes text more consumable and practical right away, because there is a natural introduction, body and conclusion.
    
    So, in order to fill up Infinity with topics, we could simply implement a parser, that, given text, is able to identify the "problem specification", "solution suggested", and "implementation steps" from a traditional "introduction-body-conclusion" type of publications.
    
    For making reading more straightforward, we could even join them up, providing a single document with a line at the left in the color, indicating the type of content.
    
    For example:
    
    <img src="https://wiki.mindey.com/shared/shots/9591612f2c32abed7163bc255.png" width="640px">
    ​
"item:source-date": ""
"item:permalink": "/method/816/?l=lt"
"item:owner": "Mindey"
"item:created": "2018-09-15T18:33:54.504000"
"item:ownerlink": "/user/147/Mindey"
# <!-- LINKS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:link:add": "/admin/hlog/link/add/?parent=816"
"item:link:items":
"item:project:items":

# <!-- COMMENTS
# –––––––––––––––––––––––––––––––––––––––––––––––––– -->
"item:comment:items":
- "id": "a-711"
  "mtrans": |

    Kitaip tariant: [https://wiki.mindey.com/shared/shots/1017b5309975b3acc49290e02-on-importing-web-content.mp4←(https://wiki.mindey.com/shared/shots/1017b5309975b3acc49290e02-on-importing-web- turinys.mp4).
    
    Tolesnės mintys: [https://wiki.mindey.com/shared/shots/609ea329e0f97fa49e87c96e6-text-classifier-fooden-thoughts.mp4person(https://wiki.mindey.com/shared/shots/609ea329e0f97fa49e87c96e6-text-lass mintys.mp4).

  "text": |
    In other words:
    [https://wiki.mindey.com/shared/shots/1017b5309975b3acc49290e02-on-importing-web-content.mp4](https://wiki.mindey.com/shared/shots/1017b5309975b3acc49290e02-on-importing-web-content.mp4).
    
    Further thoughts:
    [https://wiki.mindey.com/shared/shots/609ea329e0f97fa49e87c96e6-text-classifier-further-thoughts.mp4](https://wiki.mindey.com/shared/shots/609ea329e0f97fa49e87c96e6-text-classifier-further-thoughts.mp4).
  "owner": "Mindey"
  "ownerlink": "/user/147/Mindey"
  "permalink": "/method/816/?l=lt#a-711"
  "created": "2018-09-16T09:34:50.937000"
"base:js": "/static/js/base.c7357c06cc89.js"