[osis-core] <resp>

[Chris Little]

Okay... Troy pointed out to me we already have a resp attribute in 
globalWith/WithoutType and that it is xs:string.  But he points out that 
he doesn't "know how to use it to encode all the information needed: who 
/ what / when," which points to the need for a best practice statement 
for the manual, if not constraint via a pattern.

Given that it's already implemented as xs:string, I'm sure the best 
practice route will be preferrable, though we can probably be fairly 
confident that no one has actually used the resp attribute to date in 
any documents.

--Chris

Chris Little wrote:

> Hmm, I find myself in the rather diagreeable position of agreeing with 
> Troy. :)
> 
> I'm not sure that he isn't thinking of the resp attribute on 
> revisionDesc, but I think the availability of resp in any location would 
> be invaluable for translation & linguistic annotation (the latter 
> actually being what Troy is using it for here).
> 
> I would argue that it would be better if we could stick it into an 
> attribute that would be better, though, since it is essentially 
> information about a container (I assume).
> 
> TEI's version is here: http://www.tei-c.org/Vault/GL/P3/ref/RESP.htm . I 
> would suggest something like adding resp to globalWith/WithoutType as 
> type xs:string.  Or with a pattern that allows encoding name, date, & 
> comment, like Troy's example (e.g. "[A-Za-z0-9 
> ]+(\|([0-9]{4}\-[0-9]{2}\-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2})?\|[A-Za-z0-9 
> \-\:]+)?", using pipe as field divider).
> 
> --Chris