title: Is this a valid REST API?
body: <p>I am designing an API.</p>
  
  <p>There's the user profile, accessible at</p>
  
  <p><a href="http://example.org/api/v1/users" rel="nofollow">http://example.org/api/v1/users</a> (resp. <a href="http://example.org/api/v1/users/%3aid" rel="nofollow">http://example.org/api/v1/users/:id</a>)</p>
  
  <p>Now, the user's profile will be dynamic.
  So we will allow an API function to add a new profile attribute.</p>
  
  <p>Is the following a valid REST API URL for this?</p>
  
  <p>POST <a href="http://example.org/api/v1/users/attributes" rel="nofollow">http://example.org/api/v1/users/attributes</a></p>
  
  <p>Indeed, to retrieve a specific user, the user's id would be appended to the <code>.../users/</code> URL.
  Now if I use the "<code>attributes</code>" element after <code>/users/</code>, would that somehow break the user id pattern for the URL?</p>
  
  <p>I'd like to keep the base URL to be <code>api/v1/users</code> though, because logically I am modifying the users profile still...</p>
  
  <p>EDIT: The attributes would be added valid for all profiles, it's independent of a user. Say the profile has "name", "surname", "email", and I want to add "address" to all profiles (Of course I know that users with a missing "address" field would not get the new attribute)</p>
  
  <p>What is a good practice to address such an issue?</p>