You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
erefType =
erefAttributes,
## Reference cross-reference: modelled as cross-reference to the corresponding bibliographical item in a References section
CitationType,
## The textual content of the element. The `text` is what we wish to show the link as (e.g., the "content" of `<xx>my link text</xx>`)
ErefBody
CitationType =
## Bibliographic item that the citation applies to, referenced as the anchor of a bibliographic description
attribute bibitemid { xsd:IDREF },
(
## Describes the location of the cited information resource within the subject of the bibliographic item.
## Multiple ``bibLocality``s are interpreted as discontinuous references.
locality* |
## Describes the location of the cited information resource within the subject of the bibliographic item in a multi-level manner.
## For example, the hierarchical specification "Part IV, Chapter 3, Paragraphs 22-24"
## is represented as a single `bibLocalityStack`, composed of those three localities
## (as opposed to three `bibLocality` references, which would be treated as three discontinuous references).
## Multiple ``bibLocalityStack``s are themselves interpreted as discontinuous references
localityStack*
),
## Date of the citation, typically date of publication.
## A combination of the date time elements year, month and day should be specified.
## Specification of month and day are optional.
## This date is not intended for disambiguation, since `bibitemid`
## already identifies the source unambiguously; it is added for ease of processing, in case author-date
## citations cannot straightforwardly extract the date from the bibliographic source
date?
ErefBody =
## The textual content of the element. The `text` is what we wish to show the link as (e.g., the "content" of `<xx>my link text</xx>`)
PureTextElement+
—is difficult to process, because ErefBody can be pure text, whereas CitationType is a group of locality elements: he is asking for ErefBody to have a wrapper element.
The request is reasonable, and processing eref as is has made metanorma code complex for having to fish out locality from surrounding plain text. The refactor needed will also not impact PDF, as eref and its contents are resolved to xref with no locality elements in Presentation XML.
It is nonetheless a non-trivial refactor, and I want to defer it until after I do the terms refactor for Presentation XML.
The text was updated successfully, but these errors were encountered:
In relaton/relaton-models#56 (comment), @andrew2net points out that the current content model of eref, which is a mix of text and elements—
—is difficult to process, because ErefBody can be pure text, whereas CitationType is a group of
locality
elements: he is asking for ErefBody to have a wrapper element.The request is reasonable, and processing
eref
as is has made metanorma code complex for having to fish outlocality
from surrounding plain text. The refactor needed will also not impact PDF, as eref and its contents are resolved to xref with nolocality
elements in Presentation XML.It is nonetheless a non-trivial refactor, and I want to defer it until after I do the terms refactor for Presentation XML.
The text was updated successfully, but these errors were encountered: