-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UD syntax: underscores in extended relations #27
Comments
OK, you indeed do have a point here. And maybe I am being too catious with not using colons in the values, as we could suppose that the prefix is only the part before the first colon, i.e. the software doing the prefix stripping will be smart enough to take the shortest rathen than the longest match.
It still looks a bit funny, but maybe this is the least of all evils. |
Drat, I now remembered another reason why I didn't wan't colons in UD relations: in the TEI are actually the values of So, I have to think again about this... |
OK, I though about it and I'm afraid I can't change the current practice, so the underscore will stay. I don't like your suggestion with using
If it is any consolation, note that the UD-SYN taxonomy/category/catDesc/term actually contains the real UD category with colons. So, for user-facing applications, don't show them the value of |
Yes, I am aware of the fact that the colon is not allowed in
I am using colons in links:
but in taxonomy ids, I use Ok, let's keep it as is. |
Ah, I see! You were miles ahead of me in #5, I didn't even properly look at the above, much less figure out what you meant. Sorry about that, at that time I didn't know I was dealing with a guru... But you would have to explain to me how the above can be used in practice. I currenlty just do something like this: ParlaMint/Scripts/check-links.xsl Line 134 in 8db7591
So, how woud you use your Also, given the definition of |
using xPath in How I understand it: But how it can be used in XSLT is a really good question! Problem is that the dynamic evaluation of XPath is not widely supported: http://exslt.org/dyn/functions/evaluate/ |
So it is, interesting.
Hmm, the TEI link above certainly supports your understanding, alas, not mine. I would expect #my.id to be exactly that, i.e.
Yes, I was sceptical, as far as I know XPath is a first-class citisen only in XLST 3.0, and there is not much software that supports it. Actually, Saxon does, but only the commercial editions, not SaxonHE, which I use. OK, I guess I could buy it, but I would like my software to be portable (even in nobody does port it..).
That sounds even scarier! Might as well start programming in LISP again :) I think I need to sleep on this one... |
OK, slept on it, and I'm afraid that the solution to have the colon in ud-syn: IDREF is just too convoluted, so we stay with underscore. But, as mentioned,
Which might be a small consolation. |
I have moved to the annotation part of our project and looked at UD extended syntactic relations again (#5).
@TomazErjavec, I don't want to push you too obstinately but I think that a solution with underscores
_
in extended relations is not good and can be confusing for users who are habituated to colons:
.As I see, you are willing to do changes in ParlaMint schema. So I am trying it one more time.
If I understand you, you don't want to use a
:
in taxonomy because of a possible collision with prefixes. So I'm suggesting using@type
and@subtype
in relational links.Current:
Suggestion:
My solution doesn't go against UD standard it just split relation and its extension. I don't think that we have to introduce a new extended syntactic relations standard...
@TomazErjavec .
Please, can you look at it one more time?
Is it really necessary to create a new "standard" for UD syntax?
Can you figure out another better solution? (ideally where relation and extension would be in a single string...
rel:ext
)The text was updated successfully, but these errors were encountered: