W3C home > Mailing lists > Public > public-rif-wg@w3.org > July 2008

RE: the role of FLD in extensions (was Re: one thing we forgot)

From: Boley, Harold <Harold.Boley@nrc-cnrc.gc.ca>
Date: Mon, 7 Jul 2008 09:18:53 -0400
Message-ID: <E4D07AB09F5F044299333C8D0FEB45E904FFE224@nrccenexb1.nrc.ca>
To: "Chris Welty" <cawelty@gmail.com>, <kifer@cs.sunysb.edu>
Cc: "Sandro Hawke" <sandro@w3.org>, "RIF WG" <public-rif-wg@w3.org>

Chris, Sandro,

BLD is ready for freeze now.
FLD will be ready this week.


-----Original Message-----
From: public-rif-wg-request@w3.org [mailto:public-rif-wg-request@w3.org]
On Behalf Of Chris Welty
Sent: July 7, 2008 9:36 AM
To: kifer@cs.sunysb.edu
Cc: Sandro Hawke; RIF WG
Subject: Re: the role of FLD in extensions (was Re: one thing we forgot)

I don't think this is resolved sufficiently to decide.  We can discuss
further in the upcoming months, in particular as we move our focus to
FLD and 
how it gets instantiated.  For now, it is too late to make a change that
we do 
not all completely agree on.

Other than this point on dialect identification, Michael, is BLD and FLD
  If so let us know asap so we can freeze and review it.


Michael Kifer wrote:
> On Sat, 05 Jul 2008 22:59:21 -0400 Sandro Hawke <sandro@w3.org> wrote:
>> This last bit reminds me why I think we don't actually need a fight
>> I why I decided I was okay with the text in FLD at F2F10).  I think
>> you're trying to serve the extension/dialect designers who want their
>> product to be a blessed standard.  I think I'm trying to serve the
>> extension/dialect designers who just want to do their own thing on
>> Web, without official blessing, and somehow have it interoperate.
>> okay with FLD constraining the first camp, and (realistically,
>> practically) nothing we do can constrain the second camp.  The second
>> camp needs social and technical mechanisms for forward and backward
>> compatibility, to actually get interoperation, but they're probably
>> interested in filling into our framework.
> Agree completely. People designing private extensions are free to take
> they want and to discard anything that doesn't suit them. They can
even come up
> with a completely different interchange format. Nothing we can or
should do
> here.
> The point of FLD is to provide a sufficiently attractive way for
people to
> easily design dialects without the need to go through the pain of a
> definition (cf. the direct BLD specification vs. the derived spec).
But even
> then they can decide to deviate quietly or convince us to change
things. FLD
> just says that for officially blessed dialects they should try the
> 	--michael  

Dr. Christopher A. Welty                    IBM Watson Research Center
+1.914.784.7055                             19 Skyline Dr.
cawelty@gmail.com                           Hawthorne, NY 10532
Received on Monday, 7 July 2008 13:19:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:47:51 UTC