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.

Sign up for GitHub

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

Jump to bottom

introduction to namespaces based on (a bit of) a fallacy #2626

Open
sydb opened this issue Dec 2, 2024 · 2 comments
Open

introduction to namespaces based on (a bit of) a fallacy #2626

sydb opened this issue Dec 2, 2024 · 2 comments
Assignees
@lb42
Labels
TEI: Guidelines & Documentation
Milestone
Guidelines 4.9.0

Comments

@sydb
Copy link
Member

sydb commented Dec 2, 2024

The first sentence of #SGname is “A valid XML document necessarily specifies the schema in which its constituent elements are defined.”. Problem is, it is not true. An XML document that has no indication of its schema may well be valid against several schemas. (And invalid against millions, but that is irrelevant.) To put it another way

<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>tiny valid TEI document</title>
      </titleStmt>
      <publicationStmt>
        <p>unpublished, except on this ticket.</p>
      </publicationStmt>
      <sourceDesc>
        <p>born digital</p>
      </sourceDesc>
    </fileDesc>
  </teiHeader>
  <text>
    <body>
      <p>Here is a tiny snippet of text.</p>
    </body>
  </text>
</TEI>

is valid against both tei_all and tei_lite (and is not valid against DocBook, or XHTML, or NEMSIS, or …), but does not say what schema it is valid against.

Seems to me the entire paragraph needs a bit of a re-write.
@sydb sydb added this to the Guidelines 4.9.0 milestone Dec 2, 2024
@sydb sydb assigned lb42 Dec 2, 2024
@lb42
Copy link
Member

lb42 commented Dec 3, 2024 •
edited
Loading

How about "A valid XML document necessarily specifies or implies some schema within which its constituent elements are defined and rules about their usage are given: this is a part of what it means to be "valid". By contrast, a well formed XML document is not required to specify a schema at all. Nonetheless, it may well be useful to indicate that the element names used in it have some defined provenance. It might also be desirable to include in a document elements that are defined (possibly differently) in different schemas. A cabinet-maker's schema might well define an element called <table> with very different characteristics from those of a documentalist's."

@sydb
Copy link
Member Author

sydb commented Dec 3, 2024

Seems fine to me, thus #2627.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lb42 lb42

Labels
TEI: Guidelines & Documentation
Projects
None yet
Milestone
Guidelines 4.9.0
Development

No branches or pull requests
2 participants
@sydb @lb42