W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2005

[ESW Wiki] Update of "its0506ReqConstraints" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Mon, 27 Jun 2005 01:53:56 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050627015356.4550.64586@localhost.localdomain>
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by YvesSavourel:

  These constraints may need to be defined at the schema level or they may need to be defined for specific instances of an element.
- '''[[CL''' A certain constraint (e.g. container size) may only hold for a certain tool wihtin the overall processing chain. Thus, the important thing about the constraint is to ensure that the constraint holds when data is passed to that particular tool. Accordingly, a specific tool "sets" the constraint. When data is passed between other tools of the processing chain, the constraint may not be relevant.''']]'''
- '''[[YS''' I'm adding the paragraph below to cover Christian's comment, but I'm not sure if it's really useable: I would expect the constraint to be linked to the data itself rather than the context. Because the next logical step would be that one can have different constraints depending on the context, then how do you apply those possibly conflicting constraints to the same chunk of data? ''']]'''
- '''[[FS-''' As will be mentioned in the extreme paper (final version), a description of the processing model or processing pipeline (you can call it like you want) might help. But we don't need to decide now, that's s.t. for the recommendation.''']]'''
  In some cases, the constraint may be applicable only for a given context or a given tool.
Received on Monday, 27 June 2005 03:34:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:04 UTC