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


Help: OASIS Mailing Lists Help | MarkMail Help

xslt-conformance message

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

Subject: Which file should be the basis for pointing into XSLT?

Hi everyone!

I have obtained the DSSSL scripts used by James to create the XSLT 
Recommendation document.  I was going to modify them to produce a rendition 
of the document useful for navigation purposes for the test suite 

I've been trying to think of the best way to render the Recommendation for 
our use in creating the pointers and for the user's use when we use the 
pointers in our document ... but, I need your opinion.

Should I base the navigation of the XSLT specification on the XML source 
file or on the HTML rendition?  I'm speaking here of when one of our tests 
references one of the normative locations of the XSLT Recommendation, where 
should it point?

I am of two minds:

(1) I figured the XML source of the XSLT specification is normative and the 
HTML rendition is just that, a rendition of the normative document, so we 
could be referencing the normative document and users of the suite could 
then navigate into the source document (but what would they use for browsing?)

(2) I also figured the HTML rendition of the XSLT specification is what 
most (all?) users of our test suite will be using, hence the pointers could 
be relative to an XHTML version of the rendition document ... but would 
there ever be other renditions?

I can modify the DSSSL scripts to go either way, I'm just not sure what the 
committee thinks should be done.

Looking in Tony's document, he is basing his pointers on the XML source of 
the recommendation ...

     "An element from the XSLT namespace may have any attribute..."

     XML Source: /spec[1]/body[1]/div1[2]/div2[1]/p[4]

But the document people will be navigating will be the HTML document ... 
the corresponding XPointer really isn't very useful, but could be what I 
base my indexing on:

     HTML Output: /html[1]/body[1]/p[26]

I think that perhaps what we do is document the XML XPointer but use the 
HTML XPointer for jumping into a modified version of the HTML rendition 
with anchors for every text node.  I'll work out a way to synchronize the two.

What say you?

One of the action items out of the last meeting was prototyping ideas 
regarding the submitter's document where we have to specify how a submitter 
structures the information about a given test they have developed.  Are 
there any intermediate results that can be shared so I can include the use 
of these pointers into that intermediate work?


................ Ken

G. Ken Holman                    mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.             http://www.CraneSoftwrights.com/m/
Box 266, Kars, Ontario CANADA K0A-2E0   +1(613)489-0999   (Fax:-0995)
Web site: XSL/XML/DSSSL/SGML services, training, libraries, products.
Book: Practical Transformation Using XSLT and XPath ISBN1-894049-05-5
Article:          What is XSLT? http://www.xml.com/pub/2000/08/holman
Next public instructor-led training:     2000-09-19/20,2000-10-03/05,
-        2000-10-09/10,2000-10-19,2000-11-12,2000-12-03/04,2001-01-27

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

Powered by eList eXpress LLC