/**
     * The workspace the style is part of, or <code>null</code> if the style is global.
     */
    WorkspaceInfo getWorkspace();

    /**
     * Sets the workspace the style is part of.
     */
    void setWorkspace(WorkspaceInfo workspace);

    /**
     * The workspace the layer group is part of, or <code>null</code> if the layer group is global.
     */
    WorkspaceInfo getWorkspace();

    /**
     * Sets the workspace the layer group is part of.
     */
    void setWorkspace(WorkspaceInfo workspace);

/**
 * Access limits to a style.
 */
public class StyleAccessLimits extends AccessLimits {

    public StyleAccessLimits(CatalogMode mode) {
        super(mode);
    }
}

/**
 * Access limits to a layer group.
 */

public class LayerGroupAccessLimits extends AccessLimits {

    public LayerGroupAccessLimits(CatalogMode mode) {
        super(mode);
    }

}

    /**
     * Returns the access limits for the specified style, or null if there are no limits.
     */
    public StyleAccessLimits getAccessLimits(Authentication user, StyleInfo style);

    /**
     * Returns the access limits for the specified layer group, or null if there are no limits.
     */
    public LayerGroupAccessLimits getAccessLimits(Authentication user, LayerGroupInfo layerGroup);

} This is unlike stores which must be contained within a workspace. A `null` workspace specifies that the style / layer group is global, and is "inherited" all workspaces. This is more clearly explained with an example.

Consider two workspaces, "foo" and "bar". And 3 styles "point", "line", and "poly":

* "point" is global, and has no workspace
* "line" references the "foo" workspace
* "poly" references the "bar" workspace

Now consider a *global* WMS GetCapabilities request, `/geoserver/wms?request=GetCapabilities`. Global services request contain only global entities, so the resulting document would contain only the "point" style.

Considering the request against the virtual "foo" endpoint, `/geoserver/foo.wms?request=GetCapabilities` would result in all the global styles, plus the ones local to foo, which includes "point", and "line". 

Similarly the request against the "bar" endpoint would contain the styles "point" and "poly".

To summarize:

# A global requests contains global styles and layer groups
# A virtual / workspace request contains all global styles/layer groups plus ones defined local to the workspace

h3. Behaviour with Layer Groups

Some further explanation of the handling of workspace local layer groups is required. Since a layer group
is really just a container for a set of layers, and styles, whether or not a layer group can be local is dictated by its contents. Which basically means that in order for a layer group to be local to a workspace, its contents must be local to the same workspace, or global. In other words  it is not possible for a layer group to be local to a workspace and access anything outside of that workspace that is not global. Since layers are by definition contained within a workspace this mostly amounts to styles. 

h3. Data Directory Changes

Workspace specific styles and layer groups are stored relative to the workspace root rather than the data directory root.