concept nest attribute in category rails

This is an excerpt from Manning's book Rails 4 in Action: Revised Edition of Rails 3 in Action.
You can create new instances of this model through the ticket form by using nested attributes. Nested attributes have been a feature of Rails since version 2.3, and they allow the attributes of any kind of association to be passed from the creation or update of a particular resource. In this case, you’ll pass nested attributes for a collection of new Attachment objects while creating a new Ticket model. The best part is that the code to do all this remains the same in the controller.
In this section, you set up the form that creates new Ticket objects to also upload files and create associated Attachment objects, by using nested attributes. This process was made possible by moving the responsibility of handling file uploads out of the Ticket model and into the associated Attachment model. The accepts_nested_attributes call in the Ticket model, as well as the simple_fields_for call in app/views/tickets/_form.html.erb, also played vital roles in getting this to work.
You’re done with nested attributes! Earlier we mentioned that the files uploaded to your application are publicly available for anybody to access because these files are uploaded to the public directory. Any file in the public directory is served up automatically by any web server, bypassing all the authentication and authorization in your Rails application. This is a bad thing. What if one of the projects in your application has files that should be accessed only by authorized users?

This is an excerpt from Manning's book Rails 3 in Action.
You can create new instances of this model through the ticket form by using nested attributes. Nested attributes have been a feature of Rails since version 2.3, and they allow the attributes of an association to be passed from the creation or update of a particular resource. In this case, you’ll be passing nested attributes for new asset objects while creating a new Ticket model. The best part is that the code to do all of this remains the same in the controller.
Hooray, the scenario passed! In this section, you set up the form that creates new Ticket objects to also create three associated Asset objects by using nested attributes. This process was made possible by moving the responsibility of handling file uploads out of the Ticket model and into the associated Asset model.