-
Notifications
You must be signed in to change notification settings - Fork 2
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
Rework odd #67
Rework odd #67
Conversation
Do we want a warning on the edge case, e.g. pantomime:
Schematron rule in
to add at least a stage direction. |
…bly not in use; remove unnecessary examples
This is done in tei drama customization, I first uncommented it, not remove it alltogether... not 100% sure why it was there in the first place but it was already switched off in the current working draft:
|
I have still 14 closed value lists. Will relax the restrictions of all of them but indicate which values are supported by the API as tested with the
|
OK, now I am running into troubles: As @lehkost pointed out in issue #46 there is a more recent release of the guidelines than installed in my Oxygen ODD Framework. An since version (see the issue) there has been a change to encoding sex/gender which is not reflected in our current way of encoding + is not reflected in the schema that I am currently producing. Don't know how to best proceed with this issue at the moment |
If there isn't a strong reason that prevents us from doing so I would suggest to base our ODD on the latest TEI version which at the moment is 4.8.1 (https://github.com/TEIC/TEI/releases). @ingoboerner Can you update your Oxygen framework to that version? |
Create a TEI customization (based on TEI Drama ODD) that implements the necessary restrictions for the DraCor API to work.
The derived schema can be used to validate TEI files to be included in DraCor corpora. It allows for greater flexibility in the application of the TEI Guidelines than the original "legacy" ODD derived schema.
The conformance to the API will be tested with Schematron rules that are embedded into the RelaxNG schema.
The ODD also includes definitions for the so-called "features" that were identified in the CLS INFRA Deliverable "On Programmable Corpora" (https://zenodo.org/records/7664964). It includes the explanations of the features developed for the API Ontology (https://github.com/ingoboerner/dracor-ontology/blob/main/v1/dracor_api_ontology.ttl) The identifiers of the features (xml:id s) should allow a automatic linking to the Schemas in the OpenAPI spec (originally, including the links to the ontology, e.g. https://github.com/dracor-org/dracor-api/blob/extend_openapi/api.yaml#L1637-L1639)
At some point it should be possible to gather all
<constraintSpec>
elements (currently linked with@corresp
to theThe examples from the legacy ODD have been moved to a separate ODD file; eventually it would make sense to re-include them; an open question remains how to proceed in regards to the "Encoding Guidelines" included as a draft in the legacy ODD.
For the initial discussion see also issue #66.