norman.walsh.name: Comments on /2004/10/18/frangelicohttp://norman.walsh.name/2004/10/18/frangelico/comments.atom2012-02-13T08:41:18.664089ZComment 1 on /2004/10/18/frangelicohttp://norman.walsh.name/2010/09/25/oauth#comment00012004-10-18T15:44:03Z2004-10-18T15:44:03ZJirka Kosekda39a3ee5e6b4b0d3255bfef95601890afd80709

I was big fan of XLink in past, but now I don't like it much because it depends on #FIXED attributes in DTD which is now considered bad thing and it is not supported in Relax NG for example. If I correctly understand XLink specification each simple link must have attribute xlink:type="simple" present on a corresponding linking element. But in RNG you can't specify this default value in schema so you should write 

<phrase xl:href="http://www.example.com/" xl:type="simple">inline link</phrase>
instead of 
<phrase xl:href="http://www.example.com/">inline link</phrase>
This seems to me as too verbose and hard to sell given the lack of generic XLink tools on market. If the xl:type="simple" is really neccessary I would prefer other way of linking then XLink -- the old one or invent something as generic as XLink but more useable. I think that something as HLink (http://www.w3.org/TR/hlink/) link types definition specified in an external file and attached by some global attribute (similar to xsi:schemaLocation, but now for links) could work. Integrating something like HLink into XLink should remove most drawbacks of XLink IMHO.
Comment 2 on /2004/10/18/frangelicohttp://norman.walsh.name/2010/09/25/oauth#comment00022004-10-19T21:12:53Z2004-10-19T21:12:53ZRasmus Kajda39a3ee5e6b4b0d3255bfef95601890afd80709

The content model of attribution is "(db._text | db.personname)", but I would rather have it "(db._text | db.personname)*", so it can contain both a personname and some other text, such as:

<attribution><personname>Rasmus Kaj</personname>, in a comment on this blog</attribution>

It there a reason for only accepting either but not both? Or is it just a + sign missing on line 1005 of pool.rnc?

Comment 3 on /2004/10/18/frangelicohttp://norman.walsh.name/2010/09/25/oauth#comment00032004-10-20T19:53:38Z2004-10-20T19:53:38ZNorman Walshda39a3ee5e6b4b0d3255bfef95601890afd80709

Taking a peek at how attribution is defined in the DTD, I think the + sign is missing. Fixed (locally).

Comment 4 on /2004/10/18/frangelicohttp://norman.walsh.name/2010/09/25/oauth#comment00042004-10-23T12:23:44Z2004-10-23T12:23:44ZRasmus Kajda39a3ee5e6b4b0d3255bfef95601890afd80709

Thank you! I hope I didn't cut of any XLink comments, as I would be much interested to see what comes out of that ... One thing that I would like to see, and that I don't think XLink provides, is the ability to use "link shortcuts". Example:

I spend my time at a university, and thus sometimes I have reason to link to course info. But a link into the course catalog is a 100-character string that I can't keep in my head. But all courses has a unique id of six characters, e.g. FG4711. So I put href="course:FG4711" in my documents and have my xslt sort it out. A more standardized way to manage that would be nice.