floater wrote:
Could anyone give me a 10-minutes-in-XML lession? (Comparing with 14days in XML, etc, )

Suppose I have a database(oracle, sybase, etc). I want to display the data in html pages. What are the steps to go from db to html?

db are maintained by dba, sql will be used to query/operate data. html prototypes are generated by graphics designers, html code and css. What are the roles in the middle? What are the middle supplementals, like xsl, dtd, etc?

Using java, supposed. No code is necessary, but tools are better than general comments.

Thanks.

wishmaster wrote:
don't really understand what you intend to do...
but, anyway, use JDBC to grab data from database, use JSP to present data. This is the way in Java, in this case, I am not sure why you need XML, even you really want XML output, then you only need XSL to style your data and DTD or schema to validate your XML structure. What you mentioned in your post is more of templating and often used in content management system such as Interwoven TeamSite or Vignette V5.

coder wrote:
you can see my last post, I recommend a good site you can master xml in ten minutes by learn the Tutorials & References and some xsl tools.

If you want to refine the process, there is my option:
1. define the DTD
2. generate the sample xml(It is used to be test xml by xsl)
3. a group generate the real xml
a group generate the xsl refer to the html

may I get one point?

floater wrote:
Here is a skeptical chart of the flow. The green ones are java classes, we don't need to worry about them(assume we know everything about them since there are tools out there already). The blue ones are of my concern! CSS is relative easy, photoshop + dreamweaver + frontpage can do it and it is done during prototyping.(any comment on this???)


/**********************************************************
You can use DTD or Schema to govern what the xml data structure should be or any other rules you want the data to conform with or get validated. I am not sure why you need a class for xml generator since all leading DB vendors (MS/Oracle/IBM/Sybase) have built-in support for XML and xml data can be direct output on demand. You do need a DTD or Schema to control the data output for business validation and transformation. photoshop + dreamweaver + frontpage can do UI only not DTD or schema, you may use XML Spy or Stylus Studio for either DTD or Schema, Turbo XML is good too. They are for XSLT too.
**********************************************************/


But DTD and XSL are problematic. I know *how* to do these, that's not the issue here. My problem is who and when these should be done, any tools to simplify these developments. For example, is there any tool to visualize dtds(note that we have plenty of tools to check sql tables, right?). In the same fasion, is there any tool for xsl? Since blues are input to java files, and some we have to create them, my focus is on who(roles) and when(dependencies) to create them. By seperating the processes to create them, I could further understand the functionalities of each and make them flexible to each other(loosely coupled and concurrently-developing).


/**********************************************************
Actually, UI Designers should be responsible for user interface only, XML developers should be responsible for DTD/Schema development and they are independent of UI tasks, as long as you get them what they need to finish their work, there is no clear dependency I observe. UI is typically for end-users, and DTD or Schema is mainly for business analysts. Once UI prototypes are developed (basically a static site simulating functionalities in real world business environment), XML developers should be fairly comfortable to create DTD/Schema and XSLT to transform XML data into web representations for different end-users. This process is straightforward.
**********************************************************/


Sorry if I misled you. Don't worry about jdbc, jsp or content management since we are using xml, but not templating. We know or will know how to do this flow with xml(BTW, thanks for the book). But I just want to refine the process to create these artifacts(dtd, xsl).

Cocoon has a similar flow to this, so are several others. I've done a little, but not an expert on this. Apparently, it needs more experience to see through than what I know.

coder wrote:
you can see my last post, I recommend a good site you can master xml in ten minutes by learn the Tutorials & References and some xsl tools.

If you want to refine the process, there is my option:
1. define the DTD
2. generate the sample xml(It is used to be test xml by xsl)
3. a group generate the real xml
a group generate the xsl refer to the html

may I get one point?

coder wrote:
我还不善于用英语表达想法(这是我最佩服各位的啦)，为避免词不达意，所以用中文了

1. DTD的生成可以省略。所有数据采用一种xml格式，DTD不用也可以。
2. 你的流程图好像只是数据浏览，如果是这样，可以考虑使用xsql技术，一行java代码都不用写，而且性能非常好。

wishmaster wrote:

coder wrote:
XSQL
Oracle 公司开发的 Oracle XML Devleper Kit（简称 XDK）的一个组件。
更多信息请看 http://technet.oracle.com/tech/xml

只是一个简单Demo
1. URL格式:
http://yourcompany.com/AvailableFlightsToday.xsql?City=NYC

2. AvailableFlightsToday.xsql
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="FlightList.xsl"?>
<xsql:query connection="demo" bind-params="City" xmlns:xsql="urn:oracle-xsql">

SELECT Carrier, FlightNumber, Origin, TO_CHAR(ExpectedTime,'HH24:MI') Due
FROM FlightSchedule
WHERE TRUNC(ArrivalTime) = TRUNC(SYSDATE)
AND Destination = ?
ORDER BY ExpectedTime

</xsql:query>

3. 如果注释引入xsl的那句，就会直接输出xml

irisjacky wrote:
Finally, whatever background you have or how intelligent you are, it is totally booshit to learn a technology in 10 minutes or even so called "14 days".

floater wrote:
Wishmaster is right, I was just asking for a high level, functional-wise view of transferring xml to xhtml, not any specific tech details. The reason I restrict to 10 min is to abstract the implemental details out of what we *really* have to do. For example, using dtd or xml schema doesn't matter, we count as one step and leave the decision to later on; similar to sax or dom.

Thanks anyway. I like your last comment, , that's why I hate those books. b*llsh*t indeed. I was partially making fun of it.

wishmaster wrote:
I know you were simply putting together a rough project plan...