Class Table internally supports names with multiple components (not limited only to the trio of database, schema and table name): it has methods setIndex/getIndex; the class even has a constructor that takes a list of names as its parameter. In some applications, it would be convenient to have access to these methods (at least the getter), so why not include them in the MultiPartName interface?