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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uoml-discuss message

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


Subject: Re: [uoml-discuss] UOML discuss subject one - Proposed UOML TC Name& Statement of Purpose


Dear Pine Zhang, dear all,

thank you for your message. Ars Aperta agrees to the proposed items you
have written and we would like to seize this opportunity for thanking
the Sursen company for pushing the UOML forward.

Nonetheless, Ars Aperta would like to add one more item: that UOML must
be based on the RelaxNG schema, or at least must be able to integrate
any RelaxNG-based XML schemas.

RelaxNG schema is the default base schemas for several interoperable
standards and formats, the OpenDocument Format being one of them.

Some interesting links :
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=relax-ng
http://xml.coverpages.org/relax-ng.html
http://www.relaxng.org


Regards,

-- 
Charles-H.Schulz,
Associ¨¦ / Associate,
Ars Aperta.



pine zhang a ¨¦crit :
>
> Dear all:
>
> This is Pine Zhang from UOML Alliance .
>
> As we will form a technical committee of UOML in OASIS, the TC charter
> is necessary. Following the requirement of TC template, each item will
> be discussed week by week till it is formed to be a final charter.
>
> the first subject for this week is£ºProposed UOML TC Name.
>
> Here I would like to copy the guideline form the TC template:
>
> "[The name of the TC, such name not to have been previously used for
> an OASIS TC and not to include any trademarks or service marks not
> owned by OASIS. The proposed TC name is subject to TC Administrator
> approval and may not include any misleading or inappropriate names.
> The proposed name must specify any acronyms or abbreviations of the
> name that shall be used to refer to the TC.]"
>
> *The proposed TC Name could be*: "OASIS Unstructured Operation Markup
> Language Technical Committee", abbreviation = UOML TC.
>
> The second subject is £ºProposed UOML TC Statement of Purpose
>
> The guideline of this item forms the TC template:
>
> ¡°A statement of purpose, including a definition of the problem to be
> solved¡±
>
> *The Proposed UOML TC Statement of Purpose could be:*
>
> The Unstructured operation markup language Standard defines an XML
> schema for universal document operations. The schema is suitable for
> operating written documents, including create, view, modify, query
> information that can be printed in paper, e.g. books, magazine,
> newspaper, office documents, maps, drawings, blueprints, but is not
> restricted to these kinds of documents. There are several commercial
> and free applications available based on UOML, with more currently
> under development.
>
> The purpose of this TC is to create an open, XML-based operation
> standard for unstructured documents.
>
> The resulting standard must meet the following requirements:
>
>    1. It must be suitable for written documents, i.e. information that
>       can be printed in paper, including books, magazine, newspaper,
>       office documents, maps, drawings, blueprints, but is not
>       restricted to these kinds of documents.
>    2. It must define universal operations to these documents,
>       including create, view, modify, query, retrieve.
>    3. It must be compatible with the W3C Extensible Markup Language
>       (XML) v1.0 and W3C Namespaces in XML v1.0 specifications,
>    4. It must deal with after-typesetting information suitable for
>       presenting the document,
>    5. It must be friendly to document related applications.
>    6. It must be cross-platform, program language independent.
>
> Will you agree to the two proposed items or any other ideas? Any
> suggestion by the subject is welcome.
>
> Thank you very much for your comments.
>
> Sincerely
>
> Pine Zhang
> UOML Alliance
> Tel:+86-10-82331166-2413
>
> Cel:+86-13488717090
> Fax:+86-10-82332929
> Email:pine_zhang@sursen.com
>




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