idnits 2.17.1 draft-pradeep-kumar-xplorer-ismirsmgps-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 107 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 3 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 42 instances of too long lines in the document, the longest one being 36 characters in excess of 72. ** There are 20 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 18, 2020) is 1439 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 HTTP Pradeep Kumar Xplorer 2 Internet-Draft 3 Intended status: Standards Track Individual 4 Expires: Nov 18 2020 May 18, 2020 6 Need for integration of social media information retrieval statistics and GPS 7 draft-pradeep-kumar-xplorer-ismirsmgps-00 9 Abstract 11 This document describes the need for integration of social media information retrieval statistics and GPS 13 Status of This Memo 15 This Internet-Draft is submitted in full conformance with the 16 provisions of BCP 78 and BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF). Note that other groups may also distribute 20 working documents as Internet-Drafts. The list of current Internet- 21 Drafts is at http://datatracker.ietf.org/drafts/current/. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 This Internet-Draft will expire on Jul 17,2016. 30 Copyright Notice 32 Copyright (c) 2013 IETF Trust and the persons identified as the 33 document authors. All rights reserved. 35 This document is subject to BCP 78 and the IETF Trust's Legal 36 Provisions Relating to IETF Documents 37 (http://trustee.ietf.org/license-info) in effect on the date of 38 publication of this document. Please review these documents 39 carefully, as they describe your rights and restrictions with respect 40 to this document. Code Components extracted from this document must 41 include Simplified BSD License text as described in Section 4.e of 42 the Trust Legal Provisions and are provided without warranty as 43 described in the Simplified BSD License. 45 Table of Contents 46 1. Introduction ............................................... 2 47 2. Background ..................................................2 48 3. General Information of the service ..........................2 49 4. Authors Addresses ...........................................3 50 5. Acknowledgements ............................................3 52 1. Introduction 54 To implement an httpi:// service in browser similar to https 56 2. Background 57 Right now URL's are hardcoded. I propose an httpi:// service 58 that would allow dynamic links that can be updated by the httpi 59 service in the text that you are viewing. So every time interval like 60 a minute or so, the content you are viewing using the httpi:// service 61 in your browser can show newer links that you can traverse or navigate 63 3. General Information of the service 65 Having a parallel beowser realm, that allows intelligent updates of 66 navigatable links from WWW intelligent computing realm. Instead of using 67 http:// you just need to type httpi:// in your URL and the texts you view 68 would not have any hardcoded navigatable links but those suggested by 69 the WWW brain. 71 A browser user should be able to type httpi:// in URL field and wait. 72 The cache could fill with those suggested by the WWW brain. 74 Please view draft-pkx-wwwogc. I have suggested a httpsso:// mode also. 75 I am suggesting these modes for http for professional and it should be 76 as a pulldown or Options menu as an interface for the user. 78 httpssoi - single signon with intelligence 79 httpauto - auto mode for browsing 80 httpssoiauto - Using the browser like a TV channel 81 httpiauto 83 All Combinations of http httpi httpsso and httpauto could be implemented. 85 So i launch my browser and type httpsso://www.service.com. In this mode 86 for one session you hav to type your username and password only once. IT would 87 let you relate multiple accounts in your first session or whenever you navigate 88 to sites that need authentication. 90 In httpsso mode i should be able to type httpsso://www.dhyanayoga.info/logs and 91 see the sso identities of who is viewing my site. If there are millions of users, 92 then i should be able to see some groups they belong to , some thing similar to 93 twitter groups model can be used.. SO i should know if Sonoma YOgis are accesing my site 94 by an Icon in my logs that point to that group.The Twitter model groups should be 95 automatically created by httplogs of an user using some Servers that they pass through 96 and an internet users sso identity should be part of those groups automatically 98 Anything thats seen as a website to a User should have logs. To someone who 99 does not program or have education in computer science a Twitter or facebook 100 page is like an information site for some user group or subject. Such pages 101 should know who accessed them by appending logs. So if i have a twitter page 102 http://twitter.com/PradeepXplorer I should know who peeks into my page by 103 typing http://twitter.com/Pradeepxplorer/logs. I object to facebook giving me 104 free account and only they knowing who views my page and twitter also. 106 If i launch and type httpi://www.site.info , it would be showing navigatable 107 links that are not created manually. The WWW brain would suggest navigatable 108 links. Imagine having a tablet or laptop while you are relaxing and you can 109 cruise the intelligently by httpiauto:// 111 If you type httpauto://www.site.info you can watch the site like a TV channel 112 but manually directed by hardcoded URLs or URIs 114 I publish a site with no hardcoded URL URI's. If i view the site 115 http://www.pradeepkumarxplorer.com it does not show any navigatable links. 116 if i View using httpi://www.pradeepkumarxplorer.com or by using a USer interface 117 switch or OPtion it should show me navigatable links suggested by WWW brain as 118 well as the hard coded URL. I also propose two user actions in addition to click 119 on a URL. A user should be able to highlight a text and do Re search by a user action 120 and also navigate to a URL suggested by the WWW brain. It could change dynamically depending 121 on whats available. ALso i should be 122 able to highlight a portion of text or whatever i am viewing and navigate 123 and it should lead me to either one document suggested by INtelligent WWW brain 124 or multiple documents. 126 I also propose a scribe version of httpd and smtpd or mail protocol 127 daemon so pen interfaces can be used by browsers and email clients. 129 4.Authors' Addresses 131 Pradeep Kumar Xplorer 132 EMail: pradeepan88@hotmail.com 133 URI: http://www.pradeepkumarxplorer.com 135 5.Acknowledgement