[tei-council] idno -> ptr

Kevin Hawkins kevin.s.hawkins at ultraslavonic.info
Thu Jun 20 12:34:11 EDT 2013


Good idea.  I've put in a feature request:

https://sourceforge.net/p/tei/feature-requests/462/

On 6/20/13 11:55 AM, Hugh Cayless wrote:
> I do want to raise one small quibble that doesn't likely affect implementing the ticket, but which I think should be kept in mind for the future. It *is* possible to have an HTTP URI which is also an identifier, and in that case, I'd argue for keeping it in <idno>. I doubt there are any examples in the Guidelines, but it's the kind of thing we may see more of as Linked Data picks up steam. For example, the URI http://papyri.info/biblio/8276/ref denotes an actual book, and resolves to http://papyri.info/biblio/8276, which is a bibliographic record. Worldcat ids, like http://www.worldcat.org/oclc/185922478 function in the same way, and I can easily see people wanting to use them inside <bibl>s.  I would. Maybe some thinking about the appropriate @type to use for these is warranted...
>
> Hugh
>
> On Jun 20, 2013, at 10:11 , Syd Bauman <Syd_Bauman at Brown.edu> wrote:
>
>> I went to process my assigned task from the minutes of our April
>> meeting, "remove our own dis-recommended use of <idno> in the
>> bibliography". Supposedly this is because we "agreed that these fixes
>> need to be made. <idno> wrapped in <analytic>, <monogr> <series>,
>> will change @type="url" to <ref>".
>>
>> However, we have no <idno type='url'> wrapped in <analytic>,
>> <monogr>, or <series> in the Guidelines. (Neither in main TEI
>> namespace nor in Examples namespace.) We do have dozens of 'em
>> directly inside <biblStruct>, and I think the same logic applies:
>> those that are pointing to a web page should be <ptr> (or <ref>, but
>> see [1]), not <idno>.
>>
>> So I went through the list of 'em. The vast majority obviously point
>> to a page (e.g., end in ".html"), so I consider those candidates for
>> conversion. I took a look at the 37 of them that were not obvious at
>> a glance, running `wget` on each of them. 30 fetched a file (not
>> surprisingly, most of which were named "index.html" :-).
>>
>> However, 7 did not resolve to a file, but rather gave an error of
>> some sort (see [2] for details). What I've done for now is turn *all*
>> of the <idno type='url'> into <ptr>, adding a subtype="winita" (work
>> is needed in this area) attribute to the 7 that do not resolve
>> properly. I'm hoping someone will volunteer to track 'em down and fix
>> 'em before next week.
>>
>> NOTE: Since I cannot build P5 here (I'm at the ambulance station
>> today and only have my Mac, not a Debian-based system), I probably
>> won't check this in until after I can check it later tonight.
>>
>> Notes
>> -----
>> [1] Actually, <ptr> will do just as well as <ref>, and the only one
>>     example I found that is already a <ptr> or <ref> is a <ptr>.
>>     Since
>>     I have no content to dream up to put inside <ref>, I'll use <ptr>
>>     for now. If & when we dream up content we can use <ref>.
>>
>> [2] Output form `wget` on each of the 7 problematic URLs follows.
>>
>>     ---------http://www.w3.org/TR/REC-CSS21/:
>>     --2013-06-20 09:30:44--  http://www.w3.org/TR/REC-CSS21/
>>     Resolving www.w3.org... 128.30.52.37
>>     Connecting to www.w3.org|128.30.52.37|:80... connected.
>>     HTTP request sent, awaiting response... 404 Not Found
>>     2013-06-20 09:30:45 ERROR 404: Not Found.
>>
>>     ---------http://portal.acm.org/citation.cfm?id=963653:
>>     --2013-06-20 09:30:45--
>>     --http://portal.acm.org/citation.cfm?id=963653
>>     Resolving portal.acm.org... 64.238.147.56, 64.238.147.53
>>     Connecting to portal.acm.org|64.238.147.56|:80... connected.
>>     HTTP request sent, awaiting response... 301 Moved Permanently
>>     Location: http://dl.acm.org/citation.cfm?id=963653 [following]
>>     --2013-06-20 09:30:45--  http://dl.acm.org/citation.cfm?id=963653
>>     Resolving dl.acm.org... 64.238.147.56, 64.238.147.53
>>     Connecting to dl.acm.org|64.238.147.56|:80... connected.
>>     HTTP request sent, awaiting response... 403 Forbidden
>>     2013-06-20 09:30:45 ERROR 403: Forbidden.
>>
>>     ---------http://ota.ahds.ac.uk/documents/creating/:
>>     --2013-06-20 09:30:45--
>>     --http://ota.ahds.ac.uk/documents/creating/
>>     Resolving ota.ahds.ac.uk... 163.1.0.23
>>     Connecting to ota.ahds.ac.uk|163.1.0.23|:80... connected.
>>     HTTP request sent, awaiting response... 404 Not Found
>>     2013-06-20 09:30:46 ERROR 404: Not Found.
>>
>>     ---------http://hdl.handle.net/1956/1875:
>>     --2013-06-20 09:30:46--  http://hdl.handle.net/1956/1875
>>     Resolving hdl.handle.net... 38.100.138.166, 38.100.138.165,
>>     --132.151.9.184, ...
>>     Connecting to hdl.handle.net|38.100.138.166|:80... connected.
>>     HTTP request sent, awaiting response... 303 See Other
>>     Location: http://bora.uib.no/handle/1956/1875 [following]
>>     --2013-06-20 09:30:46--  http://bora.uib.no/handle/1956/1875
>>     Resolving bora.uib.no... 129.177.6.72, 2001:700:200:6::72
>>     Connecting to bora.uib.no|129.177.6.72|:80... connected.
>>     HTTP request sent, awaiting response... 302 Found
>>     Location: https://bora.uib.no/handle/1956/1875 [following]
>>     --2013-06-20 09:30:47--  https://bora.uib.no/handle/1956/1875
>>     Connecting to bora.uib.no|129.177.6.72|:443... connected.
>>     ERROR: cannot verify bora.uib.no's certificate, issued by
>>     --`/C=NL/O=TERENA/CN=TERENA SSL CA':
>>       Self-signed certificate encountered.
>>     To connect to bora.uib.no insecurely, use
>>     --`--no-check-certificate'.
>>     ---------http://portal.acm.org/citation.cfm?id=827192:
>>     --2013-06-20 09:30:47--
>>     --http://portal.acm.org/citation.cfm?id=827192
>>     Resolving portal.acm.org... 64.238.147.56, 64.238.147.53
>>     Connecting to portal.acm.org|64.238.147.56|:80... connected.
>>     HTTP request sent, awaiting response... 301 Moved Permanently
>>     Location: http://dl.acm.org/citation.cfm?id=827192 [following]
>>     --2013-06-20 09:30:47--  http://dl.acm.org/citation.cfm?id=827192
>>     Resolving dl.acm.org... 64.238.147.56, 64.238.147.53
>>     Connecting to dl.acm.org|64.238.147.56|:80... connected.
>>     HTTP request sent, awaiting response... 403 Forbidden
>>     2013-06-20 09:30:47 ERROR 403: Forbidden.
>>
>>     ---------http://edis.ifas.ufl.edu/BODY_AE038:
>>     --2013-06-20 09:30:47--  http://edis.ifas.ufl.edu/BODY_AE038
>>     Resolving edis.ifas.ufl.edu... 128.227.242.126
>>     Connecting to edis.ifas.ufl.edu|128.227.242.126|:80... connected.
>>     HTTP request sent, awaiting response... 301 Moved Permanently
>>     Location: /body_ae038 [following]
>>     --2013-06-20 09:30:48--  http://edis.ifas.ufl.edu/body_ae038
>>     Reusing existing connection to edis.ifas.ufl.edu:80.
>>     HTTP request sent, awaiting response... 404 Not Found
>>     2013-06-20 09:30:48 ERROR 404: Not Found.
>>
>>     ---------http://www.cta.dmu.ac.uk:8000/AnaServer?teidoc+0+start.anv:
>>     --2013-06-20 09:30:48--
>>     --http://www.cta.dmu.ac.uk:8000/AnaServer?teidoc+0+start.anv
>>     Resolving www.cta.dmu.ac.uk... 146.227.164.96
>>     Connecting to www.cta.dmu.ac.uk|146.227.164.96|:8000... failed:
>>     --Connection refused.
>>
>> --
>> N.B.: New e-mail address as of 2013-07-01 will be
>>        s.bauman at neu.edu
>> --
>> 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
>


More information about the tei-council mailing list