Minutes 2006-03-10
Participants
-
Mikael Nilsson
-
Tomas Baker
-
Thomas Fisher
-
Andy Powell
-
Pete Johnston
DC-RDF Dependencies
-
Namespace policy updates.
-
New draft in Madrid 2005 - clearer language and DCAM compliance, as well as dc -> dcterms copy of terms.
-
Trustees wants this change to happen.
-
DCMI Type namespace remains.
-
Pete suggests removing actual URIs from policy.
-
Mainly affects DC-RDF examples.
-
XML encoding
-
In progress
-
Does not affect RDF encoding.
-
GRRDL to map XML -> RDF is something we want.
-
DC-TEXT syntax
-
Need a draft "Recommended resource" by the time public comment period is started
-
Pete is working on it
-
Property definition updates
-
in progress
-
May affect examples, otherwise no dependency
-
Domains/ranges introduction
-
Need to introduce into DCAM
-
Need to update DCMI Terms doc (through UB). Will update current draft and discuss in UB meeting in Seattle
-
Try to not make DCRDF dependent on DCAM changes or DCMI Terms changes. Needs to mention domains and ranges, but can try to do so in a neutral way
DC RDF draft
-
Plan for parallel Note/recommended resource containing most difficult discussions
-
Encoding document itself to be kept concise.
-
Use same examples in RDF and in XML?
-
Can we update published recommendations to adjust examples to DCMI Terms updates (wording or domains/ranges)?
-
Publish short(ish) Release Notes and Roadmap together with new RDF encoding, to initiate discussion.
Namespace change
-
Previously, a new namepsace for DC terms has been proposed, based on modified semantics of DC RDF binding.
-
Now proposed to leave current namespace, and ignite discussions through public comment period.
-
Need to contact primary stakeholders such as Adobe for getting feedback. Do this at the time of publishing the draft.