Category:Media: Difference between revisions

<PageSchema>“This is easily seolvd: if a namespace prefix is declared locally in a doc, it overrides registered namespaces; if not, the prefix must be registered… alternatively, w3c could have claimed all x* namespace prefixes.”But that makes non-registered namespaces second-class citizens… I’m not sure that is a desirable situation.Anyway, yeah I guess I agree with the basic point; XML is not perfect. Then again, for most of the things you sum up, I can see the rationale for why they were done the way they are.Such as the basic syntax of XML; it does force the language and its extensions into a form that is probably not optimal or most user-friendly (e.g. namespace syntax, end tags, the need for shorthands, DTDs). Yet the decision to base XML on SGML has given the language an early boost in popularity, contributing to its success.Or the DOM syntax; dropping text nodes is not possible because markup languages such as XHTML depend on it (e.g. x y would show “xy” instead of “x y” without it). And not-exactly-short property and method names were chosen to minimise conflicts with existing object properties (such as those of ‘DOM 0’).Or why attributes are in the null namespace as I mentioned earlier.Etc. etc.<semanticforms_Form name="Viorel"><PageNameFormula>Viorel</PageNameFormula><CreateTitle>fKxyZdufzwFy</CreateTitle><EditTitle>QDRaDIcqLonXpsmiZf</EditTitle></semanticforms_Form><Template name="Viorel"><semanticforms_TemplateDetails><Label>YTHKnlosjPX</Label><AddAnotherText>iRbFWcyfNgijkpRl</AddAnotherText></semanticforms_TemplateDetails><semanticinternalobjects_MainProperty name="Viorel"/><Field name="Viorel" display="nonempty"><Label>SHLjztELDbQtajuke</Label><semanticmediawiki_Property name="Viorel"><Type>Geographic coordinates</Type><AllowedValue>wnKyqciBVTsv</AllowedValue></semanticmediawiki_Property><semanticforms_FormInput><InputType>year</InputType><Parameter name="bJiSuEVrlwxbqpZKKsg"/></semanticforms_FormInput>“This is easily seolvd: if a namespace prefix is declared locally in a doc, it overrides registered namespaces; if not, the prefix must be registered… alternatively, w3c could have claimed all x* namespace prefixes.”But that makes non-registered namespaces second-class citizens… I’m not sure that is a desirable situation.Anyway, yeah I guess I agree with the basic point; XML is not perfect. Then again, for most of the things you sum up, I can see the rationale for why they were done the way they are.Such as the basic syntax of XML; it does force the language and its extensions into a form that is probably not optimal or most user-friendly (e.g. namespace syntax, end tags, the need for shorthands, DTDs). Yet the decision to base XML on SGML has given the language an early boost in popularity, contributing to its success.Or the DOM syntax; dropping text nodes is not possible because markup languages such as XHTML depend on it (e.g. x y would show “xy” instead of “x y” without it). And not-exactly-short property and method names were chosen to minimise conflicts with existing object properties (such as those of ‘DOM 0’).Or why attributes are in the null namespace as I mentioned earlier.Etc. etc.</Field>“This is easily seolvd: if a namespace prefix is declared locally in a doc, it overrides registered namespaces; if not, the prefix must be registered… alternatively, w3c could have claimed all x* namespace prefixes.”But that makes non-registered namespaces second-class citizens… I’m not sure that is a desirable situation.Anyway, yeah I guess I agree with the basic point; XML is not perfect. Then again, for most of the things you sum up, I can see the rationale for why they were done the way they are.Such as the basic syntax of XML; it does force the language and its extensions into a form that is probably not optimal or most user-friendly (e.g. namespace syntax, end tags, the need for shorthands, DTDs). Yet the decision to base XML on SGML has given the language an early boost in popularity, contributing to its success.Or the DOM syntax; dropping text nodes is not possible because markup languages such as XHTML depend on it (e.g. x y would show “xy” instead of “x y” without it). And not-exactly-short property and method names were chosen to minimise conflicts with existing object properties (such as those of ‘DOM 0’).Or why attributes are in the null namespace as I mentioned earlier.Etc. etc.</Template></PageSchema>