- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Feb 2015 19:50:06 +0000
- To: public-nfc@w3.org
The ```id``` field is left to be used by applications. The NDEF technical spec (http://www.eet-china.com/ARTICLES/2006AUG/PDF/NFCForum-TS-NDEF.pdf) says: >The value of the ID field is an identifier in the form of a URI reference [RFC 3986] (see sections 2.4.3 and 4.4). The required uniqueness of the message identifier is guaranteed by the generator. The URI reference can be either relative or absolute; NDEF does not define a base URI which means that user applications using relative URIs MUST provide an actual or a virtual base URI (see [RFC 3986]). Re: > If the NDEF format isn't flexible enough that we can accomplish that, then mozilla is unlikely to implement anything. I think what I proposed above should technically solve the requirement. There are a couple of ways how exactly to achieve that, so we need to discuss that. But there is no doubt that if we want to achieve that web pages can read only "web tags", it can be done by a special formatting, but by _using_ the NDEF format with an encapsulated internal formatting, and not by redefining the NDEF format itself. -- GitHub Notif of comment by zolkis See https://github.com/w3c/nfc/issues/76#issuecomment-75617644
Received on Monday, 23 February 2015 19:51:17 UTC