Re: Communicating status information about WebNFC [Was: Planning to close Web NFC Community Group due to inactivity unless we hear from you]

Hi Ian,

On 30. May 2025, at 17.06, Ian Jacobs <ij@w3.org> wrote:

On May 30, 2025, at 8:31 AM, Kostiainen, Anssi <anssi.kostiainen@intel.com<mailto:anssi.kostiainen@intel.com>> wrote:

Hi Ian,

On 29. May 2025, at 17.57, Ian Jacobs <ij@w3.org<mailto:ij@w3.org>> wrote:
* The WebNFC Specification has stabilized. The group may still make changes based on implementation feedback.
* WebNFC is currently shipping in one browser engine (Chromium) and available in multiple browsers on multiple devices.
* We invite people to use this API with caution because it may change. We welcome feedback and deployment stories.
* MDN includes developer documentation about the API.
* WebNFC is not a W3C standard and is not currently on the W3C standards track. However, once the group detects interest in a second implementation we expect to pursue standardization.

Do those statements resonate? (Feel free to correct them and edit them.)

Thanks, this is a good summary.

Do you want the group to maintain its status or do you plan to have a centralized CG tracker for this information that is perhaps semi-automatically kept up to date with some help from the community?

That’s a great question. Here’s where I think we will end up at some point:

* Status information like the above will be a mix of generic and context-specific text.
* We are thinking of generating the generic text from metadata maintained by editors or the CG. But the context-specific text will need to be maintained by the editors or CG.
* Tooling will help us by looking for signals in a variety of places and then saying “Does this spec’s metadata need to be updated?”

If you are interested in helping us develop some of these components, that would be welcome. In the meantime, I recommend manual checks every few months to see if the statements need updating.

I’m certainly happy to review and test drive your components and ideas with this group.

My gut feeling is don't over-engineer the solution. It probably takes a few iterations to get right. A wiki-style platform might be all we need for an MVP.

Thanks,

-Anssi