W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > April 2012

Re: [all] suggestions for consolidating requirements

From: Arle Lommel <arle.lommel@gmail.com>
Date: Fri, 27 Apr 2012 10:51:49 -0800
Cc: "David Lewis" <dave.lewis@cs.tcd.ie>, <public-multilingualweb-lt@w3.org>
Message-Id: <FA7A6F24-6215-4B55-8749-D2C69F832C0B@gmail.com>
To: "Moritz Hellwig" <Moritz.Hellwig@cocomore.com>
> We said metadata should only be added never be removed, right?

I'd disagree with this principle. There are times it is entirely appropriate to strip a metadata item in a process. Mo's example is a good one: dropRule would delete itself when used properly. But there are other cases as well. For example, if a process marks up a text with term candidates and a subsequent process rejects them, I would expect that process to delete them, not leave them in. (One could argue it should alter them and mark that it rejected them, but for most purposes simply stripping the tag/attribute would make more sense since downstream processes probably have no need to know that an upstream process incorrectly identified a term candidate that another process cleared up.)

What I do think we should say is that metadata should not be removed without reason. What we don't want is a process to simply drop metadata it doesn't understand, but for a process that knows what it is doing to remove it is another thing entirely.


Received on Friday, 27 April 2012 18:52:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:43 UTC