5 Oct
2008
5 Oct
'08
4:35 p.m.
Hi devs,
I'm working on implementing the new link format we've decided, i.e.:
label>reference>param1=value1 ... paramN=valueN
Note that there's a potential ambiguity with the following link:
text>param=value
Since this can be considered as either:
* label = text, reference = "param=value"
* reference = text, parameters = "param=value"
Thus we have to decide that it's fordbidden to use "=" in document
names or we need to find a different link format.
I think forbidding "=" is fine.
WDYT?
Thanks
-Vincent
5 Oct
5 Oct
4:52 p.m.
Vincent Massol wrote:
Hi devs,
I'm working on implementing the new link format we've decided, i.e.:
label>reference>param1=value1 ... paramN=valueN
Note that there's a potential ambiguity with the following link:
text>param=value
Since this can be considered as either:
* label = text, reference = "param=value"
* reference = text, parameters = "param=value"
Thus we have to decide that it's fordbidden to use "=" in document
names or we need to find a different link format.
I think forbidding "=" is fine.
WDYT?
That's one thing I didn't like at the proposed link syntax. Why not
request parameters to always be on the third position? The semantic
shouldn't influence the syntax, I really don't like sniffing to
determine what that fragment does. And I don't think we should forbid
characters in document names.
Another option would be to use different delimiters, for example > as
the delimiter between label and reference, and | as a delimiter before
parameters (note that > and | were both valid delimiters in the old syntax)
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
5922
days inactive
5922
days old
1 comments
2 participants
participants (2)
-
Sergiu Dumitriu -
Vincent Massol