Abbie,
Here are my comments about draft FSP.
1. I am curious about the title of this document. It is a
framework about personalization service, so why do it is named as
FSP? Does FPS more appropriate?
2. I agree that the idea of having an uniform personalization
service is great. However, due to the widely deployment of personalized
portals, it is very difficult to integrate them together. For example,
my.yahoo.com, and myvoicestream.com. As such, even if you shift the
responsibility from origin web servers to the edge, the edge still need to
record the subscriber profiles of different portals for each
person, which is a serious scalability issue.
3. "The content provider may not be aware of many types of
information about the subscriber, including geographic location, QoS
policy, device type, and access rate, which could dramatically increase
the efficiency of any personalization task undertaken on their behalf."
I can not see a strong relationship between the information you
listed here and existing personalizeation service which focus on habits
and perferences. It may be used to create new personalizated service.
Thanks.
-Weisong