documentation and parsing for seals

[EleanorRobson]

I'm working with Raquel on Pyoracc and we need clarification & documentation on the @seal element — is it independent of the hierarchy of @obverse etc., or is it a child of @obverse & similar?

Relatedly, I'm unclear about the structure of @labels for seals in @translation and the doco isn't very helpful.

In the translit I have:

@seal 1

1. {[na₄]}KIŠIB

   lem: kunuk[seal]N

2. [{m}]mu#-ra-nu

   lem: Muranu[1]PN +.

And in the (labelled) translation:

@seal 1 @label 1 - 2 Seal of Muranu

Pyoracc flags this as an error but the Oracc parser doesn't. Both Pyoracc and the Oracc parser are happy with:

@label seal 1 1 - seal 1 2 Seal of Muranu.

Which seems correct to me. Is the parser wrongly allowing the first, or should Pyoracc also accept it?

[stinney]

I will fix the docs, but for now Jamie's response is correct: seal is a surface level element so is a sibling of obverse etc. Labels in seals do need the surface component as well.

Catching missing surface components in labels is tricky, but I think it belongs on the bug list because, yes, this is potentially confusing.

All the best,

Steve

-------- Original Message --------

From: "Eleanor Robson" notifications@github.com Sent: Thursday, October 20, 2016 5:06 AM To: "oracc/oraccdoc" oraccdoc@noreply.github.com Subject: [oracc/oraccdoc] documentation and parsing for seals (#4)

I'm working with Raquel on Pyoracc and we need clarification & documentation on the @seal element — is it independent of the hierarchy of @obverse etc., or is it a child of @obverse & similar?

Relatedly, I'm unclear about the structure of @labels for seals in @translation and the doco isn't very helpful.

In the translit I have:

@seal 1

1. {[na₄]}KIŠIB

   lem: kunuk[seal]N

2. [{m}]mu#-ra-nu

   lem: Muranu[1]PN +.

And in the (labelled) translation:

@seal 1 @label 1 - 2 Seal of Muranu

Pyoracc flags this as an error but the Oracc parser doesn't. Both Pyoracc and the Oracc parser are happy with:

@label seal 1 1 - seal 1 2 Seal of Muranu.

Which seems correct to me. Is the parser wrongly allowing the first, or should Pyoracc also accept it?

You are receiving this because you were assigned. Reply to this email directly or view it on GitHub: https://github.com/oracc/oraccdoc/issues/4

[EleanorRobson]

Further to this issue, Jake emails regarding the doco at http://oracc.museum.upenn.edu/doc/help/editinginatf/primer/structuretutorial/#h_sealings:

" We have been trying to follow the Oracc structure tutorial documentation, indicating the presence of a seal impression with $ seal and then putting @seal before transliterating the seal. But we are getting a syntax error in the $ seal line. I can just delete that line and everything checks out okay, but I don’t think I want to do that, do I?"

I've told him yes, he does, on the basis that the checker is de facto the authority. But the doco at this point needs correcting, and the section at http://oracc.museum.upenn.edu/doc/help/editinginatf/primer/structuretutorial/#h_seal should be deleted.

[stinney]

It would be helpful to see the input/error and to know if this is parsing with the server or with Nammu?

The following is OK, per the documentation:

[stinney@oracc ~]$ cat seal.atf &P343434 = Some Sealed Tablet

project: cdli

1. a $ seal 1

$ seal 2

@seal 1

1. du-du

@seal 2

1. da-da [stinney@oracc ~]$ ox -cvm seal.atf [stinney@oracc ~]$

[EleanorRobson]

On further investigation It turns out that J is confusing Nammu's syntax-checking with Oracc validation. PyOracc doesn't recognise "seal" as a valid component of an $-line. I'll report to Raquel.