<br><br><div class="gmail_quote">2010/4/21 Bjoern Hoehrmann <span dir="ltr"><<a href="mailto:derhoermi@gmx.net">derhoermi@gmx.net</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">* Felix Sasaki wrote:<br>
>> The registration is based on an obsoleted template. Could you resubmit<br>
>> it using the RFC 4288 template? (In particular, the field names have<br>
>> changed, and some fields have been split into multiple fields).<br>
><br>
>Yes, will do.<br>
<br>
</div>Thanks.<br>
<div class="im"><br>
>> >Applications which use this media type:<br>
>> > This new media type is being registered to allow for deployment of ITS<br>
>> >1.0 on the World Wide Web.<br>
>><br>
>> This should give an idea what kinds of applications use the media type<br>
>> (revision control software, word processing software, ...)<br>
><br>
>Propose to add: "ITS 1.0 information can be used e.g. by localization tools<br>
>to extract localizable units (e.g. text strings) as an input to the<br>
>localization process."<br>
<br>
</div>That would be fine, something shorter like "Localization tools" would<br>
do, too.<br></blockquote><div><br>OK.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
>> >Additional information:<br>
>> > File extension:<br>
>> > its<br>
>> > Fragment identifiers:<br>
>> > A syntax identical to that of "application/xml" as described in<br>
>> IETF<br>
>> >RFC 3023.<br>
>><br>
>> RFC 3023 does not define fragment identifier syntax for application/xml.<br>
><br>
>OK - I propose to leave the "Fragment identifiers" part out.<br>
<br>
</div>Works for me.<br></blockquote><div><br>Thanks.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
>> > Base URI:<br>
>> > As specified in IETF RFC 3023, section 6.<br>
>><br>
>> RFC 3023 does not actually say something relevant here, for example, it<br>
>> is unclear whether xml:base is considered for application/its+xml.<br>
><br>
>OK.<br>
<br>
</div>(I am assuming, if ITS allows to specify resource identifiers somewhere,<br>
that the specification already defines how they are resolved, in that<br>
case this field could also be left out. That would adress my concern.)<br></blockquote><div><br>OK, will leave that out. <br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
>> I do note that it is not actually clear to me what documents would be<br>
>> labeled with this type, for instance, what would be the root element of<br>
>> such documents?<br>
><br>
>Any XML document containing ITS 1.0 "its:rules" elements can be labelled<br>
>with application/its+xml. At<br>
><a href="http://www.w3.org/TR/its/EX-link-external-rules-2.xml" target="_blank">http://www.w3.org/TR/its/EX-link-external-rules-2.xml</a><br>
>you see an example of a document linking to a file with ITS 1.0 "rules". The<br>
>link target is at<br>
><a href="http://www.w3.org/TR/its/EX-link-external-rules-1.xml" target="_blank">http://www.w3.org/TR/its/EX-link-external-rules-1.xml</a><br>
>as you can see the link target does not have "its:rules" as a root element.<br>
>The processing semantics here is that linked rules are gathered in document<br>
>order.<br>
<br>
</div>I see. That should be noted in the registration then, I would put it<br>
upfront, but the "Published specification" field would be suitable<br>
aswell.</blockquote><div><br>OK, will make a description upfront.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Could there be any confusion for some particular document if<br>
application/its+xml or some other (+xml) type should be used? I'm<br>
thinking of <a href="http://www.w3.org/TR/xslt#result-element-stylesheet" target="_blank">http://www.w3.org/TR/xslt#result-element-stylesheet</a> like<br>
situations in particular.<br></blockquote><div><br>I don't think that such a conflict will occur, since the version attribute of ITS is mandatory at the "its:rules" element, see <a href="http://www.w3.org/TR/its/#its-version-attribute">http://www.w3.org/TR/its/#its-version-attribute</a> . Hence the situation is clearer than in the "XSL vs. AXL" example: if there is an "its:rules" element, gather its content as ITS rules and use them for ITS processing, otherwise not. <br>
<br>Felix<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<font color="#888888">--<br>
</font><div><div></div><div class="h5">Björn Höhrmann · mailto:<a href="mailto:bjoern@hoehrmann.de">bjoern@hoehrmann.de</a> · <a href="http://bjoern.hoehrmann.de" target="_blank">http://bjoern.hoehrmann.de</a><br>
Am Badedeich 7 · Telefon: +49(0)160/4415681 · <a href="http://www.bjoernsworld.de" target="_blank">http://www.bjoernsworld.de</a><br>
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · <a href="http://www.websitedev.de/" target="_blank">http://www.websitedev.de/</a><br>
</div></div></blockquote></div><br>