[tei-council] keeping @ident unique

Lou Burnard lou.burnard at retired.ox.ac.uk
Sun Jan 5 06:52:04 EST 2014


I suggest:

a) change the name of the module to "certaintyModule" or similar

b) establish as a point of principle that there is a single name space 
for the identifiers of all identifiable objects (modules, elements, 
classes, macros...) and document this in tcw21



  should always be On 05/01/14 11:45, Sebastian Rahtz wrote:
> the current P5 build fails with this error:
>
>> <Messages>
>>    <ERROR>"certainty" in specDesc: TEI[1]/text[2]/body[3]/div["CE"]/div["CECERT"]/div["CECECE"]/p[7]/specList[8]/ refers to attribute "locus" which does not exist</ERROR>
>>    <ERROR>"certainty" in specDesc: TEI[1]/text[2]/body[3]/div["CE"]/div["CECERT"]/div["CECECE"]/p[7]/specList[8]/ refers to attribute "degree" which does not exist</ERROR>
>>
> Why, you ask, since <certainty> does have an attribute “locus”? well, it’s a laxness on the checking script which looks for things
> with an @ident of “certainty” when it meets <specDesc key=“certainty”>; which falls foul of the fact that we have two
> things called “certainty”:
>
> 	Source/Specs/certainty.xml:<elementSpec xmlns="http://www.tei-c.org/ns/1.0" module="certainty" ident="certainty">
> 	Source/Guidelines/en/CE-CertaintyResponsibility.xml:<moduleSpec xml:id="DCE" ident="certainty"><altIdent type="FPI”>Certainty
>
> while I can of course fix the validator, this seems like an unsatisfactory state of affairs which we should avoid if
> we possibly can.
>
> I dont propose any action today, but its an accident waiting to happen again.
> --
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>



More information about the tei-council mailing list