https://github.com/iluwatar/java-design-patterns-web/issues/8 Update pattern categories and tags

role-object/README.md

@@ -5,9 +5,7 @@ folder: role-object
 permalink: /patterns/role-object/
 categories: Structural
 tags:
- - Java
- - Difficulty-Medium
- - Handle Body Pattern
+ - Extensibility
 ---
 
 ## Also known as
@@ -23,12 +21,14 @@ individual objects, different contexts are kept separate and system configuratio
 
 ## Applicability
 Use the Role Object pattern, if:
-- you want to handle a key abstraction in different contexts and you do not want to put the resulting context specific interfaces into the same class interface.
-- you want to handle the available roles dynamically so that they can be attached and removed on demand, that is at runtime, rather than fixing them statically at compile-time.
-- you want to treat the extensions transparently and need to preserve the logical object identity of the resultingobject conglomerate.
-- you want to keep role/client pairs independent from each other so that changes to a role do not affect clients that are not interested in that role.
+
+- You want to handle a key abstraction in different contexts and you do not want to put the resulting context specific interfaces into the same class interface.
+- You want to handle the available roles dynamically so that they can be attached and removed on demand, that is at runtime, rather than fixing them statically at compile-time.
+- You want to treat the extensions transparently and need to preserve the logical object identity of the resultingobject conglomerate.
+- You want to keep role/client pairs independent from each other so that changes to a role do not affect clients that are not interested in that role.
 
 ## Credits
+
 - [Hillside - Role object pattern](https://hillside.net/plop/plop97/Proceedings/riehle.pdf)
 - [Role object](http://wiki.c2.com/?RoleObject)
-- [Fowler - Dealing with roles](https://martinfowler.com/apsupp/roles.pdf)
+- [Fowler - Dealing with roles](https://martinfowler.com/apsupp/roles.pdf)