Use of cardinalities in templates
Use of cardinalities in templates
I see one important problem of cardinality-type roles in template signatures. If we leave role types as dm:Cardinality, it'll be required to learn by heart (or hardcode in the software) the URIs of the most used ones. Is it worth the efforts to decompose templates to the level of hasmaximum and hasminimum integers? But roles in the templates can not be optional, therefore it is not clear for me - what to do with "any"="infinity" restriction?
-
HansTeijgeler
- Posts: 283
- Joined: Sun Jan 22, 2012 10:02 pm
Re: Use of cardinalities in templates
Hi Victor,
My advice would be: put them on a(n electronic) cheat sheet in your mapping software. How many will that be? Using a cheat sheet would have another advantage: you don't have to memorize the logic of those cardinalities vs the ends of the relationship by asking the right questions.
Using URIs avoids the problem you describe with roles in templates that may not be left empty. In the RDL we can create a set of cardinality definitions that covers all required permutations, including ones where the optionality applies, such as infinity.
Regards,
Hans
My advice would be: put them on a(n electronic) cheat sheet in your mapping software. How many will that be? Using a cheat sheet would have another advantage: you don't have to memorize the logic of those cardinalities vs the ends of the relationship by asking the right questions.
Using URIs avoids the problem you describe with roles in templates that may not be left empty. In the RDL we can create a set of cardinality definitions that covers all required permutations, including ones where the optionality applies, such as infinity.
Regards,
Hans