# "*": "https://raw.githubusercontent.com/wefindx/schema/master/method/oo-item.yaml" # "base:title": "0oo - Object Models Search" "og:title": "Object Models Search" "og:description": "Searching and making are not that different: your `search operation` on a retail store is `make operation` for a manufacturer. There are middlemen though: the `design companies`. So, imagine a search, where you can request objects be created, if they are not found, based on your object models. So, how would this work? 1. A distinction would be introduced, called "Object Instance" : "Object Class". 2. Instead of just simple UI input field, the search engine would have a "Class constructing UI" (Class Builder), where a user can enter properties of the class. For example, if you search a girlfriend …" "og:image": "https://avatars0.githubusercontent.com/u/28134655" "og:url": "/method/15001/" "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": "Language" "layout:set-language-post-action": "/i18n/setlang/" "layout:csrf-token": "2Q8lE8z5OQNLSksJVFWTN1vv2twECSBzMb45oxZyhZDm2qMs2olOXsyh1DW3IRPQ" "layout:input-next": "/method/15001/" "layout:languages": [{"code": "ja", "is-active": "false", "name": "日本語"}, {"code": "lt", "is-active": "false", "name": "Lietuviškai"}, {"code": "zh-hans", "is-active": "false", "name": "简体中文"}, {"code": "en", "is-active": "true", "name": "English"}, {"code": "ru", "is-active": "false", "name": "Русский"}, {"code": "oo", "is-active": "false", "name": "O;o,"}] # "item:parent:intents": [{"url": "/intent/1087/", "title": "Augmented Workforce"}, {"url": "/intent/1013/", "title": "Economic Growth"}, {"url": "/intent/1010/", "title": "Manufacturing Industry"}] "item:title": "Object Models Search" "item:summary": "A search engine, that works by composing classes and uploading object models, and can make things, if it doesn't find ones that already exist." "item:voting": +2 "item:voting:add": "/admin/hlog/voting/add/?method=15001" "item:voting:csrf_token": "2Q8lE8z5OQNLSksJVFWTN1vv2twECSBzMb45oxZyhZDm2qMs2olOXsyh1DW3IRPQ" "item:voting:submit-value-option": {"selected": "[-]", "value": "-"} "item:voting:submit-value-option": {"selected": "[+]", "value": "+"} "item:base-administration": false "item:body": | Searching and making are not that different: your `search operation` on a retail store is `make operation` for a manufacturer. There are middlemen though: the `design companies`. So, imagine a search, where you can request objects be created, if they are not found, based on your object models. So, how would this work? 1. A distinction would be introduced, called "Object Instance" : "Object Class". 2. Instead of just simple UI input field, the search engine would have a "Class constructing UI" (Class Builder), where a user can enter properties of the class. For example, if you search a girlfriend with green eyes and blue skin, and many other characteristics you prefer, then you would be constructing an "Object Class" with these characteristics. 3. The back-ends would be a database that indexes many markets where the various object classes exist, or are made. For example, "Amazon" (or Tinder) is where final products hang out, and "MFG" (or "Schools" of thought) is where they may be made. Traditionally, search engines went the road of massive text indexing. This search would, instead, focus on indexing warehouses, resource locations, and supply-chains as compiler for products, when warehouses have not. This kind of "object-forming generative search" would be much more creative, and generate many trade and manufacturing orders, facilitating economic growth. "item:source-date": "" "item:permalink": "/method/15001/?l=en" "item:owner": "Mindey" "item:created": "2021-04-22T18:43:53.105953" "item:ownerlink": "/user/147/Mindey" # "item:link:items": - "id": "l-34001" "url": "https://github.com/samsquire/startups#23-manufacture-app" "text": "Manufacture app" "note": "Startup ideas list" "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/15001/?l=en#l-34001" "created": "2021-09-15T00:35:43.404884" "item:link:add": "/admin/hlog/link/add/?parent=15001" "item:project:items": "item:project:add": "/admin/hlog/project/add/?parent=15001" "item:comment:add": "/methods/addnote?parent=15001" "item:comment:add:csrf_token": "2Q8lE8z5OQNLSksJVFWTN1vv2twECSBzMb45oxZyhZDm2qMs2olOXsyh1DW3IRPQ" "item:comment:form": |
  • Mark if the comment raises new questions.
  • Mark if the comment contributes potential solutions.
  • Mark if the comment contributes facts for reasoning.
  • Please, log in. # "item:comment:items": - "id": "a-180001" "text": | Your idea addresser app made me think of this idea - I would like the key interface with my computer to be search. Search someone's name, email text, file text - anything and results should show up. I should be able to provide a complex query about attributes of the solution I want and find them. Like a join but a converging function of multiple variables. Like What If. "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/15001/?l=en#a-180001" "created": "" - "id": "a-181001" "text": | I have an idea in my startups list called manufacture app. The idea being is you could request a phone with certain specs or laptop. Upload PCB designs and 3d models and get it manufactured. I have linked it. "owner": "chronological" "ownerlink": "/user/198/chronological" "permalink": "/method/15001/?l=en#a-181001" "created": "" "base:js": "/static/js/base.c7357c06cc89.js"