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] [Fwd: RE: [Fwd: WS-RX Public Review]]


Hi Sanjay,

  No requirement at this point. utf-8 and iso 8859-1 are probably the most
typical.

Mary 

> -----Original Message-----
> From: Patil, Sanjay [mailto:sanjay.patil@sap.com] 
> Sent: Thursday, August 10, 2006 3:55 PM
> To: mary.mcrae@oasis-open.org
> Cc: ws-rx-editors@lists.oasis-open.org
> Subject: FW: [ws-rx-editors] [Fwd: RE: [Fwd: WS-RX Public Review]]
> 
>  
> Hi Mary,
> 
> There is a question in the email below for OASIS Staff - Does 
> OASIS have a requirement around the character encoding of their specs?
> 
> -- Sanjay
> 
> -----Original Message-----
> From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com]
> Sent: Thursday, Aug 10, 2006 12:50 PM
> To: Anish Karmarkar; ws-rx-editors@lists.oasis-open.org
> Cc: Doug Davis; Paul Fremantle
> Subject: RE: [ws-rx-editors] [Fwd: RE: [Fwd: WS-RX Public Review]]
> 
> I've been playing around with the various config settings 
> that OO provides around HTML conversion. Attached is the best 
> looking one. This is produced by setting "Load/Save"->"HTML 
> Compatibility"->"Export" to "HTML 3.2". With regards to 
> Anish's list of items:
> 
> 1) Page breaks
> 
> Still no page breaks though there is a bit more whitespace at 
> the beginning of every section. I'd say this was "fixed".
> 
> 4) Table headings not readable.
> 
> Still broken.
> 
> 5) TOC hyperlinks.
> 
> No hyperlinks. We need to figure out how important this 
> requirement is.
> 
> 7) Relative hyperlinks no functioning.
> 
> Still broken; none of the local ID targets are defined.
> 
> 10) Exemplar message format.
> 
> This looks a lot better, but it still doesn't look like the 
> PDF (no shading).
> 
> 11) Section/subsection numbers adjoin section/subsetion titles.
> 
> Still broken.
> 
> 12) Appendix number formatting.
> 
> Still broken.
> 
> 13) (new) Status boilerplate in smaller font.
> 
> I have another question as well. The OO HTML converter allows 
> you to pick the character encoding. Does OASIS have a 
> requirement around the character encoding of their specs?
> 
> - gp
> 
> 
> > -----Original Message-----
> > From: Anish Karmarkar [mailto:Anish.Karmarkar@oracle.com]
> > Sent: Monday, August 07, 2006 10:50 AM
> > To: ws-rx-editors@lists.oasis-open.org
> > Cc: Doug Davis; Paul Fremantle
> > Subject: Re: [ws-rx-editors] [Fwd: RE: [Fwd: WS-RX Public Review]]
> > 
> > Per Paul's suggestion I used the 'save as' menu item to 
> general HTML.
> > This did take care of some of the issues listed in my 
> previous email.
> > See my comments inlined below on which problems are fixed by this.
> > 
> > HTML/gifs/pngs attached.
> > 
> > -Anish
> > --
> > 
> > Anish Karmarkar wrote:
> > > I generated an HTML version to see what it does (nothing
> > checked in).
> > > 
> > > Pl. note that whey you try to do a 'save as' and select the right 
> > > type, it gives a warning about conversion from ODT to HTML.
> > But when
> > > you do 'export' to XHTML it does not give the same warning.
> > > 
> > > Few things I noticed in the XHTML version:
> > > 
> > > 1) There are no page breaks in HTML, so there isn't any spacing 
> > > between start of a new section and end of previous
> > subsection. In the
> > > ODT/PDF version the start of a new section starts a new page.
> > > 
> > 
> > Since this is HTML, there isn't much that can be done about 
> this other 
> > than perhaps increase the spacing before a section start 
> (in addition 
> > to the page break in ODT).
> > 
> > > 2) The dots in subsection numbering are missing. eg, "1.3" 
> > appears as "13"
> > > 
> > 
> > This is fixed.
> > 
> > > 3) The section and subsection titles are indented (they 
> are not in 
> > > PDF/ODT version)
> > >
> > 
> > This is fixed.
> > 
> > > 4) Table headings (1st row) is not readable as the background and 
> > > foreground are of the same color (except for the tables in
> > section 4)
> > > 
> > 
> > This problem still remains.
> > 
> > > 5) It would be nice if the TOC had hyperlinks.
> > > 
> > 
> > Not fixed.
> > 
> > > 6) OASIS logo missing in the XHTML version (I'm guessing
> > this can be
> > > fixed pretty easily).
> > > 
> > 
> > Fixed.
> > 
> > But now the 2 title lines run over each other.
> > 
> > > 7) Relative hyperlinks are incorrect (eg, pointers to references, 
> > > sections).
> > > 
> > 
> > The href values are now correct, but there aren't the right 
> > corresponding 'id's.
> > 
> > > 8) Similar to #6 above, figure 1 & 2 are missing. We'll
> > have to make
> > > them available as a separate files on docs.oasis-open.org
> > > 
> > 
> > This is fixed, but we still need to make these png/gif 
> files available 
> > on docs.oasis-open.org
> > 
> > > 9) Bullet numbering in section 3 is screwed up (every bullet is 
> > > numbered as 1).
> > > 
> > 
> > This is fixed.
> > 
> > > 10) Exemplar message format can be improved upon. There are
> > horizontal
> > > lines after every line.
> > > 
> > 
> > This problem just got worse. Now the indentation is lost too.
> > 
> > > 11) There is no space between the section/subsection 
> number and the 
> > > section/subsetion title.
> > > 
> > 
> > This problem remains.
> > 
> > > 12) Appendix numbering isn't right and isn't visible.
> > > 
> > 
> > This is fixed.
> > But the appendix number is in a different color than the appendix 
> > title, and indented.
> > 
> > > HTH.
> > > 
> > > -Anish
> > > --
> > > 
> > > Doug Davis wrote:
> > >>
> > >> Gil - can you handle this one since you know how to do the
> > RDDL stuff?
> > >> thanks,
> > >> -Doug
> > >>
> > >>
> > >>
> > >> *Paul Fremantle <paul@wso2.com>*
> > >>
> > >> 08/07/2006 10:01 AM
> > >>
> > >>     
> > >> To
> > >>     ws-rx-editors@lists.oasis-open.org
> > >> cc
> > >>     
> > >> Subject
> > >>     [ws-rx-editors] [Fwd: RE: [Fwd: WS-RX Public Review]]
> > >>
> > >>
> > >>     
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Folks
> > >>
> > >> I note that we need an HTML version of the spec. I know OO
> > has that
> > >> capability, but it would be good if we tested it and 
> make sure its 
> > >> working.
> > >>
> > >> Paul
> > >>
> > >> -------- Original Message --------
> > >> Subject:                  RE: [Fwd: WS-RX Public Review]
> > >> Date:                  Thu, 3 Aug 2006 17:05:48 -0400
> > >> From:                  Mary McRae <mary.mcrae@oasis-open.org>
> > >> Reply-To:                  <mary.mcrae@oasis-open.org>
> > >> Organization:                  OASIS
> > >> To:                  'Paul Fremantle' <paul@wso2.com>, 
> > >> <sanjay.patil@sap.com>
> > >>
> > >>
> > >>
> > >> Hi Paul,
> > >>
> > >>  Hopefully the comment lists will be functional in the 
> next day or 
> > >> two; there's no need to *set up* anything as this was 
> done for all 
> > >> TCs at the same time. The most important thing is to 
> make sure the 
> > >> specification is in the proper format - please check the
> > templates at
> > >> docs.oasis-open.org/templates/ and make sure that you have the 
> > >> appropriate cover page boilerplate text, notice, etc.
> > >>
> > >>  When you're ready to make the formal submission, note
> > that I'll need
> > >> the spec in three formats: editable source, HTML, and PDF.
> > >>
> > >>  That should be it, but please feel free to send me a
> > pointer to the
> > >> spec and I'll do a quick check before you produce all of
> > the versions
> > >> and point out anything that should be changed.
> > >>
> > >> Mary
> > >>
> > >>
> > >>  >
> > >>  > -------- Original Message --------
> > >>  > Subject:                  WS-RX Public Review
> > >>  > Date:                  Mon, 31 Jul 2006 23:05:45 +0100
> > >>  > From:                  Paul Fremantle <paul@wso2.com>
> > >>  > To:                  Mary McRae <mary.mcrae@oasis-open.org>, 
> > >> "Patil, Sanjay"
> > >>  > <sanjay.patil@sap.com>
> > >>  >
> > >>  >
> > >>  >
> > >>  > Mary
> > >>  >
> > >>  > The WS-RX TC has now closed all substantive issues, and
> > we  > are
> > >> aiming to have a vote for CD and PR on the call 8/17. We 
>  > would 
> > >> like to be ahead of the game in terms of getting ready for that.
> > >>  >
> > >>  > Our issues editor is starting to prepare for capturing any  > 
> > >> raised issues. I believe we need to setup the comments
> > list  > using
> > >> the new comments facility. And we need to inform you.
> > >>  > Have I missed anything?
> > >>  >
> > >>  > What else can we do to be aforehand in our preparations?
> > >>  >
> > >>  > Yours,
> > >>  > Paul
> > >>  >
> > >>  > --
> > >>  >
> > >>  > Paul Fremantle
> > >>  > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair  >  > 
> > >> http://feeds.feedburner.com/bloglines/pzf
> > >>  > paul@wso2.com
> > >>  >
> > >>  > "Oxygenating the Web Service Platform", www.wso2.com  >
> >  >  >  >
> > >> > --  >  > Paul Fremantle  > VP/Technology, WSO2 and OASIS
> > WS-RX TC
> > >> Co-chair  >  > http://feeds.feedburner.com/bloglines/pzf
> > >>  > paul@wso2.com
> > >>  >
> > >>  > "Oxygenating the Web Service Platform", www.wso2.com  >
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >>
> > >> Paul Fremantle
> > >> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> > >>
> > >> http://feeds.feedburner.com/bloglines/pzf
> > >> paul@wso2.com
> > >>
> > >> "Oxygenating the Web Service Platform", www.wso2.com
> > >>
> > >>
> > 
> 



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