Ubiquitous Language is a shared language that is used by all stakeholders in a project to improve communication and reduce misunderstandings. It helps in defining data models and business logic, ensuring accurate understanding and implementation of analytics tasks. The language (and model) should evolve as the team's understanding of the domain grows.
Domain experts should object to terms or structures that are awkward or inadequate to convey domain understanding; developers should watch for ambiguity or inconsistency that will trip up design.
-- Eric Evans
This page contains terms that have a special meaning in the domain of mathematics, GIS, mountaineering, etc. that should be used in code for naming classes, methods, variables, etc. or may be found in documentation.
Language Conflicts
Where name conflicts occur with coding conventions, assume the ubiquitous language dominates unless the context is in purely programming documentation (and even if then, should be sparse).
For areas of overlapping domains, language is assumed to be consistent within a particular package. Where there are conflicts of terms, there is usually a hierarchy of packages (such as trip planning using GIS), in which case, the dependent package’s terms are assumed to overwrite the dependency’s.
=====
map resource
list of routes
complete region
list of custom ticks
media
photo
photo annotated
video
album
geography region
geography region
gis
feature large
type
point
marker interest
type
marker route
type
network
type
point
path point
path segment
classification
forward climbing segment
backward climbing segment
path segment classification
region
type
point
trip path
path set
gps
marker
point
track
point
travel mode
climbing
route
overwrite
pitch
rock style attribute
variation
rack
travel style
trip
day overwrite to route
route method
path recorded
reference
reference
report
trip summary
trip introduction
trip
article
report photo
report video