You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During researching for PR #33 I noticed that for ATOM IDs the code is using the urn URI scheme. This is not wrong per se, but IMHO the tag scheme is better. I've checked the ATOM feeds of some big sites, and all were using the tag scheme. It doesn't need a registration at IANA and also contains more information than a simple UUID.
Highly appreciated. Actually, the urn:uuid is not always neccessary, as far as I researched now. Acutally, it seems to prevent RSS readers to read any further than one item in my setup. So the tag method seems to be a better way to go IMHO.
Weird, BTW: No matter what I pass on with $newItem->setId($url), all UUID for every Entry remain the same?! Is there any reason for that and how I could fix this?
Weird, BTW: No matter what I pass on with $newItem->setId($url), all UUID for every Entry remain the same?! Is there any reason for that and how I could fix this?
During researching for PR #33 I noticed that for ATOM IDs the code is using the
urn
URI scheme. This is not wrong per se, but IMHO thetag
scheme is better. I've checked the ATOM feeds of some big sites, and all were using thetag
scheme. It doesn't need a registration at IANA and also contains more information than a simple UUID.Here are some opinions and information:
What do you guys think about that?
The text was updated successfully, but these errors were encountered: