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

 


Help: OASIS Mailing Lists Help | MarkMail Help

humanmarkup message

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


Subject: [humanmarkup] TC Core Documents


Title: TC Core Documents
Hi Everyone,

I wanted to let you all know that I have uploaded new versions of HM.frameworks and HMI.glossary, standardizing text-only presentation and going into greater comprehensiveness. These have yet to be edited by Kurt Cagle and put into basic XML on their way to being transformed through XSLT into XHTML in the simplest, most direct web presentation we can build hewing to the presentation style and formats of W3D and other OASIS TCs.

We are inviting comments and suggestions.Warning: frameworks is rather massive, weighing in at 9,000 plus words. And that is admitted missing quite a few entries for such areas as military disciplines and many of the arts which are so interpretation-bound that attempting to approach a description of what is standard was simply beyond our (my) ability at this time.

 Included in these new versions are working definitions for all ontological frameworks and standard definitions for the glossary to ensure harmonization with existing XML usages, OASIS usages, W3C usages, academic usages and business usages.

This is what is meant by moving into Phase 1 and once these documents have been processed into XML they become true working drafts for us. Note, while we strive to keep the language as small and adaptable as we can make it, our informing documents actually need to be as comprehensive as they can be to ensure that our basis of research and study is solid.

Also, just in case you were not aware of it, I believe this practice makes us among the first to adopt a comprehensive approach to putting all of our concrete committee work into comprehensive and fully compliant well-formed XML form.

Kurt has already processed the HM.requirements document, so it may be referred to in order to get an idea of what we are doing, where we are going and why our documents remain in text-only form until so processed, so that we do not have to spend time deleting one or another set of formatting commands and codes in order to put our documents into their penultimate form before we start pouring concrete to set them in figuratively final form.

I am currently working on HM.applications, and other members are working on others of these documents. As stated earlier, we welcome comments and suggestions and if you would like to take on a document with which you would like perform a similar service, please let us know with a realistic, projected ETA. (Note, frameworks took more than 100 hours, glossary took more than 30, so these tasks are decidedly largish commitments.

Ciao,
Rex
-- 
Rex Brooks
GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth
W3Address: http://www.starbourne.com
Email: rexb@starbourne.com
Tel: 510-849-2309
Fax: By Request


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


Powered by eList eXpress LLC