Link to this page
Brinell Test Ontology-EMMO
Acronym | BTO-EMMO |
Visibility | Public |
Description | Brinell Test Ontology (BTO) has developed for representing the Brinell testing process, testing equipment requirements, test pieces charactristics, and related testing parameters and their measurement procedure according to DIN EN ISO 6506-1 standard. Versions info: V2 developed using BFO+CCO top-level ontologies. V3 developed using EMMO+CHAMEO top-level ontologies. V4 developed using PROVO+PMDco top-level ontologies. V5 developed using BFO+IOF top-level ontologies. |
Status | Alpha |
Format | OWL |
Language | English |
Contact | Hossein Beygi Nasrabadi, hossein.beygi-nasrabadi@bam.de |
Categories | Other |
No views of BTO-EMMO available
Id | https://w3id.org/emmo#EMMO_3e7add3d_e6ed_489a_a796_8e31fef9b490
https://w3id.org/emmo#EMMO_3e7add3d_e6ed_489a_a796_8e31fef9b490
|
---|---|
Preferred Name | Data |
Definitions |
A causal object whose properties variation are encoded by an agent and that can be decoded by another agent according to a specific rule.
EncodedData is the class where inventions that don't actually exist whould be placed.
For example, the blueprint of a bridge is an encoded data. When the bridge will be built, than the blueprint will also be a semiotical entity.
Another example is Superman, that exists only as a set of magazines, drawings, novels, movies, but not in the real world.
Variations in data are generated by an agent (not necessarily human) and are intended to be decoded by the same or another agent using the same encoding rules.
Data are always generated by an agent but not necessarily possess a semantic meaninig, either because it's lost or unknown or because simply they possess none (e.g. a random generation of symbols). A data object may be used as the physical basis for a sign, under Semiotics perspective.
We call "decoding" the act of recognise the variation according to a particular rule and generate another equivalent schema (e.g. in the agent's cognitive apparatus, as another form of data).
We call "interpreting" the act of providing semantic meaning to data, which is covered by the semiotic perspective.
|
Synonyms |
EncodedContrast
EncodedData
|
Type | http://www.w3.org/2002/07/owl#Class |
All Properties
definition | A causal object whose properties variation are encoded by an agent and that can be decoded by another agent according to a specific rule. EncodedData is the class where inventions that don't actually exist whould be placed. For example, the blueprint of a bridge is an encoded data. When the bridge will be built, than the blueprint will also be a semiotical entity. Another example is Superman, that exists only as a set of magazines, drawings, novels, movies, but not in the real world. Variations in data are generated by an agent (not necessarily human) and are intended to be decoded by the same or another agent using the same encoding rules. Data are always generated by an agent but not necessarily possess a semantic meaninig, either because it's lost or unknown or because simply they possess none (e.g. a random generation of symbols). A data object may be used as the physical basis for a sign, under Semiotics perspective. We call "decoding" the act of recognise the variation according to a particular rule and generate another equivalent schema (e.g. in the agent's cognitive apparatus, as another form of data). We call "interpreting" the act of providing semantic meaning to data, which is covered by the semiotic perspective. |
---|---|
altLabel |
EncodedContrast
EncodedData
|
prefLabel | Data
|
label | Data
|
comment | Variations in data are generated by an agent (not necessarily human) and are intended to be decoded by the same or another agent using the same encoding rules.
Data are always generated by an agent but not necessarily possess a semantic meaninig, either because it's lost or unknown or because simply they possess none (e.g. a random generation of symbols). A data object may be used as the physical basis for a sign, under Semiotics perspective.
We call "decoding" the act of recognise the variation according to a particular rule and generate another equivalent schema (e.g. in the agent's cognitive apparatus, as another form of data).
We call "interpreting" the act of providing semantic meaning to data, which is covered by the semiotic perspective.
EncodedData is the class where inventions that don't actually exist whould be placed.
For example, the blueprint of a bridge is an encoded data. When the bridge will be built, than the blueprint will also be a semiotical entity.
Another example is Superman, that exists only as a set of magazines, drawings, novels, movies, but not in the real world.
|
wikipediaReference | |
elucidation | A causal object whose properties variation are encoded by an agent and that can be decoded by another agent according to a specific rule.
|
isDefinedBy | |
prefixIRI | EMMO_3e7add3d_e6ed_489a_a796_8e31fef9b490
|
seeAlso | |
subClassOf | |
type | |
example | A Radio Morse Code transmission can be addressed by combination of perspectives.
Physicalistic: the electromagnetic pulses can be defined as individual A (of type Field) and the strip of paper coming out a printer receiver can be defined as individual B (of type Matter).
Data: both A and B are also DiscreteData class individuals. In particular they may belong to a MorseData class, subclass of DiscreteData.
Perceptual: B is an individual belonging to the graphical entities expressing symbols. In particular is a formula under the MorseLanguage class, made of a combination of . and - symbols.
Semiotics: A and B can be signs if they refers to something else (e.g. a report about a fact, names).
A signal through a cable. A sound wave. Words on a page. The pattern of excited states within a computer RAM.
|
disjointWith |
Delete | Subject | Author | Type | Created |
---|---|---|---|---|
No notes to display |
- Problem retrieving properties:
Notes
Add NCBO Web Widgets to your site for BTO-EMMO
Widget type | Widget demonstration |
---|---|
|
Step 2: Follow the Instructions
For more help visit NCBO Widget Wiki |
|
Example 1 (start typing the class name to get its full URI)
Example 2 (get the ID for a class) Example 3 (get the preferred name for a class) Step 2: Follow the Instructions
For more help visit NCBO Widget Wiki |
|
Step 2: Follow the InstructionsCopy the code below and paste it to your HTML page <iframe frameborder="0" src="/widgets/visualization?ontology=BTO-EMMO&class=https%3A%2F%2Fw3id.org%2Femmo%23EMMO_0e03a375_8af8_46db_88ae_a45fe2d2940f&apikey=YOUR_API_KEY"></iframe> For more help visit NCBO Widget Wiki |
|
Step 2: Follow the InstructionsCopy the code below and paste it to your HTML page <link rel="stylesheet" type="text/css" href="/widgets/jquery.ncbo.tree.css"> <script src="/widgets/jquery.ncbo.tree-2.0.2.js"></script> <div id="widget_tree"></div> var widget_tree = $("#widget_tree").NCBOTree({ apikey: "YOUR_API_KEY", ontology: "BTO-EMMO" }); You can also view a detailed demonstration For more help visit NCBO Widget Wiki |