-
Notifications
You must be signed in to change notification settings - Fork 0
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
Statement instances #14
Comments
Also, since property qualifiers attach to statement instances these will need to be duplicated on each statement instance. Property qualifiers are the spq on this sheet. |
Can you give me an example triple? |
@wsalesky this example should cover the different aspects of this issue. I'm not sure about the "?" in the statement instance. Feel free to choose whatever you think will work as a separator between the number portion of the URI and the randomly generated string. For events, each person, place, and keyword will be a direct property with a statement instance/qualifiers like this. For relationships, each direct property will require the same. swd:event8559-387 swdt:event-place swd:place/2785 ; swd:event8559-387 swdt:event-keyword swd:keyword/natural-disasters ; |
@dlschwartz So the date would get repeated for each person, place, keyword? |
@wsalesky no, your right, they shouldn't! Sorry. The dates should be direct properties of the event. If relationships are dated they would need to be serialized as qualifiers. Event: swd:event8559-387 swdt:event-keyword swd:keyword/natural-disasters ; swd:event8559-387 swdt:not-before "0498-10" ; swd:event8559-387 swdt:not-after "0499-09" ; Relationship: |
How does this look?
|
@wsalesky I don't think we need the "keyword/natural-disasters" as part of the statement instance. Also, the event dates need to be direct properties. swd:event8559-387 swdt:event-place swd:place/2785 ; swd:event8559-387 swdt:event-keyword swd:keyword/natural-disasters ; swd:event8559-387 swdt:not-before "0498-10"^^xsd:gYearMonth ; swd:event8559-387 swdt:not-after "0499-09"^^xsd:gYearMonth ; |
How does this look:
|
@wsalesky the statement instances look good! But I'm afraid we've still need to change the event dates from property qualifiers to direct properties. We need:
|
@wsalesky each direct property will require its own statement instance. These need to be unique within the triple store but don't need to be persistent (in the case that we need to edit the TEI and re-run the serialization).
A good way to keep it unique and to keep all direct properties associated with their factoid of origin will be to use the factoid URI as the basis of the statement instance. Something like this should work.
https://spear-prosop.org/801-2 + [a distinctive character?] + a randomly generated alphanumeric string of appropriate length:
https://spear-prosop.org/801-2?a4cp
The distinctive character should be something that won't appear elsewhere that would allow us to isolate substring-before to get the factoid URI.
The text was updated successfully, but these errors were encountered: