EpiDoc: Epigraphic Documents in TEI XML / Request Features / #129 additional default attribute value suggestions for biblScope@unit

BODARD Gabriel - 2017-10-06

I have no objection to this. Perhaps we could crowdsource a list of (no more than 5-6) additional values from the Markup list, and also decide which are sufficiently arcane to remain user-defined.

Are the EpiDoc Guidelines explicit about the fact that this is an open, not closed, list of values?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tom Elliott - 2017-10-06

I don't think the EpiDoc guidelines talk about this at all.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tom Elliott - 2017-10-06

I have now written to markup about this: http://lsv.uky.edu/scripts/wa.exe?A2=ind1710&L=markup&F=&S=&P=2467

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tom Elliott - 2017-10-16

On-list suggestions to date:

appendix

band

book

database id

figure

folio

note

section

tome

verse
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Emmanuelle Morlock - 2017-10-17

"entry" should be added too (for dictionnary/encyclopedia entries, often ordered alphabetically so with no page number or item number)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tom Elliott - 2017-10-17

I agree that we should retain "entry" and the other values currently inherited from the TEI: volume, issue, page, line, chapter, part, column, entry.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Emmanuelle Morlock - 2017-10-17
  
  Thanks Tom,
  
  it tested it with oxygen and the new values were not presented., Even after
  updating the oxygen tei framework.
  Sorry for the bothering ticket : I should have checked the GL first!
  
  I went to GitHub looking for the source spec or ODD…
  In https://github.com/TEIC/TEI/blob/dev/P5/Source/Specs/att.citing.xml
  found my answer (but with some kind of inversion I guess. So maybe all that
  was not completely unuseful…
  
  <valItem ident="column">
  the element identifies
  an entry number or label in a list of entries.
  </valItem>
  
  <valItem ident="entry"> <desc versionDate="2017-06-24" xml:lang="en">the element
  
  identifies a column.
  </valItem>
  
  sorry again
  best
  Emmanuelle
  
  De: Elliott Tom paregorios@users.sf.net paregorios@users.sf.net
  Répondre: [epidoc:feature-requests]
  129@feature-requests.epidoc.p.re.sf.net
  129@feature-requests.epidoc.p.re.sf.net
  Date: 17 octobre 2017 at 17:24:01
  À: [epidoc:feature-requests] 129@feature-requests.epidoc.p.re.sf.net
  129@feature-requests.epidoc.p.re.sf.net
  Sujet: [epidoc:feature-requests] #129 additional default attribute value
  suggestions for biblScope@unit
  
  I agree that we should retain "entry" and the other values currently
  inherited from the TEI: volume, issue, page, line, chapter, part, column,
  entry.
  
  [feature-requests:#129]
  https://sourceforge.net/p/epidoc/feature-requests/129/ additional default
  attribute value suggestions for biblScope@unit
  
  Status: unread
  Group: 8.24
  Labels: schema
  Created: Thu Oct 05, 2017 09:46 PM UTC by Tom Elliott
  Last Updated: Tue Oct 17, 2017 02:55 PM UTC
  Owner: nobody
  
  The current EpiDoc schema inherits some "suggested" values for @unit on
  biblScope (and other citation-related elements). These suggested values are
  inherited from the TEI
  http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.citing.html,
  but EpiDoc workshop participants note that a number of additional values
  (common to epigraphic publication), could usefully be added:
  
  fascicle
  
  item
  
  plate
  
  Sent from sourceforge.net because you indicated interest in
  https://sourceforge.net/p/epidoc/feature-requests/129/
  
  To unsubscribe from further messages, please visit
  https://sourceforge.net/auth/subscriptions/
  
  Related
  
  Request Features: ~~#129~~
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2017-10-17

Group: 8.24 --> 9.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tom Elliott - 2017-10-20

status: unread --> accepted

assigned_to: Tom Elliott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2018-02-20

Group: 9.0 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2018-02-20

I think this is a simple decision: which of the long-ish list of suggestions from Markup should we set in stone (or at least wet clay) as EpiDoc recommended values. Also make sure this is documented in the Guidelines, making clear that this is an open, not closed, list.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2019-01-22

Group: future --> 9.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scott Vanderbilt - 2019-10-22

Group: 9.1 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scott Vanderbilt - 2019-10-22

Bumped -> Future.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scott Vanderbilt - 2020-01-21

assigned_to: Tom Elliott --> Scott Vanderbilt

Group: future --> 9.2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scott Vanderbilt - 2020-01-21

Bumped -> Future.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scott Vanderbilt - 2020-06-16

Scott to determine final list in accordance with discussion during ticket sprint call on 2020-06-16.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2020-08-07

@sarcanon Do you plan to have this implemented by September 2020 (as per the [Milestone:9.2] assignment)?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scott Vanderbilt - 2020-09-14

status: accepted --> done
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scott Vanderbilt - 2020-09-14

Implemented.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

additional default attribute value suggestions for biblScope@unit

XML text markup for ancient documents

Group

Searches

Help

#129 additional default attribute value suggestions for biblScope@unit

Related

Discussion

Related