Proposal to refine usage of epo:hasNutsCode and epo:hasCountryCode in epo:Address #685
Unanswered
cristianvasquez
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Apologies if this has been discussed before, and please feel free to move this to the discussions section if it's more appropriate.
I've been looking into how addresses and locations are modelled, particularly in this diagram corresponding to epo-4.0.0.
I noticed that both addresses and locations have
epo:hasNutsCode
andepo:hasCountryCode
. At first glance, this seems like it could lead to unnecessary data replication.Additionally,
dct:Location
may or may not include an addressIt seems more intuitive to me that an address should always belong to a location, rather than the other way around. The current relationship between Location and Address is a bit confusing in this regard.
Has there been any consideration of a model where Location has
epo:hasNutsCode
andepo:hasCountryCode
, these properties are removed from Address, and Address is linked to Location instead?Beta Was this translation helpful? Give feedback.
All reactions