file: ddf--entities--geo--country.csv
headers: country, name, gendercountry is entity set, gender is entity domain
would give primary key gender
Updated logic handles this correctly.
Moreover, imagine you want to set a property geo on a country entity
with updated logic
in ddf--entities--geo.csv you can't because geo MUST be key
in ddf--entities--geo--country.csv you can because country will be key if used next to geo
defining country property on geo is still possible in ddf--entities--geo file or any other entity set file.
defining geo on geo is still impossible (was never possible) due to csv ambiguity.
Old logic was wrong.
file:
ddf--entities--geo--country.csvheaders:country, name, gendercountryis entity set,genderis entity domain would give primary keygenderUpdated logic handles this correctly.
Moreover, imagine you want to set a property
geoon acountryentitywith updated logic in ddf--entities--geo.csv you can't because
geoMUST be key in ddf--entities--geo--country.csv you can becausecountrywill be key if used next togeodefining
countryproperty ongeois still possible in ddf--entities--geo file or any other entity set file. defininggeoongeois still impossible (was never possible) due to csv ambiguity.