canmove, Confirmed users
2,887
edits
(→section 6.5.1. TZ: added issue about dropping language saying shouldn't use UTC) |
(→section 6.1.5. XML: link to XML dead article and also note HTML(5)+microformats has killed XML on the web) |
||
| Line 154: | Line 154: | ||
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. | 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) | 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, let alone a need to round-trip it thru this format (c.f. [http://blog.jclark.com/2010/11/xml-vs-web_24.html XML is dead on the web, killed by JSON] at least for APIs. For formats/documents, HTML(5)+microformats have handily beat XML on the Web). | ||
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. | ||