Thursday, April 2, 2009
Wednesday, July 16, 2008
Mobile Operating Systems
A Mobile operating system, also known as a Mobile platform, or a Handheld operating system, is the operating system that controls a mobile device—similar in principle to an operating system such as Linux or Windows that controls a desktop computer.
Major Mobile operating systems:
Symbian OS is an open operating system, designed for mobile devices, with associated libraries, user interface frameworks and reference implementations of common tools, produced by Symbian Ltd. It is a descendant of Psion's EPOC and runs exclusively on ARM processors.
The S60 Platform (formerly Series 60 User Interface) is a software platform for mobile phones that uses Symbian OS. S60 is currently amongst the leading smartphone platforms in the world. It is developed primarily by Nokia and licensed by them to other manufacturers including Lenovo, LG Electronics, Panasonic and Samsung.
UIQ (formerly known as User Interface Quartz) by UIQ Technology is a software platform based upon Symbian OS. Essentially this is a graphical user interface layer that provides additional components to the core OS, to enable the development of feature-rich mobile phones that are open to expanded capabilities through third-party applications.
MOAP (Mobile Oriented Applications Platform) is the software platform for NTT DoCoMo's FOMA service for mobile phones. MOAP(S) is supported by Symbian OS based phones from a number of manufacturers such as Fujitsu, Sony Ericsson Japan, Mitsubishi, Sharp and others. Unlike Series 60 and UIQ, other platforms based on Symbian, MOAP(S) is not an open development platform. MOAP(L) is supported by Linux-based phones from Panasonic and NEC. MOAP(L) is also not an open development platform.
UIQ (formerly known as User Interface Quartz) by UIQ Technology is a software platform based upon Symbian OS. Essentially this is a graphical user interface layer that provides additional components to the core OS, to enable the development of feature-rich mobile phones that are open to expanded capabilities through third-party applications.
MOAP (Mobile Oriented Applications Platform) is the software platform for NTT DoCoMo's FOMA service for mobile phones. MOAP(S) is supported by Symbian OS based phones from a number of manufacturers such as Fujitsu, Sony Ericsson Japan, Mitsubishi, Sharp and others. Unlike Series 60 and UIQ, other platforms based on Symbian, MOAP(S) is not an open development platform. MOAP(L) is supported by Linux-based phones from Panasonic and NEC. MOAP(L) is also not an open development platform.
Latest Version: Symbian OS v9.5
Announced in March 2007. It provides the concept of demand paging which is available from v9.3 onwards. Applications should launch up to 75% faster. Native support for mobile digital television broadcasts in DVB-H and ISDB-T formats and also location services. Additionally, SQL support is provided by SQLite.
Symbian OS v9.5 is the result of continued deep collaboration with Symbian OS licensees, the world’s leading handset vendors, and its user interface platform partners MOAP, S60 and UIQ.
Windows Mobile is a compact operating system combined with a suite of basic applications for mobile devices based on the Microsoft Win32 API. Devices that run Windows Mobile include Pocket PCs, Smartphones, Portable Media Centers, and on-board computers for certain automobiles. It is designed to be somewhat similar to desktop versions of Windows, feature-wise and aesthetically. Additionally, third-party software development is available for Windows Mobile.
Windows Mobile 6, formerly codenamed "Crossbow", was released on February 12, 2007 at the 3GSM World Congress 2007. It comes in three different versions: "Windows Mobile 6 Standard" for Smartphones (phones without touchscreens), "Windows Mobile 6 Professional" for Pocket PCs with phone functionality, and "Windows Mobile 6 Classic" for Pocket PCs without cellular radios.
3) Research In Motion
Research In Motion is a Canadian wireless device company. It is best known as the developer of the BlackBerry handheld communication device.
RIM develops its own software for its devices, using C++, C and Java technology. RIM also develops and sells embedded wireless data components.
4) Android
The Android platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the Android SDK. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.
Android will ship with a set of core applications including an email client, SMS program, calendar, maps, browser, contacts, and others.
Palm OS (also known as Garnet OS) is an embedded operating system initially developed by U.S. Robotics' owned Palm Computing, Inc. for personal digital assistants (PDAs) in 1996. Palm OS is designed for ease of use with a touchscreen-based graphical user interface. It is provided with a suite of basic applications for personal information management. Besides Palm, several other licensees have manufactured devices powered by Palm OS. The currently licensed version from ACCESS is now called Garnet OS
Latest Version: Palm OS Cobalt
Palm OS Cobalt (6.0) was introduced on February 10, 2004, but is not offered anymore from ACCESS (see next section). Palm OS 6.0 was renamed to Palm OS Cobalt to make clear that this version was initially not designated to replace Palm OS 5, which adopted the name Palm OS Garnet at the same time.
Palm OS Cobalt introduced modern operating system features to an embedded operating system based on a new kernel with multitasking and memory protection, a modern multimedia and graphic framework (derived from Palm's acquired BeOS), new security features, and adjustments of the PIM file formats to better cooperate with Microsoft Outlook.
Palm OS Cobalt 6.1 presented standard communication libraries for telecommunication, Wi-Fi, and Bluetooth connectivity. Despite other additions, it failed to interest potential licensees to Palm OS Cobalt.
BREW (Binary Runtime Environment for Wireless) is an application development platform created by Qualcomm for mobile phones. It was originally developed for CDMA handsets, but has since been ported to other air interfaces including GSM/GPRS. BREW is a software platform that can download and run small programs for playing games, sending messages, sharing photos, etc. The main advantage of BREW platforms is that the application developers can easily port their applications between all Qualcomm devices. BREW runs between the application and the wireless device's chip operating system so as to enable a programmer to develop applications without needing to code for system interface or understand wireless applications.
iPhone OS is the operating system developed by Apple Inc. for the iPhone and iPod touch. Like Mac OS X, from which it was derived, it uses the Darwin foundation. iPhone OS has four abstraction layers: the Core OS layer, the Core Services layer, the Media layer, and the Cocoa Touch layer. The operating system takes less than half a gigabyte (GB) of the device's total memory storage
The latest released version of iPhone OS is 2.0, released on July 11, 2008
8) SavaJe
SavaJe (pronounced savage) was the developer of the SavaJe OS, a Java OS for advanced mobile phones. Based on Sun Microsystems' Micro Edition, their phones offer a Swing-based development platform for creating richer user interfaces.
9) Mobilinux
Mobilinux is a Linux-based operating system targeting smartphones. It was announced by MontaVista Software on April 25, 2005. Mobilinux is based on open source and open standard technology, designed for scalability and maximized battery power usage for single-chip mobile phones. More than 35 million phones and other mobile devices run on Mobilinux, far more than any other commercial Linux.
10) Maemo platform
The Maemo platform is the software stack for Nokia Internet Tablets, which includes Internet Tablet OS and the Maemo SDK. The Maemo platform is developed by the Maemo Software department within Nokia.
11) Red Flag Linux
Red Flag Linux is a Chinese Linux distribution. Red Flag's logo is Tux carrying a prominent red flag. Red Flag Linux 6.0 was published on September 29, 2007. Version 6.0 is based on the Linux distribution Asianux 3.0, which was released on September 22, 2007. It includes Linux 2.6.22.6, KDE 3.5.7 and X.Org 7.2.
12) JavaFX Mobile
JavaFX Mobile is a Java operating system for mobile devices initially developed by SavaJe Technologies and purchased by Sun Microsystems in April 2007. It is part of the JavaFX family of products. The JavaFX Mobile operating system provides a platform for PDAs, smartphones and feature phones. It features a Java SE and Java ME implementation running on top of a Linux kernel.
13) DoJa
DoJa profile is Java environment specification for DoCoMo's i-mode mobile phone.
DoJa is based on the Java ME CLDC API that is defined in the Java Community Process (JCP). DoJa is a profile defined by NTT DoCoMo to provide communications and other input-output processing, user interface (GUI) and other features/functions unique to i-mode, and extension libraries defined by individual phone terminal makers to add original functions. However, in contrast with other Java ME profiles like Mobile Information Device Profile (MIDP) or Information Module Profile (IMP), DoJa is not defined as a Java Specification Request (JSR), hence it's often called a "proprietary" Java ME profile.
14) Openmoko Linux
Openmoko Linux is an operating system for smartphones developed by FIC. It is a general-purpose Linux distribution comprising various pieces of free software. Openmoko Linux is part of the Openmoko project to create a family of completely open source mobile phones. Openmoko Linux uses the Linux kernel, GNU libc, the X.Org server plus their own graphical user environment built using the GTK+ toolkit and the Matchbox window manager. The OpenEmbedded build framework and a modified version of ipkg package system, called Opkg, are used to create and maintain software packages.
15) Qtopia
Qtopia is an application platform for Embedded Linux-based mobile computing devices such as personal digital assistants, mobile phones, and web pads. It is being developed by Trolltech.
Wednesday, May 28, 2008
Tuesday, May 27, 2008
The INOX at Urvasi in Vijayawada
The bastion and capital of Telugu Movie Industry known for its traditional modes of honoring movies, is now officially penetrated by the ultra-urban-wannabe-US multiplex culture. For those who enjoy the tranquility and pacific atmosphere of multiplexes this is a dream come true, but for someone like me this is sad.
I am not from Vijayawada, but I have been there several times, seen many movies and celebrated their oil paint posters (where flex/digital format posters co-exist), banners, garlands, decorations and the works, which are all associated with the typical traditional Andhra/Coastal Andhra movie culture; all which happen at Hyderabad too, but not at nearly the same traditional intensity that I see in Vijayawada. It was last year that the Urvasi complex had shut down and I heard they are converting it into a multiplex. Later in the year, the rumor was it will be INOX.
If INOX at Urvasi rolls out like all other INOX chains in the country then the spirit of movie watching that Vijayawada is the capital for is dead. The improved seating, utility facilities, parking space, no-smoking facility, safety measures are all welcome, but naming the theaters as screen 1, 2, 3 is not, in fact it is lifeless. True, they have retained the parent name Urvasi, but retaining the names of Rambha Urvasi and Meneka would have been classic. No doubt, Vijayawada folks are wealthy enough so ticket price will not be an issue, but the Rs 10 guy is out.
It will be an interesting cultural experiment to see how Vijayawada marries their unique culture to this ultra-urban atmosphere that INOX will create. How much of its tradition will be compromised to INOX--will there be cut-outs (although, i do not remember Urvasi complex to be known for its movie exhibition like other theaters in Vijayawada), banners, and most essentially will there be "hungama" in the theater (during releases of the major stars) or will it all be tranquil? And most importantly, will the quintessential distinction be wiped out: Daily 4 Shows at each screen or the multiplex-timings?
I wish the people of Vijayawada appeal to the owners and their roots to retain the names of Rambha, Urvasi, and Menaka instead of Screen 1, 2, 3. Sadly, for me, this means that there will be multiplexes coming in other power/wealth centers of coastal Andhra; it is only a matter of time now.
It will be interesting to see how these centers of traditional moviegoers mix their movie culture to that of the multiplex.
Webinar Planning
Webinar
A webinar is a type of web conference, although the direction of the presentation more often than not is primarily one way from the presenter to the audience as in a Webcast, which is transmission of information in one direction only, like watching a concert on the internet. A webinar however can be designed to be interactive between the presenter and audience. A webinar is 'live' in the sense that information is conveyed according to an agenda, with a starting and ending time. In most cases, the presenter may speak over a standard telephone line, pointing out information being presented on screen, and the audience can respond over their own telephones, preferably a speakerphone. The word 'webinar' is a portmanteau combining the words web and seminar.
Webinar planning involves five stages:
1. Event Strategy
2. Event Design, Setup and planning
3. Event promotion
4. Live Event or During the Event
5. Event follow up
I. Event Strategy:
Strategy begins with determining the highest-level goal. Who do you want to reach? What response do you want from them at the end of the event? How many such responses are you seeking? Do you have a specific budget number to work with, or must you request your budget once you’ve assessed your needs and likely ROI? What topic is relevant and interesting to your target audience?
Select a date.
Following are the factors need to be consider in selecting a date.
1. Avoid holidays, and the days immediately preceding them.
2. Mondays and Fridays average lower attendance than Tuesdays, Wednesdays and Thursdays.
3. Events held in the last two weeks of your quarter typically receive less Sales support, because their focus then is usually closing business rather than prospecting.
4. Events held early in the quarter have a better chance to raise sales in that quarter.
5. Need to check if there is any tradeshows that may conflict
6. Consider the time zones of your expected audience. Since most attendees will participate at their desks, when will they be there? If you market nationwide, a good time is 1 p.m. Central time. If you market in only one or two time zones, schedule the event between 11 a.m. and 1 p.m. Many prospects like to attend during lunchtime.
Speaker Selection:
Who will be the main presenter? Choose a recognized expert, an author, a person who has succeeded in solving the problem presented—the more respected and known, the better your attendance. Selecting someone outside of your organization lends credence to the value of the event. Remember that the keynote presenter doesn't necessarily present the complete Webinar. Others, including you or your associates, can also participate. Big-name presenters may be easier to get than you think. Of course, you can pay them, if that's in your budget. Once they learn about the planned promotion of the event, the amount of publicity they'll get, and the exposure to an audience they want to reach, they may reduce their fee or do it for free. An offer to share the leads might be all it takes. The Webinar gives them a platform, access to an audience, a chance to be the expert and gain more recognition for themselves or their company. But a big-name presenter is not essential. Putting all your eggs in one basket may build a bigger audience for that one Webinar, but a series of content-focused events pull more and better qualified leads in the long run. Multiple events offer prospects more convenient options of dates and times.
Action Plan:
Determine the target audience, desired response from attendees, and goal number of attendees to reach
Decide the interesting and relevant topic and speaker(s) that attract enrollment and draw attendees towards the desired response
Design event promotion campaign to reach ideal target audience
Determine amount of time necessary to define, promote, design and prepare event (6 weeks is a good start).
Calculate required budget for promotion, content, web seminar & telephony costs, inducements and follow up
Optional: Calculate estimated Return on Investment to justify managing budget level up or down
• Optional: Revise spending plan to match revised budget
• Commit to event and proceed to next stage.
II. Event Design, Setup & Planning
First it is important to think about how you want to structure your enrollment page. What information is essential for you to gather prior to the event (name, address, e-mail, etc.). As your enrollment page is established, consider the objective of the event and what you’re looking to gather. Several of your qualifying questions will be very important to determining the quality of each lead.
Furthermore, think about how you want the description page to read and how you will describe the Webinar. From a marketing perspective, it is important that the reader is intrigued with the content and needs to be soft sold into wanting to attend. Make sure to select either a logo or a featured picture of the presenter to post in concert with the written text.
Content of the Presentation:
Use slide transitions and animations to keep the audience stimulated. Offer statistics, illustrations, real-world examples and quotes to add substance. The more credibly and concretely you can make your case, the fewer audience members will be left sitting on the fence. Real-world examples are particularly valuable for helping audience members absorb and assimilate abstract concepts. Examples often help the audience relate to the content as well. Illustrating data graphically, with a very clean minimalist approach tends to help audiences comprehend it quickly and comfortably.
In general, a 30-35 minute presentation length is optimum for marketing seminars. If the seminar is too short, attendees may not feel they’ve received a substantial value. If the presentation is too long, you may not retain as much of the audience through to your call to action at the end. Or, the audience may be so saturated and fatigued that they feel less vigorous about responding to your call to action. It is generally ideal to leave at least 10 minutes reserved for Q&A after the presentation and initial statement of the call to action.
Action Plan:
•Designate an event Host or a Producer to manage the technical aspects of the event.
• Establish elements for your
• Write compelling event title and description
• Design enrollment questions (customize to include qualifying criteria)
• Define user/attendee experience: drop-off webpage to leave attendees at after event and other touch points.
• Select and orient Host, Speaker(s), and any support Panelists
• Approve and confirm enrollees if applicable
• Develop the content for the presentation
• Review reports leading up to the session to be prepared for volume of attendees (remember, usually 50% of enrollees attend)
• Review event details again to ensure all preparations have been completed
• Rehearse for the event itself and practice the sequence of steps (typically 24 hours before event is best)
• Schedule and draft automated Thank-you-for-attending, and Sorry-you-couldn’t-make-it e-mails
• Plan how event attendee data will be parsed and quickly distributed to appropriate Salesperson (CRM – integration, batch import, manual process, etc.)
• Assemble event-specific talk tracks and sales collaterals to assist sales reps converting attendees to purchasers
• Optional: Schedule calling campaign by sales force for 1-3 days after the event to qualified attendees and enrollees
• Optional: Create PDF version of final presentation for making available to attendees
• Optional: Schedule marketing offer e-mail one week after event
• Option: Assign numeric weightings to each possible answer for enrollment qualifying questions to allow automatic scoring and ranking of leads
• Option: Consider creating a program of related events to promote at once (additional perceived value, mindshare and cost savings)
III Event Promotion
Event promotion is crucial to your overall success. You will have a variety of tools to choose from, and constraints to counterbalance. Your limiting factor may be a small target population, in which case you may opt to use multiple techniques focusing on that target to get the highest possible yield. Or, your limiting factor may be budget, in which case you may opt to use only the lowest cost promotion techniques targeting the easiest to reach prospects. Whatever your parameters, the following tips are intended to help you manage and achieve your goals.
Events frequently use some combination of the following promotional vehicles:
• Home page placements
• E-mail invitations
• Newsletters
• Banner ads
• Press releases
• Partner co-marketing
E-mail campaigns
E-mail campaigns are frequently used to promote web seminars. There are some common assumptions about response rates, enrollment rates, attendance rates and lead ratios you’ll consider when deciding how many invitations to send to reach a certain audience size goal
Your response rate will vary depending on a variety of factors including the:
• Richness of your purchased or owned e-mail list
• Use of unsolicited lists versus known leads
• Resonance of your event title and description to your target audience
• Quality of your invitation copy
• Ability of your invitation to get past spam filters
• Appeal of your brand and any guest speakers
• Amount of advanced notice you provide your invitees
• Time and day of the week your event is scheduled at
• Ease of filling out your enrollment form
In general you get a better response rate from lists of people who already know your organization than from “cold” lists you buy or rent from 3rd parties. The following numbers assume a “cold” list.
If you make reasonable efforts to account for the above, on average you can assume you need to send 100 invitations for each enrollee. Typically 40-60% of enrollees will attend. Typically 5-15% of attendees will qualify as “A” (likely to buy soon) leads. A similar fraction will also qualify as “B” (interested but with a less urgent need) leads. A lesser percentage of those who enroll but do not attend will likely qualify as “A” and “B” leads, as well. Your sales conversion rate is highly dependent on your product offering, marketplace and sales team. That said, 15% is a common rate. A gross assumption suggests you’ll close 1-5 sales per 10,000 e-mail invitations. There are many steps you can take to optimize these ratios for your unique situation. Your results may vary.
Whatever promotional vehicles you use, each should include a unique tracking ID as part of its HTML link to the event enrollment page. This will allow you to analyze which promotional vehicles are getting the greatest response.
Reminders for registrants are an important part of delivering the largest audience to your web seminar. Statistically, reminders e-mailed 24 hours and 1 hour in advance of the event seem to have the greatest benefit. For some event topics and audiences, it may make financial sense for you to leave telephone reminders a day or two in advance of the event. Yes, this includes extra cost and time. The benefit is generally that it adds an extra psychological dimension, which seems to make a noticeable increase in attendance rates.
Action Plan
• Design event promotion campaign to reach ideal target audience
• Promotion usually begins 3-4 weeks prior to event
• Select combination of e-mail, home-page placements, web ads, banner ads, newsletters, direct mail, Sales invitations, PR, and viral marketing you will use to promote event
• Specify lead-source tracking ID’s to measure which sources are most effective and efficient
• Execute the campaign and drive enrollment traffic
• Send reminders (1 week and 1 hour in advance) to your enrollees
• Optional: Call enrollees the day before to orally remind them of event
IV During the Webinar:
Action Plan:
• Review event details and follow-up campaign readiness
• Open event 30 minutes early to streamline attendees’ join process
• Control and minimize last-minute changes to presentations
• Prepare Record and Playback File, polls and seed questions
• Have attendees submit text questions via Q&A which you’ll selectively answer out loud
• Acknowledge questions submitted by attendees by immediately responding, even if with a deferral
• Save Q&A
• Save Polling answers for marketing data
V: Post-Event Follow Up
Following the event, you should have a few key objectives; disseminating leads, spurring Sales team follow up, leveraging the event recording, and executing follow-up communications to your enrollment list.
First and foremost, is using the information and data derived to direct your Sales team to follow up with the most-primed opportunities. You will want to sort the information as quickly as possible and deliver it to your Sales team. Typically this means grading the leads and sorting them by territory or whatever other criteria your organization uses to divide leads. In addition, you want to effectively position and promote access to the recorded file of the session via e-mails and other avenues.
A targeted campaign of “thank you’s” and “sorry we missed you” e-mails will be executed to those that attended and those that enrolled, but missed the event— respectively. With ongoing reporting tools monitoring those that access the record and playback files, you can continue to derive leads. Moreover, by effectively using the automated e-mail functions, communication with those that enrolled and those that enrolled and attended is easy.
Action Plan
· Send automatic event follow up e-mails (sorry-we-missed-you to non-attendees and thanks-for-attending to attendees)
· Export your customized event report data to disburse to your sales force, prioritizing leads with highest scores.
· Post the event recording file with its own enrollment questions to gather more leads going forward
· Draw on your post event reports to continue to communicate, and convert, attendees to customers.
· Measure which lead sources yielded highest enrollment, attendance, and requests for 1:1 consultation or sales.
· Hold more events, further amortizing startup costs, and adding experience-based refinements for even better ROI
· Optional: Convert Q&A into edited FAQ
· Optional: Edit your event recording to remove “live” foibles and remove extraneous information that is not pertinent to on-demand format
Wednesday, May 14, 2008
web 3.0
Web 1.0 was therefore the first decade of the Web: 1990 - 2000. Web 2.0 is the second decade, 2000 - 2010.Web 3.0, in my opinion is best defined as the third-decade of the Web (2010 - 2020), during which time several key technologies will become widely used. Chief among them will be RDF and the technologies of the emerging Semantic Web. While Web 3.0 is not synonymous with the Semantic Web (there will be several other important technology shifts in that period), it will be largely characterized by semantics in general.
Web 3.0 is an era in which we will upgrade the back-end of the Web, after a decade of focus on the front-end (Web 2.0 has mainly been about AJAX, tagging, and other front-end user-experience innovations.) Web 3.0 is already starting to emerge in startups such as Radar Networks, but will really become mainstream around 2010.
Web 3.0 Examples:
Another prime example of a Web 3.0 technology is powerset.com which is developing 'natural-language search', which refers to the ability of search engines to answer full questions such as 'Which US Presidents died of disease?'. In some cases, the sites that appear in the results do not reference the original search terms, reflecting the fact that the web knows, for instance, that Reagan was a US President, and that Alzheimer's is a disease. According to Barney Pell, chief executive of Powerset “ Their engine reads every page of the web sentence by sentence and returns results by drawing on a general knowledge of language and what specific concepts in the world mean, and their relationship with one another."
Web 3.0 Layers
Web 3.0 is divided into three distinct layers:
API services form the foundation layer. These are the raw hosted services that have powered Web 2.0 and will become the engines of Web 3.0 — Google’s search and AdWords APIs, Amazon’s affiliate APIs, a seemingly infinite ocean of RSS feeds, a multitude of functional services, such as those included in the StrikeIron Web Services Marketplace, and many other examples. Some of the providers, like Google and Amazon, are important players, but there is a huge long tail of smaller providers. One of the most significant characteristics of this layer is that it is a commodity layer. As Web 3.0 matures, an almost perfect market will emerge and squeeze out virtually all of the profit margin from the highest-volume services — and sometimes squeeze them into loss-leading or worse.
Aggregation services form the middle layer. These are the intermediaries that take some of the hassle out of locating all those raw API services by bundling them together in useful ways. Obvious examples today are the various RSS aggregators, and emerging web services marketplaces like the StrikeIron service.
Application services form the top layer, and this is where I believe the biggest, most durable profits will be found. These will not be like the established application categories we are used to, such as CRM, ERP or office, but a new class of composite applications that bring together functionality from multiple services to help users achieve their objectives in a flexible, intuitive and self-evident way.
Web 3.0 Technologies:
Web 3.0 is sometimes called Semantic Web, a term coined by Tim Berners Lee, the man who first invented www.
Web 3.0 will have 4 main features like a Semantic Web where a machine or robot can read a website or check our daily schedules; 3D Web-a virtual walk through unfamilier places without leaving one’s own seat; Media-centric searches understanding natural-lauguage queries or photos, and the Pervasive Web that’s everywhere-on your PC, on your cellphone, on your cloths, jewelry, your kitchen, bathroom and office. Web 3.0 is here for sure. But it has to be experienced.
What is Semantic Web?
The Semantic Web is an evolving extension of the World Wide Web in which the semantics of information and services on the web is defined, making it possible for the web to understand and satisfy the requests of people and machines to use the web content. It derives from W3C director Tim Berners-Lee's vision of the Web as a universal medium for data, information, and knowledge exchange.
Semantic Web promises to put a lot more intelligence — artificial intelligence — out there in the network of networks, and is certainly a step in the right direction
At its core, the semantic web comprises a set of design principles, collaborative working groups, and a variety of enabling technologies. Some elements of the semantic web are expressed as prospective future possibilities that are yet to be implemented or realized. Other elements of the semantic web are expressed in formal specifications. Some of these include Resource Description Framework (RDF), a variety of data interchange formats (e.g. RDF/XML, N3, Turtle, N-Triples), and notations such as RDF Schema (RDFS) and the Web Ontology Language (OWL), all of which are intended to provide a formal description of concepts, terms, and relationships within a given knowledge domain.
Features of Semantic web:
1) The Semantic Web is not just a single Web. There won't be one Semantic Web, there will be thousands or even millions of them, each in their own area. They will connect together over time, forming a tapestry. But nobody will own this or run this as a single service.
2) The Semantic Web is not separate from the existing Web. The Semantic Web won't be a new Web apart from the Web we already have. It simply adds new metadata to the existing Web. It merges right into the existing HTML Web just like XML does, except this new metadata is in RDF.
3) The Semantic Web is not just about unstructured data. In fact, the Semantic Web is really about structured data: it provides a means (RDF) to turn any content or data into structured data that other software can make use of. This is really what RDF enables.
4) The Semantic Web does not require complex ontologies. Even without making use of OWL and more sophisticated ontologies, powerful data-sharing and data-integration can be enabled on the existing Web using even just RDF alone.
5) The Semantic Web does not only exist on Web pages. RDF works inside of applications and databases, not just on Web pages. Calling it a "Web" is a misnomer of sorts — it's not just about the Web, it's about all information, data and applications.
6) The Semantic Web is not only about Artificial Intelligence (AI) , and doesn't require it. There are huge benefits from the Semantic Web without ever using a single line of artificial intelligence code. While the next-generation of AI will certainly be enabled by richer semantics, is not the only benefit of RDF. Making data available in RDF makes it more accessible, integratable, and reusable — regardless of any AI. The long-term future of the Semantic Web is AI for sure — but to get immediate benefits from RDF no AI is necessary.
7) The Semantic Web is not only about mining, search engines and spidering. Application developers and content providers, and end-users, can benefit from using the Semantic Web (RDF) within their own services, regardless of whether they expose that RDF metadata to outside parties. RDF is useful without doing any data-mining — it can be baked right into content within authoring tools and created transparently when information is published. RDF makes content more manageable and frees developers and content providers from having to look at relational data models. It also gives end-users better ways to collect and manage content they find.