The current description around person:identifier in CPV contains an apparently broken link to intended eIDAS (2014) identity attribute mapping with CPV. I tried to open the link, including by first logging in with my EU Login and the page shows a Page Not Found error whether logged in or not. Probably you want to fix this link.
Moreover, the more interesting question is that the new, eIDAS 2 related ARF v1.3.0 documentation includes an annex for defining the attribute schema of the Person Identifier (PID) that will be issued in future as a QEAA (Qualified Electronic Attribute Attestation) to EU citizens' EUDIW wallets. The annex defines familiar-looking attributes, but it doesn' contain any reference to your vocabulary.
I would through this issue suggest to create and publish as new work the PID-attribute-to-CPV-property mapping (similar that was the attempt in now broken eIDAS mapping document?), unless you have this already in your backlog.
I came across with the topic & issues while drafting a new local verifiable credential (or EAA, in eIDAS terms) schema, that refers to some of the CPV 2.1.0 properties as credential attributes. Aim is that in future those attributes can be mapped directly (if possible) to the PID equivalents, if/as users will be using their PID & wallet to authenticate to the services that use this EAA in context of the authenticated user/data subject and their services.
The current description around person:identifier in CPV contains an apparently broken link to intended eIDAS (2014) identity attribute mapping with CPV. I tried to open the link, including by first logging in with my EU Login and the page shows a Page Not Found error whether logged in or not. Probably you want to fix this link.
Moreover, the more interesting question is that the new, eIDAS 2 related ARF v1.3.0 documentation includes an annex for defining the attribute schema of the Person Identifier (PID) that will be issued in future as a QEAA (Qualified Electronic Attribute Attestation) to EU citizens' EUDIW wallets. The annex defines familiar-looking attributes, but it doesn' contain any reference to your vocabulary.
I would through this issue suggest to create and publish as new work the PID-attribute-to-CPV-property mapping (similar that was the attempt in now broken eIDAS mapping document?), unless you have this already in your backlog.
I came across with the topic & issues while drafting a new local verifiable credential (or EAA, in eIDAS terms) schema, that refers to some of the CPV 2.1.0 properties as credential attributes. Aim is that in future those attributes can be mapped directly (if possible) to the PID equivalents, if/as users will be using their PID & wallet to authenticate to the services that use this EAA in context of the authenticated user/data subject and their services.