PropertyOf Relation Mention
(Redirected from Property Relation Mention)
Jump to navigation
Jump to search
A PropertyOf Relation Mention is a Relation Mention of a PropertyOf Relation.
- AKA: Property Relation Mention, Entity Property Relation Mention, Entity Property Mention.
- Context:
- In English, it can:
- include an Adjective, such as big, red, winged, etc.
- have the Semantic Relation Mention Pattern of “ADJ NN”.
- It can be an Object Function in a Object-Oriented Programming Paradigm.
- In English, it can:
- Example(s):
- “A rainbow is multicolored.” (PropertyOf(rainbow, multicolored) ⇒ True)
- “I saw a multicolored rainbow today.” (PropertyOf(rainbow, multicolored) ⇒ True)
- “The black cat lept onto the sofa.” (PropertyOf(cat, black) ⇒ True)
- “The cat weighed in at 6kg.” PropertyOf(6kg, cat) ⇒ True.
- “My cat is 5 years old” PropertyOf(5years,cat) ⇒ True.
- …
- Counter-Example(s):
- “Socrates is mortal.” (a Subsumption Relation Mention)
- “A car has wheels.” (a Meronomy Relation Mention; aka: Part-Of/Composed-Of relationship)
- “John Smith swapped cars with Jane Smith since last May". An Event Relation Mention.
- “Paul Martin succeeded Jean Chretien on Dec 12, 2003.” (a Successor Relation Mention)
- See: PropertyOf Relation Record, Attribute, Class.
References
2017a
- (Wikipedia, 2017) ⇒ https://en.wikipedia.org/wiki/Property_(programming) Retrieved:2017-7-16.
- A property, in some object-oriented programming languages, is a special sort of class member, intermediate in functionality between a field (or data member) and a method. The syntax for reading and writing of properties is like for fields, but property reads and writes are (usually) translated to 'getter' and 'setter' method calls. The field-like syntax is easier to read and write than lots of method calls, yet the interposition of method calls "under the hood" allows for data validation, active updating (e.g., of GUI elements), or implementation of what may be called “read-only fields".
See an instructive example for C# language below.
- A property, in some object-oriented programming languages, is a special sort of class member, intermediate in functionality between a field (or data member) and a method. The syntax for reading and writing of properties is like for fields, but property reads and writes are (usually) translated to 'getter' and 'setter' method calls. The field-like syntax is easier to read and write than lots of method calls, yet the interposition of method calls "under the hood" allows for data validation, active updating (e.g., of GUI elements), or implementation of what may be called “read-only fields".
2017b
- (Underscore, 2017) ⇒ Underscore, a JavaScript library http://underscorejs.org/#propertyOf Retrieved:2017-7-16
- QUOTE: propertyOf_.propertyOf(object)
Inverse of _.property. Takes an object and returns a function which will return the value of a provided property.
(in section Object Functions)
- QUOTE: propertyOf_.propertyOf(object)
1983
- (Shaw et al., 1983) ⇒ Shaw, M., Borison, E., Horowitz, M., Lane, T., Nichols, D., & Pausch, R. (1983). "Descartes: A programming-language approach to interactive display interfaces". ACM Sigplan Notices, 18(6), 100-111. DOI:10.1145/872728.806856
- ABSTRACT: This paper shows how the principles of programming methodology and language design can help solve the problem of specifying and creating interactive display interfaces for software systems. Abstraction techniques, such as abstract data types, can support both the specification of display interfaces and the implementation of those interfaces in a variety of styles. These abstraction techniques also guide the organization of software systems that will use display interfaces. We are developing a system that includes specifications, interface description tools, prototype organizations, and runtime support. The emphasis is on flexibility and on the separation of policy from particular instances. Preliminary results from implementations in a prototype domain indicate the feasibility of the approach.