Added full-featured example

[Maloney, Christopher (NIH/NLM/NCBI) [C]]

Described here:  https://github.com/NCBITools/DtdAnalyzer/tree/master/test/split-example.  This is a more full-featured example, with a lot of stuff extracted from the JATSCon paper.  The file split-mockup.daz.xml includes my ideas about how to include the “!dtd” and “!module” annotations into the dtdanalyzer output.

 

We can use this as our main test case.

 

Chris Maloney

NIH/NLM/NCBI (Contractor)

Building 45, 5AN.24D-22

301-594-2842

 

[Demian Hess]

You are a rockstar!

--
You received this message because you are subscribed to the Google Groups "DtdAnalyzer" group.
To post to this group, send email to dtdan...@googlegroups.com.
To unsubscribe from this group, send email to dtdanalyzer...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dtdanalyzer?hl=en.

--
Demian Hess

Avalon Consulting, LLC
527 Maple Avenue East, Suite 200, Vienna, VA 22180

Mobile: 301-943-8307
Fax: 845-367-5496
he...@avalonconsult.com

[Maloney, Christopher (NIH/NLM/NCBI) [C]]

I wish it were true! 

 

I’ve been working on the structured-comment-extractor on and off for the last few days, in a separate branch.  If you are interested to look at it or help with it, I can push the branch up to Github.  It is pretty straightforward, but a little bit tedious.

 

Audrey has been going gangbusters on the Schematron (#9) and the documentor (#4 and #7).  Maybe if you get time you could work on the comparator?  And/or helping to figure out how to configure it and package it?

 

Chris Maloney

NIH/NLM/NCBI (Contractor)

Building 45, 5AN.24D-22

301-594-2842

 

[Audrey Hamelers]

Thanks for the example, Chris. Now I should be able to add an index page to the documentor XSLT. I added tag pages that list each item tagged with that tag—I hope that was what the two of you had in mind for tags! (The word "tag" has lost all meaning after that sentence, hasn't it?)

Are we including modules in the dtddocumentor html output? If so, can one of you give me an idea of what you imagine a "module" page looking like? And, if other items should link to that module, how they should do so on their pages?

Thanks!

—Audrey

P.S. Chris, you could always play Rock Band for the rock star "experience"

[Audrey Hamelers]

By the way, I added a title to Chris's daz output mockup, ran it through my current dtddocumentor xslt, zipped up the result and put it in https://github.com/NCBITools/DtdAnalyzer/tree/master/test/split-example

[Maloney, Christopher (NIH/NLM/NCBI) [C]]

I do think we should include a modules section in the documentation output.  I put it in the mockup (http://www.ncbi.nlm.nih.gov/books/NBK100354/figure/hess-fig1/?report=objectonly).  I would think that each module should get a page that lists everything defined in that module. 

 

Even with no special annotations, because of Demian’s additions, we know the system id of everything read by the parser.  So you could make a distinct-values list of those, lop off the path part, leaving just the filename part, or something like that.  It might be nice to leave everything except a relative path from the main dtd module, so that you’d get “mathml/mmlalias.ent”, instead of just “mmlalias.ent”, but that might be tricky.  To be robust, you’d need to grab the system id of the main .dtd module, and compute relative paths from that.   There might be an XSLT library to do that, but I don’t know of one off the top of my head.  Probably not worth it in the first go-around – we could make a “maybe/someday” ticket for this case.

 

Chris Maloney

NIH/NLM/NCBI (Contractor)

Building 45, 5AN.24D-22

301-594-2842