Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What does it mean that an endpoint id must conform to the Namespace Specific String syntax from RFC 2141?

April 26, 2017conform endpoint Id mean namespace rfc String syntax

0

Posted

What does it mean that an endpoint id must conform to the Namespace Specific String syntax from RFC 2141?

1 Answer

0

Posted

Endpoint identifiers are used in two attributes: the “id” attribute in the sx:sync element, and the “by” attribute in the sx:history element. The requirement in section 2.1, item 1 states that “All endpoint identifiers MUST conform to the syntax for Namespace Specific Strings (the NSS portion of a URN) in RFC 2141.” In practice, what this means is that the endpoint id could be a simple string like “ABC123”, or it could be a URN such as a UUID. Both examples meet the NSS syntax requirement. It is up to the application developer to decide which type of endpoint id makes more sense for their application. For simple applications, it might be possible to ensure that the “id” and “by” attributes are unique without having to use UUIDs. For more complex applications, the application developer might decide that a UUID or URL is more appropriate.