RE: Approach to USDL variant management

Dear Norbert,
thanks for your feedback. Some comments from my side below


-          In fact we will present the ideas to the W3C and check whether it would be an option that they host such a tool

-          We will follow up and concretize the "processes." So far it is indeed unclear how much governance is needed and how long-lasting the processes will be

-          I agree that license costs shouldn't be involved

In addition, the BPMN ext. mechanism is not  a full-fledged alternative in my opinion. Let me clarify this along the four pillars of the proposed solution


1.       Canonical Grammar : UN/CEFACT Core Component Technical Specification (CCTS)

2.       Context Logic: UN/CEFACT Unified Context Methodology Technical Specification

3.       Tooling: Knowledge Integration Library

4.       Processes: Tool-supported processes for governance

As far as I can see, there is neither 1, 2, nor 4 in the BPMN ext. mechanism. Please let me know if I am wrong.

Best
Daniel

From: public-xg-usdl-request@w3.org [mailto:public-xg-usdl-request@w3.org] On Behalf Of Weissenberg, Norbert
Sent: Freitag, 11. März 2011 11:57
To: public-xg-usdl@w3.org
Subject: WG: Approach to USDL variant management

Hello Daniel, hello all,

the protocol for my feedback is okay, the alternative BPMN 2.0 extension mechanism is already mentioned.

One thought mentioned in the session might be added: is the USDL-v2 the language visible in all contexts,
and is there an inverse process of reducing the kernel visible in all contexts.

The path can be followed iff
- W3C (or another std org) can be conviced to run the central schema registry
- the processes are defined in an acceptable way, i.e. there is a good probability to get needed attributes accepted quickly, e.g. in a test stage.
- and there is no licence cost.

The pro is that the schema is centrally controlled and parties can profit by extensions of others.
The con is that this control might be a long-lasting process not agile enoth for the industry. That might kill the approach.
We should then evaluate if BPMN extension mechanism is enough.

-Norbert-

Von: public-xg-usdl-request@w3.org [mailto:public-xg-usdl-request@w3.org] Im Auftrag von Oberle, Daniel
Gesendet: Freitag, 11. März 2011 10:52
An: Public XG USDL (public-xg-usdl@w3.org); Member XG USDL
Cc: Stuhec, Gunther
Betreff: RE: Approach to USDL variant management

Dear all,
since there is no audio and we did  not take separate notes of your feedback could you please:


-          Recap the feedback you gave

-          Let us know if there are alternate approaches which we might have missed

-          Give us your general thoughts whether we should follow this path

Would be nice if you could do so until our next regular call on 21st of March.

Sorry for the inconvenience
Daniel

PS: Please reply to the mailinglist, if possible

From: member-xg-usdl-request@w3.org [mailto:member-xg-usdl-request@w3.org] On Behalf Of Kadner, Kay
Sent: Donnerstag, 10. März 2011 15:46
To: Public XG USDL (public-xg-usdl@w3.org); Member XG USDL
Subject: RE: Approach to USDL variant management

Dear USDL interested colleagues,

Thanks again for that lively discussion and feedback in yesterday's call about USDL Variant management. Please find the minutes in our Wiki at http://www.w3.org/2005/Incubator/usdl/wiki/2011-03-09_Approach_to_USDL_variant_management. You can also review the slides there. Unfortunately, the recording did not work as expected. We'll give it another try when we present this to Mr. Jaffe.

Best Regards,
Kay Kadner

-----Original Appointment-----
From: Kadner, Kay
Sent: Dienstag, 19. Mai 2009 12:20
To: Public XG USDL (public-xg-usdl@w3.org); Member XG USDL; Fluegge, Barbara; Holger Last; 'matthias.dabisch@attensity.com'; 'Massimo Romanelli'; Oberle, Daniel
Cc: Fasse, Axel; 'Stewart Welbourne'; 'Peltz, Christopher'; Leidig, Torsten; 'Schulte, Stefan'; Hellinger, Christian (external); 'Blackwell, Ken'; 'Weissenberg, Norbert'; Stuhec, Gunther; Frenzel, Petra; Neidecker-Lutz, Burkhard; 'K. Kutsikos'; Markus Radmayr; 'Nils Meyer'; Greguletz, Nicole; Schaeffler, Martin
Subject: Approach to USDL variant management
When: Mittwoch, 9. März 2011 15:30-16:30 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna.
Where: phone conference


Dear Members and potential users of USDL,

One important issue for a language like USDL is the management of variants and deviations from the original specification. In other words, we expect that various versions will be derived from the original USDL, where each of these versions will be dedicated to some specific domain, like car repair, financing, health, or simply countries. In this call, we present an approach to handle these variations. Of course, we like to discuss that with you and get feedback and opinions about that approach.

Please find the dial-in details below. We are looking forward to a lively discussion.

Best Regards,
Kay Kadner

https://sap.emea.pgiconnect.com/D044576
Participant Passcode:    6533560918

Dial in numbers:
Germany, Frankfurt:      +49 69 71044 5497
Australia, Sydney        +61 2 8223 9948
USA, New York:   +1 212 999 6675
Canada, Montreal:        +1 514 315 7878
France, Paris:           +33 (0)1 70 99 43 40
Greece, Athens:  +30 210 969 6487
UK, London:              +44 20 7153 9921
Finland, Helsinki:       +358 9 2319 3954
Austria, Vienna          +43 2 68220 59207
Sweden, Stockholm        +46 8 5051 3640

Dr. Kay Kadner
Senior Researcher   I   Chair of W3C USDL XG   I   SAP Research Dresden
SAP AG   I   SAP Research   I   Chemnitzer Str. 48   I   01187 Dresden   I   Germany

T +49 351 4811-6127   I   F +49 6227 78-44576   I   M +49 172 4639220   I   mailto:kay.kadner@sap.com
www.sap.com/research<http://www.sap.com/research>

Please consider the impact on the environment before printing this e-mail.


Pflichtangaben/Mandatory Disclosure Statements:
http://www.sap.com/company/legal/impressum.epx
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten.
Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung
oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die
empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have
received this e-mail in error, you are hereby notifi ed that any review, copying, or distribution of it is strictly prohibited.
Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.