Closed cristianolongo closed 8 years ago
For UID field can be used everything which guarantees persistent, globally unique identifier for the calendar component. I was thinking something as indicate in the RFC : "date-create(text format)@agenda-unica" but we can use IRI too.
The URI of the individual representing the event (it should be ?item) is a unique identifier for the event in the universe.
On Fri, Aug 5, 2016 at 2:40 PM, Federico Frasca Polara < notifications@github.com> wrote:
For UID field can be used everything which guarantees persistent, globally unique identifier for the calendar component. I was thinking something as indicate in the RFC : "date-create(text format)@agenda-unica" but we can use IRI too.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/opendatahacklab/free-agenda/issues/56#issuecomment-237840047, or mute the thread https://github.com/notifications/unsubscribe-auth/AG3jgJsrHZEcLmsvJLVSHos2TYhbiziPks5qcy9SgaJpZM4JdiLR .
Update done using URI for UID.
Use the URI for UID generate a warning in the RFC 5545 validator because the strings are too long
it has to be split as indicated in the RFC itself. I think this fix should be propagated to other fields.
Th UID field is empty. Check in the specification if the event IRI can be used as event UID