In the list below, the starred, left-anchored requirements are the ones
that were voted as "core" at least by 5 people. I bolded these
requirements on the wiki page [1] for now.
I admit that I'm not sure what this means - need to think about it some
more - but it is interesting that only one "general" requirement and no
class requirements were considered core. Instead, people felt strongly
about property and value requirements.
-------
1 Meta-Requirements
*1.1 R-208 A place for human-readable documentation for properties
*1.2 R-214 Application Profile administrative information
1.3 R-34 Available Class Definition
1.4 R-224 Use sub-super relations in validation
*1.5 R-117 Define context of constraints
*1.6 R-129 Machine Understandable Syntaxes
1.7 R-220 Define used vocabulary
1.8 R-115 Closed World Assumption (CWA)
*1.9 R-205 Varying levels of "error"
1.10 R-206 Limit number of namespaces in a profile
*1.11 R-207 Support multiple levels of description
2 General requirements
2.1 Validate for uniqueness of IRIs
2.2 R-10 Define Disjoint Properties
2.3 R-171 Validate IRIs by Dereferencing
2.4 R-171bis Validate resource (media) type returned from dereferencing
2.5 R-98 Check Validity Of IRIs
*2.6 R-211 Cardinality constraints
3 Class requirements
3.1 R-209 Define valid classes
3.2 R-7 Disjoint Classes
3.3 R-225 Validation of associated classes in one Description Set
4 Property requirements
*4.1 R-210 Define valid properties
4.2 R-67 Boolean property patterns
*4.3 R-68 Required Properties
4.4 R-69 Optional Properties
*4.5 R-70 Repeatable Properties
*4.6 R-71 Conditional Properties
4.7 R-72 Recommended Properties
*4.8 R-25 Property Domain
5 Value Requirements
*5.1 R-35 Property Range
*5.2 R-43 Literal Value Comparison
*5.3 R-44 Pattern Matching on RDF Literals
5.4 R-47 Specify and validate language tags
*5.5 R-49 Property occurs once per language tag
*5.6 R-30 Define value lists
--
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600
|