OASIS XML Localisation Interchange File Format (XLIFF) TC

Hi TC folks,   In the xliff 2.0 spec, the following constraints are given on construction of fragment identifiers:   ·          A fragment identifier MUST match the following format: <_expression_>      ::= "#" ["/"] <selector> {<selectorSeparator> <selector>} <selector>        ::= [<prefix> <prefixSeparator>] <id> <prefix>          ::= NMTOKEN <id>              ::= NMTOKEN <prefixSeparator> ::= "=" <selectorSeparator>  ::= "/"   Is [“/”] to be interpreted as optional depending on whether the implementer wishes the fragment identifier to be relative or absolute?   For instance, are these two essentially equivalent?   #f=f1/u=u1/1 #/f=f1/u=u1/1   Only the first one is relative and the second is absolute? Which in the case of file is the same.   Thanks, Ryan  

Hi Ryan,   Yes.   -ys     From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Ryan King Sent: Wednesday, June 17, 2015 2:06 AM To: 'xliff@lists.oasis-open.org' Subject: [xliff] Question on fragment identifier   Hi TC folks,   In the xliff 2.0 spec, the following constraints are given on construction of fragment identifiers:   ·        A fragment identifier MUST match the following format: <_expression_>      ::= "#" ["/"] <selector> {<selectorSeparator> <selector>} <selector>        ::= [<prefix> <prefixSeparator>] <id> <prefix>          ::= NMTOKEN <id>              ::= NMTOKEN <prefixSeparator> ::= "=" <selectorSeparator>  ::= "/"   Is [“/”] to be interpreted as optional depending on whether the implementer wishes the fragment identifier to be relative or absolute?   For instance, are these two essentially equivalent?   #f=f1/u=u1/1 #/f=f1/u=u1/1   Only the first one is relative and the second is absolute? Which in the case of file is the same.   Thanks, Ryan