Hi Wendy, On Mon, Oct 14, 2013 at 2:51 PM, Wendy Roome <[email protected]>wrote:
> The ALTO java lib I downloaded a while back gives errors like: > Parsing error: Expected a ':' after a key at 10 [character 1 line 3] > "10" is offset in file. > > Now I see where your design comes from. We used some different parsers and hence different design. > As for internationalization problems, my proposed "syntax-error" field is > very different from the "reason" field proposed a year or so ago. > > The original "reason" field gave the explanation for all types of errors. > The problem is that the ALTO client would like to display that to the end > user to explain what went wrong. But if that were in a language the end > user didn't understand, it was useless. > > However "syntax-error" has a very limited audience. The contents only need > to make sense to the ALTO client developer. Just tell the end user, "Oops, > internal error." > > As for internationalization problems, why aren't the field names also a > problem? They're all in english. And HTTP seems to survive even though it > has english header names and status codes. Ditto for HTML, SIP, etc, etc. > > Distinguishing messages between those to developers and those to end users is important. To avoid issues with the review (the problem with "reason" as Richard A. mentioned), let's add a sentence to emphasize that the syntax-error text is technical, for developer debugging purposes. Thanks. Richard > - Wendy Roome > > From: "Y. Richard Yang" <[email protected]> > Date: Mon, October 14, 2013 13:16 > To: Wendy Roome <[email protected]> > Cc: Richard Alimi <[email protected]>, IETF ALTO <[email protected]> > > Subject: Re: [alto] Adding explanation for E_SYNTAX error > > A problem is that this is essentially the "reason" field as Richard A. > mentioned, and then we have the internationalization problem.... >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
