Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RFC 7953 - VAVAILABILITY component #654

Open
22 tasks
niccokunzmann opened this issue Jun 24, 2024 · 0 comments
Open
22 tasks

RFC 7953 - VAVAILABILITY component #654

niccokunzmann opened this issue Jun 24, 2024 · 0 comments
Labels
feature

Comments

@niccokunzmann
Copy link
Member

In order to claim compatibility to RFC 7953, we should add an Availability component equivalent to Event to represent VAVAILABILITY

Add

  • class Availability
  • dtstamp REQUIRED
  • uid REQUIRED
  • busytype
  • class
  • created ONCE
  • description ONCE
  • dtstart REQUIRED
  • last-mod ONCE
  • location ONCE
  • organizer
  • priority
  • seq
  • summary ONCE
  • url
  • dtend XOR duration
  • categories
  • comment
  • contact
  • recurid ONCE
  • rrule ONCE
  • Examples from RFC

See also:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@niccokunzmann