Changes between Version 1 and Version 2 of PersistentValidationResults
- Timestamp:
- 09/03/09 04:49:42 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PersistentValidationResults
v1 v2 35 35 == Proposal == 36 36 37 38 37 Validation status is either "valid", "not valid", or "not determined". This last status is the initial validation status when validation has not yet run. Currently the statuses "valid" and "not valid" are shown in the search results. Showing "not determined" as well is a minor change.[[BR]][[BR]] 39 38 A validation report is also stored in the DB. It contains any XSD or schematron validation messages, a reference to the schematron file that was used, a timestamp, and if applicable a message saying that the metadata profile could not be determined. There is basic support for multiple metadata profiles, using different Schematron rules for different profiles.[[BR]][[BR]] 39 40 TODO answer Simon Pigot's remark: "profile support is basic? what does it mean? should be there already; in trunk that is"[[BR]][[BR]] 41 TODO maybe expand the proposal to allow for Validation Result States in a context; as discussed with François:[[BR]] 42 francois: for persistent validation results, you only store valid / not valid /not determined status ? we could not have multiple validation level support like ISO ( not )valid / INSPIRE ( not )valid status / ... for example ?[[BR]] 43 heikki_: no, a "validation report" as a whole is stored, that combines results from xsd and schemtron validation. To store ISO/INSPIRE/etc. differences in statuses, this would need adapting[[BR]] 44 francois: so changes we made for geocat.ch on multiple validation level could be ok with that.[[BR]] 45 heikki_: I don't know what those changes are[[BR]] 46 francois: let's first vote for your proposal and see later if we could add multiple validation level.[[BR]] 47 heikki_: ok, if you like to have more, separate statuses, that should be easy to do[[BR]][[BR]] 48 49 40 50 An icon indicating the validation status, that links to the validation report if the metadata is not valid, can be included in the search results page an/or in the show metadata page. This indicates something about the quality of the metadata to users, and may encourage metadata providers to produce more valid metadata.[[BR]][[BR]] 41 51 [[Image(ngr.validationresults.searchresults.png)]] 42 52 [[BR]][[BR]] 53 43 54 44 55 === Backwards Compatibility Issues ===