Minimum Requirements for Digital Asset Code Attribution

If we use a piece of code from one of the templates, and ostensibly do not change much besides Party, Owner, Supervisor, what are the minimum requirements for code attribution?

This below being the default attribution in the 1_Token example in the Daml Documentation

-- Copyright (c) 2021 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
-- SPDX-License-Identifier: Apache-2.0

I’m no legal expert, but they should be governed by the license, in this case Apache-2.0 as you can see from your example (we do use other licenses though - take note!). The full text will be available in a LICENSE file at the root of the project.

In your example, I think section 4 (c) applies:

You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

Again, please do not take this as legal advice. If in doubt, seek advice of a qualified lawyer.

Thank you for that

I thought there would be something required for derivative works. If someone on the forum can paste in a snippet of the attribution code block from a non-trivial derivative work, that’d be handy for future reference.

I think I may be misunderstanding your question. What do you expect as an attribution in addition to

-- Copyright (c) 2021 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
-- SPDX-License-Identifier: Apache-2.0

and a LICENSE file?

Could you give an example?

OK, I understand now, that is all you need.

Please excuse my denseness.