David Orain has posted a summary of last week's 3GSM conference in Barcelona. Apart from the staggering growth of this forum (50,000 attendees this year, from 34,000 last year and 24,000 back in 2002), the other headline messages he noted were:
# 1 --- Java is the de facto standard for FMC (Fixed/Mobile Convergence) service development and deployment;
# 2 --- Identity is the common, most critical component across converged services, service delivery platform and IMS;
# 3 --- Participation is key to address the device, services, network, data center, DRM and OSS/BSS challenges created by FMC.
Those look reassuringly familiar.
He also noted the dominant theme that "content is king". That's an interesting one from the identity perspective, because (as I've been saying for 3 or more years now) it's a classic case of what I call 'mediated web commerce'. That is, the mobile telco has to function as a delivery and billing channel for services which it does not itself create.
That implies a set of trusted relationships which allows the mobile telco to deliver the correct content to the right subscriber, and accurately return payment to the service/content provider. It's a classic use case for federation. I guess that makes federation mainstream... if we needed confirmation.
Posted by racingsnake
@ 11:17 AM GMT+00:00
I think anyone likely to be reading this blog has reached the stage where incoming email accumulates at a greater rate than one can sensibly deal with it.
I suspect we're on a similar curve with regard to blogging. Some days, blogworthy stuff accretes faster than I could redact and publish it.. at least in any form you long-suffering folks would want to see.
Not sure yet what to do about that --- though I watch with great interest and some technical envy the use of tag clouds, aggregators and the like.
Having just done a quick Google on it and found nothing, I hereby assert my right to be identified as the originator of the term
memetrawler... though the implementation of this invaluable future tool must, unfortunately, be left as an exercise for the reader ;^) Do let me know how you get on.
©Robin Wilton, February 2006
Posted by racingsnake
@ 10:07 AM GMT+00:00
Bob Blakley of IBM has written a thought-provoking piece on Kim's 'First Law',
here.
He makes a number of very valid points; for instance, that the 'Law' is not really a 'law' as one commonly understands that term in the technical world. I expect Kim is getting fed up with this frequent comment on the 'Laws' --- but it bears saying.
Sometimes (as in Bob's case) it's a reasoned argument based on his analysis that this particular 'Law' is a statement of
"things as we want them to be rather than things as they necessarily are" [my paraphrase]. That's a fair point, and once Bob has re-cast the 'Law' as a statement of requirements, he goes on to point out the value of a discussion of whether those requirements are desirable or feasible. And that's worth doing.
Other times, people balk at the use of the term 'Laws' because they suspect that this is a Microsoft ploy to establish an opinion-forming impression that this view of identity is 'self-evident and immutable'. Whether or not that's true at a corporate level is up to you to evaluate, but I don't think anyone who has actually debated this stuff with Kim would impute that motive to him personally.
Because the 'First Statement of Requirements' (as I guess I will have to call it for consistency's sake... how about FSOR for short) mentions 'ownership' of one's identifying information, Bob breaks identity down into two versions: your self-image (the representation you make of information about yourself) and your reputation (the representation others make of information about you). Biographies are often very different stories from auto-biographies.
In Bob's analysis, identities are subjective. I don't agree 100% with that
in the context of Bob's argument, because a lot of the data he subsequently includes in 'identity' is objective: for example, a bank's information about your credit history. There are those who hold that accounting data is subjective, but they tend either to be exponents of 'creative book-keeping', or on the more extreme fringes of 'post-structuralist discourse' theory. Pragmatically speaking, data such as credit history is objective; though if you decide to take the contrary position with your bank, do let me know the result.
Bob goes on to say, and again I agree, that often we agree to give out 'reputation' data because it's more convenient to do so than to try to live without doing so. So we agree that our banks hold data about the transactions we initiate --- a credit card purchase, for instance. When considering data privacy and user consent, though, we have to be careful about these cases, because they are not necessarily as simple as they appear. For instance, who counts as a 'third party' in this case? There are more of them involved than the average consumer might assume: there's the merchant, of course. There's probably a credit card company. There may well be a credit checking bureau or transaction authorisation service which provides an intermediate approval rather than involving the issuing bank online in real time. Subsequently the merchant's acquiring bank will also be involved.
Bob's right that a system in which all of these parties may only exchange this transaction data with the user's explicit in-line consent would be unworkable. What happens in practice is that, as far as the user is aware of it, consent is usually derived from some original set of banking terms and conditions relating to credit card payments. You, as the card-holder, agreed to that exchange of data more or less explicitly when you signed the forms. And uncomfortable though that thought may be, those of us who are conscious of it still go on using plastic payment, because of the relative inconvenience of being more rigorous about data privacy.
However, that doesn't mean we shouldn't open up these areas of 'implicit compromise', 'tacit connivance', call it what you will. The existing way of doing things has, let's face it, been arrived at more or less organically, by a set of evolutions, mutations and incremental changes driven largely by the service provider, not the user. (The UK use of 'cheque guarantee cards' is a case in point, which I will have to come back to at another time).
What ought to prompt change (or at least a thorough re-examination of assumptions) is the extent to which the user is now being expected to 'participate', to 'take greater care of personal data', 'shred sensitive documents', and actively manage an ever-widening range of online relationships.
When Bob comes to a concluding paragraph or two, it seems to me that he closes the door rather too firmly on the notion of user consent to data exchange. Here's how he puts it:
"It's clear that this "First Law requirement" isn't feasible --- a system which actually obeyed this law would be illegal (because it would withold information in cases in which the law requires it to disclose information without the data subject's consent), and it would be dangerous to the data subject (because it would withold personal information even in critical situations if consent couldn't be obtained --- for example when the data subject is unconscious and injured after an accident)."
I would cast it slightly differently.
--- First, even if one regards the First Law as canonical (and we started out by suggesting that it is not), then I think Bob would agree that the 'First Law could not and should not be universally applicable'.
--- If it is, instead, a Statement of Requirements, then again, it is not a statement of universal and unqualified requirements; it is a statement of qualified requirements which apply to varying extents in different circumstances.
--- The example Bob ends with does not, in my view, either follow from his premises or support his conclusion, and here's why:
He elides the distinction between 'personal information' and 'identifying information'; in a medical emergency, with an unconscious injured patient, the patient's identity does not, of itself, help the physician. It help the physician insofar as it allows her/him to retrieve relevant healthcare information about the patient --- and while knowing the patient's identity is a useful way of retrieving that information, it is not a necessary condition for doing so.
For instance, if if it is reasonable to assume that the physician used the unconscious patient's driving licence as the 'index' to find the patient's healthcare record, it is no less reasonable to assume that the patient could be issued with a 'healthcare card' which either carried the relevant healthcare data itself, or provided an 'index' allowing retrieval of that data from elsewhere. Neither mechanism need disclose the patient's identity as well as their emergency healthcare data.
This post is now far longer than I originally intended --- but I told you Bob's piece was thought-provoking! Incidentally, so was another (independent but related) conversation I had at IBM on Wednesday. More on that story later.
I'll just end with a plea to Bob: don't leave us in suspense! You promised to write soon about the subtle relevance of privacy vs. security to this knotty problem... how about it?
Posted by racingsnake
@ 09:56 AM GMT+00:00
[
Comments [2]
]