Dan Matei gave us the beginning of a set of SES use cases, which, when
combined with what we have in ISBD and Jon's date example, may help us
get a better picture of the scope of SES. My interpretation of what we
have so far is:
*Structured literal:
-- date/time
[URI(someResource)] [URI(hasPublicationDate)]
[sesURI:http://www.w3.org/2001/XMLSchema#date "2013"]
[URI(someResource)] [URI(hasDate)] [sesURI:http://ex.com/123 "03/08/13"]
-- MARC fixed fields
[URI(someResource)] [URI(has008Field)] [sesURI:http://ex.com/xyz
"810908s1982\\\\nyua\\\\\\\\\\000\1\eng\\"]
*Text with markup and (presumably) a schema or "set of mapping rules"
[URI(Beatles)] [URI(hasAppelation)] [sesURI:http://ex.com/abc.xls
"<name><nosort>The</nosort>Beatles</name>"]
[URI(Dostoyevsky)] [URI(hasAppelation)] [sesURI:http://ex.com/cde.xls
"<firstName>Fyodor</firstName><patronimic>Mikhaylovich</patronimic><surname>Dostoyevsky</surname>"]
[URI(someResource)] [URI(isbd:hasPublicationStatement)]
[sesURI:http://ex.com/isbdArea4.php "Helsinki : Buena Vista, [2002]"]
[URI(human, feminine] [URI(designatedBy)] [sesURI:http://ex.com/bcd
"<form number="singular">woman</form><form number="plural">women</form>"]
--
There may not be a difference in practice between structured literals
and marked-up literals, but for some reason I find the categorization
helpful. As Jon said on one conference call, the sesURI might point to
code or, for example, to a regular expression that "maps" the string to
a data description. At least, that is how I am interpreting "mapping
rules" in the DCAM sense. It would be nice to know what to expect when
one de-references the sesURI.
I have made all of this up, so if it's wrong perhaps someone can correct
it and we can begin a section of use cases on the wiki, or add these to
the pages of examples.
kc
--
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet
|