If one could specify a comma separated list of tag keys: autos,bikes,boats one for each Tagger Group for example, you would have a near-complete custom routing system. You could then have a listing Collections container vehicles/ with each child having a tag from one or many Tagger groups.
Currently the workaround might be having child resources of vehicles and sending Tagger links to those child elements, but the tag key still has to be in the URL so you'd get "vehicles/autos/tags/blue/" but if each group could be a URL piece that the gateway "listened" for, you could then just do: "vehicles/autos/blue/" <= full routing for that section of the site. Only because the child Resources of vehicles could have a one-to-many relation with the Tagger groups, whereas you'd have to create symlinks in multiple containers to do this with standard parent/child relations.
If one could specify a comma separated list of tag keys:
autos,bikes,boats
one for each Tagger Group for example, you would have a near-complete custom routing system. You could then have a listing Collections containervehicles/
with each child having a tag from one or many Tagger groups.Currently the workaround might be having child resources of
vehicles
and sending Tagger links to those child elements, but the tag key still has to be in the URL so you'd get "vehicles/autos/tags/blue/" but if each group could be a URL piece that the gateway "listened" for, you could then just do: "vehicles/autos/blue/" <= full routing for that section of the site. Only because the child Resources ofvehicles
could have a one-to-many relation with the Tagger groups, whereas you'd have to create symlinks in multiple containers to do this with standard parent/child relations.