Open blelump opened 9 months ago
I have also come across this challenge. For reference, the categories are specified here in the label overlay: https://github.com/the-human-colossus-foundation/oca-spec/tree/master/docs/specification#label-overlay
"and MAY include the following attributes:
attribute_categories
The attribute_categories attribute contains category identifiers.
category_labels
The attribute_categories attribute maps key-value pairs where the key is the attribute name and the value is a human-meaningful category label in a specific language.
{ "capture_base":"EVyoqPYxoPiZOneM84MN-7D0oOR03vCr5gg1hf3pxnis", "type":"spec/overlays/label/1.0", "language":"en", "attribute_labels":{ "dateOfBirth":"Date of birth", "documentNumber":"Passport Number", "documentType":"Document", "fullName":"Name", "height":"Height", "issuingState":"Issuing State or organization (in full)", "photoImage":"Portrait image", "sex":"Sex" }, "attribute_categories":[ "cat-1", "cat-2", "cat-3", "cat-4" ], "category_labels":{ "cat-1":"Mandatory header", "cat-2":"Mandatory personal data elements", "cat-3":"Mandatory identification feature", "cat-4":"Optional data elements" } }
Example 5. Code snippet for a Label Overlay (language: en)."
Categories are not implemented within ADC.
I support the removal of categories, but am interested to hear arguments to the contrary.
Problem overview
As defined in the label overlay, categories exhibit an abstract concept related to spatial arrangement. The spatial arrangement itself is a presentation layer concern.
Proposal
Remove categories from the label overlay to clearly separate the data presentation layer from the data itself.