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.

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

Label and description when there are multiple direct properties #6

Open
dlschwartz opened this issue Sep 21, 2022 · 4 comments
Open

Comments

@dlschwartz
Copy link
Collaborator

@wsalesky we didn't discuss the implication for label and description of there being multiple direct properties in a factoid.

  • Events usually have multiple direct properties (each date attribute, each tei:persName, each tei:placeName, each keyword value on a @ref attribute.
  • Relationships with tei:relation/@mutual will have at least two direct properties
  • Relationships where tei:relation/@Active or tei:relation/@Passive have more than one value there will be multiple direct properties
  • Relationships embedded in event factoids will have multiple as well.

In all of these instances, we will need to decide where to attach rdfs:label and rdfs:desc. It seems a shame to duplicate all of this on every statement instance. I'll discuss this with Steve and follow up here in this issue.

@dlschwartz
Copy link
Collaborator Author

I heard back from Steve. As I suspected, he said that rdfs:label typically appears on properties and entities, but not on statement instances. So we need to drop those.

Issues to think through:

  • We don't assign rdfs:label to person, place, or keyword URIs from SPEAR because those will come from the serialization of the person, place, and keyword data when we get to that.
  • For events, we need to assign something to the subject item we generate out of the TEI that functions as a URI for the event. For an event like "The French Revolution" that would probably be an rdfs:label. The way we use tei:event/tei:desc (which is the only thing we have to work with) the appropriate vocabulary would be schema:description.
  • Steve says that we can attach labels and/or descriptions to the factoid URI. However, that isn't really done in wikidata. I suppose the question is why would we be doing this. Unless I'm mistake, we have internal reasons for wanting simple prose rendering of the factoid (i.e. with xml stripped) and the whole tei:desc (including xml tags). It might not be such a big deal that no one familiar with wikidata would think to look for this. All entities and properties will be labeled and that's what wikidata users would be looking for anyway. We would find this useful and it wouldn't be anything other than superfluous to a wikidata user.

Proposal:

  • Reserve rdfs:label for entities and properties (to be generated out of persons, places, keywords).
  • Attach the simple string to the subject/object URI for event factoids.
  • Attach the simple string to the factoid URI using schema:description.
  • Attach the xml (tei:desc) to the factoid URI using rdf:XMLLiteral (which seems a good fit?).

@dlschwartz
Copy link
Collaborator Author

Here are some examples:

Attach simple string to an event entity

  • swd:event8559-387 schema:description "In 498/9 A. Gr. 810 the hotspring of Abarne stopped for three days."@en ;
  • event entity derived from ab[@subtype="event"]/idno
  • string takes //ab[@subtype="event"]//event/desc and strips out the xml

Attach simple string to factoid URI (this will apply to all factoid types)

Attach xml to the factoid URI (the paths will be the same as above)

<desc xmlns="http://www.tei-c.org/ns/1.0">
                            <persName ref="http://syriaca.org/person/2591">Alypius</persName> 
                            and 
                            <persName ref="http://syriaca.org/person/3775">Anonymous 3775</persName>
                            were married.
                        </desc>
```" ;

@wsalesky
Copy link
Collaborator

wsalesky commented Oct 3, 2022

How does this look?

@prefix swds: <http://spear-prosop/entity/statement/>.
@prefix swdt: <http://syriaca.org/prop/direct/>.
@prefix sp: <http://syriaca.org/prop/>.
@prefix sps: <http://syriaca.org/prop/statement/>.
@prefix spr: <http://syriaca.org/prop/reference/>.
@prefix spq: <http://syriaca.org/prop/qualifier/>.
@prefix swdref: <http://spear-prosop/reference/>.
@prefix schema: <http://schema.org/>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix prov: <http://www.w3.org/ns/prov#>. 

<https://spear-prosop.org/8559-387> schema:description "In 498/9 A. Gr. 810 the hotspring of Abarne stopped for three days."@en ;
<https://spear-prosop.org/8559-387> rdf:XMLLiteral  "<desc xmlns="http://www.tei-c.org/ns/1.0"> In <choice>
                                <reg>
                           <date notBefore="0498-10" notAfter="0499-09" calendar="Gregorian">498/9</date>
                        </reg>
                                <orig>
                           <date when-custom="0810" datingMethod="Seleucid">A. Gr.
                                        810</date>
                        </orig>
                        </choice> 
                     <placeName ref="http://syriaca.org/place/2785">the hotspring of Abarne</placeName>  stopped for
                            three days. </desc>" ;
swd:event:8559-387 schema:description "In 498/9 A. Gr. 810 the hotspring of Abarne stopped for three days."@en ;
swdref:8559-387 spr:part-of-series <http://syriaca.org/spear> ;
swdref:8559-387 spr:part-of-series <https://spear-prosop.org/8559-387> ;
swds:8559-387 spr:wasDerivedFrom <https://spear-prosop.org/8559-387> ;
swdref:8559-387 spr:creator <http://syriaca.org/documentation/editors.xml#dschwartz> ;
swdref:8559-387 spr:reference-bibl <http://syriaca.org/bibl/633> ;
swdref:8559-387 spr:reference-bibl <urn:cts:syriacLit:nhsl8559.syriacCorpus57:76> ;
swdref:8559-387 spr:reference-bibl <http://syriaca.org/bibl/657> ;
swds:8559-387 spq:certainty <incerta> ;
swds:8559-387 schema:description "In 498/9 A. Gr. 810 the hotspring of Abarne stopped for three days."@en ;
swd:event8559-387 swdt:event-place swd:place/2785 ;
swd:event8559-387 sp:event-place swds:8559-387 ;
swds:8559-387 sps:event-place swd:place/2785 ;
swd:event8559-387 swdt:event-keyword swd:keyword/natural-disasters ;
swd:event8559-387 sp:event-keyword swds:8559-387 ;
swds:8559-387 sps:event-keyword swd:keyword/natural-disasters ;
swds:8559-387 spq:not-before "0498-10"^^xsd:gYearMonth ;
swds:8559-387 spq:not-after "0499-09"^^xsd:gYearMonth ;```

@dlschwartz
Copy link
Collaborator Author

@wsalesky this gets everything we want, which is great. We do pick up an unneeded duplicate of this line:
swds:8559-387 schema:description "In 498/9 A. Gr. 810 the hotspring of Abarne stopped for three days."@en ;

That isn't necessarily a problem, but it isn't necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants