Skip to main content

Home/ Sensorica Knowledge/ Group items tagged anticipation

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Kurt Laitner

Mihai Nadin - Wikipedia, the free encyclopedia - 0 views

en.wikipedia.org/Mihai_Nadin

*mihainadin value anticipation semiotics possiblism

shared by Kurt Laitner on 17 Jan 13 - No Cached
  • Kurt Laitner on 17 Jan 13
     
    Another clever Romanian - important figure to look into. Anticipation interesting in same way as futureful and other concepts from Jarno Kopenen - semiotic thread runs though Pierre Levy's work as well on IEML
Kurt Laitner

Intel CTO: Smart Sensors, Wearable Tech Coming Soon - Hardware - - 0 views

www.informationweek.com/...240146405

big data sensors hard and soft

shared by Kurt Laitner on 28 Jan 13 - No Cached
  • He described the process in terms of not only "hard sensors" that track physical attributes such as light, heat, pressure and motion, but also "soft sensors" such as a user's calendar, social network activity and Web browsing habits. "What context awareness does is collect all of that, some of which is up-to-the-minute on the physical sensors and some of which is accumulated incrementally over a long expanse of time through these soft senses, to create devices that really anticipate your needs," he said.
  • Kurt Laitner on 28 Jan 13
     
    hard and soft sensors creating context awareness
Tiberius Brastaviceanu

What is an ontology and why we need it - 1 views

protege.stanford.edu/...ntology101-noy-mcguinness.html

protege ontologies infrastructure tutorial

shared by Tiberius Brastaviceanu on 29 Jul 12 - Cached
  • an ontology designer makes these decisions based on the structural properties of a class.
  • 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.
  • Classes describe concepts in the domain
  • ...16 more annotations...
  • 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:
  • 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.
  • some fundamental rules in ontology design
  • 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.
1 - 3 of 3
Showing 20▼ items per page