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

Is this folia valid? And how to handle it... #69

Open
kosloot opened this issue Mar 5, 2019 · 3 comments
Open

Is this folia valid? And how to handle it... #69

kosloot opened this issue Mar 5, 2019 · 3 comments
Assignees
@proycon @kosloot
Labels
question

Comments

@kosloot
Copy link
Collaborator

kosloot commented Mar 5, 2019

Given this FoliA example:

<?xml version="1.0" encoding="UTF-8"?>
<FoLiA xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://ilk.uvt.nl/folia" xml:id="apart" generator="libfolia-v0.11" version="1.5">
  <metadata type="native">
    <annotations>
    </annotations>
  </metadata>
  <text xml:id="text">
    <div xml:id="text.div.1">
      <head xml:id="head">
	<t>Kop</t>
      </head>
      <p xml:id="text.div.1.p.1">
	<t>OK?</t>
      </p>
      <s xml:id="text.div.1.s.1">
        <t>Inleiding</t>
        <w xml:id="text.div.1.s.1.w.1">
          <t>Inleiding</t>
        </w>
      </s>
    </div>
  </text>
</FoLiA>

it is accepted by the validator and also folialint.
There is maybe an issue here with the <div> having both a Sentence AND a Paragraph.
This is valid FoLiA, but maybe it is against the 'gut feeling' that in this case the Sentence should be embedded in a Paragraph. Should this feeling be formalized? (an how)
And if not, this has ramifications for a lot of FoLiA based software, liike Ucto, Frog, TICCL etc., that assumes OR sentences OR paragraphs with sentences.
@proycon
Copy link
Owner

proycon commented Mar 5, 2019

Yes, it is valid indeed. I agree it would be nicer when it's homogenous but I don't think we can/should enforce that in FoLiA itself, if tools like ucto/frog pose such extra constraints then that's fair enough I'd say.

@kosloot
Copy link
Collaborator Author

kosloot commented Mar 5, 2019 •
edited
Loading

Hmmm. imposing such implicit semantics might hit us hard in the future. But making homogeneity a strict prerequisite is maybe hard to implement. (can a DTD express this at all?)
Maybe it is good to document this as 'good behavior' for FoLiA users. Or have the validator point it out?
I will consider adding warnings (or even fatal errors) to the tools in my control.

@kosloot
Copy link
Collaborator Author

kosloot commented Mar 5, 2019

see also issue #42

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

@proycon proycon

@kosloot kosloot

Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@proycon @kosloot