http://www.ibm.com/developerworks/rational/library/basic-profile-linked-data/
I've only skimmed this but I thought the section on "validation and
constraints" might be of interest from the perspective of the
discussions on DC Application Profles/Description Set
Profiles/"structural constraints" etc, e.g.
===
RDF has the happy characteristic that "it can say anything about
anything." This means that, in principle, any resource can have any
property and there is no requirement that any two resources have the
same set of properties, even if they have the same type or types. In
practice, though, the properties that are set on resources usually
follow regular patterns that are dictated by the uses of those
resources. Although a particular resource might have arbitrary
properties, when viewed from the perspective of a particular
application or use case, the set of properties and property values
that are appropriate for that resource in that application will often
be predictable and constrained. For example, if a server has resources
that represent software products and bugs, for the purposes of
displaying information in tabular formats, creating and updating
resources, or other purposes, a client might want to know what
properties software products and bugs have on that server,. The Basic
Profile Validation and Constraints specification aims to capture
information about those properties and constraints.
===
It doesn't look as if that stuff was included in the W3C Member
Submission document here
http://www.w3.org/Submission/2012/SUBM-ldbp-20120326/
I know there's a W3C Linked Data Platform WG
http://www.w3.org/2012/ldp/charter
http://www.w3.org/2012/ldp/wiki/Main_Page
http://lists.w3.org/Archives/Public/public-ldp-wg/
looking at this general area but I haven't followed it closely enough
to know whether the constraints angle is on their agenda
Pete
--
Pete Johnston
|