Group items tagged

Basic Myograph for rings and strips 1 $7,385

what if people saw the patents

aying dormant

new ways that we can incorporate these patents into new products?"

Marblar also obtained access to many patents from the University of Pennsylvania and from ETRI,

The site also partnered with Samsung,

or its potential to bring the patents of Marblar users to life.

Any idea that Samsung likes could find its way into Samsung technology, with 10 percent of the royalties going to the Marblar users who brought it to life

The contributors to a Marblar project might be helping an inventor out of the goodness of their heart, but they also stand to gain if a particular product gets the green light. Marblar rewards users who provide useful data or information by giving them "marbles," the websites namesake currency.

In the spirit of crowdsourcing, other Marblar users can help out a particular inventor whose idea they want to see come to life.

"As you submit product ideas and contribute market data or technical data, you get more marbles," Perez said.

The more marbles a person earns, the bigger the cut he or she gets in the royalty check if the product makes it to market.

Another website, Quirky

have a store dedicated to selling its users products

patents have become more associated with litigation than productivity.

"Patent trolls buy up patents to extract money, with no intention of actually creating a product," he said. "Marblar is like the anti-troll. We're looking for new ways to commercialize."

A class can have subclasses that represent concepts that are more specific than the superclass.

Here we discuss general issues to consider and offer one possible process for developing an ontology. We describe an iterative approach to ontology development: we start with a rough first pass at the ontology. We then revise and refine the evolving ontology and fill in the details. Along the way, we discuss the modeling decisions that a designer needs to make, as well as the pros, cons, and implications of different solutions.

In practical terms, developing an ontology includes: �         defining classes in the ontology, �         arranging the classes in a taxonomic (subclass–superclass) hierarchy, �         defining slots and describing allowed values for these slots, �         filling in the values for slots for instances.

We can then create a knowledge base by defining individual instances of these classes filling in specific slot value information and additional slot restrictions.

Slots describe properties of classes and instances:

some fundamental rules in ontology design

There is no one correct way to model a domain— there are always viable alternatives. The best solution almost always depends on the application that you have in mind and the extensions that you anticipate. 2)      Ontology development is necessarily an iterative process. 3)      Concepts in the ontology should be close to objects (physical or logical) and relationships in your domain of interest. These are most likely to be nouns (objects) or verbs (relationships) in sentences that describe your domain.

how detailed or general the ontology is going to be

what we are going to use the ontology for

concepts in the ontology must reflect this reality

We suggest starting the development of an ontology by defining its domain and scope. That is, answer several basic questions: �         What is the domain that the ontology will cover? �         For what  we are going to use the ontology? �         For what types of questions the information in the ontology should provide answers? �         Who will use and maintain the ontology?

plan to use

domain

If the people who will maintain the ontology describe the domain in a language that is different from the language of the ontology users, we may need to provide the mapping between the languages.

One of the ways to determine the scope of the ontology is to sketch a list of questions that a knowledge base based on the ontology should be able to answer, competency questions

These competency questions are just a sketch and do not need to be exhaustive.

We heard that the government should be more focussed on helping innovative firms to grow and, particularly, on serving the needs of small and medium-sized enterprises (SMEs)

greater cooperation with provincial programs

innovation support is too narrowly focussed on R&D – more support is needed for other activities along the continuum from ideas to commercially useful innovation

more productive and internationally competitive economy

whole-of-government program delivery vehicle – the Industrial Research and Innovation Council (IRIC)

SR&ED program should be simplified

includes non-labour costs, such as materials and capital equipment, the calculation of which can be highly complex

the base for the tax credit should be labour-related costs, and the tax credit rate should be adjusted upward

fund direct support measures for SMEs

promoting the growth of firms

facilitating access by such firms to an increased supply of risk capital at both the start-up and later stages of their growth.

building public–private research collaborations

National Research Council (NRC) should become independent collaborative research organizations

become affiliates of universities

create opportunity and demand for leading-edge goods

encouragement of innovation in the Canadian economy should become a stated objective of procurement policies and programs.

the government needs to establish business innovation as a whole-of-government priority

put innovation at the centre of the government's economic strategy

Innovation Advisory Committee (IAC) – a body with a whole-of-government focus that would oversee the realization of our proposed action plan, as well as serve as a permanent mechanism to promote the refinement and improvement of the government's business innovation programs going forward.

focus resources where market forces are unlikely to operate effectively or efficiently and, in that context, address the full range of business innovation activities, including research, development, commercialization and collaboration with other key actors in the innovation ecosystem

the closer the activity being supported is to market, and therefore the more likely it is that the recipient firm will capture most of the benefit for itself.

specific sectors

of strategic importance

concentrated in particular regions

succeed in the arena of global competition

let's consider the terminology we use for events

event triggers

triggers

in response

event handler

event

onInstall function

onOpen function.

onEdit function

the simple event handlers are restricted in what they are permitted to do:

The spreadsheet containing the script must be opened for editing

cannot determine the current user

cannot access any services that require authentication as that user

Calendar, Mail and Site are not anonymous and the simple event handlers cannot access those services.

can only modify the current spreadsheet. Access to other spreadsheets is forbidden.

see Understanding Permissions and Script Execution.

The onOpen function runs automatically when a user opens a spreadsheet.

add custom menu items to the spreadsheet's menu bar.

onEdit function runs automatically when any cell of the spreadsheet is edited.

record the last modified time in a comment on the cell that was edited.

The onInstall function is called when a script is installed from the Script Gallery.

setting up custom menus for the user.

the script can call onOpen from onInstall.

Installable event handlers are set on the Triggers menu within the Script Editor, and they're called triggers in this document.

When a specific time is reached

When a form is submitted

When a Spreadsheet is edited

When a Spreadsheet is opened.

They can potentially access all services available to the user who installed the handler.

are fully-capable scripts with none of the access limitations of simple event handlers

may not be able to determine which user triggered the event being handled

The spreadsheet containing the script does not have to be open for the event to be triggered and the script to run.

You can connect triggers to one or more functions in a script. Any function can have multiple triggers attached. In addition, you can add trigger attributes to a function to further refine how the trigger behaves.

When a script runs because of a trigger, the script runs using the identity of the person who installed the trigger, not the identity of the user whose action triggered the event. This is for security reasons.

Installing an event handler may prompt for authorization to access

An event is passed to every event handler as the argument (e). You can add attributes to the (e) argument that further define how the trigger works or that capture information about how the script was triggered.

an example of a function that sends email to a designated individual containing information captured by a Spreadsheet when a form is submitted.

With Google Apps, forms have the option to automatically record the submitter's username, and this is available to the script as e.namedValues["Username"]. Note: e.namedValues are only available for Google Apps domains and not for consumer Google accounts.

The available attributes for triggers are described in the following tables.