So as not to take up time on the call tomorrow, and also to reach a
wider group, here is my update on the W3C work:
W3C has also been on hiatus during the holidays, but the meetings resume
on Thursday. They meet weekly. There will also be a face-to-face meeting
mid-February in Boston. (I will be there.)
My guess as to what will transpire over the next months (and it is a
guess) is that W3C will develop a fairly technical, detailed spec for
validation. Because it will be technical and detailed, this is going to
take some time. They will probably not address a user interface for the
validation, although there are some members of the group for whom this
is a priority. I suspect that will be offered outside of the W3C process
by some.
I think that we can assume that the details of the rules for validation
will be covered by W3C. I also think that we can assume that the spec
will be more detailed than what our community generally needs. This
means that there could be room for the development of a user view to a
core of requirements. In my opinion, a lot could be accomplished with
just a few requirements:
- simple cardinality (mandatory/optional, repeatable/not-)
- value checking (allowed values, valid data-types)
- property/class grouping (e.g. propertyX is used for classY)
The DSP covers this and more. We might want to consider a "DSP-core"
that hides some of the "more". I think it's worth looking at the
BIBFRAME profiles [1].
Something the DSP doesn't do but that will be prominent in the W3C work
is tying validation to rdf:type declarations. DSP has resourceClass but
not as a focus for validation. I think we should look at that.
kc
[1] http://www.loc.gov/bibframe/docs/bibframe-profiles.html
--
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600
|