Cyc Database
Vocabulary
E-Mail Comments to: opencyc-doc@cyc.com
Last
Update: 4/5/02
Copyright© 1996-2002. All rights reserved. See Terms of Usage.
Return to Documentation Contents
Return to Vocabulary Contents
Physical Tables
#$SISPhysicalSchema sis
physical schema
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Descriptions of mappings from a Structured
Information System (SIS) to a physical representation of it.
guid: bd5905d2-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$CommunicationConvention #$MathematicalOrComputationalThing
#$PhysicalTableSchema physical
table schema
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$PhysicalTableSchema
represent physical database tables. They are often referred
to as 'physical tables'. The current vocbulary does not
distinguish between the abstract structure, perhaps shared
by many copies, and the copies themselves, perhaps
containing different data. When representing a database
table, a 'logical schema', an instance of #$LogicalTableSchema,
is mapped to a physical schema. The logical schema is the
context for the axioms which interpret the physical schema.
The physical schema is associated with a physical database
(some instance of #$PhysicalDatabase).
guid: c10ae65f-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$CommunicationConvention
#$tableName table name
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$tableName TABLE
STRING) means that STRING is a string used as the name for
the physical database table TABLE.
guid: c10ae829-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$tableOfDB table of
d b
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$tableOfDB TABLE DB)
means that the physical table TABLE is part of the physical
database DB. A physical table may be part of only one
database, but a database may have many tables.
guid: c10ae68f-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$recordCount record count
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$recordCount TABLE
N) indicates that physical table TABLE has N records. This
information is used by DB-query applications in assessing
cost of DB calls. Assertions using this predicate are
usually updated by code at application initialization time.
guid: bd67c785-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
Physical Fields
#$Field-LogicalOrPhysical field
- logical or physical
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
The class of all fields, physical or logical, in
the schemas of structured information sources.
guid: bd5fc8eb-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$Thing
#$PhysicalField physical field
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
The collection of all CycL representations of
physical table fields.
guid: bd61fcb3-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$Thing
#$SchemaPF schema p f
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
RESULT is a #$PhysicalField in
the #$PhysicalTableSchema
ARG1, which represents the physical database field named ARG2.
guid: bd61f8c8-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryRelation #$IndividualDenotingFunction
#$ReifiableFunction
#$Individual
#$fieldName field name
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$fieldName ARG1 ARG2)
means that ARG2 is the name (name string) of the #$PhysicalField
represented by ARG1
guid: bd5bf14f-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$TupleInDataBase tuple
in data base
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Considering PropositionalInformationThings as
abstracted databases, a set of bindings for a set of fields
which belong together are a TupleInPIT. For example, in the
part of a grocery receipt which lists the items and the
price, each item-price pair is a TupleInPIT.
guid: bd58c573-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$Tuple
Logical Tables
#$SISLogicalSchema sis
logical schema
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances represent the propositions that define
the schema (not the actual content) of a structured
information source. For schemas for database tables, see the
spec #$LogicalTableSchema.
The axioms for interpreting a structured information source
are expressed as assertions involving instances of #$LogicalField,
which serve as prototypes for the values in the fields of
the info source. The actual content of the info source, to
the extent that this content is ever imported into the Cyc
KB, is represented as assertions in some instance of #$PropositionalInformationThing.
guid: bd63d200-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$PropositionalInformationThing
#$LogicalTable tabular
(structured information source)
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
The collection of all contexts (mts) in which the
actual content of a database table is represented. The
schema (defining information) for a #$LogicalTable will
be represented in an instance of #$LogicalTableSchema.
An instance of #$LogicalTable will
be related to an instance of #$LogicalTableSchema
with the predicate #$usesSchema.
guid: bd65aaa9-9c29-11b1-9dad-c379636f7270
direct instance of:
#$MicrotheoryType
direct specialization of:
#$PropositionalInformationThing #$IndexedInfoSource
#$DBContext db context
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
guid: bd58a7d0-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType #$MicrotheoryType
direct specialization of:
#$IndexedInfoSource #$Microtheory
#$LogicalTableSchema tables
(structured information sources)
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances represent the propositions that define
the schema (not the actual content) of a database table, or
other information sources that can be considered as abstract
tables. They are often referred to as 'logical tables'. The
axioms for interpreting a database table are expressed as
assertions involving instances of #$LogicalField,
which serve as prototypes for the values in the fields of
the table. The actual content of a database table, to the
extent that this content is ever imported into the Cyc KB,
is represented in some instance of #$LogicalTable.
guid: bd588004-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$PropositionalInformationThing #$IndexedInfoSource
#$physicalLogicalSchemaMap physical
logical schema map
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$physicalLogicalSchemaMap
PHYSICAL LOGICAL) indicates that PHYSICAL is a physical
table corresponding to the logical table LOGICAL.
guid: c10ae67a-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$SISContent sis content
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
The class of microtheories which represent the
information content of #$StructuredInformationSources.
guid: bd5a3a78-9c29-11b1-9dad-c379636f7270
direct instance of:
#$Collection
direct specialization of:
#$PropositionalInformationThing
#$usesSchema uses schema
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$usesSchema ?CONTENT
?SCHEMA) means that CONTENT (a #$LogicalTable or
other #$SISContent)
is defined/structured according to the relations represented
in the #$SISLogicalSchema SCHEMA.
guid: bd5e8bf3-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
Logical Fields
#$LogicalField lf
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$LogicalField are
also referred to as `#$SchemaLF terms', because they are
created with the #$IndividualDenotingFunction
#$SchemaLF. To
interpret fields of a table, we create terms to represent
the field and make assertions about them, treating them as
prototypes for the values of a given tuple. #$SchemaLF terms may be
used to write interpretation axioms for any information
source which can be treated as an abstract table.
guid: bd5ea3b5-9c29-11b1-9dad-c379636f7270
direct instance of:
#$RelationshipType
direct specialization of:
#$SchemaLF schema l f
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
RESULT is a #$LogicalField in
the #$LogicalTableSchema
ARG1, uniquely determined by the #$LogicalFieldAttribute ARG2.
guid: bd5ab49e-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryRelation #$ReifiableFunction
#$IndividualDenotingFunction
#$Individual
#$LogicalFieldAttribute logical
field attribute
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$LogicalFieldAttribute
are used as tags within the function #$SchemaLF to generate
terms that stand for a #$LogicalField of a
table. There is an informal convention - not enforced in
code - that the names of #$LogicalFieldAttributes
should begin with 'LF'. Many #$LogicalFieldAttributes
have rules associated with them that infer various kinds of
information about the resulting #$LogicalFields.
guid: bd58808d-9c29-11b1-9dad-c379636f7270
direct instance of:
#$RelationshipType
direct specialization of:
#$LFAttribute-Function l
f attribute - function
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$LFAttribute-Function
are functions which return instances of #$LogicalFieldAttribute.
guid: c0fd5a6e-9c29-11b1-9dad-c379636f7270
direct instance of: #$FunctionCategory
direct specialization of:
#$IndividualDenotingFunction #$ReifiableFunction
#$explicitFields explicit fields
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$explicitFields
PIT L-FIELD) means that L-FIELD is explicitly present in the
#$PropositionalInformationThing
PIT. A PropositionalInformation thing is typically the
content of some information source. If something is an #$explicitFields
of a source's PIT, we expect that the source has a binding
for that field, such as a field in a datbase table. There
may be other objects which are implicitly referred to by the
information source, but these are referred to with #$implicitFields.
guid: bd64be31-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$implicitFields implicit fields
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$implicitFields
PIT LF) indicates that LF is implicitly present in PIT. We
we expect a binding for that field to exist, although the
IBO whose meaning is represented by the PIT does not
explicitly state what the binding is. For example, in a
database of employees, there are explicit fields for names
of employees, but we represent the employee associated with
each record by an implicit logical field.
guid: bd5d520e-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$fields fields (binary predicate)
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$fields PIT
L-FIELD) indicates that the logical field L-FIELD is present
in PIT, either explicitly or implicitly. Typically, most
GAFs involving #$fields
are concluded from the more specific relations #$implicitFields
and #$explicitFields.
One can make a direct assertion in cases where it is unknown
if L-FIELD is implicit or explicit.
guid: bd680a9a-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
direct specialization of:
#$propositionalInfoAbout
#$logicalPhysicalFieldMap logical
physical field map
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$logicalPhysicalFieldMap
?PF ?LF) means that the #$LogicalField ?LF
is the information content of the particular #$PhysicalField,
?PF. See also #$physicalLogicalTableMap and #$physicalLogicalSchemaMap.
guid: bd5f2e12-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$keysOfTable keys
of table
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
The keys for tables using the #$LogicalTableSchema
ARG1 are the logical fields represented by the terms in the
#$TermSet ARG2.
guid: bd616ba1-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$LogicalFieldCategory logical
field category
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
guid: bd58c3ed-9c29-11b1-9dad-c379636f7270
direct instance of: #$SecondOrderCollection
direct specialization of:
#$RelationshipType
Composite Fields
#$componentFields component fields
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
The value of the #$LogicalField ARG1
can be partly decomposed into the value of the #$LogicalField ARG2.
guid: bd5c2935-9c29-11b1-9dad-c379636f7270
direct instance of: #$TransitiveBinaryPredicate
#$AsymmetricBinaryPredicate
#$FieldCombiningMethod field
combining method
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$FieldCombiningMethod
are methods for combining component #$LogicalField
instances into their composite fields.
guid: c10c218b-9c29-11b1-9dad-c379636f7270
direct instance of: #$CollectionType #$ObjectType
direct specialization of:
#$Collection
#$compositeFieldFormat composite
field format
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
This predicate is used to express how to either a)
derive the value of a #$compositeFields by combining the
values for two or more explicit fields, or b) derive the
values of #$containedFields by extracting them from one
explicitField. (#$compositeFieldFormat
FIELD METHOD LIST-O-FIELDS) means that the value of the #$LogicalField FIELD
is composed of the values of the fields in LIST-O-FIELDS,
according the the #$FieldCombiningMethod METHOD.
guid: bd6253e8-9c29-11b1-9dad-c379636f7270
direct instance of: #$TernaryPredicate
Assertions About Fields
#$informStatement inform statement
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$informStatement
MT PROP) means that the #$ELSentence-Assertible
PROP is true in the information context MT. Note that (#$informStatement
MT PROP) implies that (#$ist MT PROP).
guid: bd5c2cd8-9c29-11b1-9dad-c379636f7270
direct instance of: #$MicrotheoryDesignatingPredicate
#$MicrotheoryPredicate
#$BinaryPredicate
direct specialization of:
#$ist-Information
Decoding Fields
#$fieldCodes field codes
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$fieldCodes FIELD
VALUE MEANING) indicates that if the value of the logical or
physical field FIELD is VALUE, it should be interpreted to
mean MEANING.
guid: bd60cb78-9c29-11b1-9dad-c379636f7270
direct instance of: #$TernaryPredicate
#$ReifiedMapping reified mapping
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$ReifiedMapping
collect sets of code-denotation mappings, specified by
assertions involving #$codeMapping. #$usesMapping can be
used to specify an instance of #$ReifiedMapping
to interpret a particular field in a physical table.
guid: c10aeb11-9c29-11b1-9dad-c379636f7270
direct instance of:
#$Collection
direct specialization of:
#$CommunicationConvention
#$codeMapping code mapping
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$codeMapping MAP
CODE DENOTATION) specifies one mapping for the reified
mapping MAP. When a table uses MAP to interpret some field,
the value CODE in that field will be interpreted as
DENOTATION. DENOTATION will typically be a Cyc constant, but
it might be a string or a number.
guid: c10aeb35-9c29-11b1-9dad-c379636f7270
direct instance of: #$TernaryPredicate
#$usesMapping uses mapping
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$usesMapping
P-FIELD MAP) indicates that the physical field P-FIELD
should be interpreted with the set of mappings MAP.
guid: bd5a1f14-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
#$dependentMapping dependent mapping
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
The #$ReifiedMapping
ARG4 will be used to interpret the #$PhysicalField
ARG3 when the #$PhysicalField
ARG1 has the value ARG2.
guid: bd653b6a-9c29-11b1-9dad-c379636f7270
direct instance of: #$QuaternaryPredicate
#$fieldDependsOn field
depends on
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
The value of the #$LogicalField ARG1
depends on the value of the #$LogicalField ARG2.
guid: bd58df50-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
Field Formats
#$DatabaseDataFormat database
data format
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$DatabaseDataFormat
are data formats for physical database fields. Examples
include things such as the various possible formattings of a
social security number: as a 9-digit integer, a 9-char
string, or an 11-char string with two dashes, etc.
guid: c10c218c-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$CommunicationConvention
#$fieldDataFormat field
data format
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$fieldDataFormat
P-FIELD FORMAT) indicates that the data in the physical
field P-FIELD has the data format FORMAT.
guid: bd653781-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
Field Datatypes
#$DatabaseDatatype database datatype
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$DatabaseDatatype
are datatypes that database fields might be declared to
follow. If a field is marked as a particular type, e.g.,
DATE, the entries in that field must be dates.
guid: c10b5d55-9c29-11b1-9dad-c379636f7270
direct instance of:
#$ObjectType
direct specialization of:
#$AttributeValue
#$fieldDataType field
data type
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$fieldDataType
P-FIELD TYPE) means that the physical field P-FIELD has the
data type TYPE. It is possible for a person to update this
predicate at table-description time, but it is usually
preferable to update this automatically by examining the
database directly.
guid: bd6734c6-9c29-11b1-9dad-c379636f7270
direct instance of: #$BinaryPredicate
Proprietary Constants
#$ProprietaryConstant proprietary constant
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
Instances of #$ProprietaryConstant
and any assertions involving them will be omitted from
non-proprietary KBs and will not displayed in
non-proprietary applications. Typically, one would create
specs of #$ProprietaryConstant
to correspond to the owner of the proprietary information,
e.g. AcmeConstant for constants proprietary to Acme corporation.
guid: c10ada4d-9c29-11b1-9dad-c379636f7270
direct instance of:
#$Collection
direct specialization of:
#$Thing
Relevant Functions
#$Row row (relationship)
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
guid: c10c55e0-9c29-11b1-9dad-c379636f7270
direct instance of:
#$IndividualDenotingFunction
#$BinaryRelation #$Individual
#$CharOfHexFn char
of hex fn
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
(#$CharOfHexFn HEX)
returns the ascii character corresponding to HEX, where HEX
is a hexadecimal number between 0 and 255, represented as a
string of length 2 containing the digits 1 through F. Note
that many characters in that range are non-printing or may
be interpreted as control characters when displayed by some
programs. This function is useful in dealing with database
tables which use such characters (actually, binary values
masquerading as character fields) to encode other content.
guid: bd614095-9c29-11b1-9dad-c379636f7270
direct instance of: #$UnaryFunction #$IndividualDenotingFunction
#$Individual
#$DBObjectFn db
object fn
**COMMENT NOT REVIEWED**
**GAFs NOT REVIEWED**
guid: bd593685-9c29-11b1-9dad-c379636f7270
direct instance of: #$UnreifiableFunction
#$BinaryFunction #$Individual
Copyright© 1996-2002. All rights reserved. See Terms of Usage.