Groups - SOA-EERP TC Regular Teleconference modified

[wtcox@comcast.net]

SOA-EERP TC Regular Teleconference has been modified by Mr. William Cox*

Date:  Wednesday, 18 February 2009
Time:  09:00pm - 10:00pm ET

Event Description:
Regular teleconference meeting of the OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC.

Conference call by FreeConferenceCall.com
Conference Dial-in Number: +1 712 432-1601
Access Code: 168837#

PLEASE DO NOT USE SKYPE VOICE CALLING - the connection quality makes it hard to have a productive meeting.

If you're OUTSIDE the US, contact William Cox off-list or send an email note to the TC list for dial-in information. You can call the US number above.

Please note that International numbers and codes do not change from meeting to meeting, and are local to many countries.

TEXT CHAT DURING MEETING:
http://webconf.soaphub.org/conf/room/soa-eerp/

If you haven't used this chat before (or don't have cookies enabled in your browser), after you connect click on "Setting" in the top bar, and change the default name to yours. Select "Save Settings" to save your name and other settings in a cookie for your next use.

Agenda:
Call Roll

Approve previous minutes (http://www.oasis-open.org/committees/download.php/31286/SOA-EERP%2020090204%20Minutes%20Draft.doc)

Action Item Review

Old Business
     Discuss work on translations for planned contributions (Andy Lee)

New Business
     Architectural requirements for BQoS (Bill Cox)

Adjourn

Minutes:
SOA-EERP TC Meeting Minutes (Approved)
20090218 9:00pm New York Time (EST)
20090219 Morning East Asia Time

Call Roll
	Attending: Rex Brooks, William Cox, Dongpu Fu, Carl Mattocks, Andy Lee
	Symon Chang, Chuan Liu (observer)

Approved previousminutes without changes. Unanimous consent.
(http://www.oasis-open.org/committees/download.php/31286/SOA-EERP%2020090204%20Minutes%20Draft.doc)

Action Item Review
	0007 (Andy) Write conceptual framework and timeline on how EERP and specs would be used in an enterprise
	0006 (Andy) Ensure that Hong Zhou joins TC
	0005 (Andy) Provide English translation of Chinese documents in Contribution Folder
	All pending -- Andy not yet to a phone.

Old Business
	Discuss work on translations for planned contributions (Andy Lee)
	ACTION Andy Translate specifications and schemas to English and contribute to the TC by next meeting.

New Business
	Architectural requirements for BQoS (William Cox) Introduction based on email found in the archives at 		http://lists.oasis-open.org/archives/soa-eerp/200902/msg00007.html (William Cox)

Discussion led off with the points in the email and followup emails on the list.

Rex: Interested third party components can also include any certifications, licenses, public keys, etc-what we are calling in the SOA Reference Architecture the "Execution Context."  I would add Third Party Services to the bullet points for core components of BQoS, and for Reputation ratings and regulatory compliance, if needed.

Carl: Based on experience selecting service providers, et.g Amazon.com, freelancers, I look for how many times that service has been provided, the service by that particular provider, or total services from a provider, and other computations. Very basic fact is how many times that service has been provided.

Bill: meaningful in certain cases - but in (say( electricity, done it billions of times. Could that instead be keyed or contained to the WS-Rating ?

Carl: Want to assess acceptability of the service, the provider, the specific implementation of the service.

Rex: Useful for the core: indication of whether a service has details or other things - indicator for confidence that service is reliable enough to use. Mentioned as third party components. Not nec in the schema, but "yes we have this" and where do you store it? URI for the potential additional info?

Bill: Recast in terms of potential ratings? Where it is doesn't matter logically, only in the size of what's sent on the wire.

Discussion: Third party things like BBB have a page for a merchant. Could use that url to show.

Bill Cox: But a vendor doesn't put links to every possible service party rating service. Make a key value that can be used to locate such ratings..

Rex: Do as a key, or as a URL; I'm more concerned that there's a way that a potential consumer of the service can get information. Hold for services that aggregate other services, pass that along to the actual end user.

Bill: An aggregator stands behind the aggregation, level of information on ratings is probably the service provider.

Carl: People like Dun&Bradstreet and Better Business Bureaus aggregate the track record in reports. To be a supplier to the US Govt, you have to provide a DUNS number. Very broadly a requirement.

Bill: Rating for the provider, or the service, or something else?

Rex: Some combination of both. not just about rating the service for confidence or reliability - any third part action (regulatory measures compliance, 3rd party certification)

Bill Cox: Architecturally that serves as a key, then

Carl: If we limit our thoughts to quality of SERVICE rather than the quality of PROVIDER we might draw a box around what we're looking at.

Bill Cox: Proposed that one could select or list industries and use cases that could use BQOS and use them as a lens to examine the inclusion/non-includion. What kind of industry/service set are you thinking about?

Carl: Professional services -- really mean a service that is being commoditized, usually provided by a so-called professional (with licenses, certificates) - for instance, a radiologist, CPA, data modeler.

Bill Cox: What is price?  The service?

Carl: Characteristics are well defined, nothing to change. Read an xray.

Bill: Like Medical industry in US - diagnosis code, service code, and a complete taxonomy.

Rex: Along lines of health care suppliers, provide reporting services, e.g. new class in health care that aggregates the output of a radiology lab (e.g.) , sends a copy to the patient, doctor, insurer, regulatory agency.

Bill: Another use case: the service is provision of energy - nat gas, oil, electriciy - and units are part of the transaction.

Carl: if it can be commoditized, scope is previously defined, there are no unknowns.

Bill: Energy, at a time, 100 MWHours.

Carl: For accounting, there's a unit, a time, and a context.

Bill Cox: Aggregation is extremely important. Want to have the aggregator take from its suppliers, deliver the same type of artifact to its customers.

Rex: Pretty simple example: a flight delay, or contract with an airline to get you from NY to LAX at a particular time, and there's a flight delay. Ticket on Continental, weather isn't attributable to the seller/aggreator or the airline. Changes of state that need to be reported, important QOS problem. Part of agg of services, within that aggregation has to be reported/best if reported. Should be some mechanism available that if it's delayed you hear.

Bill: What would you use to decide who will take you from JFK-LAX next week?

Rex: If a service will inform you about changes, a criterion may be notification.

Bill: Differentiation - e.g. notification of delays - can we hope to differentiate all of those? This could be a large information set.

Rex: Can put in a service description that you...take extra care. Travelocity makes that claim a lot, that if there's construction on your hotel they'll notify.

Bill: Multiple levels of service comparison.  Carl's commoditization - are there standard services? What does the service provider do to differentiate?

Bill: How do you formalize that in a way to make it both comparable and useful.

Carl: Do you go for the basic service or the premium,

Bill: Are we in the business of defining services? I thought that was WSDL and business process descriptions?

Carl: Can do a commoditized/standardized service. can't have optional things.

Rex: The task is to find the right balance between complexity and sufficiency - sufficient amount of info.

Bill: Assuming that services we compare are the same, and the same services can be compared. Let's continue on the email list.

Adjourned 10:16pm EST

This event is one in a list of recurring events.
Other event dates in this series:

Wednesday, 07 January 2009, 09:00pm to 10:00pm ET
Wednesday, 21 January 2009, 09:00pm to 10:00pm ET
Wednesday, 04 February 2009, 10:00pm to 10:45pm ET
Wednesday, 04 March 2009, 09:00pm to 10:00pm ET
Wednesday, 18 March 2009, 09:00pm to 10:00pm ET
Wednesday, 01 April 2009, 09:00pm to 10:00pm ET
Wednesday, 15 April 2009, 09:00pm to 10:00pm ET
Wednesday, 29 April 2009, 09:00pm to 10:00pm ET
Wednesday, 13 May 2009, 09:00pm to 10:00pm ET
Wednesday, 27 May 2009, 09:00pm to 10:00pm ET
Wednesday, 10 June 2009, 09:00pm to 10:00pm ET
Wednesday, 24 June 2009, 09:00pm to 10:00pm ET
Wednesday, 08 July 2009, 09:00pm to 10:00pm ET
Wednesday, 22 July 2009, 09:00pm to 10:00pm ET
Wednesday, 05 August 2009, 09:00pm to 10:00pm ET
Wednesday, 19 August 2009, 09:00pm to 10:00pm ET
Wednesday, 02 September 2009, 09:00pm to 10:00pm ET
Wednesday, 16 September 2009, 09:00pm to 10:00pm ET
Wednesday, 30 September 2009, 09:00pm to 10:00pm ET
Wednesday, 14 October 2009, 09:00pm to 10:00pm ET
Wednesday, 28 October 2009, 09:00pm to 10:00pm ET
Wednesday, 11 November 2009, 09:00pm to 10:00pm ET
Wednesday, 09 December 2009, 09:00pm to 10:00pm ET
Wednesday, 23 December 2009, 09:00pm to 10:00pm ET

View event details:
http://www.oasis-open.org/apps/org/workgroup/soa-eerp/event.php?event_id=21788

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able to
copy and paste the entire link address into the address field of your web
browser.

BEGIN:VCALENDAR
METHOD:PUBLISH
VERSION:2.0
PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-WR-CALNAME:My Calendar
BEGIN:VEVENT
CATEGORIES:MEETING
STATUS:TENTATIVE
DTSTAMP:20090304T000000Z
DTSTART:20090219T020000Z
DTEND:20090219T030000Z
SEQUENCE:12
SUMMARY:SOA-EERP TC Regular Teleconference
DESCRIPTION:Regular teleconference meeting of the OASIS Service-Oriented
  Architecture End-to-End Resource Planning (SOA-EERP) TC.\n\nConference
  call by FreeConferenceCall.com\nConference Dial-in Number: +1 712
  432-1601\nAccess Code: 168837#\n\nPLEASE DO NOT USE SKYPE VOICE
  CALLING - the connection quality makes it hard to have a productive
  meeting.\n\nIf you're OUTSIDE the US\, contact William Cox off-list or
  send an email note to the TC list for dial-in information. You can
  call the US number above.\n\nPlease note that International numbers
  and codes do not change from meeting to meeting\, and are local to
  many countries.\n\nTEXT CHAT DURING
  MEETING:\nhttp://webconf.soaphub.org/conf/room/soa-eerp/\n\nIf you
  haven't used this chat before (or don't have cookies enabled in your
  browser)\, after you connect click on "Setting" in the top bar\, and
  change the default name to yours. Select "Save Settings" to save your
  name and other settings in a cookie for your next use.\n\nGroup: OASIS
  Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP)
  TC\nCreator: Mr. William Cox*
URL:http://www.oasis-open.org/apps/org/workgroup/soa-eerp/event.php?event_id=21788
UID:http://www.oasis-open.org/apps/org/workgroup/soa-eerp/event.php?event_id=21788
END:VEVENT
END:VCALENDAR