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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx-editors message

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


Subject: RE: [ws-rx-editors] RE: Public Comments Form


There is issue of what happens when you do an HTTP GET on
"http://www.oasis-open.org/ws-rx/200608/"; (note the trailing slash). If
I remember correctly we decided, when we put up the last CD, that such
links should also map to the RDDL documents.

- gp 

> -----Original Message-----
> From: Patil, Sanjay [mailto:sanjay.patil@sap.com] 
> Sent: Wednesday, August 16, 2006 8:19 AM
> To: Robin Cover
> Cc: mary.mcrae@oasis-open.org; Marc Goodner; 
> ws-rx-editors@lists.oasis-open.org
> Subject: RE: [ws-rx-editors] RE: Public Comments Form
> 
> 
> While waiting for the HTML version, can we get started with 
> creating the structure for the other artifacts.
> 
> Following is what I think needs to happen. Editors, please 
> chime in with your yes/no/wait signal before Robin starts 
> cranking the wheels.
> 
> The zip package (without the HTML version is at) - 
> http://www.oasis-open.org/committees/download.php/19691/WSRM-CD4.zip
> 
> The map of the links to their artifacts is:
> 1> http://docs.oasis-open.org/ws-rx/wsrm/200608 ==>
> wsrm-1.1-rddl-cd-04.html
> 2> http://docs.oasis-open.org/ws-rx/wsrmp/200608 ==>
> wsrmp-1.1-rddl-cd-04.html
> 3> 
> http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-spec-cd-04.pdf
> ==> wsrm-1.1-spec-cd-04_diff.pdf
> 4>
> http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-schema-2
00608.xsd
> ==> wsrm-1.1-schema-200608.xsd
> 5>
> http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-wsdl-200608.wsdl
> ==> wsrm-1.1-wsdl-200608.wsdl
> 6>
> http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-spec-cd-04.pdf
> ==> wsrmp-1.1-spec-cd-04.pdf
> 7>
> http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-schema
-200608.xs
> d ==> wsrmp-1.1-schema-200608.xsd
> 
> One question this raises is - should we add links to the 
> different formatted specifications from the RDDL? I think we should.
> 
> -- Sanjay
> 
> 
> >-----Original Message-----
> >From: Robin Cover [mailto:robin@oasis-open.org]
> >Sent: Wednesday, Aug 16, 2006 1:35 AM
> >To: Patil, Sanjay
> >Cc: mary.mcrae@oasis-open.org; Marc Goodner; 
> >ws-rx-editors@lists.oasis-open.org
> >Subject: RE: [ws-rx-editors] RE: Public Comments Form
> >
> >Typically, it takes some manual steps to create the proper 
> links when 
> >we install the spec components (prose documents, schemas, 
> WSDLs, RDDLs, 
> >etc). I'll be glad to help with this; having the "clear map 
> of URLs and 
> >the artifacts" as Sanjay advises will help ensure a good result.
> >
> >None of the (currently) manual steps is so complicated as to defy 
> >automation, and indeed, full automation (with TC member 
> upload) is the 
> >goal.
> >
> >As to the manner of implementing server redirects: in an OASIS Staff 
> >meeting tomorrow (2006-08-16) I plan to renew a request for 
> support by 
> >OASIS IT programming staff to set up better web server 
> behaviors using 
> >Apache directives -- e.g., for delivering a RDDL when a 
> namespace URI 
> >is dereferenced.  The current implementation nominally 
> "works" but is 
> >clunky, and does not support the kind of behavior (I think) 
> we want to 
> >see in web browsers.
> >Hopefully I'll have good news on this topic soon.
> >
> >Robin Cover
> >
> >==============
> >
> >On Tue, 15 Aug 2006, Patil, Sanjay wrote:
> >
> >> Mary,
> >>
> >> I don't think that unpacking the zip file will resolve to the 
> >> appropriate directory structure by itself. We may need some manual 
> >> moving around of files and tweaking of URLs to ensure that -
> >> a> The two RDDL files are retrievable via a GET on their respective
> >> namespace URI
> >> b> The URLs (total of five if I am not mistaken) for the
> >specifications
> >> and ancillary artifacts referred to in the RDDL files are 
> correctly 
> >> working
> >>
> >> Editors, could you please provide a clear map of URLs and
> >the artifacts
> >> that are supposed to be sitting behind them. That might 
> simplify the 
> >> tasks of the OASIS staff a little bit.
> >>
> >> -- Sanjay
> >>
> >>
> >> ________________________________
> >>
> >> 	From: Mary McRae [mailto:marypmcrae@gmail.com]
> >> 	Sent: Tuesday, Aug 15, 2006 16:14 PM
> >> 	To: 'Marc Goodner'; Patil, Sanjay; mary.mcrae@oasis-open.org
> >> 	Cc: ws-rx-editors@lists.oasis-open.org
> >> 	Subject: RE: [ws-rx-editors] RE: Public Comments Form
> >>
> >>
> >> 	Marc's correct -- at this point in time, only staff can 
> upload to 
> >> docs.oasis-open.org. It's our goal to build an interface that will 
> >> support member uploads, but that project's on hold until we
> >get past the
> >> email server restoration.
> >>
> >> 	All I should need is the single zip file which should 
> resolve to the 
> >> appropriate directory structure.
> >>
> >> 	Regards
> >>
> >> 	Mary
> >>
> >>
> >>
> >>
> >> ________________________________
> >>
> >> 		From: Marc Goodner [mailto:mgoodner@microsoft.com]
> >> 		Sent: Tuesday, August 15, 2006 6:35 PM
> >> 		To: Patil, Sanjay; mary.mcrae@oasis-open.org
> >> 		Cc: ws-rx-editors@lists.oasis-open.org
> >> 		Subject: RE: [ws-rx-editors] RE: Public Comments Form
> >>
> >>
> >>
> >> 		I agree. I believe we had always planned on 
> posting the docs at the 
> >> namespace location there anyway. I think the zip
> >is already
> >> prepared that could be used to stage it. Only OASIS staff 
> can upload 
> >> there is my understanding.
> >>
> >>
> >>
> >> 		From: Patil, Sanjay [mailto:sanjay.patil@sap.com]
> >> 		Sent: Tuesday, August 15, 2006 2:15 PM
> >> 		To: mary.mcrae@oasis-open.org
> >> 		Cc: ws-rx-editors@lists.oasis-open.org
> >> 		Subject: RE: [ws-rx-editors] RE: Public Comments Form
> >>
> >>
> >>
> >>
> >>
> >> 		I think using the docs repository may be a 
> better idea since that 
> >> may also provide stable URI for hyperlinking from
> >RDDL files.
> >> Editors, do you agree?
> >>
> >>
> >>
> >> 		If we take the docs repository route, then I 
> think we will need to 
> >> work with the OASIS staff to get the document
> >area set up,
> >> etc. Could we get all of that done before this week's
> >conf-call (on 8/17
> >> at 1 PM PST)?
> >>
> >>
> >>
> >> 		-- Sanjay
> >>
> >>
> >>
> >> ________________________________
> >>
> >> 			From: Mary McRae [mailto:marypmcrae@gmail.com]
> >> 			Sent: Tuesday, Aug 15, 2006 14:00 PM
> >> 			To: Patil, Sanjay; mary.mcrae@oasis-open.org
> >> 			Cc: ws-rx-editors@lists.oasis-open.org
> >> 			Subject: [ws-rx-editors] RE: Public 
> Comments Form
> >>
> >> 			Hi Sanjay,
> >>
> >>
> >>
> >> 			  If I can unzip the package to the 
> docs repository, I will be 
> >> able to point to each of the formats
> >separately as
> >> well as the collection of ancillary files. This is the most 
> >> user-friendly approach. If the files aren't to be uploaded to 
> >> docs.oasis-open.org, I'd recommend one combined zip,
> >separate copies of
> >> the spec itself in each of the three formats, and a separate
> >zip of the
> >> ancillary files. That way the reviewers can download just 
> the version 
> >> they want to review along with the ancillary data.
> >>
> >>
> >>
> >> 			Mary
> >>
> >>
> >>
> >> ________________________________
> >>
> >> 				From: Patil, Sanjay
> >> [mailto:sanjay.patil@sap.com]
> >> 				Sent: Tuesday, August 15, 2006 4:49 PM
> >> 				To: mary.mcrae@oasis-open.org
> >> 				Cc: ws-rx-editors@lists.oasis-open.org
> >> 				Subject: RE: Public Comments Form
> >>
> >> 				Mary,
> >>
> >>
> >>
> >> 				Would it be fine to provide you 
> a single link that points to .zip 
> >> package containing specifications
> >in the three
> >> formats along with RDDL files, and WSDL, schema files (WSDL
> >and schema
> >> artifacts are included in the specifications as well), 
> etc. Or do you 
> >> expect separate links for the three formats?
> >>
> >>
> >>
> >> 				Copying the Editors Team here 
> to cut short the turnaround time.
> >>
> >>
> >>
> >> 				-- Sanjay
> >>
> >>
> >>
> >> ________________________________
> >>
> >> 				From: Mary McRae
> >> [mailto:marypmcrae@gmail.com]
> >> 				Sent: Monday, Aug 14, 2006 19:07 PM
> >> 				To: Patil, Sanjay
> >> 				Subject: RE: Public Comments Form
> >>
> >> 				Excellent! I'll need a link to the
> >> meeting minutes where the decision is recorded (they can be 
> >unofficial)
> >> as well as a link to the document(s) in 3 formats: editable source,
> >> (X)HTML, and PDF. You can send it to me, and please copy 
> tc-admin so
> >> that it gets officially logged.
> >>
> >>
> >>
> >> 				Mary
> >>
> >>
> >>
> >> ________________________________
> >>
> >> 				From: Patil, Sanjay
> >> [mailto:sanjay.patil@sap.com]
> >> 				Sent: Monday, August 14, 2006 9:55 PM
> >> 				To: mary.mcrae@oasis-open.org
> >> 				Subject: RE: Public Comments Form
> >>
> >>
> >>
> >> 				Thanks Mary! The background information
> >> is certainly helpful.
> >>
> >>
> >>
> >> 				Our TC is going to vote for PR in this
> >> week. After that, is just an email with link to the PR draft is
> >> sufficient to notify the OASIS Administrator  (yourself in 
> >this case I
> >> suppose)?
> >>
> >>
> >>
> >> 				-- Sanjay
> >>
> >>
> >>
> >> ________________________________
> >>
> >> 				From: Mary McRae
> >> [mailto:marypmcrae@gmail.com]
> >> 				Sent: Monday, Aug 14, 2006 18:29 PM
> >> 				To: Patil, Sanjay
> >> 				Subject: RE: Public Comments Form
> >>
> >> 				Hi Sanjay,
> >>
> >>
> >>
> >> 				  The comment process has a storied past
> >> :-)  Originally an email list to which anyone could post, it became
> >> riddled with spam. The cure at the time (three years ago?) was to
> >> replace the list with a web form - the only "person" that 
> >could actually
> >> post to the list was the form. Besides all of the problems 
> associated
> >> with a form for trying to provide comments, spammers 
> >eventually figured
> >> out how to mimic the form and spam the comment lists. This 
> >problem had
> >> been going on for well over a year when we finally reverted 
> >back to the
> >> email list, but this time requiring an authenticated 
> >subscription. So,
> >> the posts that you see with the template information were 
> >provided via
> >> the comment form which has now been disabled. The 
> >instructions posted on
> >> the TC comment page do ask posters to provide some 
> >information, which we
> >> can only hope that they'll follow.
> >>
> >>
> >>
> >> 				Regards,
> >>
> >>
> >>
> >> 				Mary
> >>
> >>
> >>
> >> ________________________________
> >>
> >> 				From: Patil, Sanjay
> >> [mailto:sanjay.patil@sap.com]
> >> 				Sent: Monday, August 14, 2006 6:55 PM
> >> 				To: mary.mcrae@oasis-open.org
> >> 				Subject: Public Comments Form
> >>
> >>
> >>
> >> 				Hi Mary,
> >>
> >> 				My understanding is that the only
> >> channel for receiving comments from the public during the PR 
> >period is
> >> via the ws-rx-comment list. Is that right?
> >>
> >> 				I was browsing through the public
> >> comment lists of some other TCs and noticed that the comment emails
> >> include some template information at the top (submitter's name,
> >> organization, etc). I wonder whether that information was 
> explicitly
> >> included by the submitter following some guideline, or it 
> >was a result
> >> of some comments form usage. Please clarify.
> >>
> >> 				-- Sanjay
> >>
> >>
> >
> 


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