FragmentSelectors: multiple dcterms:conformsTo ?

I (think that I ) have a use case best described as conforming to two
orthogonal specs. The Feb 8 core is silent  on multiple conformsTo.
Since there is(?) no machine semantics for conformsTo, multiples seem
harmless.  But possibly the OA spec should be more explicit  because
the explanatory text  in Sec 3.2.1 speaks of "the" standard:
"Clients MUST process the value of the FragmentSelector based on the
standard that it conforms to".

If multiples are permitted, then in case the conformance specs
conflict,  it may be necessary to allow the oa:List or rdf:List o
provide the order of application of the processing guided by the
conformance specs and remind the reader of its necessity.

Bob


-- 
Robert A. Morris

Emeritus Professor  of Computer Science
UMASS-Boston
100 Morrissey Blvd
Boston, MA 02125-3390

IT Staff
Filtered Push Project
Harvard University Herbaria
Harvard University

email: morris.bob@gmail.com
web: http://efg.cs.umb.edu/
web: http://wiki.filteredpush.org
http://www.cs.umb.edu/~ram
===
The content of this communication is made entirely on my
own behalf and in no way should be deemed to express
official positions of The University of Massachusetts at Boston or
Harvard University.

Received on Wednesday, 6 March 2013 17:39:50 UTC