- From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
- Date: Tue, 12 Aug 2014 08:19:14 -0700
- To: Martin Hepp <martin.hepp@unibw.de>, Dan Brickley <danbri@google.com>
- CC: "Evain, Jean-Pierre" <evain@ebu.ch>, Dan Brickley <danbri@danbri.org>, Yves Raimond <yves.raimond@gmail.com>, David Marland <david.marland@bbc.co.uk>, W3C Web Schemas Task Force <public-vocabs@w3.org>, Richard Wallis <Richard.Wallis@oclc.org>, Dan Scott <denials@gmail.com>
That's putting quite a burden on the client. Big clients, such as those that can be produced by Google and Yahoo, might have access to sufficient information to handle situations where data routinely does not match the schema. However, small and medium clients are going to be in a much worse situation. How are they to proceed? peter On 08/12/2014 06:44 AM, Martin Hepp wrote: > In general, I would leave the interpretation / cleansing to the client in here rather than constraining the publication of data too much. In the end, data quality and data semantics are twins, see > > http://link.springer.com/chapter/10.1007%2F978-3-540-39648-2_2 > > Best > > Martin > > > > On 12 Aug 2014, at 15:08, Dan Brickley <danbri@google.com> wrote: > >> On 12 August 2014 14:03, Evain, Jean-Pierre <evain@ebu.ch> wrote: >>> By non-integer I guess you mean e.g. string (or else) - then fine >> >> Yes. It's possible people sometimes number with 10.1, 10.2 etc too, >> which technically looks like a Float though they're not intended for >> mathematical use really... >> >> Dan >> > >
Received on Tuesday, 12 August 2014 15:19:54 UTC