Hi,
We use the following schema for instance documents that virtually represent
a site in our CMS:
http://www.livestoryboard.com/lsbwork/schemas/2003/03/site.xsd
It validates instance documents that represent a site/project's hierarchy
past the page level (i.e. /site/folder/page/regions/region/content_piece).
In addition, it details application specific metadata that is used to tell a
transformation what to do. (Critiques welcome)
Haven't transformed it to SVG, but it sounds like an fun project :)
Best,
-Rob
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-
list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of Wendell Piez
Sent: Thursday, September 18, 2003 10:37 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Dan,
At 09:23 AM 9/18/2003, you wrote:
From what I've seen of this and the other examples, they all seem
oriented around data at the webpage level. What I'm trying to do is far
more at the website level (admittedly the two are the same thing, just
seen from different perspectives). In particular, I've not seen any
examples that produce wireframe sitemaps similar to the one at
http://www.pernoctator.com/XML/whitegoods.svg which for me was the most
important (certainly the hardest!) part of what I'm trying to make.
Yes. It might be fun to write a set of extractors that would pull metadata
out of Docbook, Forrest, DITA, TEI or whatever "web pages" into your XML,
so it can be used to map them.
Cheers,
Wendell
___&&__&_&___&_&__&&&__&_&__&__&&____&&_&___&__&_&&_____&__&__&&_____&_&&_
"Thus I make my own use of the telegraph, without consulting
the directors, like the sparrows, which I perceive use it
extensively for a perch." -- Thoreau
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
