- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 07 Jun 2006 05:55:20 +0000
- To: public-i18n-its@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3320 Summary: Using IDs for nodes instead of / in addition to XPath Product: ITS Version: WorkingDraft Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: ITS tagset AssignedTo: fsasaki@w3.org ReportedBy: fsasaki@w3.org QAContact: public-i18n-its@w3.org See comments from at Daniel Glazman and Werner Donne at http://lists.w3.org/Archives/Member/member-i18n-its/2006AprJun/0097.html: [[Daniel Glazman (invited expert in the CSS working group): "Why don't you use IDs for elements (and keys for attributes), instead of the - computationally expensive - XPath?" My reply was: It would be good to do that, but you can do it only if you have control over the whole data in the localization workflow. I heard a similar comment from Iris Orris (Microsoft) at the Unicode conference, but it seems to me this scenario works only for data inside big corporates. - Werner Donne gave a talk on "Managing Multilingual Legislation With XML", see http://xtech06.usefulinc.com/schedule/detail/17 . In his approach, he added "metadata" about versioning into XML documents. The meta data was used for alignment of EC documents. Werner said the ITS approach of global rules seems promising for such versioning, since it has no or limited impact on the document(s). One potential issue he saw (again, see Daniel above) was the computational cost of XPath for large documents.]]
Received on Wednesday, 7 June 2006 05:55:27 UTC