-
Notifications
You must be signed in to change notification settings - Fork 4
ISODoc: Terms and Definitions
Nick Nicholas edited this page Jan 26, 2018
·
19 revisions
terms =
element terms {
attribute id { text },
term*
}
# Ignore
terms_subsection =
element terms_subsection {
attribute identifier { text },
section_title?,
( term* | terms_subsection+ )
}
term =
element term {
attribute id? { text },
preferred+, definition, note*, admitted*,
termexample*, termdomain?, termdeprecates, termsource
}
preferred =
element preferred { TextElement }
admitted =
element admitted { TextElement }
termdeprecates =
element deprecates { TextElement }
note = element note { paragraph+ }
termdomain = element domain { text }
termexample = element example { paragraph+ }
# I'd argue example is in fact basic block; the ISO standard constraint to plain text is not universal
definition = element definition { paragraph+ }
termsource =
element source {
origin, origin_status, noteIfModified?
}
origin =
element origin { bibliographic_item }
# need to type in UML
origin_status =
element status { ( "identical" | "modified" ) }
noteIfModified =
element note { paragraph }
Items for discussion (threaded: identify by number)
-
term@identifier: renamed from "anchor", need to be consistent. Use either identifier or anchor for internal identifiers of block
-
termexample: I’d argue termexample is in fact a basic block; the ISO standard constraint of it to be a plain string is not universal
-
termsource/origin: needs to have type in UML as bibliographic_item
-
Definitions in ISO can include figures and formulae, but let’s leave that out of this more general spec.
-
Term/Source is not an Item, but a Citation