#533 Add profileDesc as optional child biblFull
As per discussion on TEI-L on 2014-11-14, I suggest to add profileDesc as an optional child biblFull. There are two use cases on my side:
- documenting entries in the HAL system (see https://hal.inria.fr/hal-00762664v3/tei) with keywords and classification schemes
- documenting journal list with classification schemes
"Kevin Hawkins seemed in phase with this. I quote: I would support a proposal to add profileDesc as an optional child of biblFull. Not only do you provide a user case for adding "various keywords and classifiers" to your bibliographic descriptions, but I can imagine descriptive and annotated bibliographies that include things like a UDC or Dewey class number or the language(s) of the work. All of these would better fit in <profileDesc> than elsewhere in the current model of biblFull."
We're wondering whether a) you mean biblFull or biblStruct, and b) whether allowing textClass inside bibl* would suffice. There's a lot of stuff in profileDesc that isn't really appropriate...
Assigning to Hugh Cayless to progress at F2F meeting raleigh 2014-11-17
The discussion should clearly be about biblFull at this stage, with the idea that we provide a bibliographic description of a document in the same way as we describe a TEI encoded document by means of a header. From this perspective it makes no sense to be picky with profileDes cans just select sub-components. (we could describe an audio file and use settingDesc. We would of course also need abstract. I would avoid surgery (+ the cos if someone comes afterwards with extra needs...). As to biblStruct, I would suggest to open a specific ticket (it's a stronger move).
We need to discuss this further, so I will raise it on the Council list.