design - What is the best way to handle the restriction of an API? -

So far our main domain has been given an abstract name by name, whose name is first name, last name, middle initial etc. Is with the methods. As we are expanding the domain for Spain, we thought that they only talk about names, first names, aliases and others. Name or mid-secondary etc. have no significance for them.

At present, the API is present and a person's interface is being used at many places in Spain. The same place should also be used, therefore, the name of my choice is Spain, name from PersonName. But, if I do this then I will first expose the API for name, middle, initial etc. which are not applicable to Spain's domain.

My question is, are we still maintaining backward compatibility, existing segregation? Any refactoring or design tips are highly appreciated.

I'm also not sure what your question is "to expand SpainPersonName from PersonName", Do you mean to make Spain or to make a successor from a person's name?

In any case, let me speculate that the person's abstraction can be a defective, a separation should be widely applied, at least in those situations where it is implemented, is not it? We do not think the Spanish word as the first name versus the last name, as you speak well. Perhaps the intangible need to think again In my experience, GivenName Plus is an abstract most widely applied one based on family name, even for Asian cultures where the order of the name is not "normal".

Being creative, I think that you have to map Spanish first and second aliens to the abstract last name, because it's (first and second nickname) that we speak Spanish as our "last name" If you can do this, then you are doing well.