Hi all,
here are further merge candidates for our requirements based on Karen's list.
Thank you Karen for the analysis and thank you Antoine for pointing me to this.
Literal value list or URI value list
-------------------------------------
R-30-ALLOWED-VALUES-FOR-RDF-OBJECTS
R-37-ALLOWED-VALUES-FOR-RDF-LITERALS
--> recommendation: VALUE-LISTS [Thomas, ]
Validate against more than one namespace or profile
--------------------------------------------------------------
R-117-CONTEXT-SENSITIVE-CONSTRAINTS
constraints that apply to everything in a specified context (with context I meant all kind of contexts as for example classes, APs, ...) [Thomas]
R-118-NAMESPACE-SENSITIVE-CONSTRAINTS
constraints that apply to everything in a specified namespace (e.g. foaf)
Allow various levels of error reporting
--------------------------------------------
R-205-VARYING-LEVELS-OF-ERROR
R-135-CONSTRAINT-LEVELS
R-158-SEVERITY-LEVELS-OF-CONSTRAINT-VIOLATIONS
R-193-MULTIPLE-CONSTRAINT-VALIDATION-EXECUTION-LEVELS
--> recommendation: VALIDATION-LEVELS [Thomas]
-----
R-33-NEGATIVE-OBJECT-CONSTRAINTS
R-200-NEGATIVE-LITERAL-CONSTRAINTS
--> recommendation: NEGATIVE-VALUE-CONSTRAINTS [Thomas]
-----
R-29-CLASS-SPECIFIC-RANGE-OF-RDF-OBJECTS
R-36-CLASS-SPECIFIC-RANGE-OF-RDF-LITERALS
--> recommendation: CONTEXT-SPECIFIC-VALUE-RANGE [Thomas]
-----
R-38-DEFAULT-VALUES-OF-RDF-LITERALS
R-31-DEFAULT-VALUES-OF-RDF-OBJECTS
--> recommendation: DEFAULT-VALUES [Thomas]
-----
R-32-MEMBERSHIP-OF-RDF-OBJECTS-IN-CONTROLLED-VOCABULARIES
R-39-MEMBERSHIP-OF-RDF-LITERALS-IN-CONTROLLED-VOCABULARIES
--> recommendation: MEMBERSHIP-OF-VALUES-IN-CONTROLLED-VOCABULARIES [Thomas]
--> recommendation: MEMBERSHIP-IN-CONTROLLED-VOCABULARIES [Thomas]
pattern matching
--------------------
R-44-PATTERN-MATCHING-ON-RDF-LITERALS
R-141-NEGATIVE-PATTERN-MATCHING-ON-RDF-LITERALS
R-21-IRI-PATTERN-MATCHING-ON-RDF-SUBJECTS
R-22-IRI-PATTERN-MATCHING-ON-RDF-OBJECTS
R-23-IRI-PATTERN-MATCHING-ON-RDF-PROPERTIES
-1 for matching these requirements. I see them as different constraints [Thomas]
You may also have further merge candidates...
Best,
Thomas
--
Thomas Bosch, M.Sc. (TUM)
PhD Student
GESIS - Leibniz Institute for the Social Sciences
Social Science Metadata Standards
Visitors Address: B2,1, D-68159 Mannheim
Postal Address: P.O.Box 12 21 55, D-68072 Mannheim
Tel: + 49 (0) 621 / 1246-271
Fax: + 49 (0) 621 / 1246-100
Web: http://www.gesis.org
Website: http://boschthomas.blogspot.com/
GitHub: https://github.com/boschthomas/PhD
________________________________________
Von: Antoine Isaac [[log in to unmask]]
Gesendet: Donnerstag, 6. November 2014 18:25
An: Bosch, Thomas
Cc: Karen Coyle
Betreff: Merging DC AP requirements
Hi Thomas,
This is a quick question about your volunteering to prepare a list of requirements to merge, as we discussed it with Karen this week.
Are you still able to work on it?
We would like to present the candidate merges to the group for the call next Tuesday, to get decision on them. This would imply circulating them a bit in advance! At least Monday would be good. Is it doable? Would you need some help?
Note that Karen has created a pad with the requirement analysis that she had posted two weeks ago:
https://etherpad.wikimedia.org/p/requirements_analysis
This could be a useful list to get inspiration, since some of these clusters actually have requirements that may be merged.
Or you can use it to put down some notes of your own, next to Karen's list!
Cheers,
Antoine
|