an ontology designer makes these decisions based on the structural properties of a class.
Instructables - Make, How To, and DIY - 2 views
www.instructables.com
howto tutorials projects design reference crafts OpenSource electronics internet device
shared by Tiberius Brastaviceanu on 22 Dec 11
- Cached
19More
What is an ontology and why we need it - 1 views
-
an ontology is a formal explicit description of concepts in a domain of discourse (classes (sometimes called concepts)), properties of each concept describing various features and attributes of the concept (slots (sometimes called roles or properties)), and restrictions on slots (facets (sometimes called role restrictions)). An ontology together with a set of individual instances of classes constitutes a knowledge base. In reality, there is a fine line where the ontology ends and the knowledge base begins.
- ...16 more annotations...
-
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.
-
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.
-
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?
-
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
Value Equation Tutorial - Google Slides - 2 views
44More
Design Like No One Is Patenting - How SparkFun Stays Ahead of the Pack - 0 views
-
Electronics supplier SparkFun designs dozens of products a year and they haven’t patented a single one. It’s worked out pretty well so far.
-
makes its living by shipping kits and components like bread boards, servo motors and Arduino parts to a mixture of students, hobbyists, and professionals making prototypes
-
the company has made its name is in a stable of its own custom parts and kits, the designs for which it gives away for free.
- ...40 more annotations...
-
“We find that people will copy your design no matter what you do,” she says. “You might as well just play the game and go ahead and innovate. It’s fun, it keeps us on our toes.”
-
the open hardware model means that SparkFun’s existence depends not on any particular product, but on an ongoing relationship with customers that’s not too dissimilar to the loyalty commanded by a fashion house.
-
You can learn a lot about what a company cares about by looking at what they give away and what they protect.
-
SparkFun’s actual value is in the community of fans and loyal customers that keep coming back, and the expertise under its roof in servicing their needs.
-
“We try to do small runs and order in small quantities. Especially something that’s going to be obsolete quickly.”
-
along with inventory and CMS management, tries to predict demand for different components and ensure they get ordered with sufficient lead time to account for how long it takes to get there.
-
the innovation (revisions and new releases) here at SparkFun is organic and not planned,” says Boudreaux, “But we do a few things to make sure we are keeping up.”
-
monitors all costumer feedback from emails to the comment section that is present on every page of the company’s site. They also ensure that team members have time to tinker in the office, write tutorials, and visit hackerspaces and maker events. “For us, designing (and revising) widgets is the job.”
-
“They eat these products up, even if the products are not ready for the mainstream & educator community due to minimal documentation or stability.”
-
symbiotic relationship with these early adopters, where feedback helps SparkFun revised and improve products for use by the rest of the community
-
“There’s balance in everything,” says Boudreaux, “Innovation does not necessarily need speed in order to create valuable change. Sometimes innovation works at a slower pace, but that does not mean it is any less valuable to those that benefit from it, and we are constantly balancing the needs of two very different customers.”
-
“We have to be willing to kill ideas that don’t work, take a lot of tough criticism, and move fast. If we stay agile, we stay relevant.”
2More
Pitching Your Product - SparkFun Electronics - 0 views
-
The product itself including design, quality, documentation, uniqueness. The market and competition. Feasibility.