Profiling and personalization (PnP or "WAI") allows authors the ability to set Component Presentations for certain Target Groups. CD-side controls or tags then present the correct Component Presentations based on the user's profile.
Does PnP work over the CD Webservice?
If PnP is better suited for .aspx / .jsp "setups" would these be better alternatives for "profiling over OData (CD Webservice)?"
- Ambient Data Framework? Following Eric Huiza's ADF-in-a-nutshell post, I think we might use claims. Would using ADF make sense to influence the Component Presentations based on metadata in the components matching a given visitor "type?"
- REL logic. In the recent SDL Tridion community webinar, Mihai Cadariu explained how his REL Standard Library can offer if/else type logic. I can see how this could be used to show certain content to different (types of) users but I'm not sure how the delivery website would pass this information to the CD Webservice.
- Deliver-side "parsing" where delivery-side code gets a full page and parses it to show hide certain content.
Use case: in a CD Webservice request, get back certain component presentations based on component metadata (or Target Groups if possible?); in this case the roles might be "secured" content versus "not secured."