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  February 2012

DC-ARCHITECTURE February 2012

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

DCAM: Alistair on SoDC Constraint Language (2007)

From:

Thomas Baker <[log in to unmask]>

Reply-To:

DCMI Architecture Forum <[log in to unmask]>

Date:

Tue, 21 Feb 2012 21:09:23 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (156 lines)

And finally...

----------------------------------------------------------------------
http://aliman.googlecode.com/svn/trunk/sodc/SoDC-0.2/constraints/index.html

    SoDC-CL -- A Language for Expressing Syntax Constraints on Graph-based (Meta)data

        1. Introduction @@TODO
            SoDC-CL is a language for expressing application-specific syntax
            constraints over graph-based (meta)data.

            The two basic components of a SoDC-CL document are "graph profiles"
            and "resource description profiles" -- "resource profiles" for
            short.

        2. Resource Profiles
            A resource profile is a set of constraints on the properties of a
            resource described in some graph. The following constraints can be
            expressed in a resource profile...

            (property cardinality constraints)
                exact cardinality -- the resource must have exactly n values for a given property
                minimum cardinality -- the resource must have at least n values for a given property
                maximum cardinality -- the resource must have at most n values for a given property

            (property value constraints)
                URI value -- the resource must have only URI values for a given property
                blank node value -- the resource must have only blank node values for a given property
                plain literal value (language optional) -- the resource must
                   have only plain literal values for a given property
                plain literal value (language required) -- the resource must
                   have only plain literal values with language tags for a given property
                TODO plain literal value (language optional, fixed) -- the
                   resource must have only plain literal values for a given
                   property, and where the plain literal has a language tag, it
                   must take a given value
                TODO plain literal value (language required, fixed) -- the
                   resource must have only plain literal values with a given
                   language tag for a given property
                TODO typed literal value -- the resource must have only typed
                   literal values for a given property
                TODO typed literal value (datatype fixed) -- the resource must
                   have only typed literal values with a given datatype for a
                   given property TODO XML literal value -- the resource must have
                   only XML literal values for a given property

            (given property value constraints)
                TODO given URI value -- the resource must have a given URI
                   value for a given property
                TODO given plain literal value -- the resource must have a
                   given plain literal value for a given property
                TODO given typed literal value -- the resource must have a
                   given typed literal value for a given property

            (referential integrity constraints)
                TODO URI value reference -- the URI value of a given property
                   must also be the subject of another description within the same
                   graph
                TODO blank node reference -- the blank node value of a given
                   property must also be the subject of another description within
                   the same graph 
                TODO reference with profile -- the URI or blank
                   node value of a given property must also be the subject of
                   another description within the same graph, and the given
                   profile must be specified in that description

        3. Graph Profiles
            A graph profile is a set of constraints on a graph. The following constraints 
            can be expressed...

                TODO the graph must describe exactly n resources
                TODO the graph must describe at least n resources
                TODO the graph must describe at most n resources
                TODO the graph must describe exactly n resources with resource profile p
                TODO the graph must describe at least n resources with resource profile p
                TODO the graph must describe at most n resources with resource profile p
                TODO all resources in the graph must have a resource profile
                TODO all resources in the graph must have resource profile p

            Those marked "TODO" have not yet been implemented in SoDC-CL.

        4. SoDC-CL Language & Examples
            For convenience of implementation, the SoDC Constraints Language is
            defined as an XML language. The W3C XML Schema defining the
            language is at the link below...

                sodc-cl.xsd -- SoDC-CL Schema

            For example, the SoDC-CL document below defines two resource
            profiles. The first constrains a resource to have exactly one plain
            literal value for the dc:title property, and at least one URI value
            for the dc:creator property. The second constrains a resource to
            have at least one plain literal value for the foaf:name property...

            <?xml version="1.0" encoding="UTF-8"?>
            <constraints name="simple constraints" 
              xmlns="http://purl.org/net/sodc/cl">

              <profile uri="http://example.com/profile/simple#book">
                <constraint property="http://purl.org/dc/elements/1.1/title">
                  <cardinality>1</cardinality>
                </constraint>
                <constraint property="http://purl.org/dc/elements/1.1/title">
                  <value>
                    <plainliteral/>
                  </value>
                </constraint>
                <constraint property="http://purl.org/dc/elements/1.1/creator">
                  <mincardinality>1</mincardinality>
                </constraint>
                <constraint property="http://purl.org/dc/elements/1.1/creator">
                  <value>
                    <uri/>
                  </value>
                </constraint>
              </profile>
              
              <profile uri="http://example.com/profile/simple#person">
                <constraint property="http://xmlns.com/foaf/0.1/name">
                  <mincardinality>1</mincardinality>
                </constraint>
                <constraint property="http://xmlns.com/foaf/0.1/name">
                  <value>
                    <plainliteral/>
                  </value>
                </constraint>
              </profile>
              
            </constraints>

            Note that resource profiles are identified by URIs. This allows a
            profile to be applied to specific resources in a graph (see below).

        5. Applying Resource Profiles in SoDC-XML

            A resource profile must of course be applied to specific resources
            in some graph. In other words, some information must be provided
            which can be used to determine which resources in some graph must
            match which resource profiles.

            The SoDC-XML syntax is designed to allow this information to be
            embedded in the graph, via the profile element.

            For example, the graph below has embedded profile information...

            <?xml version="1.0" encoding="UTF-8"?>
            <graph xmlns="http://purl.org/net/sodc/xml">  

              <resource>
                <uri>http://example.com/book#1</uri>
                <profile>http://example.com/profile/simple#book</profile>
                ... etc ...

-- 
Tom Baker <[log in to unmask]>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

November 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
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


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

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