[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: re meeting Feb 27; Rex, welcome back; this bounced: pleaseforward to huml list for me?
Hi Everyoen,
My apoologies for forwarding this so late. I just dove in and read
it, absent-mindedly thinking that it had gone to the list, but it
hadn't. So I am rectifying that now.
We can discuss this in the meeting.
Regards,
Rex
>Date: Mon, 27 Feb 2006 00:12:00 -0500
>From: cognite@cognizor.com
>To: rexb@starbourne.com
>Subject: re meeting Feb 27; Rex, welcome back; this bounced: please forward
> to huml list for me?
>X-ELNK-Trace:
>f25cfa3189d42b8c94f5150ab1c16ac04be4f309a0cc41dd9ed7966bf378174f545bc0e9bd23bda6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
>X-Originating-IP: 216.17.228.198
>X-Rcpt-To: <rexb@starbourne.com>
>X-DPOP: Version number supressed
>
> for <huml@lists.oasis-open.org>; Mon, 27 Feb 2006 02:00:05 -0500
>Date: Mon, 27 Feb 2006 02:00:05 -0500
>Received: from smtp.cognizor.com ([209.15.77.16]) by cognizor.com ;
>Mon, 27 Feb 2006 01:00:04 -0600
>From: cognite@cognizor.com
>To: huml@lists.oasis-open.org
>Subject: Huml teleconf Feb. 27, prep: xml generating with tags huml_X, python
>X-Mailer: Cyclonic Webmail - Build 4.00
>X-Mime: Produced by Stallion Networking Mime-Engine Ver: 2.03
>X-WMSoftware: Cyclonic Webmail (C) 1998-2000
>Message-ID: <114102360401@aquarius.hosting4u.net>
>X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on
> hermes.oasis-open.org
>X-Spam-Status: No, hits=2.8 required=7.0 tests=NO_REAL_NAME,
> THE_FOLLOWING_FORM autolearn=no version=2.64
>X-Spam-Level: **
>
>
>Re: More thoughts on how to implement our huml terms schema for xml
>generation, using python. Illustration, huml_timePeriod, below.
>
>Conveniently, the form of xml tags is the same as for python names:
>
>============ http://www.travelthepath.com/intro.html
>========= excerpt
>
>XML Rules
>
>There are a few simple rules that XML documents need to follow.
>
>All XML documents must have a root tag, and all XML elements must be
>properly nested within the root tag.
>
>All XML elements must have a begin tag and matching end tag (case counts).
>
>Tag names cannot include spaces, but can include underscores,
>letters, and numbers.
>
>Any empty tags must have an ending slash.
>
>Attribute values must always be quoted.
>
>All entities and special characters must be used properly
>
>NOTE: If you follow all these rules with HTML, you are actually
>creating XHTML!
>
>Beyond these few simple rules, you have a lot of free reign as to
>what your XML documents will contain.
>
>========
>
>Note that python variable names have the same allowable character set.
>
>Thus, per the proposal in the huml version under consideration,
>http://www.oasis-open.org/apps/org/workgroup/humanmarkup/download.php/13219/huml-base-rev093-SC.html
>a prefix for all huml tags might be attached with _, thus:
>
>huml_timePeriod.
>
>For example, we might have an entry such as this where following the
>huml tag itself, named attributes in quotes give interpretive
>information beyond the occurrent term itself:
>
><huml_timePeriod
>type = "lunisolar"
>schema = "Indian Civil Calendar est. government of India 1957"
>reference = "http://webexhibits.org/calendars/calendar-indian.html";
>approx_equiv = "March 20 (21 in leap years) thru 31 days"
>unispelling = "cEt+r"
>unicode = '...TBD...'
>>Caitra</huml_timePeriod>
>
>These attributes could be rendered as instance attributes for
>instances of a python class.
>
>To use the pyfo module to generate corresponding xml from python,
>then, there is a python dictionary (association list) of the
>following form.
>Single-quotes and commas have been added to what shows in the tagged
>entry itself (above).
>
>attr_dict_cEtr = {'type' = "lunisolar",
>'schema' = "Indian Civil Calendar est. government of India 1957",
>'reference' =
>"http://webexhibits.org/calendars/calendar-indian.html";,
>'approx_equiv' = "March 22 (21 in leap years) thru April 20",
>'unispelling' = "cEt+r",
>'unicode' = '...TBD...'}
>
>The xml is then produced by calling the function pyfo of the module pyfo,
>thus:
>
>xml_output = pyfo( ('huml_timePeriod', "Caitra", attr_dict_cEtr))
>
>Seems feasible so far, and perhaps even perspicuous! A parser would be
>called for to do the opposite direction, "unpyfo()" or xml2py(), perhaps.
>
>The advantage is that the whole schema can be maintained in a very simple
>form in python, say as a set of classes. As changes in the schema
>are made, everything can be quickly re-generated. Instance-specific
>information is readily storable in dictionaries like that used in
>the illustration, and using ordinary OOP techniques, say, can
>supplement or override defaults as appropriate.
>
>SC
>
>copyright by author, S. Candelaria de Ram, 26 Feb. 2006.
>
>
>
>
>_______________________________________________________
>
>
>
>
>
>
>
>Begin forwarded message:
>
>Date: 27 Feb 2006 06:58:47 -0000
>From: MAILER-DAEMON@mail.oasis-open.org
>To: cognite@cognizor.com
>Subject: failure notice
>
>
>admin@lists.oasis-open.org
--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-849-2309
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]