canmove, Confirmed users
2,675
edits
VCard4: Difference between revisions
→section 6.1.5. XML: more details on why an XML property is a bad idea, incorporate feedback and extra detail from Joseph Smarr
(→issues: update draft # ref) |
(→section 6.1.5. XML: more details on why an XML property is a bad idea, incorporate feedback and extra detail from Joseph Smarr) |
||
| Line 140: | Line 140: | ||
6.1.5. XML | 6.1.5. XML | ||
While it has been clarified that this property is NOT for duplicating any vCard properties/values, | While it has been clarified that this property is NOT for duplicating any vCard properties/values, this still seems like a bit of a hack. | ||
There haven't been sufficient real world use cases presented to justify this property. | There haven't been sufficient real world use cases presented to justify this property. | ||
What precise (end user scenario) problem is it necessary to (help) solve? | What precise (end user scenario) problem is it necessary to (help) solve? | ||
Frankly, this looks like a hack for a specific implementation and not something that belongs in this generic spec. | |||
For instance, people might be using all kinds of other data around contact info but it's not vCard's job to provide some place to stick it. | |||
You could always invent your own X-STORED-EXTRA-DATA field. | |||
Such proprietary data is unlikely to be interoperable anyway, therefore we shouldn't pretend to make it superficially look like it by putting in a specific property for it. Better to leave implementations to use their own opaque proprietary properties for proprietary extensions. | |||
Also, this property will be very confusing to new implementers who may either not even be aware of or not care about the XML serialization (c.f. XML is dead on the web, killed by JSON), let alone a need to round-trip it thru this format. | |||
Recommendation: DROP XML property, and encourage implementers who think they need it or want to implement to propose an extension instead. | Recommendation: DROP XML property, and encourage implementers who think they need it or want to implement to propose an extension instead. | ||