JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-ARCHITECTURE Archives


DC-ARCHITECTURE Archives

DC-ARCHITECTURE Archives


DC-ARCHITECTURE@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-ARCHITECTURE Home

DC-ARCHITECTURE Home

DC-ARCHITECTURE  July 2012

DC-ARCHITECTURE July 2012

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Limiting the use of string in DCAM design patterns

From:

Karen Coyle <[log in to unmask]>

Reply-To:

DCMI Architecture Forum <[log in to unmask]>

Date:

Sat, 14 Jul 2012 07:18:31 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (145 lines)

On 7/13/12 1:52 PM, Corey A Harper wrote:

> So, when Karen asked Dan:
>>>>> On 6/24/12 9:32 AM, Dan Matei wrote:
>>>>> [URI(Beatles)] [URI(hasAppelation)]
>>>>> [<name><nosort>The</nosort>Beatles</name>]
>>> Sorry, my question was pretty vague. I mean:
>>> how is a consuming program to know if this is a literal or an SES?
>
> The answer is, because the AP makes that explicit, and that AP's URI
> comes with explicit, machine readable instructions & reference code
> for decoding and mapping that SES to *something*. That something could
> be specific to an implementation. It could be idiomatic JSON (with or
> without a corresponding class of object in some programming language,
> or RDF-XML, or a SOLR schema, or...

Corey, yes, fine, but HOW? That's the question, in my mind. How does the 
AP make that explicit? It could be by defining an rdfs:datatype for the 
SES. That would formally declare it, and presumably the URI of the 
datatype would (best practice) lead to a definition (human readable 
and/or machine-actionable) of the datatype and to the mapping, e.g.

<rdfs:Datatype rdf:about="http://myexample.com/karensSES/"/>

My main question is whether the SES is something *different* from 
rdfs:datatype, and if so, how is it different? The definition of RDF 
datatype is:

"A datatype consists of a lexical space, a value space and a 
lexical-to-value mapping."

There is more to this definition at
   http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Datatypes

The document excludes certain XML datatypes as well:
http://www.w3.org/TR/2004/REC-rdf-mt-20040210/#dtype_interp

That's a discussion that I'm not sure I am going to be able to 
understand. But it all brings me back to:

Is the DCAM SES different from the rdfs:datatype? If so, how? And if so, 
how do we express this formally?

kc




>
> Sorry for the length of this email. One more coming in reply to the
> Anti-patterns, then will send an agenda for Monday.
>
> -Corey
>
> On Thu, Jul 12, 2012 at 11:21 AM, Richard Urban
> <[log in to unmask]> wrote:
>> Hi all,
>>
>> Looping back around to this…
>>
>>
>> On Jun 26, 2012, at 9:04 AM, Karen Coyle wrote:
>>
>>
>> We'll need to wait for Jon and Gordon to weigh in, but I know that Jon has
>> been at a conference and may be in the midst of lengthy travels. However,
>> they have indeed created a number of SES's that are not "formal" datatypes
>> in the sense you mean, both in RDA in RDF and ISBD in RDF. It's easier to
>> see in the latter because each ISBD area is treated as an SES:
>>
>> http://metadataregistry.org/schemaprop/show/id/2135.html
>>
>> You can see how these appear in the Description Set Profile for ISBD:
>>
>> http://wiki.dublincore.org/index.php/DCAM_Revision_ISBD_DSP
>>
>> While these have been declared as SES's, I don't believe that they are
>> actionable at the moment, in the sense that I don't know of a "mapping rule"
>> for the declared SES's. Nor is it clear to me the relationship of the
>> declared SES and the ISBD RDF properties for that area. So let's hope Jon's
>> travels go well and he arrives refreshed ;-).
>>
>>
>> Here may be where I am confused.   According to the current DCAM
>> documentation,  a "syntax encoding scheme" **IS** an RDF Datatype
>> (http://www.w3.org/2000/01/rdf-schema#Datatype).   And simply declaring that
>> ISBD *IS* an SES (or particular ares are), doesn't necessarily make it so.
>> RDF defers to the XML Schema specifications for defining a preset list of
>> datatypes, but also provides the criteria for extending it to include new
>> datatypes
>> (http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#datatype-components).
>>
>> Again, the one RDF datatype that seems similar is the XMLLiteral, which
>> provides these definitions for XML here:
>> http://www.w3.org/TR/rdf-concepts/#section-XMLLiteral
>>
>> Can we provide a similar definition for ISBD,  assuming the work that ISBD
>> AP group does produce a model of IBSD that would be equivalent to the XML
>> model.  (this needs some more investigation, IMHO).
>>
>> Lexical Space
>> is the set of all strings
>>
>> which are self-contained ISBD content (??)
>> (ISBD does not indicate a character encoding space,  I presume this is
>> deferred to the MARC format for electronic records)
>> for which the embedding between an arbitrary ISBD tag (??) yields a document
>> conforming to the ISBD namespace (???)
>>
>> The value space
>> is a set of entities, called ISBD values, which is:
>> disjoint from the lexical space;
>> disjoint from the value space of any XML schema datatype (Does ISBD have
>> it's own sub-data types, i.e. dates. enumerated list of abbreviations,
>> etc.??)
>> and in 1:1 correspondence with the lexical space
>>
>> The lexical-to-value mapping
>> is a one-to-one mapping from the lexical space onto the value space…
>>
>> This is just a quick paraphrasing of the XML Literal documentation,  I have
>> not thoroughly tested whether this is actually a valid definition of an ISBD
>> Literal datatype.
>>
>> If this is *not* what we want to do to accommodate ISBD here,  it may be
>> necessary to relax the DCAM's specification of what an SES is (i.e. remove
>> the requirement that an SES isA RDF Datatype).
>>
>> Richard
>>
>>
>>
>>
>>
>>
>
>
>

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

Top of Message | Previous Page | Permalink

JISCMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2014
March 2014
February 2014
January 2014
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
September 2005
August 2005
July 2005
June 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
March 2004
February 2004
January 2004
November 2003
October 2003
September 2003
August 2003
June 2003
May 2003
April 2003
March 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
December 2000
November 2000
October 2000


WWW.JISCMAIL.AC.UK

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager