2 ms·
And because nobody wants to pay the namespace cost upfront, we all end up with vin, vin_no, viNumber, vinNum etc instead of iso3779:vin, for example. Every tim
by smarx007 3y ago
And because nobody wants to pay the namespace cost upfront, we all end up with vin, vin_no, viNumber, vinNum etc instead of iso3779:vin, for example. Every time we work with more than one API, it's prudent to try aligning the terms used by those APIs.
- lmm 3y agoIn my experience you have to have the duplication before you factor it out; trying to design those terms up front when you have no use cases, or even one use case, is doomed to failure. So you're always going to need to start with something non-standard, figure out the standard based on that experience, and then migrate to align to the standard.
- taeric 3y agoRight, this is pretty much exactly what I meant by XML started with all the complexity that other things will add. I will happily cede that data is a huge area where "duck typing" is far and away the correct choice. Taxonomies of data fail all the time. With odd rules that are largely defined by their exceptions.