[tei-council] [tei:bugs] #617 <num> not a part of att.segLike (and thus of att.fragmentable)

[James Cummings]

likewise from me.

-James

On 26/06/14 13:48, Martin Holmes wrote:
> +1 from me.
>
> Cheers,
> Mrtin
>
> On 14-06-26 04:25 AM, Fabio Ciotti wrote:
>> I would close this ticket with a rejection since my arguments have
>> been accepted or not refuted.
>>
>> FC
>>
>> 2014-05-27 11:12 GMT+02:00 Fabio Ciotti <fabio.ciotti at uniroma2.it>:
>>> In general I would say no, since I don't think the TEI schema should
>>> change so deeply for the requirements of a single user, especially if
>>> there is a reasonable solution inside the actual schema. But if you
>>> feel it would be nice to contact the submitter personally I can do it
>>> (anyway many months have passed and probably they did find a
>>> solution).
>>>
>>> Fabio
>>>
>>> 2014-05-22 17:27 GMT+02:00 Martin Holmes <mholmes at uvic.ca>:
>>>> Should we contact the submitter to see whether they have any good
>>>> arguments that make nesting <w>, <phr> or <seg> inside <num> to solve
>>>> the problem an inadequate solution?
>>>>
>>>> Cheers,
>>>> Martin
>>>>
>>>> On 14-05-22 05:37 AM, Peter Stadler wrote:
>>>>> Sounds reasonable.
>>>>> +1 for rejecting
>>>>>
>>>>> Am 22.05.2014 um 12:39 schrieb Fabio Ciotti <fabio.ciotti at UNIROMA2.IT>:
>>>>>
>>>>>> My opinion is to reject the request since:
>>>>>>
>>>>>> 1) the same happens for many phrase level elements with similar
>>>>>> semantic functions as <date> or <measure> etc. For simmetry we should
>>>>>> change them all
>>>>>> 2) <w> is (should) be used to carry morpho-syntactic features of its
>>>>>> content, whil <num> bears a semantic tract of its content, so they
>>>>>> have different markup semantic
>>>>>> 3) there is a fairly simple solution for both the issues, that is
>>>>>> nesting <w> or <phr> inside <num>
>>>>>> 4) in the worst case the issue can be faced with a local extension of
>>>>>> TEI scheme.
>>>>>>
>>>>>> Fabio
>>>>>>
>>>>>>
>>>>>> assigned_to: Fabio Ciotti
>>>>>> Comment:
>>>>>>
>>>>>> Assigning to Fabio Ciotti for triage, reporting to council, and implementation
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> [bugs:#617] <num> not a part of att.segLike (and thus of att.fragmentable)
>>>>>>
>>>>>> Status: open
>>>>>> Group: AMBER
>>>>>> Created: Tue Oct 29, 2013 09:39 PM UTC by Ville Marttila
>>>>>> Last Updated: Tue Oct 29, 2013 09:39 PM UTC
>>>>>> Owner: Fabio Ciotti
>>>>>>
>>>>>> Considering that the element <num> is parallel to the element <w> in
>>>>>> annotating a number, which can from a linguistic point of view be
>>>>>> considered a word-level unit, it should also belong to the att.segLike
>>>>>> class. This would not only provide it with the @function attribute for
>>>>>> annotating its syntactic function but would also include it in the
>>>>>> att.fragmentable class, allowing the annotation of incomplete numbers
>>>>>> (esp. Roman numerals which are often quite long and can easily be
>>>>>> partially lost).
>>>>>>
>>>>>> ________________________________
>>>>>> --
>>>>>> tei-council mailing list
>>>>>> tei-council at lists.village.Virginia.EDU
>>>>>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>>>>>
>>>>>> PLEASE NOTE: postings to this list are publicly archived
>>>>>
>>>>>
>>>>>
>>>> --
>>>> tei-council mailing list
>>>> tei-council at lists.village.Virginia.EDU
>>>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>>>
>>>> PLEASE NOTE: postings to this list are publicly archived


-- 
Dr James Cummings, James.Cummings at it.ox.ac.uk
Academic IT Services, University of Oxford