From 9b56279e001dcf76ac0ca8ebd815d114683b086c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Magnus=20B=C3=A4ck?= Date: Tue, 29 Jun 2021 22:50:54 +0200 Subject: [PATCH] Add guidelines for naming link types This puts in writing what has been the de facto naming standard for all current event types. --- eiffel-syntax-and-usage/event-design-guidelines.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/eiffel-syntax-and-usage/event-design-guidelines.md b/eiffel-syntax-and-usage/event-design-guidelines.md index 27f59c63..e9a81f6a 100644 --- a/eiffel-syntax-and-usage/event-design-guidelines.md +++ b/eiffel-syntax-and-usage/event-design-guidelines.md @@ -33,7 +33,4 @@ The design of Eiffel events is governed by the following guidelines: * __Information model integrity over reader convenience:__ Eiffel events are not convenient to read – or to publish – as they require graph traversal in order to derive any meaningful information. Do not work around this by including convenience information (typically duplication). Such measures will never be completely satisfactory. Instead the primary concern of event design is information model integrity; readability and usability is the concern of services built upon that data source. * __Key names in camelCase:__ All key names shall use camelCase. * __Enumerations in CAPS_WITH_UNDERSCORE:__ All enumerated values shall use CAPS_WITH_UNDERSCORE. - - - - +* __Link types are nouns:__ Link types shall have names that fit the pattern "\ is the \'s \", implying that they are nouns that describe the relationship between the source and the target event.