The SDG Sandbox creates a space for the review of data models produced by WP4 - Data semantics, formats and quality - in the context of the preparatory work for the Single Digital Gateway Regulation.
14
stars
9
forks
source link
Birth certificate: structure and naming convention #60
Ingrid (FIN): please consider short, meaningful and intuitive names for XSD/XML elements and simple, easy to follow structure.
e.g. this one is 8-level deep: birthCertificate --> certifies --> birth --> child --> person --> identifierPerson --> identifiers --> identifier --> identifierIdentifier. Do we really need such a complex structure?
you get lost easily in those identifierXXXX fields, ID or code sounds much simpler and could be used consistently under each element since the parent element specifies what/whose ID or code is in question.
Ingrid (FIN): please consider short, meaningful and intuitive names for XSD/XML elements and simple, easy to follow structure.
e.g. this one is 8-level deep: birthCertificate --> certifies --> birth --> child --> person --> identifierPerson --> identifiers --> identifier --> identifierIdentifier. Do we really need such a complex structure?
you get lost easily in those identifierXXXX fields, ID or code sounds much simpler and could be used consistently under each element since the parent element specifies what/whose ID or code is in question.