OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: The Understanding Key Partitions TN


Title: [uddi-spec] Groups - OASIS UDDI Membership.xls uploaded
I've revisited this TN, and I'm convinced that we should expand it. One thing I'd really like to add is how one can implement a strict policy on permission to publish keys.
 
It's easy to state that a publisher may not publish any key for which they do not own the keygenerator tModel, but we run into a little trouble with keyGenerator tModels. We don't want to hand the parent keyGenerator tModel over to a publisher for the period during which they publish theirs, and we don't want to have a huge exception in the policy, right? So I thought I'd outline a procedure whereby the owner of the parent keyGenerator tModel publishes the keyGenerator tModel, then uses custody transfer to hand that tModel off to the publisher who wants it. All very simple and using nothing but the existing APIs, but not completely obvious to a neophyte. And that's what TNs are for, right? And this particular TN looks pretty empty without this.
 
I'll be trying to write the revised TN before the face-to-face (heck, I have ALL weekend, right?), and I'll try to post it to KAVI (if...) before then so members who aren't attending the face-to-face get their chance to explain to me that I'm an idiot beforehand :-)
 
Tony Rogers
 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]