Re: Re: [uoml] uoml sample document

[stephen.green@systml.co.uk]

Some further points
1.
In the past I have found it easiest to first draft the document
in open office .odt then transfer the text to either XHTML or
docbook XML (see example below) then generate both .odt and .pdf
from that in the OASIS style
2.
We need a copy of the OASIS file and namespace naming rules from
Mary maybe.

All the best

Stephen Green

example using docbook:

<?xml version="1.0" encoding="ISO-8859-1"?>
<article status="working draft">
	<articleinfo>
		<productname>UBL 2 BITS Sample</productname>
		<title>UBL 2 Sample International Scenario Business Process  
Definitions</title>
		<authorgroup>
			<author>
				<affiliation>
					<orgname>SystML</orgname>
					<address>
						<email>stephen.green@systml.co.uk</email>
					</address>
				</affiliation>
				<firstname>Stephen</firstname>
				<surname> Green</surname>
			</author>
			<author>
				<affiliation>
					<orgname>HavanaWave AG</orgname>
					<address>
						<email>Sacha.Schlegel@HavanaWave.com</email>
					</address>
				</affiliation>
				<firstname>
					<?nospell-start?>Sacha<?nospell-end?>
				</firstname>
				<surname>
					<?nospell-start?>Schlegel<?nospell-end?>
				</surname>
			</author>
		</authorgroup>
		<pubdate>18 December 2006</pubdate>
		<legalnotice role="notices">
			<title>Notices</title>
			<para>Copyright (C) OASIS Open (2006-2007). All Rights Reserved.

This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared,
copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to
OASIS, except as needed for the purpose of developing OASIS
specifications, in which case the procedures for copyrights
defined in the OASIS Intellectual Property Rights document must
be followed, or as required to translate it into languages other
than English.

The limited permissions granted above are perpetual and will not
be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided
on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE
USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.</para>
		</legalnotice>
		<abstract>
			<para/>
		</abstract>
	</articleinfo>
	<section>
		<title>Business Process Definitions</title>
		<para>These are sample process profiles using
ebXML Business Process Specification <xref linkend="ebbp"/> for  
corresponding UBL 2 <xref linkend="ubl"/> international scenario  
sample documents.
		</para>
		<table>
			<title>Process Definition Files</title>
			<tgroup cols="5">
				<colspec colwidth="25%"/>
				<colspec colwidth="15%"/>






Quoting stephen.green@systml.co.uk:

> Greetings Alex, UOML TC,
>
> We need to list the documents to be provided in the specification.
>
> I expect we have a list like the following at the present time:
>
> 1. Draft W3C XML Schema files
> 2. Draft specification prose document (in open document, XHTML and   
> pdf format)
> 3. Samples in both prose and XML formats
>
> Besides item 2 we will need a collection of all of the diagrams as .jpg or
> equivalent.
>
> We might also need to produce a docbook version of item 2, provided we
> have the skills. This will be an editable XML version of the prose
> specification text from which the other file formats can be generated
> (such as with XSLT, say). That way we would only need to concentraton
> editing one document. Maybe we wish to use Open Document for the
> editable version,
> in which case may I suggest we use the .odt file format. Does Red Office
> support this same file type as the one used in Open Office? It is possible
> to create pdf and XHTML from this format but maybe we need help with this
> from Mary to get the exact OASIS style right. Suggestions on how to do this
> from an Open Office file or Red Office file would be welcome. Or does it
> require docbook for the generation of the right OASIS style?
>
> Then we need a folder structure to be decided if we are to zip the package
> into one zip file for easy download.
>
> We also need to agree for the schema files:
>
> 1. the namespace format
> 2. the filename format
>
> Plus version and naming rules for the whole specification - for UOML itself.
>
> For that we need to understand the latest OASIS namespace and file naming
> rules which are not very restrictive so there is much that is just for
> the TC to decide.
>
> Do we have draft copies of the whole specification and the schema files?
>
> Enough of me for now.
>
> All the best
>
> Stephen Green
>
>
> Quoting Wang Donglin <dlwang@sursen.com>:
>
>> Dear TC members,
>> The most important topic of 2nd meeting is the discussion of UOML    
>> Specification samples and UOML work draft TOC. We will write the    
>> whole work draft according to it before March 31th. We need your    
>> comment on whether the format and expression meets the requirement   
>>  of OASIS specification. Especially, I'd like hear from Charles,    
>> Green and Lin Fong, since you are experienced OASIS contributors.
>>
>> -Alex
>>
>>> Hello,
>>>
>>> I have converted those two documents into PDF format, which was    
>>> edited by Guo Xu , please have a review in the attachment.
>>>
>>> I am looking forward to your advice.
>>>
>>> Regards
>>>
>>> Pine
>>>
>>> ----- Original Message -----
>>> From: guoxu
>>> To: uoml@lists.oasis-open.org
>>> Sent: Wednesday, February 14, 2007 9:58 PM
>>> Subject: [uoml] [SPAM] uoml sample document
>>>
>>>
>>> hi, everyone. here's the uoml sample document.
>>>
>>> there are two documents in attachment. one is instroduction of the  
>>>   draft, the other describes three samples and the structure of  
>>> the   draft.
>>>
>>> any comment or question is welcome.
>>>
>>> guoxu
>>>
>>>
>>
>>
>>
>>
>>
>>