Add note (eclipse-dataspace-dcp#227)

Author: jimmarino

specifications/dcp.profiles.md

@@ -13,7 +13,7 @@ This specification defines two profiles, which are referenced by an alias.
 | `vc20-bssl/jwt`   | [VC Data Model 2.0](https://www.w3.org/TR/vc-data-model-2.0) | [BitStringStatusList](https://www.w3.org/TR/vc-bitstring-status-list/)   | Enveloped proofs [using JWT/JOSE](https://www.w3.org/TR/vc-jose-cose/#with-jose) | Ignore `ttl`, use `validUntil` *). No JWE supported. The concrete signature algorithm is not specified, as implementors are expected to handle all reasonably well-known crypto algorithms like RSA, EC and EdDSA |
 | `vc11-sl2021/jwt` | [VC Data Model 1.1](https://www.w3.org/TR/vc-data-model)     | [StatusList2021](https://www.w3.org/TR/2023/WD-vc-status-list-20230427/) | External proofs using JWT                                                        | No JWE supported. The concrete signature algorithm is not specified, as implementors are expected to handle all reasonably well-known crypto algorithms like RSA, EC and EdDSA                                    |
 
-In its current form, the BitStringStatusList credential data
+(*) In its current form, the BitStringStatusList credential data
 model [conflicts](https://www.w3.org/TR/vc-bitstring-status-list/#bitstringstatuslistcredential) with the VC DataModel
 2.0, specifically regarding the validity period (`ttl` vs `validUntil`).