Transport Protocol 1.1 and Cross Platform Broker Implementation

[Douglas Tody]

Hi -

I don't understand this; while a HTML master is fine, there are plenty
of cases where we have Word masters which can produce HTML and PDF
as well.  In fact this is the most flexible case as then we get all
three formats.  The HTML in this case however should not be directly
edited.  I suggest that if Word is convenient continue to use it,
and merely generate the other formats when you publish the document.
I don't think the IVOA standards mandate that HTML be used as the
master document format.

 	- Doug


On Wed, 26 Aug 2009, Matthew Graham wrote:

> Hi Bob,
>
> There is an IVOA HTML template and so the easiest route might be just to 
> cut-and-paste from Word into your favourite editor. I've just done this for a 
> 45-page Word spec for exactly the same reason.
>
> 	Cheers,
>
> 	Matthew
>
>
> On Aug 26, 2009, at 4:41 PM, Bob Denny wrote:
>
>>> I'm waiting for Bruno to reply to my plea for allowing me to submit in 
>>> PDF.
>> 
>> It looks like I'm going to have to re-write these IVOA Notes from scratch, 
>> in
>> HTML. I spent hours trying to save from Word as HTML and converting PDF to 
>> HTML.
>> ALl tools and methods produce trash. The IVOA Document Standards Version 
>> 1.2 at
>> 
>> http://www.ivoa.net/Documents/DocStd/20090302/PR-DocStd-1.2-20090302.html
>> 
>> states
>> 
>>> 1.3 Format
>>> The standard format for IVOA documents is HTML, though any document
>>> preparation tools may be used that allow for the publication of HTML and 
>>> that
>>> retain the standard formatting elements and style.  Document templates are
>>> provided for MSWord and HTML at http://www.ivoa.net/Documents/templates/.
>>> Final Recommendations should also be available as printable PDF in A4 
>>> (and,
>>> optionally, US 8.5 x 11”) size.
>> 
>> However, if you use the MSWord template, it results in your having a 
>> document
>> that cannot be directly or indirectly turned into HTML "that retain[s] the
>> standard formatting elements and style". No matter how you convert, the 
>> result
>> is trash. And the RFC is closed.
>> 
>> I apologize for venting my frustration here. I just wanted to communicate 
>> my
>> desire and efforts to help the VOEvent Network grow and mature, and my
>> willingness (within reason) to provide my time and capabilities to this 
>> effort
>> without any direct compensation.
>> 
>> Anyway, if anyone is interested in reviewing the VOEvent Transport Protocol 
>> 1.1,
>> or wants to try out the Dakota Broker, please contact me at rdenny at dc3.com 
>> and I
>> can provide you with the materials.
>> 
>> -- Bob
>> 
>