-
Notifications
You must be signed in to change notification settings - Fork 18
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
Migration scripts for 11.0.0 #613
Comments
@Jamie-SA will review the changes to determine the contents of the migration scripts. |
Assigning to me to compile list of changes to include in migration scripts. |
Summary of changes in gist 11Note: doesn't exclude changes that require no migration, such as modifying annotations and adding or removing a domain or range (even though these affect inferencing). New time modelMost of the model changes probably should be done manually, because it's not a simple renaming. Object properties have to be renamed to datatype properties, but the properties of the TimeInstant object determine which datatype property to use. It could be automated but would take some work. Deleted(I think these get added to ClassesTimeInstant
DateInstant
GreenwichInstant
HumanInstant
LocalInstant
SystemInstant
PropertieshasEnd
hasActual
hasActualEnd
hasPlannedEnd
hasDeathDate
hasStart
hasActualStart
hasPlanned
hasBirthDate
hasPlannedStart
epoch
localDate
localDateTime
localTime
universalDate
universalDateTime
universalTime
isSameTimeAs
wasLastModifiedAt
Modified
AddedatDateTime
birthDate
deathDate
endDateTime
actualEndDateTime
actualEndDate
actualEndMicrosecond
actualEndMinute
actualEndYear
plannedEndDateTime
plannedEndDate
plannedEndMinute
plannedEndYear
startDateTime
actualStartDateTime
actualStartDate
actualStartMicrosecond
actualStartMinute
actualStartYear
plannedStartDateTime
plannedStartDate
plannedStartMinute
plannedStartYear
Notes on datetime migrationExample: from triples :_x gist:hasPlannedEnd :_ti .
:_ti a gist:DateInstant ;
gist:localDateTime "2022-03-16T01:01:01Z-04:00"^^xsd:datetime ;
.
You create: :_x gist:plannedEndDate "2022-03-16T00:00:00Z-04:00"^^xsd:datetime .
Note that hours, minutes, and seconds must be zeroed out for date values. There are a lot of wrinkles. For example, in gist 10, the local datetime may not have an offset, but a value for We have agreed that scripting this will take too much effort, but we will include sample changes covering a variety of conditions with the release.
|
Closing this issue to create two separate issues, one for providing examples of time model changes and one for scripting the remainder (deletions and name changes). |
@Jamie-SA Should this be assigned to you?
The text was updated successfully, but these errors were encountered: