Standards Committee Teleconference 2008 07 30: Difference between revisions
Joe.andrieu (talk | contribs) (first draft) |
Joe.andrieu (talk | contribs) No edit summary |
||
Line 8: | Line 8: | ||
==Attendees== | ==Attendees== | ||
* Joe Andrieu | * Joe Andrieu | ||
* Eve Maler | |||
==Previous Action Items== | ==Previous Action Items== | ||
#none | #none | ||
Line 18: | Line 18: | ||
==Notes== | ==Notes== | ||
We talked about outcomes from the Workshop and getting notes from the workshop into our flow. | |||
October workshop | |||
Looks good. Need to close the loop through the Doc. | |||
Next steps: User Journeys | |||
This is Iain's terminology, meaning the documentation. | |||
Difference between provisioning and where the provisioning data lives. | |||
Also difference between provisioning a relationship and provisioning the data. In other words, you don't want the data in the r-card. | |||
Policy Service | |||
Audit Service | |||
Policy: you have to give an address to a magazine service. So, if you move, you want them to get the updated address. But if you decide to change your policies unilaterally... | |||
1. You need assure the magazine agrees to the new policy. The magazine then needs to know about the policy, which may come from a different policy. | |||
Data could be bundled with policy. Or it could contain a pointer to a policy service. | |||
This policy stuff is one of the most immature areas, which is pretty grim, given the rest of the areas. | |||
IGF: CARML and AAPML | |||
Problem of system releasing data without policy is that enough users will actually do it. Which means you, perhaps permanently lose the expectation of control and then the ability to control as services get built upon receiving that data without controls. | |||
Need: machine-readable policy. | |||
===Future Agenda Topics=== | ===Future Agenda Topics=== | ||
Line 23: | Line 53: | ||
==Action Items== | ==Action Items== | ||
# Additional thoughts to one night stand notes to VRM wiki. Eve. By next Wednesday. | |||
# Close loop with and Doc and finalize Oct mtg date. Joe. By next Wednesday. | |||
==Next Meeting== | ==Next Meeting== | ||
[[Standards Committee Teleconference 2008 08 13]] | [[Standards Committee Teleconference 2008 08 13]] |
Latest revision as of 13:08, 30 July 2008
Standards Committee Teleconference Call Notes
Drafted by Joe Andrieu, July 30, 2008
Other Calls
Category:Standards Committee Teleconferences
Attendees
- Joe Andrieu
- Eve Maler
Previous Action Items
- none
Agenda
- Set Agenda
- Review previous Action Items
- Review Action Items
Notes
We talked about outcomes from the Workshop and getting notes from the workshop into our flow.
October workshop Looks good. Need to close the loop through the Doc.
Next steps: User Journeys This is Iain's terminology, meaning the documentation.
Difference between provisioning and where the provisioning data lives.
Also difference between provisioning a relationship and provisioning the data. In other words, you don't want the data in the r-card.
Policy Service Audit Service
Policy: you have to give an address to a magazine service. So, if you move, you want them to get the updated address. But if you decide to change your policies unilaterally...
1. You need assure the magazine agrees to the new policy. The magazine then needs to know about the policy, which may come from a different policy.
Data could be bundled with policy. Or it could contain a pointer to a policy service.
This policy stuff is one of the most immature areas, which is pretty grim, given the rest of the areas.
IGF: CARML and AAPML
Problem of system releasing data without policy is that enough users will actually do it. Which means you, perhaps permanently lose the expectation of control and then the ability to control as services get built upon receiving that data without controls.
Need: machine-readable policy.
Future Agenda Topics
- Discuss the distinctions between a Service Endpoint and a Service Manager.
Action Items
- Additional thoughts to one night stand notes to VRM wiki. Eve. By next Wednesday.
- Close loop with and Doc and finalize Oct mtg date. Joe. By next Wednesday.