Re: RFC - vCard and vCalendar - parse & generate

[Jay Lawrence]

There is no official specification of the XML equivalent for the v* file formats. From what I can see the process is moving along but slowly. There is also an RSS spec in the works for these files. I am get the impression that more are using the original file format rather than XML or RSS - if you have sample data please forward & I will add to my samples I have on file.

As far as capitalization - I will use VCARD (implementation -> based on BEGIN:VCARD & END:VCARD) or vCard which appears to be the 'official' name of the spec.

And yeh, upon writing this it makes sense to move them up. The Business::vFile module remains as the base class, but I will rename the others to : Business::vCalendar vs. Business::vFile::vCalendar.

The XML/RSS formats should be easy to support as well - however I am preferring to stay away from XML stuff much beyond using XML::Simple! ;-)

J

On Friday, January 3, 2003, at 12:23 PM, Chris Josephes wrote:

On Fri, 3 Jan 2003, Jay Lawrence wrote:

I am thinking more along the line of:

	Business::vFile::
		VCALENDAR
		VFILE

Isn't there an XML equivelant of the vCard specification? I know Jabber
uses an XML formatted vCard for its user directory.

What if you just used

Business::VCard
Business::VCal

That way you can leave the namespace ambiguous as to what internal format
it uses. (Ie: you wouldn't see "Business::XML::vCard" down the road.

Also, you might want to stick to Perl capitalization conventions for the
class names.

--------------------
Christopher Josephes
[EMAIL PROTECTED]