![]() Tag defs are used to formally define tag names. ![]() key: definition for a feature specific name such as filetype:jsonĬollectively we call tags and conjuncts our terms.conjunct: definition for a set of tags such as hot-water.There are three types of definitions determined by the format of their symbol name: For example, we can model that a steam boiler produces steam: def: ^steam-boilerĪssociations enable inference when querying knowledge from Haystack data. We call these relationships associations. In Haystack we build out this ontological information using symbolic tags on defs to cross-reference other defs. Ontologies extend taxonomies to include relationships between concepts. Subtyping allows us to infer semantics beyond the presence of tags. For example we define that water is a subtype of liquid. Subtyping allows us to relate terms as hyponyms and hypernyms. We use the is tag in our defs to organize our meta-model into a taxonomy through subtyping. Each of those tags now can be reflected to its definition. This allows to us to precisely define our vocabulary. As a first step we create a def for each of our tag names (or conjuncts for sets of tag names). ![]() The real power of Haystack is unleashed when we use the def framework to formally define our tag names. It is like JSON but with a richer type system since we have first class types for dates, times, references, etc. Even without defs, Haystack provides a nice framework for structuring and exchanging data. Lets start at the bottom: you can use the Haystack data model and file formats without any defs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |