Registration of media type application/its+xml

[Felix Sasaki]

2010/4/21 Bjoern Hoehrmann <derhoermi at gmx.net>

> * Felix Sasaki wrote:
> >> The registration is based on an obsoleted template. Could you resubmit
> >> it using the RFC 4288 template? (In particular, the field names have
> >> changed, and some fields have been split into multiple fields).
> >
> >Yes, will do.
>
> Thanks.
>
> >> >Applications which use this media type:
> >> >    This new media type is being registered to allow for deployment of
> ITS
> >> >1.0 on the World Wide Web.
> >>
> >> This should give an idea what kinds of applications use the media type
> >> (revision control software, word processing software, ...)
> >
> >Propose to add: "ITS 1.0 information can be used e.g. by localization
> tools
> >to extract localizable units (e.g. text strings) as an input to the
> >localization process."
>
> That would be fine, something shorter like "Localization tools" would
> do, too.
>

OK.


>
> >> >Additional information:
> >> >    File extension:
> >> >        its
> >> >    Fragment identifiers:
> >> >        A syntax identical to that of "application/xml" as described in
> >> IETF
> >> >RFC 3023.
> >>
> >> RFC 3023 does not define fragment identifier syntax for application/xml.
> >
> >OK - I propose to leave the "Fragment identifiers" part out.
>
> Works for me.
>

Thanks.


>
> >> >    Base URI:
> >> >        As specified in IETF RFC 3023, section 6.
> >>
> >> RFC 3023 does not actually say something relevant here, for example, it
> >> is unclear whether xml:base is considered for application/its+xml.
> >
> >OK.
>
> (I am assuming, if ITS allows to specify resource identifiers somewhere,
> that the specification already defines how they are resolved, in that
> case this field could also be left out. That would adress my concern.)
>

OK, will leave that out.


>
> >> I do note that it is not actually clear to me what documents would be
> >> labeled with this type, for instance, what would be the root element of
> >> such documents?
> >
> >Any XML document containing ITS 1.0 "its:rules" elements can be labelled
> >with application/its+xml. At
> >http://www.w3.org/TR/its/EX-link-external-rules-2.xml
> >you see an example of a document linking to a file with ITS 1.0 "rules".
> The
> >link target is at
> >http://www.w3.org/TR/its/EX-link-external-rules-1.xml
> >as you can see the link target does not have "its:rules" as a root
> element.
> >The processing semantics here is that linked rules are gathered in
> document
> >order.
>
> I see. That should be noted in the registration then, I would put it
> upfront, but the "Published specification" field would be suitable
> aswell.


OK, will make a description upfront.


> Could there be any confusion for some particular document if
> application/its+xml or some other (+xml) type should be used? I'm
> thinking of http://www.w3.org/TR/xslt#result-element-stylesheet like
> situations in particular.
>

I don't think that such a conflict will occur, since the version attribute
of ITS is mandatory at the "its:rules" element, see
http://www.w3.org/TR/its/#its-version-attribute . 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.

Felix



> --
> Björn Höhrmann · mailto:bjoern at hoehrmann.de · http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-types/attachments/20100421/f70c4528/attachment-0001.htm