Christoph; Again this is a general modeling question. In general the modeling choices are dependent on how you intend to compute logic, such as durations.
-- Scott On Jan 19, 4:43 am, Christoph <[email protected]> wrote: > Dear all, > > I hope not to bother you with boring questions. > I would like to model the fact that a ticket is valid for 3 months > from day of purchase. Should I just create a datatype property > "isValidForDuration" with string "3 months"? Or create a class > DateWithTimeUnit that comprises two attributes: hasValue linking to a > float, hasTimeUnit, linking to the instance "month" of another class? > > Thank you very much for your support! > > br, Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
