MailTo,DialTo,MesseageSmsMmsTo, MessengerTo,PayTo...

Is it time to implement protocols to support features to support more protocols like MailTo, DialTo, DriveTo, DiveTo, SwimTo, LightTo, PowerTo, ElectricityTo,MesseageSmsMmsTo, MessengerTo, PayTo, VideoTo, DocumentTo,VoiceTo, VoicemailTo,TextTo, ImageTo,MapTo,GraphicsTo,UMLTo,ArcheTypeTo,BluePrintTo,SignalTo,WavesTo, SoundTo,SongsTo,MusicTo,DanceTo, SatelliteCommunicationsTo.FlyTo,TicketTo, PlanTo, CalendarTo, StudyTo,MIMETypeTo,EventsTo,CodeTo,FlyTo,CruiseTo, InsuranceTo,PolicyTo,BookTo,SellTo,BuyTo,PlayTo,FunTo,TripTo,CookTo,ServeTo,CallTo,MassageTo,CureTo, CareTo, DriveTo, RingTunesTo, RingTonesTo, ItineraryTo, ContactsTo, DateTo, ApplicationFormTo ServiceRequestTo,ServiceResponseTo, OrderTo, DeliveryTo,VisitTo, QuoteTo, BoatTo, ConfigurationTo, ShipTo, PriceTo, FoodTo, GroceryTo, BooksTo, Accessories To, ClothsTo, ShiesTo,SlipppersTo, MakeUpTo, PrintTo, PhotoTo, VideoTo, TilesTo, PaintTo,CleanTo, PrayTo ,PlaceOfWorshipTo, WaterFallsTo, SportsTo, DTHTo , eDDTo, eChequeTo, ShareTo,LiveTo,BroadcastTo,TelecastTo BiometricsTo,KYCTo,eKYCTo,TransactionTo,TransferTo,WorkOrderTo,TaskTo,ScheduleTo,QRCodeTo,WaterSportsTo, MIMETypePlugInViewerTo,WaterFallVisitTo, and so on...,? Such that they are anchor's to support one touch dial,mail,email,message,messengermessages and so on to be included in HTML specifications, protocol standard's, to include in All forms of GUI interface, communication protocols, widgetsTo, workflows,messaging Frameworks, exchange server's , MIME viewer plug-in,devices,messengers, social media apps, workflow applications, vehicles,TVs, electronic devices, and so on

#ToProtocolTypeHierarchy

What do we think of this suggestion?