Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extensibility of JATS without breaking core functionality #5

Open
Melissa37 opened this issue Mar 27, 2019 · 0 comments
Open

Extensibility of JATS without breaking core functionality #5

Melissa37 opened this issue Mar 27, 2019 · 0 comments

Comments

@Melissa37
Copy link

Problem / Motivation

From Dorothy Hoskins (of Atypon), via an email string re: Texture (March 2018):
-Suggestion that JATS4R might look at the extensibility of JATS without breaking core functionality (à la DITA):

“HI, as a person who works with "green" JATS all the time, I know its extra
flexibility is both a blessing and a curse. There can be many ways to tag
content, some of which seem really stupid. However, I still think it is
smart to start from the "green" as you have maximum choice in what to pick
as your preferred tagging. There are many reasons that people come up with
for why they need some kind of tagging that you didn't think of.

For example: a hardcore semanticist will balk at having a <list> inside a
<p>, but publishers may actually continue a paragraph around the content of
a list because to them

  • it makes sense
  • their authors do it
  • the DTD allows it

so there is no good reason NOT to do it :-)

At JATS-CON this year there will be a presentation on the ever-growing JATS
standard https://jats.nlm.nih.gov/jats-con/2018/schedule2018a.html#1-900.
I think the JATS standards committee could learn something from the DITA
standards about extensibility that doesn't break core functionality. Is
that something that is being looked at in JATS4R?
Dorothy”

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant