If information provided by this website is not sufficient you can contact support by opening a ticket here: Tickets System
State Oriented Sharing is the term that we use to describe the action of sharing content in relation with a defined state of some context, some object or some thing. The objects and things that are used as the context for the sharing act can be virtual, physical or physiological.
Here are few examples for objects and things that can be used as the sharing context and the related pattern for determine their state:
- Web page : state is set by page URL
- Web domain: state is set by the domain part of the URL
- Product in the supermarket or a shop: state is set by bar-code
- Article in a printed newspaper paper: state is set by newspaper name and the title of the articles
- Automatic notifications in a train: state is set by code that identify the specific train line or by identifier on the ticket
- Some view, e.g Eifel tower: state is set by indexed image
- Song in the radio: state is set by the song title
- Noise of bus: state is set by sound signature
- Heartbeat rate: state is set by physical measurement of the heartbeat
- Some location: state is set by GPS info
State Oriented Sharing is therefore sharing of content (basic, or complex) in relation with the state of some context. The information will be presented when: State occur and User belongs to peers group with whom information has been shared.
Content Glass platform provide the means for sharing content in the form of Widgets. Widgets are mini-application and can handle basic information such as text, image, video, iframe of other website but can also handle some logic that provide some interaction with the users that share the content. For example shared shopping list or chat widget.
Content Glass provides various widgets on its social tools (see FAQ about social tools), and it also provides an API that let developers and service provides or application providers, create their own widgets and pack those widgets in libraries that can be loaded into Content Glass social tools.
Here are some examples of widgets:
- TextBox: simple text box for sharing plain text either offline or online (see FAQ about online Vs Offline sharing).
- Notes: styled notes for sharing simple text.
- IFrame: embedding iframe that show other website or web-app within the website on which CG is runnig.
- Shopping List: A widget for eCommerce for managing interactive shared list that can be used for bookmarking and/or transfer into cart.
- Chat: A widget with basic text, voice and video chat.
- Form connector: a widget that knows to attach with web-form, and allow sharing parties to fill the form together.
- Co-Browsing, Co-Reading etc': widgets that allow on-line experience of browsing, reading docs, watching slide-shows together in real-time. We call these widgets Connectors and these are of course small application that manage some interaction with and between the sharing peers.
- Expert Glass: a widget that when placed on a website it makes its owner an "expert" of Experts-Glass network in the context of website ir app. As expert user can receive queries answer those queries and get into interactive on-line session with other users that need some help, for example need to know what is the best product for them. As you can see this widget is an application in itself that function in conjunction with the broder Expert Glass application.
As you can see from thsi short list, then we talk about Content Glass Widgets we menas small-application that can have basic or complex functionality and are responsible for managing the data that is being shared.
For developers, Content Glass provide a platform for creating widgets that uses the Content Glass fraework for sharing and widgets management. In other words, developers can create their own widgets on top of content glass sharing platform and services.
Social Tools are ready made applications provided by Content Glass based on Content Glass platform. Social tools capture various scenarios of State Oriented Sharing. Content Glass currently have the following social tools and more are planed or in development but not exposed yet in the website:
Content Glass Button
Content Glass Browser plugin
The browser plugin is similar to CG-Button however it provide the same functionality without Website owner need to install the button script. Instead users install the plugin on their browser and the plugin provide the same functionality, including the ability to detect custom libraries set for specific website by special meta tag. Using the plugin users can share widgets on top of websites and share the widgets with their friends.
this tool is a bookmarklet that when clicked it inject Content Glass within thecurrently running web page. The injected script creates CG-Button as if presented when using a button that was installed directly, or as when using the browser plugin.
Expert glass is on-demand network of virtual advisory or consulting where users that wants to be in the role of "expert" can set a special widget on the website. The special widget is provided (for example) by CG-Button, when permitted by website. When the widget is set on the website it is connected with background system that makes this widget a proxy for communicating with other visitors of website that may request some help or need some advisory or consulting. Expert Glass involve another widget named ExpertsToolbar that is dynamically rendered on a website by setting special div (like this: <div cgExpertsToolbar="true"></div>). While Experts-Toolbar let users select among active experts and send queries to the network of experts, the Experts Glass widget handle the interaction between users that include both offline and/or on-line interaction.
To summarize, social tools are State Oriented Sharing apps that can be extended. For example adding more widgets that can be used for collaboration by Expert-Glass on-line or offline session. Content Glass is planing to have more tools and/or extending current tools to different environments.
Content Glass widgets are the UI by which users share information with each other. The information can be shared in an offline or on-line mode. These mode are complementary to each other. Lets take an example. User set a TextBox widget for sharing some text and put his friend in the peers group for this widget. Both users are now able to see the TextBox when getting in the same website (or page, depends on scope). This is offline mode. Offline sharing assume that uses are no interconnect with each other in real-time.
On-line sharing on the contrary assumes that users are interconnected in real-time with each other so that changes in the shared content are passed between peers in real-time. Let's go back to the TextBox, in the case of on-line sharing once one user change the text, the other will see the text changing in real-time. Lets see few more examples:
Chat widget is maybe the most obvious case of on-line sharing.
Reading PDF together - a widget can provide co reading experience. So both parties (or group of peers) can browse PDF pages at the same time. Let's put it in realistic Expert-Glass scenario , assuming expert glass is acting on a website that provide legal advice, then using the Co-reading a lawyer can browse a contract (saved as PDF) together with the the person that seek for advice, and explain to him/her the implications of different sections in the contract doc.
Form connector: how many time have you seen a web form and felt hopeless? With Form Connector widget you can get help from friend (or Advisor - Expert Glass) and fill the web form together on-line.
Selecting products together: Assuming that two brothers want to prepare a birthday party to shared friend. With the Shopping-List widget (and possibly combined with Co-Browsing) they can visit a web store and prepare a list of items they would like to buy. The list is shared both off-line and on-line so they can both build the list on-line, and leave it to another friend, currently offline to add items or change the list. Once list is ready one of them can sent it to shopping cart.
Content Glass as part of its vision aim to provide State Oriented Sharing platform from multiple environments in order to cover as much as possible situations and scenarios from human life. This includes desktops, mobile and wearable devices and in the future also controllers.
When discussing environments one can distinguish between platforms (operation systems, programming language etc') and functional environments. For our purpose we refer to 'environment' in term of a nature of specific types or patterns of state oriented sharing apps. Web for example which is broad environment may include sub divisions of more specialized environments for whom we would like to contribute some more specialized patterns of State Oriented Sharing methodology. Content Glass is intent to provide its API so it can be used on various platforms and for multiple environments
Here is a list of platforms and environments CG is planed to handle in the near and far future:
Platforms: Web programming, Androin, FirefoxOS, iOs, GM Tooltik , Tizen, Java, .C#, and other wearable and infotainment platforms.
Website: for example installing CG-Button on various websites
eCommerce sites: We prepare special widgets library for this environment with aim to use it together with Expert-Glass
Advisory boards: candidate for Expert-Glass
Mobile apps: The main stream for Object Glass, Location Glass and Place glass patters (see FAQ about Glass Patterns)
Wearable apps: Sub section of mobile apps with special focus on using physical measurements as the sharing context.
Vehicle Infotainment systems: We plan to prepare special library of widgets and reference apps for shared oriented apps that can be used on car's infotainment systems.
Desktop: Especially in relation with Desktop Glass pattern.
Glass patterns refer to different types or behaviour pattern of state oriented sharing apps. This is not a scientific term, only something that try to wrap some general nature of an application. Here are some examples:
- Website Glass: State Oriented Sharing App (SOSA) the share content in the context of website and web domains, using the URL to produce the state Id of the context (the website).
- Object Glass: SOSA for sharing content in relation with objects and things that can be identified by some code or some representation of the object that can be formulated into code (for example indexed image of the object).
- Place Glass: this pattern is not other then object glass (or website glass) but it is related with sharing that occur in the context of some place. For example an automatic system in train that 'share' multilingual translations for automatic notifications and messages for passengers. Place Glass many time tend to have ad hoc dynamic peers group to represent the group of users currently in place.
- Location Glass: this pattern usually use or add the location info as another parameter used to compose the state-id of sharing context.
- Application glass: this pattern refer to apps that uses the CG API internally so that application is combined with state oriented sharing capabilities.
- Device Glass: reffer to CG apps that uses the device-glass technology in order to provide sharing of resources directly from the desktop (or other personal device)
Content Glass services are web based services given (usually on this website) on top and in relation with content glass content and apps. Most of the services are optional and Content Glass can be used without those services. However services provide high level of management shared content in relation with as asset (e.g, website). In additions some of the services provide functionality that utilize the content gathered by CG system in relation with an asset. Some of the services are free other are not.
- Dashboard: Provide remote management of shared content for both users and providers (each audience has its own version). The dashboard provide for example the ability to delete multiple widgets from one central place or managing peers-groups.
- Analytics: A service that provide aggregated statistical data based on content that was shared in relation with some application or some web asset.
- Context Interaction: Set of services that deals with possible interaction between content shared by content glass and the underline context. On of the implementation is for example contextual ads for website, that provide the means for service personalized ads on website based on the content of widgets currently shared and viewed by a user.
- Application manager: this service is used by developers to define and manage Content Glass applications.
- Markers Glass service: The backend service of markers-glass framework. The service manage the interaction between Advertisers and Publishers of the markers-glass framework.
- Experts glass Service: The backend service of Experts Glass framework. The service is mainly deals with management of expert profiles and provide feature for locationg experts for a given category based on their previous rating.
Content Glass technology combines multiple software methodologies and algorithms which are all part of the Content Glass system and filed by Content Glass provisional and PCT patents.
- State Oriented Sharing: This is the major methodology for sharing content as related with the state of objects and things (sharing-context). State oriented sharing mechanism combine both client-side techniques and server-side techniques in order to provide the platform and API for developing CG apps.
- Search for Glass: A state-oriented-sharing technology for sharing widgets in the context of search engines. The technology also provide a mechnism for adding new semantics into search results by creating virtual-widgets made of grouping of previously found items.
- Experts Glass: This technology provide the means for ad hoc virtual consulting and/or advisory networks, using special CG widgets that allow offline and on-line collaboration between users.
- Device Glass: A technology for sharing resources directly from personal desktop or personal device using special type of widgets call Resource Proxy.
- Desktop Glass: this technology utilize Device Glass and provide provide special technique for creating interactive and collaborative mini-portals from resources located on the desktop.
- Computational SaaS: This technology will be used in the future to create SaaS like state oriented sharing apps in which personal information is not hold by the service itself but by facility that is under owner responsibility. Content Glass use this technology to provide for example personal storage for widgets and personal ownership of data when interacting with services via Service Port widgets.
Object Glass is a pattern of Content Glass State Oriented Sharing app in which widgets are associated with objects through an identifier that represent specific state of the object.
For example assuming that we would like to create state printed sharing app that allow users to share comments in related with articles on printed newspaper: the newspaper is the object, the title of the article can be used as state identifier and a comment (note or text box) widget can be shared in relation with specific article by associating its state Id parameters to the title. Sharing parties then can see the comment when referring in app to this specific newspaper, and specify the title of the article article. The entire process can use various scanning on manual entry or select from multiple choices box - what more efficient.
No, on the contrary. By default all widgets created with CG button are not public so that it will not be used as spamming tool. By default a widget can be shared only by closed group of peers. There are few exceptions:
1. Website admin of website where CG is installed can get a permission that let them make widget public. Once having this permission the admin can move the widget to public layer, which actually make the widget shared in public.
2. There is a feature call Interest group that let group subscribers share widgets in public but only among them. It means that only subscribers of the group will see the widget.Group subscribes can share widgets also without having a contact/connection relation between them. Interest groups are created only for special cases, for example websites where CG is installed can have interest group. Another example are the groups deals with sensitivity to some type of food, that let users share their self-experience with dishes served in restaurant. In the future shared-widgets will also combine the features of Glass-For-Search that let group members share widgets in corresponding with search term on search engine pages (e.g. google.com).
3. Custom applications can set widget as public where the application is installed. For example the share-poem application, that let users watch live (or offline) the process of creating poems, set the widget you create on the sharing board as public. This is why users go to share-poem page can see the widget and do not need to log-in.
Yes. You can use CG-Button and the built-in widgets for free. Note however that third party providers may charge for use of other CG apps and/or other custom Widgets prepared by them. Providers must provide a notification and get customer consent before charging for CG based app/widget.
Yes. Developers may register and get one of the available CG API libraries for the purpose of creating CG apps and.or developing custom Widget libraries. In the future we plan to launce usage based pricing packages hgat will be applied to commercial running applications. Note however that packages are not effective yet and will not be applied ntill a new announcment will provide in advance..