|
Christian Graus wrote:
I don't see why our companies would want to tell the world.
Think bigger than companies. Think industries. We already do share DTDs. Namely XHTML, SVG, CML (Chemical Markup Language) and a host of others. The whole point is so that two companies in the same industry can communicate efficiently between each other on an industry agreed standard. If we keep our DTDs locked up then they are pretty damned worthless, their value is far less.
Anyway, I believe in sharing schemas.
Christian Graus wrote:
Is it driven by people using it, or on an 'if we build it, they will come' approach ?
They provide the hosting space and industries then elect a committee to produce a schema or ten for the industry. The schema is then hosted on the site. Even just those two repositories I mentioned have thousands of schemas for everything from biometrics to graphics to automobiles.
Paul Watson
Bluegrass
Cape Town, South Africa
Shog9 wrote:
Everybody just wants to be naked and famous, Paul.
|
|
|
|
|
Paul Watson wrote:
Even just those two repositories I mentioned have thousands of schemas for everything from biometrics to graphics to automobiles.
Yes, but do people use them ?
Paul Watson wrote:
Anyway, I believe in sharing schemas.
I think it CAN be a good idea, I just don't see why it should be automatic.
Christian
No offense, but I don't really want to encourage the creation of another VB developer.
- Larry Antram 22 Oct 2002
C# will attract all comers, where VB is for IT Journalists and managers - Michael
P Butler 05-12-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not
as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
|
|
|
|
|
Christian Graus wrote:
Yes, but do people use them ?
Indeed. We actually used a standardised company stock information schema awhile back to share stock data between two companies.
Generally we are not large enough to be doing inter-company projects which require shared schemas, so we have not had much practice in it. But that one time was actually very interesting.
Christian Graus wrote:
I just don't see why it should be automatic.
You are right there. Certainly sharing schemas is not always the right thing to do. Take it on a case by case example.
Paul Watson
Bluegrass
Cape Town, South Africa
Shog9 wrote:
Everybody just wants to be naked and famous, Paul.
|
|
|
|
|
Christian Graus wrote:
Yes, but do people use them ?
All of the larger manufacturing companies do. It is also standard in the financial industry. So yes.
Not schema but for an example look at the CAD industry. No one company makes all of any of the larger products they work with many suppliers and do not requirer the same software execpt for close partners. All of the major CAD vendors support STEP and IGES to communicate with each other. The ones that stayed proprietary only are gone.
Christian Graus wrote:
I just don't see why it should be automatic.
Depends on your industry. For mine migration and sharing of data is an absolute must. So we will not buy products that do not allow us that capability. You do not have to meet our requirements and we do not have to buy your product. Simple market driven events.
"I will find a new sig someday."
|
|
|
|
|
Christian Graus wrote:
An XSD is the way to establish schema information.
You are correct here. There are some exceptions (mostly in publishing areas) but all new work is highly encouraged to use XSD's.
"I will find a new sig someday."
|
|
|
|
|
Victor Boctor wrote:
or example, I am currently looking for a DTD that defines the rules for XML files that are to include bug information
Oasis-Open.org[^] is just the thing.
I did not see a bug/issue list XML vocab there, but you can always start your own and then host it on Oasis.
I think the idea of a XML vocab repository is excellent.
http://www.xml.org/[^] also has a repository.
Paul Watson
Bluegrass
Cape Town, South Africa
Shog9 wrote:
Everybody just wants to be naked and famous, Paul.
|
|
|
|
|
I need a xml filter for Indexing services. There are any chances to find one that is working ?
Thanks a loot .
|
|
|
|
|
can someone explain to me the differences between those two functions? in the simple examples i've been doing, they seem interchangeable. and i read the MSDN xslt reference which shed some light, but not really.
particularly, it says value-of will give me a string of the matched element. great. so that means if i have <element>TESTING</element>
<xsl:value-of select="element"/> will give me "TESTING". as will <xsl:apply-templates select="element"/> which, if there is no template for "element" will use the default template, right? and the default template is basically just outputing the value of the <element> tag?
but msdn also says value-of should give me a concatenation of strings if the matched element has a substructure. so if i had
<element>
<sub>1</sub>
<bleh>2</bleh>
</element>
<xsl:value-of select="element"/> should give me "12", right? well, not when i tried it. or am i misunderstanding? anyway, that's just one question i had. the actual quote from msdn is
"If the node returned is an element with substructure, <xsl:value-of> returns the concatenated text nodes of that element's subtree with the markup removed."
the real question is what's the difference between the two and what would you use them for?
|
|
|
|
|
AFAIK, the docs are right about value-of, which is used to get a value from a node. apply templates is used to set a point at which the process of building a result will begin. They have different goals in mind, even if one can simulate the other in some circumstances.
Christian
No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
|
|
|
|
|
If you are ever interested in obtaining better documentation on XSL than what you get from Microsoft, Michael Kay's XSLT Programmer's Reference is a really good book. It's definitely a reference, not a "how to" book, and will give you examples of the different ways in which you can use the various XSL elements.
Sean Winstead
|
|
|
|
|
Although it's worth mentioning that he has an unreasonable hatred of all things from Redmond, that is indeed an excellent book and my main XSLT reference.
Christian
No offense, but I don't really want to encourage the creation of another VB developer.
- Larry Antram 22 Oct 2002
C# will attract all comers, where VB is for IT Journalists and managers - Michael
P Butler 05-12-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not
as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
|
|
|
|
|
If i want to automatically remove the asp page from cache i use
<% Response.CacheControl = "no-cache" %>
<% Response.AddHeader "Pragma", "no-cache" %>
<% Response.Expires = -1 %>
Like this in html i use
How to remove like this xml file from cache.
|
|
|
|
|
I have cache problems also, never enough. 
How are using the xml file? Is it being transformed? If so output the html lines and it should work.
|
|
|
|
|
How can I get the current line of a xml element / node ?
I am working with the MS XML DOM parser!
Daniel
---------------------------
Never change a running system!
|
|
|
|
|
Daniel,
First what do you mean by the current line. My assumption is that you mean the text value associated with an element node. Which happens to be the collection of child nodes to that element which are text nodes.
So look up in the help section that comes with MSXML4 (which I recommend if you do not have)
HRESULT get_childNodes(
IXMLDOMNodeList **childList);
and then look up TextNode. The first part from one of the sections returned is:
XML DOM Enumerated Constants
IXMLDOMNodeType enumerations specify valid settings for the Document Object Model (DOM) node type. The node type determines valid values and whether the node can have child nodes.
Values
The IXMLDOMNodeType enumeration defines the following valid values.
NODE_ELEMENT (1)
The node represents an element (its nodeTypeString property is "element"). An Element node can have the following child node types: Element, Text, Comment, ProcessingInstruction, CDATASection, and EntityReference. The Element node can be the child of the Document, DocumentFragment, EntityReference, and Element nodes.
NODE_ATTRIBUTE (2)
The node represents an attribute of an element (its nodeTypeString property is "attribute"). An Attribute node can have the following child node types: Text and EntityReference. The Attribute node does not appear as the child node of any other node type; it is not considered a child node of an Element.
NODE_TEXT (3)
The node represents the text content of a tag (its nodeTypeString property is "text"). A Text node cannot have any child nodes. The Text node can appear as the child node of the Attribute, DocumentFragment, Element, and EntityReference nodes.
So you get the list of child nodes and step through that list. Compare the node type of the child to "NODE_TEXT" (3) and you most of the way there.
Once you get the flavor it really does make sense.
"I will find a new sig someday."
|
|
|
|
|
What I mean is the current line of a xml node / element in the xml file, like the get_line() function of the IXMLDOMParseError return.
I read some attributes of a xml node / element and check if they are in the possible range (eg. - 100 < attribute < +100). If the attribute is not in the range I want to display an error with the line, where I read the attribute / node / element!
Daniel 
---------------------------
Never change a running system!
|
|
|
|
|
Have you considered using a schema to enforce your data type and valid ranges? Going in that direction may be a lot easier since you basically let the XML parser validate all of your data.
|
|
|
|
|
Do you have any sample how I can tell the MSXML DOM parser how to valid my XML file?
Daniel
---------------------------
Never change a running system!
|
|
|
|
|
Daniel S. wrote:
What I mean is the current line of a xml node / element in the xml file, like the get_line() function of the IXMLDOMParseError return.
Do not confuse the parser error messages that help identify where an error occurs by referencing the line in the file that contains the xml file with how the DOM is structured. All ascii data (non attribute values, comments, processing instructions, etc) is text nodes in the the DOM (line feeds etc. inlcuded)
To get the value of an attribute node:
hr = pIXMLDOMElement->getAttribute(bstrAttributeName, &varValue);
see "IXMLDOMAttribute" in the MSXML 4 help file for the above code sample.
YOu need to get the root node and then work your way down the child nodes handling them as appropriate.
"I will find a new sig someday."
|
|
|
|
|
I'm trying to chop the sig digits of numbers. The numbers are accessed at certain levels down the data structure, e.g. /OverallData/Year/Area/../../Value. It causes error if I use format-number(/OverallData/../../../.., ###.##), how do you do it? Also the number can be an attribute of a node. It's a pretty lazy question, but I'm in a hurry to finish off a task, thanks in advance.
|
|
|
|
|
I never tried it with a full XPath but I think you need to add apostrophs around the format string, e.g.:
<xsl:value-of select="format-number(<XPath>,'###.##&apos)" />
Hope this helps,
Bjørn.
|
|
|
|
|
I try to save my data in my pocket pc application in xml with the MSXML DOM parser. I looked on some source codes and found out that are are many different classes (interfaces) like "IXMLDOMDocumentPtr" and "IXMLDOMDocument" ... what's the different between this classes (interfaces)?
Daniel
---------------------------
Never change a running system!
|
|
|
|
|
They basicly the same. The COM interfaces without the trailing Ptr are the raw interfaces, while the ones with the ptr are smart pointers which free the COM object if the interfaces isnt referenced anymore.
|
|
|
|
|
IXMLDOMDocument is a COM interface. IXMLDOMDocument* is an interface pointer on a particular instance of a DOMDocument COM object. IXMLDOMDocumentPtr is a typedef for a _com_ptr_t that manages a IXMLDOMDocument*.
--Mike--
"Adventure. Excitement. A Jedi craves not these things."
-- Silent Bob
1ClickPicGrabber - Grab & organize pictures from your favorite web pages, with 1 click!
My really out-of-date homepage
Sonork-100.19012 Acid_Helm
|
|
|
|
|
Thanks!
Daniel
---------------------------
Never change a running system!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
