Not sure where to go for an authoritive/text book answer for this question.

Suppose a service returns a list of something e.g. Cutsomer, Employee, Fruits,.. what ever.

what should be retruned when the list is empty? I am working with people using SOAP, and they are sure that just a "success" result is enough.

Is there a analogue of LSP in OOP for SOA world? I mean should the there be a type compatibility? for example returning a list object with a single definition with no values for homegnousity.

SQL Database theory used relational calculus for rigour, what is the the analogue for API REST,SOAP or otherwise in terms of type compatibility etc.

PS : this is not about preference, but about the stablished patterns and practices. There must be somethig similar to OOP design patterns for APIs.

Not sure where to go for an authoritive/text book answer for this question.

Suppose a service returns a list of something e.g. Customer, Employee, Fruits, etc.

What should be returned when the list is empty?

I am working with people using SOAP, and they are sure that just a "success" result is enough.

Is there a analogue of LSP in OOP for SOA world? I mean should the there be a type compatibility? For example, returning a list object with a single definition with no values for homegnousity.

SQL Database theory used relational calculus for rigour, what is the the analogue for API REST,SOAP or otherwise in terms of type compatibility etc.

PS : this is not about preference, but about the stablished patterns and practices. There must be somethig similar to OOP design patterns for APIs.

Not sure where to go for an authoritive/text book answer for this question.

Suppose a service returns a list of something e.g. Cutsomer, Employee, Fruits,.. what ever.

what should be retruned when the list is empty? I am working with people using SOAP, and they are sure that just a "success" result is enough.

Is there a analogue of LSP in OOP for SOA world? I mean should the there be a type compatibility? for example returning a list object with a single definition with no values for homegnousity.

SQL Database theory used relational calculus for rigour, what is the the analogue for API REST,SOAP or otherwise in terms of type compatibility etc.

Not sure where to go for an authoritive/text book answer for this question.

Suppose a service returns a list of something e.g. Cutsomer, Employee, Fruits,.. what ever.

what should be retruned when the list is empty? I am working with people using SOAP, and they are sure that just a "success" result is enough.

Is there a analogue of LSP in OOP for SOA world? I mean should the there be a type compatibility? for example returning a list object with a single definition with no values for homegnousity.

SQL Database theory used relational calculus for rigour, what is the the analogue for API REST,SOAP or otherwise in terms of type compatibility etc.

PS : this is not about preference, but about the stablished patterns and practices. There must be somethig similar to OOP design patterns for APIs.