Re: Moving forward with the next project

Vladimir & Chris,

Thank you. What the two of you provided gave me what I needed to fill out the request, which means that the proverbial wheels are theoretically in motion over here at Adobe's HQ. I also alerted Alan that I submitted the request.

Regards...

-- Ken

> On Mar 19, 2018, at 2:29 PM, Levantovsky, Vladimir <Vladimir.Levantovsky@monotype.com> wrote:
> 
> Hi Ken,
> 
> Thank you, it looks like things are moving forward, which is encouraging!
> 
> As a follow up to Chris Lilley's email with the W3C policy links, I would like offer some additional details on your questions, and make a few points based on our last telcon and the preliminary discussions:
> 
> 1) and 2) are addressed by links Chris has already provided.
> 
> Like Chris mentioned, while we are still working on specific details that will be described in the WG charter, the following answers might help you (and others) facilitate internal discussions:
> 
> 3) A member participant is expected to contribute their expertise and knowledge on the specific subject matter of the development, and would also be expected to contribute certain resources (employee time committed to this project including specification development, conformance tests, reference implementation, etc., as applicable).
> 
> 4) The general scope of this work would be to strike the right balance and enable native support for dynamic font subsetting / augmentation / streaming of font data. While the specific details are unknown at this point, and the future charter will likely be drafted in such way that allows the WG itself to make all important final decisions - I want to emphasize that reaching an agreement to strive for [and implement] a native browser solution would eliminate the need for JS client and offer a huge performance benefits for web fonts, both for an end user and font service provider.
> 
> 5) While this activity is likely to be a continuation of the WebFonts WG work, it is clearly a departure from the prior scope as we'd no longer be defining a web font data format but rather work on specifying an implementation that can manipulate with the font data by producing / consuming dynamic subsets, incremental font updates, etc.
> 
> Thank you,
> Vlad
> 
> 
> -----Original Message-----
> From: Ken Lunde [mailto:lunde@adobe.com] 
> Sent: Monday, March 19, 2018 4:42 PM
> To: Levantovsky, Vladimir
> Cc: w3c-webfonts-wg (public-webfonts-wg@w3.org)
> Subject: Moving forward with the next project
> 
> Vladimir,
> 
> My management has tasked me with completing a form on Adobe's end in order to move forward with our participation in the next project, which is about dynamic augmentation of webfonts. I know that you're working on a charter for this project, and in case it helps to put that together, I will need answers for the following five items:
> 
> 1) Open Standard Organization (e.g. OpenSSL, Open Pegasus, etc.):
> 
> 2) What agreements do you need to sign to participate in the Open Standard? Please describe and provide a link to the forms:
> 
> 3) Please provide a brief description of the scope of the requested participation:
> 
> 4) Please provide detailed explanation of the technology in the open standard project
> 
> 5) Is this related to a prior/existing open standard project?
> 
> I imagine that the folks at Apple, Google, and Microsoft may need similar information in order to move forward as well.
> 
> Regards...
> 
> -- Ken
>

Received on Monday, 19 March 2018 23:54:01 UTC