Re: [uoml] uoml sample document

[stephen.green@systml.co.uk]

Apologies, Mary, I was somewhat amiss there.

In this case then my prototype changes to the attached update

All the best

Stephen Green


Quoting Mary McRae <mary.mcrae@oasis-open.org>:

> Hello everyone,
>
>   I posted a message the other day but maybe it was missed? Please see:
> http://www.oasis-open.org/archives/uoml/200702/msg00019.html
> which I've copied the text below for easy reference. OASIS requires   
> that all TC specifications conform to the OASIS
> Templates and adhere to our Policies and rules.
>
>   The OASIS Templates can be found at
> http://docs.oasis-open.org/templates/.
> The informative reference for all formats is the XHTML User Guide
> http://docs.oasis-open.org/templates/OASISSpecificationTemplateGuidelines.html
> which contains links to the actual requirements in the Naming and   
> Metadata Guidelines documents. Templates are provided
> for authoring in OpenOffice, Microsoft Word, and XHTML. A DocBook   
> suite is also available, but has not been updated to
> match the
> latest metadata requirements. Please note that according to the   
> OASIS TC Process all approved committee work must be
> available in the editable source, as well as PDF and XHTML.
>
>   If you need any assistance with the templates or have questions,   
> I'm more than happy to help.
>
>   Regards,
>
> Mary
>
>
>> -----Original Message-----
>> From: stephen.green@systml.co.uk [mailto:stephen.green@systml.co.uk]
>> Sent: Thursday, March 01, 2007 5:54 PM
>> To: uoml@lists.oasis-open.org
>> Subject: Re: Re: Re: [uoml] uoml sample document
>>
>> Then it would look something like this (below or attached)
>>
>>
>> Quoting stephen.green@systml.co.uk:
>>
>> > Thanks Alex
>> >
>> > Apologies that I didn't quite realise the purpose of the
>> documents as
>> > being to consider the format rather than the content.
>> >
>> > Yes the format does appear to be along the correct lines, although
>> > there would probably need to be additions such as, at the least -
>> >
>> > OASIS logo
>> > Title - such as 'Document Operation Language (UOML) 1.0'
>> >
>> > Publication Date
>> > Document identifier  - could be same as the filename if it
>> obeys the
>> > OASIS rules Editorial Status - 'Draft'
>> > Location (perhaps include this later when one is
>> established) Editors
>> > Contributors
>> >
>> > <rest of document as in the samples sent on the 14th Feb>
>> >
>> > Normative References  (if there are any, perhaps ODF, W3C
>> XML Schema,
>> > XML ) Non-Normative References  (if there are any - perhaps
>> ODF would
>> > be here) Notices (OASIS copyright)
>> >
>> > I am also reminded that it would seem to be ideal if there were no
>> > spaces in the filename but if there are spaces then no
>> double spaces.
>> > Maybe an file name without spaces like 'wd-UOML-0-1.odt' might be
>> > ideal, or 'wd-UOML-1.0.odt' but I think it best to avoid '.' except
>> > for extensions.
>> >
>> > I hope these comments are more relevant. The document
>> samples have a
>> > good structure as OASIS specification drafts, I think.
>> >
>> > All the best
>> >
>> > Stephen Green
>> >
>> >
>> >
>> >
>> >
>> > Quoting Wang Donglin <dlwang@sursen.com>:
>> >
>> >> Thanks Green.
>> >> Xu Guo has given the .odt file format for the sample
>> schedma, TOC
>> >> and instroduction in 14th Feb. Pine converted to PDF in
>> 27th Feb.
>> >> We  need your comment to these documents. After confirmation of
>> >> sample,  we will provide the whole specification according
>> to the
>> >> style of  sample.
>> >>
>> >> -Alex
>> >>
>>
>>
>>
>>
>
>

wd-UOML-0-2.odt