[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: From BPEL Editor's call - Updating the schema(s) in the spec. .
Thanks everyone. Alex, looks like your update went through fine. I do agree that Kevin's choice 3 is best for interim drafts. When we finalize the spec at the end of the TC process we will fix up all those decls without ellipses of course. Still need a volunteer for incorporating resolution for 62. Satish -----Original Message----- From: Alex Yiu [mailto:alex.yiu@oracle.com] Sent: Wednesday, April 07, 2004 9:46 PM To: Prasad Yendluri Cc: Liu, Kevin; Satish Thatte; curbera@us.ibm.com; Alex Yiu Subject: Re: From BPEL Editor's call - Updating the schema(s) in the spec. . Hi all, I just checked in Rev 1.26, which have the following changes: (1) Copy and paste the updated and corrected schema back to the main spec doc (2) Applied resolution for Issue 69 from Maciej Szefle in Section 12.5 and 12.5.1 This is my first check-in. I may miss some logistics steps. If so, please let me know and I shall correct them. If my check-in is OK, please pass the pen to next editor. Thanks! Regards, Alex Yiu Prasad Yendluri wrote: > Hi, > > I just checked in an update that took care of the default and > targetNamespace entries that were missed in the last pass. The one in > the Schema are still there but, Alex is updating that. > > Thanks, Prasad > > ------- Original Message -------- > Subject: Re: From BPEL Editor's call - Updating the schema(s) in the > spec. . > Date: Wed, 07 Apr 2004 17:04:59 -0700 > From: Prasad Yendluri <pyendluri@webmethods.com> > To: Liu, Kevin <kevin.liu@sap.com>, 'Satish Thatte' > <satisht@microsoft.com>, Alex Yiu <alex.yiu@oracle.com>, > curbera@us.ibm.com > References: > <99CA63DD941EDC4EBA897048D9B0061DA95F80@uspalx20a.pal.sap.corp> > > > Hmm, I just realized there are quite a few of the deafult declarations > that use the old URIs (I counted 11). First, I am sorry about that. I > should have been more careful. Given this, it seems easy to miss these > with each pass. May be (3) is a better choice.. > > Regards, Prasad > > Liu, Kevin wrote: > >> That's why I hesitated to say the prefix list will save us much time >> for sync in the beginning...:( >> >> Since we already decided to do that, I see at least a few ways to >> move forward: >> 1. change all the defaults to use explicit prefixes. This will >> involve a lot of tedious changes in the beginning, but once it's >> done, future changes will be minimal >> 2. For the examples where defaults are used, sync the namespaces with >> the prefix list every time we make changes to the namespace >> 3. just use placeholders for the defaults, for example something like >> xmlns = "http://..../business-process";, and add some >> explanation right after the prefix list. >> >> Personally I would say 2 is good since it reduce the sync work and >> keep the integrity of the examples. 3 is the simplest, but readers >> have to do the sync at "run time". >> >> Best Regards, >> Kevin >> >> >> -----Original Message----- >> *From:* Satish Thatte [mailto:satisht@microsoft.com] >> *Sent:* Wednesday, Apr 07, 2004 04:22 PM >> *To:* Prasad Yendluri; Alex Yiu; Liu, Kevin; curbera@us.ibm.com >> *Subject:* RE: From BPEL Editor's call - Updating the schema(s) >> in the spec.. >> >> Prasad, >> >> >> >> We still have a bunch of default namespace decls that mention the >> obsolete URIs. >> >> >> >> How do you guys want to deal with default namespaces? >> >> >> >> Satish >> >> >> >> ------------------------------------------------------------------------ >> >> *From:* Prasad Yendluri [mailto:pyendluri@webmethods.com] >> *Sent:* Wednesday, April 07, 2004 3:42 PM >> *To:* Satish Thatte; Alex Yiu; Liu, Kevin; curbera@us.ibm.com >> *Subject:* Re: From BPEL Editor's call - Updating the schema(s) >> in the spec.. >> *Importance:* High >> >> >> >> Just to let folks now, I just checked in the namespace updates >> (to be in sync with the schema) and the corresponding changes to >> examples we discussed today. Pls check and make sure the >> examples look right. >> >> I now hand the pen off to Alex/Paco for the schema updates. >> >> Also, I guess I will now await further notice to publish HTML out.. >> >> Regards, Prasad >> >> -------- Original Message -------- >> >> *Subject: * >> >> >> >> RE: From BPEL Editor's call - Updating the schema(s) in the spec.. >> >> *Date: * >> >> >> >> Wed, 7 Apr 2004 13:13:07 -0700 >> >> *From: * >> >> >> >> Satish Thatte <satisht@microsoft.com> <mailto:satisht@microsoft.com> >> >> *To: * >> >> >> >> Alex Yiu <alex.yiu@oracle.com> <mailto:alex.yiu@oracle.com>, >> Prasad Yendluri <pyendluri@webmethods.com> >> <mailto:pyendluri@webmethods.com> >> >> *CC: * >> >> >> >> Liu, Kevin <kevin.liu@sap.com> <mailto:kevin.liu@sap.com>, >> <curbera@us.ibm.com> <mailto:curbera@us.ibm.com> >> >> >> >> I am OK with using (A) - just paste schemas into Word file. The >> other options seem awkward so I guess the revision tracking will >> have to be via CVS. >> >> >> >> The separate schema is the authoritative one but we should >> obviously strive for consistency. >> >> >> >> ------------------------------------------------------------------------ >> >> *From:* Alex Yiu [mailto:alex.yiu@oracle.com] >> *Sent:* Wednesday, April 07, 2004 11:11 AM >> *To:* Prasad Yendluri >> *Cc:* Liu, Kevin; Satish Thatte; Alex Yiu; curbera@us.ibm.com >> *Subject:* Re: From BPEL Editor's call - Updating the schema(s) >> in the spec.. >> >> >> >> >> >> Hi Prasad, >> (adding Paco to the cc list) >> >> Sorry for missing the editors conf call today. >> I forgot to adjust my palm pilot to PDT (daylight saving time). >> >> Just to summarize what I did for those schema files so far: >> (1) I extracted the schema files from the word doc of Rev 1.22 >> (2) I updated the NS used in those schema files to point to "2004/03" >> (3) fix a number of typo mistakes in the schema files to make >> them a well-formed and valid XML Schema file >> >> I checked in both versions of after step (1) and after step >> (2)&(3) into the CVS. The CVS can be used to show and track the >> difference in different versions. >> >> These URLs show the CVS version-diff. >> http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/Sc hemaFiles/wsbpel_main.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H >> <http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/S chemaFiles/wsbpel_main.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H> >> >> http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/Sc hemaFiles/wsbpel_msgprop.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H >> <http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/S chemaFiles/wsbpel_msgprop.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H> >> >> http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/Sc hemaFiles/wsbpel_plinkType.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H >> <http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/S chemaFiles/wsbpel_plinkType.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H > >> >> >> >> Few things to clarify: >> (A) >> For XML Schema files, are we using the extracted XSD files as the >> main source of truth and using CVS as the main tool to keep track >> with versioning, right? >> For all other parts of the spec, we would continue to use Word >> Revisioning features to keep track of changes. (That is the >> impression that I got from a one-on-one phone conversation with >> Paco). >> >> However, if we really prefer using the Word document, I would >> suggest that whoever changes the schema need to extract them from >> the word file and run it schema against some XML schema tool to >> make sure it well-formed and valid. As you guys see, it is a >> little bit more labor intensive. >> >> Also, MS Word has an automatic formatting feature to replace a >> vanilla " with other format-oriented quotation characters (e.g. >> "abc" vs "abc"). Those characters make the XML Schema illegal. >> >> >> (B) >> If (A) is true, I guess one thing to do to reflect changes schema >> changes into the Word Doc is just copy and paste those schema >> files into the Word Doc. >> >> Otherwise, then I need to replicate changes that I back to the >> word document manually. >> >> (C) >> Is there any other goals that we may want to achieve in schema >> before the next publication of the spec draft? E.g. Issue 94 >> >> >> Thanks! >> >> >> Regards, >> Alex Yiu >> >> >> >> Prasad Yendluri wrote: >> >> >> Hi Alex, >> >> On the editor's call today, we discussed the pending tasks we >> need to accomplish prior to the publication of the next TC draft >> of WS-BPEL spec. One of the items involves updating the schema in >> the spec to be in sync with the changes you and Paco made >> recently. That is, the word version in CVS needs to be fixed up. >> Satish can perhaps clarify this better but I understand we need >> to reflect the changes via word tracking so we know what exactly >> changed. Kevin and I are coordinating and taking care of the >> other changes but, we need to have the schema changes also >> reflected prior to the publication. I took an action to ping you >> on this see if you might be able to get to it this week. Can you >> let us know.. >> >> Thanks. >> >> Prasad (for the spec editing team). >> > > > Prasad Yendluri wrote: > >> Hmm, I just realized there are quite a few of the deafult >> declarations that use the old URIs (I counted 11). First, I am sorry >> about that. I should have been more careful. Given this, it seems >> easy to miss these with each pass. May be (3) is a better choice.. >> >> Regards, Prasad >> >> Liu, Kevin wrote: >> >>> That's why I hesitated to say the prefix list will save us much time >>> for sync in the beginning...:( >>> >>> Since we already decided to do that, I see at least a few ways to >>> move forward: >>> 1. change all the defaults to use explicit prefixes. This will >>> involve a lot of tedious changes in the beginning, but once it's >>> done, future changes will be minimal >>> 2. For the examples where defaults are used, sync the namespaces >>> with the prefix list every time we make changes to the namespace >>> 3. just use placeholders for the defaults, for example something >>> like xmlns = "http://..../business-process";, and add some >>> explanation right after the prefix list. >>> >>> Personally I would say 2 is good since it reduce the sync work and >>> keep the integrity of the examples. 3 is the simplest, but readers >>> have to do the sync at "run time". >>> >>> Best Regards, >>> Kevin >>> >>> >>> -----Original Message----- >>> *From:* Satish Thatte [mailto:satisht@microsoft.com] >>> *Sent:* Wednesday, Apr 07, 2004 04:22 PM >>> *To:* Prasad Yendluri; Alex Yiu; Liu, Kevin; curbera@us.ibm.com >>> *Subject:* RE: From BPEL Editor's call - Updating the schema(s) >>> in the spec.. >>> >>> Prasad, >>> >>> >>> >>> We still have a bunch of default namespace decls that mention >>> the obsolete URIs. >>> >>> >>> >>> How do you guys want to deal with default namespaces? >>> >>> >>> >>> Satish >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> *From:* Prasad Yendluri [mailto:pyendluri@webmethods.com] >>> *Sent:* Wednesday, April 07, 2004 3:42 PM >>> *To:* Satish Thatte; Alex Yiu; Liu, Kevin; curbera@us.ibm.com >>> *Subject:* Re: From BPEL Editor's call - Updating the schema(s) >>> in the spec.. >>> *Importance:* High >>> >>> >>> >>> Just to let folks now, I just checked in the namespace updates >>> (to be in sync with the schema) and the corresponding changes to >>> examples we discussed today. Pls check and make sure the >>> examples look right. >>> >>> I now hand the pen off to Alex/Paco for the schema updates. >>> >>> Also, I guess I will now await further notice to publish HTML out.. >>> >>> Regards, Prasad >>> >>> -------- Original Message -------- >>> >>> *Subject: * >>> >>> >>> >>> RE: From BPEL Editor's call - Updating the schema(s) in the spec.. >>> >>> *Date: * >>> >>> >>> >>> Wed, 7 Apr 2004 13:13:07 -0700 >>> >>> *From: * >>> >>> >>> >>> Satish Thatte <satisht@microsoft.com> <mailto:satisht@microsoft.com> >>> >>> *To: * >>> >>> >>> >>> Alex Yiu <alex.yiu@oracle.com> <mailto:alex.yiu@oracle.com>, >>> Prasad Yendluri <pyendluri@webmethods.com> >>> <mailto:pyendluri@webmethods.com> >>> >>> *CC: * >>> >>> >>> >>> Liu, Kevin <kevin.liu@sap.com> <mailto:kevin.liu@sap.com>, >>> <curbera@us.ibm.com> <mailto:curbera@us.ibm.com> >>> >>> >>> >>> I am OK with using (A) - just paste schemas into Word file. The >>> other options seem awkward so I guess the revision tracking will >>> have to be via CVS. >>> >>> >>> >>> The separate schema is the authoritative one but we should >>> obviously strive for consistency. >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> *From:* Alex Yiu [mailto:alex.yiu@oracle.com] >>> *Sent:* Wednesday, April 07, 2004 11:11 AM >>> *To:* Prasad Yendluri >>> *Cc:* Liu, Kevin; Satish Thatte; Alex Yiu; curbera@us.ibm.com >>> *Subject:* Re: From BPEL Editor's call - Updating the schema(s) >>> in the spec.. >>> >>> >>> >>> >>> >>> Hi Prasad, >>> (adding Paco to the cc list) >>> >>> Sorry for missing the editors conf call today. >>> I forgot to adjust my palm pilot to PDT (daylight saving time). >>> >>> Just to summarize what I did for those schema files so far: >>> (1) I extracted the schema files from the word doc of Rev 1.22 >>> (2) I updated the NS used in those schema files to point to >>> "2004/03" >>> (3) fix a number of typo mistakes in the schema files to make >>> them a well-formed and valid XML Schema file >>> >>> I checked in both versions of after step (1) and after step >>> (2)&(3) into the CVS. The CVS can be used to show and track the >>> difference in different versions. >>> >>> These URLs show the CVS version-diff. >>> http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/Sc hemaFiles/wsbpel_main.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H >>> <http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/S chemaFiles/wsbpel_main.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H> >>> >>> http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/Sc hemaFiles/wsbpel_msgprop.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H >>> <http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/S chemaFiles/wsbpel_msgprop.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H> >>> >>> http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/Sc hemaFiles/wsbpel_plinkType.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H >>> <http://www-124.ibm.com/developerworks/oss/cvs/wsbpeltc/specifications/S chemaFiles/wsbpel_plinkType.xsd.diff?r1=text&tr1=1.1&r2=text&tr2=1.2&f=H > >>> >>> >>> >>> Few things to clarify: >>> (A) >>> For XML Schema files, are we using the extracted XSD files as >>> the main source of truth and using CVS as the main tool to keep >>> track with versioning, right? >>> For all other parts of the spec, we would continue to use Word >>> Revisioning features to keep track of changes. (That is the >>> impression that I got from a one-on-one phone conversation with >>> Paco). >>> >>> However, if we really prefer using the Word document, I would >>> suggest that whoever changes the schema need to extract them >>> from the word file and run it schema against some XML schema >>> tool to make sure it well-formed and valid. As you guys see, it >>> is a little bit more labor intensive. >>> >>> Also, MS Word has an automatic formatting feature to replace a >>> vanilla " with other format-oriented quotation characters (e.g. >>> "abc" vs "abc"). Those characters make the XML Schema illegal. >>> >>> >>> (B) >>> If (A) is true, I guess one thing to do to reflect changes >>> schema changes into the Word Doc is just copy and paste those >>> schema files into the Word Doc. >>> >>> Otherwise, then I need to replicate changes that I back to the >>> word document manually. >>> >>> (C) >>> Is there any other goals that we may want to achieve in schema >>> before the next publication of the spec draft? E.g. Issue 94 >>> >>> >>> Thanks! >>> >>> >>> Regards, >>> Alex Yiu >>> >>> >>> >>> Prasad Yendluri wrote: >>> >>> >>> Hi Alex, >>> >>> On the editor's call today, we discussed the pending tasks we >>> need to accomplish prior to the publication of the next TC draft >>> of WS-BPEL spec. One of the items involves updating the schema >>> in the spec to be in sync with the changes you and Paco made >>> recently. That is, the word version in CVS needs to be fixed up. >>> Satish can perhaps clarify this better but I understand we need >>> to reflect the changes via word tracking so we know what exactly >>> changed. Kevin and I are coordinating and taking care of the >>> other changes but, we need to have the schema changes also >>> reflected prior to the publication. I took an action to ping >>> you on this see if you might be able to get to it this week. Can >>> you let us know.. >>> >>> Thanks. >>> >>> Prasad (for the spec editing team). >>>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]