All,
Stefanie, Valentine, Evelyn and I met twice at SWIB to go over the DC
requirements, starting at R-1. With about 1.5 hours of work, we were
able to cover only about one dozen of the requirements, about 25%. I'll
paste our results below, some of which are questins and therefore need
either more work or decisions.
I suppose that one of the main things that we learned from this is that
much more work of this type is needed, and that the work needs to be
group work. That doesn't mean that we all need to meet for it to get
done, but some small group meetings will necessarily be required for us
to come up with a coherent set of requirements.
Our discussion has been added to the Etherpad [1], and I am pasting the
same text here below. We can discuss these at the next meeting, but we
also need to determine how to complete this task. I propose setting up a
series of small gatherings (via WebEx) to finish this first pass of the
requirements. If people are interested, we could try doing a few as a
group next week so that everyone on the call can get an idea of what the
task is like.
[1] https://etherpad.wikimedia.org/p/requirements_analysis
--------------
R1
Was: uniqueness of URIS
Now: Validate for uniqueness of URIs
100 Subsumption
Not needed because there is nothing to check - simply a function of RDF
117 Context
This becomes the question of what defines the context (check point
start) in an application profile? For SPIN, check point must be an
rdf:type. ShEx, on the other hand, defines a graph, not necessarily
based on rdf:type. DSP defines a description based on properties. (True?
Check) All constraints must be within a context, even if that context is
universal.
118 Check based on namespace
This turns out to be something different. It seems instead to be the
ability to select an appropriate AP based on some information in the
data, such as the provider, the genre, etc. This may not be an AP
requirement but a workflow requirement.
121 (change name)
compare and check numerical values across multiple properties
e.g. check that birth date is less than death date; that start is less
than end; that discounted price is less than full price.
[note to self: make sure we have a requirement for: if X, then Y is
mandatory]
R-129
We interpreted as: AP serialization must support visualization of the
data model
141 -negative datatype pattern
combine with others (from #4 above) to create a single requirement that
covers checking of any values that are datatypes with patterns (e.g.
anything that can be checked with a regex)
171
Clarify that this applies to values that are IRIs - and that those
values return a resource (anything other than an http error code)
171bis (to be added)
For values that are IRIs, be able to specify the type of resource that
must be returned (e.g. mime type, XML type)
UC-Editor 2
Seems to link to the wrong requirement. Declaration of prefixes for use
of qnames?
206
rename: limit number of namespaces in a profile
? - This seems to be outside of the profile itself, and doesn't relate
to validation
207
This describes desired AP functionality. It differs from the current DSP
because the DSP does not allow sub-descriptions. (It's not clear if
subdescriptions are needed - none are listed in the use case.)
--
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600
|