ISSUE-108: Should Contacts API have MUST instead of SHOULD for extended contact properties, is this a general issue for all specs?

Should Contacts API have MUST instead of SHOULD for extended contact properties, is this a general issue for all specs?

State:

CLOSED

Product:

Raised by:

Opened on:

2011-02-09

Description:

see http://dev.w3.org/2009/dap/contacts/#extended-contact-properties-and-parameters, section 6

"Non-standard, private properties and parameters should have a prefixed name starting with X (U+0058 LATIN CAPITAL LETTER X) or use a vendor-specific prefix. Extended properties and parameters can be defined bilaterally between user agents without outside registration or standardization. "

Related Actions Items:

No related actions

Related emails:

1. ISSUE-108: Should Contacts API have MUST instead of SHOULD for extended attributes, is this a general issue for all specs? (from sysbot+tracker@w3.org on 2011-02-09)

Related notes:

Display change log