DTD Repository
-
The purpose of a shared DTD is to established an agreed format between multiple clients. I don't see the purpose of the sort of repository you're proposing. you should also abandon DTD's - they suck. An XSD is the way to establish schema information. 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-2002Christian 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."
-
Yes, but why would competing products publicise their formats so that other products can offer easy export to customers leaving them ? And as you say, XSLT is a good tool for converting formats, although less so DTD, compared to XSD. 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-2002Christian Graus wrote: Yes, but why would competing products publicise their formats so that other products can offer easy export to customers leaving them ? Because, It is a requirement for my company to purchase 5000 seats of your product, if you want our buisness. "I will find a new sig someday."
-
Christian Graus wrote: The purpose of a shared DTD is to established an agreed format between multiple clients. I don't see the purpose of the sort of repository you're proposing. Bit contradictory that, don't you think? The repository idea is actually been done for DTDs and XSDs (the concept is the same) and I think it is a great idea. Take the medical profession for instance. They have a multitude of forms and data models. There are efforts under way to compile a central repository of XML vocabs for the medical industry. Then any doctor who needs to publish some finding can go online, get the right vocab and publish his work. Prescriptions, chemical models, gene models, medicine production chains, you name it. Oasis-Open.org[^] is just the thing. Very useful.
Paul Watson
Bluegrass
Cape Town, South AfricaShog9 wrote: Everybody just wants to be naked and famous, Paul.
Paul Watson wrote: The repository idea is actually been done for DTDs and XSDs The direct link to the site hosted by Oasis is: http://www.xml.org/xml/registry.jsp[^] There are several products for organizations to host their own internal schemas for internal and business to business usage. These are useful for validation of shared or submitted XML files for data handoffs. "I will find a new sig someday."
-
Christian Graus wrote: Yes, but why would competing products publicise their formats so that other products can offer easy export to customers leaving them ? Because, It is a requirement for my company to purchase 5000 seats of your product, if you want our buisness. "I will find a new sig someday."
Well, obviously if someone is forced to do it, that's another matter. But why would I force you to tell the world about the format you create for me ? 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: The purpose of a shared DTD is to established an agreed format between multiple clients. I don't see the purpose of the sort of repository you're proposing. Bit contradictory that, don't you think? The repository idea is actually been done for DTDs and XSDs (the concept is the same) and I think it is a great idea. Take the medical profession for instance. They have a multitude of forms and data models. There are efforts under way to compile a central repository of XML vocabs for the medical industry. Then any doctor who needs to publish some finding can go online, get the right vocab and publish his work. Prescriptions, chemical models, gene models, medicine production chains, you name it. Oasis-Open.org[^] is just the thing. Very useful.
Paul Watson
Bluegrass
Cape Town, South AfricaShog9 wrote: Everybody just wants to be naked and famous, Paul.
Paul Watson wrote: Bit contradictory that, don't you think? Not at all. I can see why if my company is going to share info with yours, we agree on a shared XSD. I don't see why our companies would want to tell the world. Paul Watson wrote: The repository idea is actually been done for DTDs and XSDs (the concept is the same) and I think it is a great idea. Is it driven by people using it, or on an 'if we build it, they will come' approach ? 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 -
Well, obviously if someone is forced to do it, that's another matter. But why would I force you to tell the world about the format you create for me ? 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-2002Christian Graus wrote: But why would I force you to tell the world about the format you create for me ? One if it is the world or just still private is open. In my case data management and migration is a very expensive task. What if you go out of buiseness? I must have the ability to migrate the data I own. (The US supreme court did rule (for the US ok) that the company that uses the product owns the data not the company that made the software product a number of years ago.) I also have the right to share my data with partners that may not be using your product. So I publish my data in a format that can be shared and managed. You may very well have a private format that is used internally, but you will have a published format that is public and very perferably based on some international standard. "I will find a new sig someday."
-
Paul Watson wrote: Bit contradictory that, don't you think? Not at all. I can see why if my company is going to share info with yours, we agree on a shared XSD. I don't see why our companies would want to tell the world. Paul Watson wrote: The repository idea is actually been done for DTDs and XSDs (the concept is the same) and I think it is a great idea. Is it driven by people using it, or on an 'if we build it, they will come' approach ? 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-2002Christian 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 AfricaShog9 wrote: Everybody just wants to be naked and famous, Paul.
-
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 AfricaShog9 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 -
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-2002Christian 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 AfricaShog9 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-2002Christian 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."