NIHVIVO-1629 Upgrade jQuery to version 1.5. NIHVIVO-2153 Change datetime fieldnames to use hyphen rather than period, since the latter generates errors in jQuery 1.5 and is not a valid CSS selector.
This commit is contained in:
parent
8e554c3975
commit
dae5369232
8 changed files with 146 additions and 284 deletions
|
@ -51,8 +51,8 @@
|
|||
<v:jsonset var="n3ForValue">
|
||||
?subject <${toDateTimeValue}> ?valueNode .
|
||||
?valueNode <${type}> <${valueType}> .
|
||||
?valueNode <${dateTimeValue}> ?dateTimeField.value .
|
||||
?valueNode <${dateTimePrecision}> ?dateTimeField.precision .
|
||||
?valueNode <${dateTimeValue}> ?dateTimeField-value .
|
||||
?valueNode <${dateTimePrecision}> ?dateTimeField-precision .
|
||||
</v:jsonset>
|
||||
|
||||
<%-- Queries for editing an existing role --%>
|
||||
|
@ -120,11 +120,11 @@
|
|||
"sparqlForLiterals" : { },
|
||||
"sparqlForUris" : { },
|
||||
"sparqlForExistingLiterals" : {
|
||||
"dateTimeField.value" : "${existingDateTimeValueQuery}",
|
||||
"dateTimeField-value" : "${existingDateTimeValueQuery}",
|
||||
},
|
||||
"sparqlForExistingUris" : {
|
||||
"valueNode" : "${existingNodeQuery}",
|
||||
"dateTimeField.precision": "${existingPrecisionQuery}"
|
||||
"dateTimeField-precision": "${existingPrecisionQuery}"
|
||||
},
|
||||
"fields" : {
|
||||
"dateTimeField" : {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue