fxdemo:01-part:11-conceptual-rules-and-constraints:11-10-local-profiles-must-preserve-parent-meaning

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
fxdemo:01-part:11-conceptual-rules-and-constraints:11-10-local-profiles-must-preserve-parent-meaning [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:11-10-local-profiles-must-preserve-parent-meaning to fxdemo:01-part:11-conceptual-rules-and-constraints:11-10-local-profiles-must-preserve-parent-meaning owenfxdemo:01-part:11-conceptual-rules-and-constraints:11-10-local-profiles-must-preserve-parent-meaning [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 2: Line 2:
 [[fxdemo:01-part:start | Go to Top ]] [[fxdemo:01-part:start | Go to Top ]]
  
-A domain profile, implementation profile, or deployment profile may specialiserealise, deploy, or test parent-layer concepts. It does not change the meaning of those parent-layer concepts.+[[dido:99_annexes:annex-b-terms-and-definitions:d:domain|Domain]] profile, implementation profile, or deployment profile may specializerealize, deploy, or test parent-layer concepts. It does not change the meaning of those parent-layer concepts. 
 + 
 +A profile may introduce additional terms, mappings, constraints, or artifacts when needed. It can identify those additions clearly and distinguish them from inherited concepts. 
 + 
 +---- 
 + 
 +<WRAP centeralign> 
 + 
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. 
 + 
 +</WRAP>
  
-A profile may introduce additional terms, mappings, constraints, or artefacts when needed. It can identify those additions clearly and distinguish them from inherited concepts. 
  
  • fxdemo/01-part/11-conceptual-rules-and-constraints/11-10-local-profiles-must-preserve-parent-meaning.1782768711.txt.gz
  • Last modified: 2026/06/29 14:31
  • by owen