Hi Roger. Thanks for expressing hopes and dreams! 8)
Related: Enosema (have copied two of principals Ron Tse and Reese Plews).
Authoritative reference for X3D is an ISO specification, which is manually edited in HTML using NetBeans and then checked with HTML Tidy. I have annotated the X3D XML schema to capture full characteristics of data structures that are beyond default expressive power (such as transient inputOnly and outputOnly fields). An XSLT stylesheet then parses the object-oriented hierarchical .xsd XML schema to produce a flat list of data structures for each and every node and node type. Functional descriptions of each node and field are pulled in from a separate XML file holding tooltips. The resultant comprehensive X3DUOM file is then easily processed to produce other APIs and products, such as Java Python and Turtle bindings. So there is much initial custom preparation, then results are straightforward to maintain in XML Schema and powerful products become possible. Details and links at
Consolation point: maintaining work flows for authoritative designs with directly testable results is more powerful, less time consuming, and much less difficult than ad hoc long-term maintenance of multiple documents. YMMV of course when pursuing such goals. Wishing best progress with your efforts. all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, navy robotics https://faculty.nps.edu/brutzman -----Original Message----- Hi Folks, Okay, I convinced my sponsor that specifications should be written in a way that they can be processed by software. More specifically, I convinced my sponsor that, under the hood, specifications should be in an XML format. My sponsor said, "Okay, fine .... provided, (1) there is a non-geeky editor that is easy for the specification writer to use, (2) the specification writer is unaware that the editor is generating XML under the hood, and (3) the generated XML is easy to understand. One more thing, (4) the editor MUST support tables." Peter Flynn wrote: > That is a sort of holy grail: that users will be able to create and > maintain their document in meaningful XML without knowing they are > doing it. Eek! Did I mislead my sponsor by recommending that specifications be written in a way that can be processed by software? /Roger _______________________________________________________________________ XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support XML implementation and development. To minimize spam in the archives, you must subscribe before posting. [Un]Subscribe/change address: https://www.oasis-open.org/mlmanage/ Or unsubscribe: xml-dev-unsubscribe@lists.xml.org subscribe: xml-dev-subscribe@lists.xml.org List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists/ |
Attachment:
smime.p7s
Description: application/pkcs7-signature