Le C be an OWL class which defines an single value cardinality constraint (cardinality==1) on some property p.
Now let i be an individual of class C, which occurs two times in a json file so that in both the occurrences the property p is present, with values respectively o and o'. When the DefaultInstanceBuilder encounter the second occurrence of i during the parsing of the json file, it throws a JsonDeserializationException :-1:
Encountered multiple values of property
However, if o and o' are equals the single value constraint is not actually violated. In such a cases I think that avoiding to throw the exception would make the api more robust against strang but correct json files.
Le
C
be an OWL class which defines an single value cardinality constraint (cardinality==1) on some propertyp
. Now leti
be an individual of classC
, which occurs two times in a json file so that in both the occurrences the propertyp
is present, with values respectivelyo
ando'
. When theDefaultInstanceBuilder
encounter the second occurrence ofi
during the parsing of the json file, it throws aJsonDeserializationException
:-1:However, if
o
ando'
are equals the single value constraint is not actually violated. In such a cases I think that avoiding to throw the exception would make the api more robust against strang but correct json files.