LocationContained in Itierry cardinality in schema different from definition

Submitted by bard on Wednesday, 22 January, 2014 - 13:12
Issue ID
139
Component
UML Location Referencing
Category
Bug report
Priority
Normal
Assigned
iancornwell
Status
Fixed
Source
Website
Description

The definition of an itinerary states multiple locations. The schema allows for 0..n . This should be 2..n

{"changeLogs":[{"date":1527783676500,"componentOLD":"- Select a value -","component":"UML Location Referencing","categoryOLD":"- Select a value -","category":"Bug report","priorityOLD":"- None -","priority":"Normal","assignedOLD":"","assigned":"iancornwell (42)","statusOLD":"- None -","status":"Fixed"},{"date":1537268948063}]}

Posted by jaderberg on January 13, 2035 Permalink

I cannot see that the tool does anything wrong here. locationContainedInItinerary is a one to one relation between the index qualifier of ItineraryByIndexLocations and Location. In the schema, since there is a qualifier, the relation will be 0..n.
If it should be 2..n it's a model or methodology issue.
I will change this to a model issue.

Posted by iancornwell on November 13, 2033 Permalink

Implemented resolution documented by Loic

Posted by RaulSchimmel on August 13, 2028 Permalink

Sometimes when you are feeling down you need some soul to inspire classes. Soul write my paper for me free inspire caching classes give such lessons that reach till you soul. Their theme resembles h to some extent. You can get life-changing lessons from here.