Difference between revisions of "Notice time"
Jump to navigation
Jump to search
m |
|||
| Line 10: | Line 10: | ||
|[[NTCTXT]]||noticeTimeText||0..1||n/a | |[[NTCTXT]]||noticeTimeText||0..1||n/a | ||
|- | |- | ||
| − | |[[OPERAT]] | + | |[[OPERAT]]||operation||0..1||n/a |
|} | |} | ||
That enabled us to model constructions like:<br> | That enabled us to model constructions like:<br> | ||
Notice is required 24 hrs in advance or when leaving the previous port if closer. | Notice is required 24 hrs in advance or when leaving the previous port if closer. | ||
Revision as of 10:31, 25 October 2009
jens 09:54, 25 October 2009 (UTC) Notice time can become a complex attribute using the operation idea Rahpael proposed and which is been used at Under Keel clearance. The construction can be like to following
| Sub-attribute | Camel Code Identifier | multiplicity | sequential |
|---|---|---|---|
| NTCHRS | noticeTimeHours | 0..1 | n/a |
| NTCTXT | noticeTimeText | 0..1 | n/a |
| OPERAT | operation | 0..1 | n/a |
That enabled us to model constructions like:
Notice is required 24 hrs in advance or when leaving the previous port if closer.