[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [geolang-comment] One or two files for English and French?
* Mary Nishikawa | | From a maintenance point of view, it also might be better to keep | the French and English in separate files as they have done. Later | on, adding other languages would only be a matter of adding on more | files. * Murray Altheim | | This could be quite a maintenance nightmare though. One versus | hundreds (or even thousands) of files? Yuck. The plan was for this TC to only mirror what was in the source standards. Once the subject identifiers are established, everyone can go on to add whatever assertions they please about these subjects, and translations of the country names are one obvious thing to do. In fact, I think it would be a good idea if the TC members as individuals publish translations into other languages. That would help people outside the TC understand what's going on, I think. * Steve Pepper | | I understand why you suggest this, but I think it poses a new | problem: The identifier for a particular country can only resolve to | a single resource (or location within a resource). So what does | http://psi.oasis-open.org/geolang/en/iso3166/#jp | resolve to? The anchor "jp" in index.html at that location, | obviously. * Murray Altheim | | Not obviously. The resource in question might also be considered as | the DOM element that the 'jp' ID is on, which in this context would | make sense. What difference would that make? | Despite the trend to leave off the document name, relying on the web | server for resolution seems poor practice for something like | PSIs. One can easily alter the server defaults so that the root of a | directory is not 'index.html', such as 'index.asp' or whatever, and | my guess is that this will continue to evolve. I agree that it will, but I don't see the problem. Leaving off the document name gives us greater freedom with respect to how the PSIs are published on the server side. What if OASIS later decides that the page must use SSI, CGI, ASP, or JSP? If we haven't included the document name we can deal with that, but if we have we'll be screwed. | I would highly recommend that we recommend against relying on the | server, and use an explicit filename: [...] Why? -- Lars Marius Garshol, Ontopian <URL: http://www.ontopia.net > ISO SC34/WG3, OASIS GeoLang TC <URL: http://www.garshol.priv.no >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC