OSLC Core Meeting June 1, 2010

Meeting logistics

See the OslcCoreMeetings for more information, more dial-in numbers and on-line meeting information.

• Conference Access
  • Toll free: 1-866-423-8350
  • Toll: 1-719-387-8273
• Participant passcode: 558663

Agenda

Today, I'd like review each of our open issues to make sure we understand them and to see if we can quickly resolve any of them. These are all from the issues page:

http://open-services.net/bin/view/Main/OslcCoreV1Issues

Creation factories

#5 Programmatic selection of creation factories. How does a client know which to use to create a resource of a given type? Same goes for delegated UI, and query capabilities. See also: http://open-services.net/pipermail/oslc-core_open-services.net/2010-May/000275.html

Is allowing a creation factory to specify shapes an acceptable solution to this problem?

Query capabilities

#24 How does client know which property's values are the query results. Is it good enough to let client assume that all property values other than oslc:reponseInfo are query results? See also: http://open-services.net/pipermail/oslc-core_open-services.net/2010-May/000260.htm

Is allowing domains to specify a shape for each query capability an acceptable solution?

Resource shapes

#23 What property do we use to indicate the property that an occurrence of oslc:Property describes? Both rdf:type and rdf:predicate are inappropriate. See also: http://open-services.net/pipermail/oslc-core_open-services.net/2010-May/000250.html

#24 How does a service make resource shapes available for its resource, common and customized. Do we host resource shape representations at open-services.net? Do we expect implementations to provide them?

Could we also use oslc:describes here?

Common properties

#15 Using "dc" for new Dublin Core namespace is unconventional, but changing may break old and misbehaving clients. See also: http://open-services.net/pipermail/oslc-core_open-services.net/2010-May/000256.html

Is Arthur's suggestion of "recommend dcterms, but tolerate dc" an acceptable solution here?

Partial Update

Good feedback so far, still need to investigate using constrained SPARQL Update and patch document format.

Link Guidance

Got some good feedback internally and have made some changes in response. Also, got some strong push-back against:

• The notion of inverse links
• The need to advise against "link properties"

I'm still trying to understand those two issues. I think more consensus building work is necessary.