<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi,</p>
<p>as regards <br>
</p>
<p>> these format-related specifications (in this case: the name
and possible<br>
> values of attributes which are used in addition to a mime
type) would<br>
> need to be documented and made known at a central place. <br>
</p>
I'd say the documentation for each would need to be accompanied by
its TEI schema, i.e. the TEI ODD file and the derived (probably)
RelaxNG schema. Then it would be a simple matter to check if a
document conforms to the mime type.<br>
<br>
Best,<br>
Tomaž<br>
<br>
<div class="moz-cite-prefix">Bryan Jurish je 21/06/2016 ob
14:22 napisal:<br>
</div>
<blockquote
cite="mid:CAMg255yjd-m3qrd-yNoLF+8PLitQNXw8jfe0ohQQ1suzzZ4U7g@mail.gmail.com"
type="cite">
<div dir="ltr">morning all,
<div><br>
</div>
<div>sounds good to me.</div>
<div><br>
</div>
<div>@Marie: can you give an estimation of how well this might
work for WebLicht?</div>
<div><br>
</div>
<div>I'll add the "format-variant=tei-dta" parameter to the DTA
TEI<->TCF web service in the next few days, so we can
see how that at least works out.</div>
<div><br>
</div>
<div>marmosets,</div>
<div> Bryan</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jun 21, 2016 at 12:32 PM,
Thomas Schmidt <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:thomas.schmidt@ids-mannheim.de"
target="_blank">thomas.schmidt@ids-mannheim.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all,<br>
<br>
revising my suggestions from the teiweblicht list according
to Bryan's<br>
proposal to use official mime-types plus parameters (instead
of<br>
x-extended custom mime types) would mean that:<br>
<br>
"text/x-tei-isospoken+xml" could become "text/tei+xml;<br>
format-variant=tei-iso-spoken" (+ tokenized=0/1)<br>
"text/x-tei-dta+xml" could become "text/tei+xml;<br>
format-variant=tei-dta" (+ tokenized=0/1)<br>
"text/x-exmaralda-exb+xml" could become "text/xml;
format-variant=exmaralda-exb"<br>
... and so forth (for other TEI oder XML based formats)<br>
<br>
Wouldn't that be a solomonic solution? What do the WebLicht
developers<br>
say? And independently of that, I think that Hanna is right
that these<br>
format-related specifications (in this case: the name and
possible<br>
values of attributes which are used in addition to a mime
type) would<br>
need to be documented and made known at a central place. I
guess it<br>
would be up to the standards committee to decide on that?<br>
<br>
Best regards,<br>
<br>
Thomas<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
<br>
<br>
On Sat, Jun 18, 2016 at 10:56 AM, Bryan Jurish <<a
moz-do-not-send="true" href="mailto:jurish@bbaw.de"><a class="moz-txt-link-abbreviated" href="mailto:jurish@bbaw.de">jurish@bbaw.de</a></a>>
wrote:<br>
> moin all,<br>
><br>
> fwiw, I agree with Dieter that we need to
differentiate between "proper"<br>
> MIME types (i.e. standardized conventions
registered with IANA) and<br>
> CLARIN-internal (rsp. WebLicht-internal)
conventions. We have been using<br>
> MIME types as the basis of the WebLicht
textSource/@type attribute,<br>
> analogous to the HTTP "ContentType" header, cf.<br>
> <a moz-do-not-send="true"
href="https://tools.ietf.org/html/rfc2045#section-5.1"
rel="noreferrer" target="_blank">https://tools.ietf.org/html/rfc2045#section-5.1</a>
. At the risk of repeating<br>
> what I've already said on the tei-weblicht list,
use of the ContentType<br>
> syntax allows us to have our cake and eat it too:
we can go ahead and use<br>
> "official" IANA-sanctioned "true" MIME types and
specify variants<br>
> ("dialects", "flavors") using parameters. The DTA
TEI<->TCF converter is<br>
> already doing this, setting textSource/@type to
either "text/tei+xml;<br>
> tokenized=0" or "text/tei+xml; tokenized=1",
depending on the relevant<br>
> properties of the input document.<br>
><br>
> just my €0.02.<br>
><br>
> marmosets,<br>
> Bryan<br>
><br>
><br>
> On Fri, Jun 17, 2016 at 1:43 PM, Dieter Van
Uytvanck <<a moz-do-not-send="true"
href="mailto:dieter@clarin.eu">dieter@clarin.eu</a>><br>
> wrote:<br>
>><br>
>> On 17/06/16 12:59, Sander Maijers wrote:<br>
>> > After all, you would want a<br>
>> > resource's metadata to be completely
descriptive of such elementary<br>
>> > aspects as internal structure and content
of the TEI files, and not<br>
>> > dependent on system configuration (served
as custom media type x or y,<br>
>> > as long as the server remains so
configured).<br>
>><br>
>> Hi Sander,<br>
>><br>
>> Thank you for sharing your opinion.<br>
>><br>
>> One side note: we are talking about detecting
the mimetype as indicated<br>
>> in the CMDI ResourceProxy attribute, see:<br>
>><br>
>><br>
>> <a moz-do-not-send="true"
href="https://www.clarin.eu/faq/how-can-i-specify-additional-details-about-resourceproxy"
rel="noreferrer" target="_blank">https://www.clarin.eu/faq/how-can-i-specify-additional-details-about-resourceproxy</a><br>
>><br>
>> So for the scenario VLO -> LR switchboard
-> processing application<br>
>><br>
>> the system configuration would not be relevant,
since the mimetype is<br>
>> explicitly mentioned in the metadata. The key
is to find agreement about<br>
>> a simple and light-weight way of designating
the variants of TEI.<br>
>><br>
>> best,<br>
>><br>
>> --<br>
>> Dieter Van Uytvanck<br>
>> Technical Director CLARIN ERIC<br>
>> <a moz-do-not-send="true"
href="http://www.clarin.eu" rel="noreferrer"
target="_blank">www.clarin.eu</a> | tel. <a
moz-do-not-send="true"
href="tel:%2B31-%280%29850091363" value="+31850091363">+31-(0)850091363</a>
| skype: dietervu.mpi<br>
>> _______________________________________________<br>
>> Teiweblicht mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:Teiweblicht@lists.informatik.uni-leipzig.de">Teiweblicht@lists.informatik.uni-leipzig.de</a><br>
>> <a moz-do-not-send="true"
href="http://lists.informatik.uni-leipzig.de/mailman/listinfo/teiweblicht"
rel="noreferrer" target="_blank">http://lists.informatik.uni-leipzig.de/mailman/listinfo/teiweblicht</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> ***************************************************<br>
> Bryan Jurish<br>
> Deutsches Textarchiv<br>
> Digitales Wörterbuch der deutschen Sprache<br>
> Berlin-Brandenburgische Akademie der Wissenschaften<br>
><br>
> Jägerstr. 22/23<br>
> 10117 Berlin<br>
><br>
> Tel.: <a moz-do-not-send="true"
href="tel:%2B49%20%280%2930%2020370%20539"
value="+493020370539">+49 (0)30 20370 539</a><br>
> E-Mail: <a moz-do-not-send="true"
href="mailto:jurish@bbaw.de">jurish@bbaw.de</a><br>
> ***************************************************<br>
><br>
> _______________________________________________<br>
> Teiweblicht mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Teiweblicht@lists.informatik.uni-leipzig.de">Teiweblicht@lists.informatik.uni-leipzig.de</a><br>
> <a moz-do-not-send="true"
href="http://lists.informatik.uni-leipzig.de/mailman/listinfo/teiweblicht"
rel="noreferrer" target="_blank">http://lists.informatik.uni-leipzig.de/mailman/listinfo/teiweblicht</a><br>
><br>
<br>
<br>
<br>
--<br>
</div>
</div>
<div class="HOEnZb">
<div class="h5">Thomas Schmidt<br>
IDS Mannheim<br>
R5, 6-13<br>
D-68161 Mannheim<br>
Tel.: <a moz-do-not-send="true"
href="tel:%2B49%20%28621%29%201581-313"
value="+496211581313">+49 (621) 1581-313</a><br>
<a moz-do-not-send="true"
href="http://agd.ids-mannheim.de/index.shtml"
rel="noreferrer" target="_blank">http://agd.ids-mannheim.de/index.shtml</a><br>
<a moz-do-not-send="true"
href="http://www.exmaralda.org" rel="noreferrer"
target="_blank">http://www.exmaralda.org</a><br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">***************************************************<br>
Bryan Jurish<br>
Deutsches Textarchiv
<div>Digitales Wörterbuch der deutschen Sprache
<div>
<div>Berlin-Brandenburgische Akademie der Wissenschaften<br>
<br>
Jägerstr. 22/23<br>
10117 Berlin<br>
<br>
Tel.: +49 (0)30 20370 539<br>
E-Mail: <a moz-do-not-send="true"
href="mailto:jurish@bbaw.de" target="_blank">jurish@bbaw.de</a><br>
***************************************************</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>