Difference between revisions of "Haystack"

From Bauman National Library
(External links)
(What is Haystack)
Line 6: Line 6:
  
 
Similar to the Chandler PIM, the Haystack system unifies handling different types of unstructured information. This information has a common representation in RDF that is presented to users in a configurable human-readable way.
 
Similar to the Chandler PIM, the Haystack system unifies handling different types of unstructured information. This information has a common representation in RDF that is presented to users in a configurable human-readable way.
 +
 +
== Why do we need Haystack ==
 +
 +
Macro trends in technology are making it increasingly cost effective to instrument and collect data about the operations and energy usage of buildings. We are now awash in data and the new problem is how to make sense of it. Today most operational data has poor semantic modeling and requires a manual, labor intensive process to "map" the data before value creation can begin. Pragmatic use of naming conventions and taxonomies can make it more cost effective to analyze, visualize, and derive value from our operational data.
  
 
== Adenine ==
 
== Adenine ==

Revision as of 20:06, 16 January 2017

Project Haystack is an open source initiative to streamline working with data from the Internet of Things. We standardize semantic data models and web services with the goal of making it easier to unlock value from the vast quantity of data being generated by the smart devices that permeate our homes, buildings, factories, and cities. Applications include automation, control, energy, HVAC, lighting, and other environmental systems.

What is Haystack

Haystack was a project at the Massachusetts Institute of Technology to research and develop several software applications around personal information management and the Semantic Web. The most notable of those applications is the Haystack client, a research personal information manager (PIM) and one of the first to be based on semantic desktop technologies. The Haystack client is published as open source software under the BSD license.

Similar to the Chandler PIM, the Haystack system unifies handling different types of unstructured information. This information has a common representation in RDF that is presented to users in a configurable human-readable way.

Why do we need Haystack

Macro trends in technology are making it increasingly cost effective to instrument and collect data about the operations and energy usage of buildings. We are now awash in data and the new problem is how to make sense of it. Today most operational data has poor semantic modeling and requires a manual, labor intensive process to "map" the data before value creation can begin. Pragmatic use of naming conventions and taxonomies can make it more cost effective to analyze, visualize, and derive value from our operational data.

Adenine

Haystack was developed in the Resource Description Framework (RDF) -aware dynamic language Adenine which was created for the project. The language was named after the nucleobase adenine and is a scripting language that is cross-platform. It is the perhaps the earliest example of a homoiconic general graph (rather than list/tree) programming language. A substantial characteristic of Adenine is that this language possesses native support for the Resource Description Framework (RDF). The language constructs of Adenine are derived from Python and Lisp. Adenine is written in RDF and thus also can be represented and written with RDF based syntaxes such as Notation3 (N3).

References

External links