There is no single correct answer, and what word you use to describe an entity depends heavily on the question — "It's an entity in which context?".
If you are talking in the context of a programming language; what paradigms are you following? If you take OOP, as an instance, you would describe the entities, which are objects, using classes. If you take Functional Programming, you would use functions to describe the entities.
If you are talking in the context of a database, where entities consist of units — classified things about which data can be stored (users, posts, etc...) — which have relations with other entities; you would use schemas to describe them.
If you are talking in the context of a software as a whole, you would come across units for handling both behavior and data, and you would describe these using domain models.
The specific use case that made me ask this question is a RESTful API I am working on.
It has several generic services that can be mapped to different endpoints
assets => /medias
assets => /documents
docs => /articles
users => /employees
etc. => /etc
I need to tell my clients which endpoint is which service, for instance, that /medias is an assets service.
I was also very curious to see how native english speakers would differentiate "kind" and "type" in code.
Ah I see, @slowmotarget! You could use the generic terms that you have mentioned, for your use case. However, a consistent use would be great. For instance, I am curious on why you have mapped docs to articles, and assets to \documents.
Also, a minor nitpick, medias is not correct. Media is a plural world, so the correct usage would be /media.
Sai Kishore Komanduri
Engineering an eGovernance Product | Hashnode Alumnus | I love pixel art
There is no single correct answer, and what word you use to describe an entity depends heavily on the question — "It's an entity in which context?".
If you are talking in the context of a programming language; what paradigms are you following? If you take OOP, as an instance, you would describe the entities, which are objects, using
classes. If you take Functional Programming, you would usefunctionsto describe the entities.If you are talking in the context of a database, where entities consist of units — classified things about which data can be stored (users, posts, etc...) — which have relations with other entities; you would use
schemasto describe them.If you are talking in the context of a software as a whole, you would come across units for handling both behavior and data, and you would describe these using
domain models.So, an entity in which context? :-)