Hello all,
please note that “entry” as in “application entry”, is actually not an object, it’s an “embellished page”, a page + object, something that is at the same time:
- a page and has the properties of a page (it’s subject to access rights, can be found on search, it’s attached in a place on the page tree, it’s displayed on the page tree and in the search - if not hidden), etc.
- but also is enriched with some additional meaning, which is marked by the presence of the object and stored in the objects properties.
- the presence of these properties also impact the display of the page - as the properties need to somehow show themselves - and the edit form - as the property values also need to be edited somehow.
My take would be for:
XClass: class (definition) or data type (definition)
XObject: object
a property of an XObject: property (or field?), or meta-data
An embellished page ( a page that contains an object of a class and whose display is controlled by the sheet associated to that class): an entry.
See also my answer to @pjeanjean here XObjects listing macro - #9 by lucaa , it contains some more / different explanation of this concept of embellished page, if this is not clear enough.
@mleduc: “class” is not a programming-oriented vocabulary. The programming world borrowed it from ontology and now we only know it from programming and believe it’s technical. But classes as in groups of things sharing the same traits is totally a thing outside programming.
Hope this helps,
Anca