XML Schema and DTD for CVS Info in XML files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello dear CVS users, I'd like to know wether there already exists an XML Schema and a DTD to include CVS information in XML files. Currently, we use the following approach to use CVS information in XML files: This is not very convenient when the information shall be extracted during a transformation with XSLT / XPath. I'd rather like to use: http://www"; cvs:Id = "$Id$" cvs:Source = "$Source" -- ... -- > It's much easier to extract information from attributes rather than from comments. Are there already some "official" CVS Schema Modules and DTD modules which can easily be combined for instance with modularized XHTML (there I currently use meta elements) or modularized SVG to validate documents containing such CVS attributes? If not, I'd develop some and provide them to the public (e.g. for inclusion with the CVS distribution). Bye - -- ITCQIS GmbH Christian Wolfgang Hujer Geschäftsführender Gesellschafter Telefon: +49 (0)89 27 37 04 37 Telefax: +49 (0)89 27 37 04 39 E-Mail: [EMAIL PROTECTED] WWW: http://www.itcqis.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+blaAzu6h7O/MKZkRAgktAJ9P6uN1n1s0nKoOzgyH3DkL+jvQGwCgtoHu ZlXnpsBqSAMSCQ1UDGeDd+4= =nG4/ -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: XML Schema and DTD for CVS Info in XML files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Deron, dear list members, Am Dienstag, 11. März 2003 23:48 schrieb Deron Meranda: > > Currently, we use the following approach to use CVS information in XML > > files: ... > > > > Comments also don't work well because the "--" (hyphen-hyphen) > sequence is illegal in XML comments. In fact, even with elements you > probably need to use CDATA escapes. I would definitely place a $Log$ > inside an element body, as in > > That's a good idea but not always possible, for instance, when there's an easy approach to add attributes but adding elements is very difficult. We simply forbid the "--" in CVS Logs, as we forbid < and & and TODO. But that's a solution working fine on a small group, whereas a widespread solution must of course take into account that some won't be aware of the "--" problem (why should they care about "--", anyway). Thank you for the hint. > Other tags could probably either be inside attributes or elements, > depending upon how structured the value is. > I do agree that XML namespaces should be used. Yeah, I like them :-) > One big problem with automatically inserting text into a document is > that of character sets. What if the XML document uses UTF-16 rather > than UTF-8 or even ISO-8859-15? But I don't know if that is easily > solved. Of course XML basically dictates that UTF-8 is the default > unless its either explicitly specified or it can be automatically > detected to be something else. Thank you very much for pointing this out. I work in an ideal environment: A Linux system completely configured to use UTF-8 (yeah, I do not use GNOME for that reason). All files - Java, Perl, PHP, XML, /etc/passwd etc. are encoded in UTF-8. Currently, if the CVS log is included in an XML document, the log's author must always be aware of the restriction XML might imply on the log comment. But this problem is generic to automatically inserting bytes into a file format like XML, it is not specific to the combination CVS / XML, so I do not think it is a problem I could solve - or do you have a hint? Actually I'd not try to solve that problem because I see no chance to do so. I could imagine a CVS-XML-solution with a Schema defining the simple types (based on regular expressions) required for the CVS Keywords, a Schema to choose to use attributes only, a Schema to use elements only and a Schema to use both - and of course a corresponding set of modules for extending old DTD-based XHTML / SVG. Are you (Deron and other list members) interested? Bye - -- ITCQIS GmbH Christian Wolfgang Hujer Geschäftsführender Gesellschafter Telefon: +49 (0)89 27 37 04 37 Telefax: +49 (0)89 27 37 04 39 E-Mail: [EMAIL PROTECTED] WWW: http://www.itcqis.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+bncQzu6h7O/MKZkRAiuOAKDPDUAaZm9oZLfjhcMK1jYqNVxaQQCfUcwx AYVMvee+/rAshFF8Areb3Fg= =xYaO -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: XML Schema and DTD for CVS Info in XML files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Todd, dear list members, Am Mittwoch, 12. März 2003 15:20 schrieb Todd Denniston: > Herr Christian Wolfgang Hujer wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hello dear CVS users, > > > > I'd like to know wether there already exists an XML Schema and a DTD to > > include CVS information in XML files. > > > I am not sure it is exactly what you want but on the cvs2cl page there is a > dtd and schema for cvs2cl's output, which might at least give you some > ideas. http://www.red-bean.com/cvs2cl/ > http://www.red-bean.com/cvs2cl/changelog.dtd > http://www.red-bean.com/cvs2cl/changelog-xml-schema.xdr > new home for cvs2cl > http://search.cpan.org/author/FLUFFY/CVSUtils-1.00/ Thank you for pointing me on this. But it's very much different because the approach of cvs2cl is in no way easily combinable with XHTML, XML Schema, SVG etc.. By the way, the so-called "Schema" there is MS BizTalk crap, not XML Schema ;-) So it's of absolutely no use ;-) especially to someone like me who tries to stricktly stick to standards :-) Thanks, Bye - -- ITCQIS GmbH Christian Wolfgang Hujer Geschäftsführender Gesellschafter Telefon: +49 (0)89 27 37 04 37 Telefax: +49 (0)89 27 37 04 39 E-Mail: [EMAIL PROTECTED] WWW: http://www.itcqis.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+b1ftzu6h7O/MKZkRAsyWAJ9AG0wQce5/HZUCwmmtTQ+qWfEYOwCgs426 CY3LNN80OpPxXlYlpZV/hnQ= =DpVm -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Cvs implementation example.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Denis, Am Freitag, 28. März 2003 10:20 schrieb Denis JULIEN: > Hi, > I have to implement a cvs for a multiple developers environment. I have > installed it without problems and I've tested the major functionalities and > it seems working fine. It's my first time on this kind of versioning system > and I don't know the good practice in term of sources organization for a > project. For example, I'm asking if we have to create a repository for > each project or create only one repository and under it, create one module > for each project. Maybe somebody can tell me what are the good practices or > where I could found examples or typical and practical implementation of > cvs in multiple developers environment. Thank in advance for your help. at our company (5 workers, Linux), we use 3 Repositories: /home/cvsroot containing normal projects, one module for each project. /home/webroot containing web projects, one module for each project + one module called common also used by other projects /home/sysroot containing a module sysroot for the administration of the machines and the user management. I don't know wether that can be considered best practice, but it works well for us. To restrict rights, for each repository there is a group. To access a repository the person must be group member. Access to CVSROOT is restricted by using the sticky bit. Some modules are restricted furthermore by having a group for them. directory rights for repository and module directories are set to 2770 (rwxrws---). Bye - -- ITCQIS GmbH Christian Wolfgang Hujer Geschäftsführender Gesellschafter Telefon: +49 (0)89 27 37 04 37 Telefax: +49 (0)89 27 37 04 39 E-Mail: [EMAIL PROTECTED] WWW: http://www.itcqis.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+hClezu6h7O/MKZkRAuVpAJwP0M/raheIKnHP55UMW/g6XWf9mACgle1n rwHJSl7kOB3T92eBPswEuKo= =S6Q2 -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS Manual, section 2.9.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello John, Am Mittwoch, 26. März 2003 03:05 schrieb John Daues: > Thanks for taking care of the 'bug'. > > I don't know enough about it yet to know what to choose (rsh, ssh, > other?) Maybe if I tell y'all the basics of the system, you can say which. > > Server is a P3 machine running Red Hat 8.0 sitting on the LAN. > Clients are 3 users. Two running Win2k, One with RH 8.0. > Clients connect by the LAN, or dialing into LAN thru modem. > > Does this point one way or the other? > (or is there more info that would help?) I made best experiences with ssh. I have tried: local access / NFS, pserver and ext (with ssh). I have not tried: ext with rsh (it's unencrypted, but else doesn't differ from ssh), Kerberos etc.. The disadvantage about rsh/ssh access is that there must be user accounts. Best case one account for each cvs user, so you can tell the users from CVS ($Author$ etc.). With local access / NFS or pserver I often ran into Lock problems. (Waiting for XYZ's lock in directory abc). That never occurred to me with ext. I use ssh instead of rsh because a) the connection is encrypted b) Authentication can be done on a Private Key / Public Key basis, which I consider much more secure than .rhosts at rsh. When using key authentication (using ssh-keygen and ~/.ssh/authorized_keys) it is not neccessary to type in the password (same as with pserver and login, but more secure for the connection). On the other hand, giving everyone an account in the system could be considered insecure, unless they need or already have accounts anyway. Then pserver is better because you can create non-system-accounts that exist only within CVS / pserver. I have also heard that it's possible to tunnel pserver through ssh or http or https, but I do not know wether that is really possible, even less I know how to configure that. Bye - -- ITCQIS GmbH Christian Wolfgang Hujer Geschäftsführender Gesellschafter Telefon: +49 (0)89 27 37 04 37 Telefax: +49 (0)89 27 37 04 39 E-Mail: [EMAIL PROTECTED] WWW: http://www.itcqis.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+hCvPzu6h7O/MKZkRAtxoAJwIKmXdJqmLAPPmpSo1pLL82bEc1gCfcq6m pWLmo7nuLFI2VXC0FqyI0pw= =hEd1 -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
