Subject: Re: Recognizing "subdocuments" From: "W. Eliot Kimber" <eliot@xxxxxxxxxxxxxx> Date: Sat, 05 Dec 1998 07:56:47 -0600 |
At 05:35 PM 12/4/98 -0600, Brandon Ibach wrote: > Section 9.5 (in the "groves" chapter) talks about generating >"auxiliary groves" via an "auxiliary parse", and that the DSSSL engine >should generate a urefnode property for each new node called "source" >which points back to the nodes in the "source grove" from which the >node was generated. So, this could be one solution (if implemented >in the engine). The question would be, would the sgml-parse function >qualify as an "auxiliary parse"? An auxiliary grove is a grove constructed by processing other nodes in a grove or groves. The sgml-parse function is not processing nodes but source (non-grove) data to construct a new grove that is not an auxiliary grove. Examples of auxiliary groves are architectural instance groves, groves constructed by parsing character data into nodes (e.g., data tokenizer groves as defined by the HyTime standard), etc. So no joy there. Cheers, E. -- <Address HyTime=bibloc> W. Eliot Kimber, Senior Consulting SGML Engineer ISOGEN International Corp. 2200 N. Lamar St., Suite 230, Dallas, TX 75202. 214.953.0004 www.isogen.com </Address> DSSSList info and archive: http://www.mulberrytech.com/dsssl/dssslist
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Recognizing "subdocuments", Brandon Ibach | Thread | Re: Recognizing "subdocuments", Brandon Ibach |
Re: Recognizing "subdocuments", Brandon Ibach | Date | Re: Recognizing "subdocuments", Brandon Ibach |
Month |