first draft for a TEI with RDFa exemplar #2431
Conversation
|
Council discussion at VF2F 16 March 2024: |
HelenaSabel
force-pushed
the
issue-1860
branch
from
151136c to
d9b67fe
Compare
|
@HelenaSabel and I have revised and updated the exemplar document P5/Exemplars/tei_rdfa.odd. To facilitate the review process, we have added the schema generated from this exemplar (P5/Exemplars/tei_rdfa.rng) so that it can be easily associated to any other files for testing. We also added a TEI example (P5/Exemplars/tei_rdfa.tei). Next steps:
@chiarcos, could you please have a look at it and make comments? |
| <moduleRef key="iso-fs"/> | ||
| <moduleRef key="nets"/> | ||
| <moduleRef key="certainty"/> | ||
| <moduleRef key="tagdocs" except="elementSpec moduleRef schemaSpec" /> |
There was a problem hiding this comment.
My instinct is that this should be
<moduleRef key="tagdocs" include="att code eg egXML gi ident tag val"/>
| <attDef mode="add" ident="about"> | ||
| <gloss xml:lang="en" versionDate="2020-07-01">rdfa-about</gloss> | ||
| <desc xml:lang="en" versionDate="2020-07-01">a SafeCURIEorCURIEorIRI, used for stating | ||
| what the data is about (a 'subject' in RDF terminology)</desc> |
There was a problem hiding this comment.
Should “'subject'” be <term>subject</term>?
| <desc xml:lang="en" versionDate="2020-07-01">a SafeCURIEorCURIEorIRI, used for stating | ||
| what the data is about (a 'subject' in RDF terminology)</desc> | ||
| <datatype> | ||
| <dataRef key="teidata.enumerated"/> |
There was a problem hiding this comment.
Huh?
We expect an enumerated list of possible values?
| </classes> | ||
| </classSpec> | ||
|
|
||
| <elementSpec ident="citeData" mode="change"> |
There was a problem hiding this comment.
Deleting @property from <citeData> isn't a viable solution going forward. The attribute on citeData is (almost) precisely the same thing, except that it doesn't play a role in defining a proper triple (it specifies how to use the document to construct triples). Do these attributes have to be absolutely global? Can we simply override the definition in this case, as we do in various places with @type, for example. I feel like some thinking about the scope of RDFa in TEI might be worthwhile.
| <dataRef key="teidata.enumerated"/> | ||
| </datatype> | ||
| </attDef> | ||
| <attDef mode="add" ident="href"> |
There was a problem hiding this comment.
@href and @src below are the HTML attributes on <a> and <img>, for example. We shouldn't add them. The RDFa spec is explaining how these built in HTML attributes interact with RDF—namely they can act in the same way as @resource. The corresponding TEI attributes are @target and @url, though there are many, many more attributes in TEI that could potentially interact with RDFa. See https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-teidata.pointer.html for a rather dizzying list.
| <dataRef key="teidata.enumerated"/> | ||
| </datatype> | ||
| </attDef> | ||
| <attDef mode="add" ident="src"> |
There was a problem hiding this comment.
See comment on @href above. We shouldn't add this.
| <dataRef key="teidata.nullOrName"/> | ||
| </datatype> | ||
| </attDef> | ||
| <attDef mode="add" ident="prefix"> |
There was a problem hiding this comment.
@prefix probably isn't needed in a TEI context since we can use @xmlns to declare prefixes. Non-XHTML HTML can't, hence the need for the attribute.
| <profileDesc> | ||
| <particDesc> | ||
| <listPerson> | ||
| <person xml:id="disco_004e" about="disco:004e" typeof="foaf:Person"> |
There was a problem hiding this comment.
I could make an argument that the @about attribute is redundant here....maybe something to think about.
See discussion in #1860