- From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
- Date: Tue, 3 Nov 2009 16:44:25 +0100
- To: public-webapps <public-webapps@w3.org>
Hi, Following our yesterday's discussion about specification of the local addresses within WARP I have the following proposal. Additionally, below there are few comments to the existing text. Change from: origin An IRI attribute that defines the specifics of the access request that is requested. Additionally, the special value of U+002A ASTERISK (*) MAY be used. This special value provides a means for an author to request from the user agent unrestricted access to network resources. Only the scheme and authority components can be present in the IRI that this attribute contains ([[!URI]], [[!RFC3987]]). subdomains A boolean attribute that indicates whether or not the host component part of the access request applies to subdomains of domain in the origin attribute. The default value when this attribute is absent is false, meaning that access to subdomains is not requested. to origin One of: - an IRI attribute that defines the specifics of the access request that is requested. Or - the special value of U+002A ASTERISK (*). This special value provides a means for an author to request from the user agent unrestricted access to network resources. Only the scheme and authority components can be present in the IRI that this attribute contains ([[!URI]], [[!RFC3987]]). - the special value of "local" (%x6c.6f.63.61.6c in ABNF). This special value provides a means for an author to request from the user agent unrestricted access to local network resources. The addressing of the resources relies primarily on IP addressing of hosts. It is up to the underlying network which version of the IP protocol is used and how local network is identified. subdomains A boolean attribute that indicates whether or not the host component part of the access request applies to subdomains of domain in the origin attribute. The default value when this attribute is absent is false, meaning that access to subdomains is not requested. This attribute applies only to the origin attribute values that rely on the DNS. The above abstract specification of locality shall allow for inclusion of IPv6,e.g. [1]. Additional comments 1. It should be clarified that the subdomains attribute applies only when the host is specified using DNS and not based on IP address. In other cases it shall be skipped. 2. " Only the scheme and authority components can be present in the IRI" "://" should be added between scheme and authority to make IRI [2] (this was discussed already in BONDI, although it is not yet in the related spec there). 3. Attributes section uses "authority" whereas the processing model section uses "iauthority". There the attributes section shall be corrected. Thanks, Marcin [1] http://tools.ietf.org/html/rfc4193#section-4.6 [2] http://tools.ietf.org/html/rfc3986#section-3 Marcin Hanclik ACCESS Systems Germany GmbH Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465 Mobile: +49-163-8290-646 E-Mail: marcin.hanclik@access-company.com ________________________________________ Access Systems Germany GmbH Essener Strasse 5 | D-46047 Oberhausen HRB 13548 Amtsgericht Duisburg Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda www.access-company.com CONFIDENTIALITY NOTICE This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited. If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Tuesday, 3 November 2009 15:45:11 UTC