Return to Answer

It does not ... Domain Driven Design makes it very clear

Operation names should come from the UBIQUITOUS LANGUAGE or be introduced into it. Parameters and results should be domain objects.

The names in software should use the same terminology that is used in the real world domain.

As user949300 notes above, Set is not part of the domain language. Therefore, it does not make sense to use Set.

From a DDD point of view, the attributes on a book, also wouldn't be called a set.

Now with respect to what the domain calls such a collection of books or their attributes ... that can be daunting and requires additional investigation to get the domain correct.

A place to start is with the English Language and Usage question on what to call a Group of Books

It does not ... Domain Driven Design makes it very clear

Operation names should come from the UBIQUITOUS LANGUAGE or be introduced into it. Parameters and results should be domain objects.

The names in software should use the same terminology that is used in the real world domain.

As user949300 notes above, Set is not part of the domain language. Likewise, the attributes on a book, also wouldn't be called a set.

Therefore, it does not make sense to use the word Set as an umbrella term for both sets and individual items.

Now with respect to what the domain calls such a collection of books or their attributes ... that requires additional investigation to get the domain correct.

A place to start is with the English Language and Usage question on what to call a Group of Books

It does not ... Domain Driven Design makes it very clear

Operation names should come from the UBIQUITOUS LANGUAGE or be introduced into it. Parameters and results should be domain objects.

The names in software should use the same terminology that is used in the real world domain.

As user949300 notes above, Set is not part of the domain language. Therefore, it does not make sense to use Set.

From a DDD point of view, the attributes on a book, also wouldn't be called a set.

Now with respect to what the domain calls such a collection of books ... that can be daunting and requires additional investigation to get the domain correct.

A place to start is with the English Language and Usage question on what to call a Group of Books

It does not ... Domain Driven Design makes it very clear

Operation names should come from the UBIQUITOUS LANGUAGE or be introduced into it. Parameters and results should be domain objects.

The names in software should use the same terminology that is used in the real world domain.

As user949300 notes above, Set is not part of the domain language. Therefore, it does not make sense to use Set.

From a DDD point of view, the attributes on a book, also wouldn't be called a set.

Now with respect to what the domain calls such a collection of books or their attributes ... that can be daunting and requires additional investigation to get the domain correct.

A place to start is with the English Language and Usage question on what to call a Group of Books

It does not ... Domain Driven Design makes it very clear

To create software that is valuably involved in users’ activities, a development team must bring to bear a body of knowledge related to those activities. The breadth of knowledge required can be daunting.

As user949300 notes above, Set is not part of the domain language. Therefore, it does not make sense to use Set.

From a DDD point of view, the attributes on a book, also wouldn't be called a set.

Now with respect to what the domain calls such a collection of books ... that can be daunting and requires additional investigation to get the domain correct.

https://english.stackexchange.com/questions/167740/groups-of-books

It does not ... Domain Driven Design makes it very clear

Operation names should come from the UBIQUITOUS LANGUAGE or be introduced into it. Parameters and results should be domain objects.

The names in software should use the same terminology that is used in the real world domain.

As user949300 notes above, Set is not part of the domain language. Therefore, it does not make sense to use Set.

From a DDD point of view, the attributes on a book, also wouldn't be called a set.

Now with respect to what the domain calls such a collection of books ... that can be daunting and requires additional investigation to get the domain correct.

A place to start is with the English Language and Usage question on what to call a Group of Books