Re: [tei-council] proc mod queries

OK, thanks for the clarification: could you supply an example we could add to the prose to make this point succintly? On 06/02/16 11:36, Magdalena Turska wrote:

Can we get back to this discussion? Section on Outputs http://teic.github.io/TEI/TD.html#TDPMOU is where I have most objections to the current prose. Starting with '@output attribute is used to associate particular processing models with a specific type of output channel or output format' I don't like the assumption that output is the same as format/channel/device, and the current wording suggests there can be one set of processing directives per 'type of output'. I think this is a common case where multiple views of the document are offered for the same channel/output/format, eg like here http://vangoghletters.org/vg/letters/let570/letter.html view of the letters with/without line endings. Format stays the same (HTML), channel/device stays the same (website), but still we would be talking two (even if only slightly) different @outputs in the odd.

Thus I believe we should avoid suggesting that `output` means `format` and state somewhere that @output is just an identifier of a certain intended processing scenario. And provide an example that illustrates this.

Am I the only one having trouble with this?

Magdalena

On 21 January 2016 at 20:57, Magdalena Turska wrote:

...

Hi Lou,

thanks for pointing this out. I believe that having @output as a closed list is indeed wrong. Not only output could be given as any format, as yet unforeseen even, but output is basically any view of the document one might want to produce, thus 'print-for-ones-who-could-not-be-bothered-with-footnotes' might well coexist with 'print-as-we-would-send-to-UOP', both targetting same format but presenting the document in a distinct way.

Thus having answered a) I believe b) is a moot point (@output value is just an identifier of a transformation defined by models for which this output applies).

Asking Simpletons doesn't hurt. Much. I hope. :)

Magdalena

On 21 January 2016 at 20:35, Lou Burnard wrote:

...

I've made a bit more progress on the "processing model" extensions to ODD proposed by the TEI Simpletons a while ago, and now have a version of P5 based on the current dev branch which includes them AND builds correctly. But I havent yet finished hacking the prose into shape, and I have some questions.

Here's the first.

The @output attribute "the intended output method" (that's clearly wrong though; surely it should be "the intended output target"?) is defined with a closed list of values "web", "print", and "plaintext".

a) why is this a closed list? I can think of lots of other possible values e.g. "mobile device", "PDF", "text-to-speech synthesizer" for starters...

b) what exactly does "plaintext" mean?

And here's the zero'th. To whom if not the Council should I be addressing this query?

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived