W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2006

[Bug 3050] Linking mechanism

From: <bugzilla@wiggum.w3.org>
Date: Mon, 27 Mar 2006 22:00:28 +0000
CC:
To: public-i18n-its@w3.org
Message-Id: <E1FNzlE-0007El-Rq@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3050





------- Comment #5 from fsasaki@w3.org  2006-03-27 22:00 -------
(In reply to comment #4)
> <its:rulesLink> sounds good to me.
> 
> One question: Where does it go? stand-alone (wherever the host format allows
> it)? or as the first entry in a <its:documentRules>?

I think it would not make sense in <its:documentRules>. Rather standalone.

> 
> For being sure we look at all the possibilities:
> 
> - This link could be also done or as a standalone attribute: <myDoc
> its:link="href">

I would prefer XLink, as Sebastian proposed at
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3050#c3 .

> 
> - Or as a PI (like for CSS): <?its-rules href="file.xml" ?>
> 
> The PI has the advantage of working everywhere (always valid even in DTD-based
> formats).

What do you mean by "valid"? Processable? That would be the case with XLink
too.

> 

(In reply to comment #3)
> Then maybe using XLink's simple link would be better: not re-inventing
> something and keeping it processable by simple tools. I'm not very familiar
> with XLink but it seems we should be able to do:
> 
> <its:link xlink:href="someRules.xml"/>
> 

++1
Received on Monday, 27 March 2006 22:00:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC