1 / 15

DC8: Architecture WG

DC8: Architecture WG. day 2 Architecture breakout group Sigfrid Lundberg (NetLab) siglun@munin.lub.lu.se Dan Brickley (ILRT/W3C) danbri@w3.org. Putting it all together. The lego click. We need architectural consistency across our specifications (HTML, XML, RDF) to support...

sadah
Télécharger la présentation

DC8: Architecture WG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DC8: Architecture WG day 2 Architecture breakout group Sigfrid Lundberg (NetLab) siglun@munin.lub.lu.se Dan Brickley (ILRT/W3C) danbri@w3.org

  2. Putting it all together... • The lego click. We need architectural consistency across our specifications (HTML, XML, RDF) to support... • Proposed Agent core / agent qualifiers • (structured) dates and coverage • deployment of agreed qualifiers • representing new qualifiers and extensions

  3. Proposed Architecture WG: DCMI: finding stuff using metadata dc-arch: “The objectives of the working group are to discuss and develop a model, strategy and roadmap for the practical deployment of Dublin Core metadata using mainstream Web technologies (XML/RDF/HTML).” (for discussion...)

  4. Drawing together discussions... • Merge activities previously scattered between... • DC-implementors (deployment!) • dc-schema (“conceptual modelling” issues) • dc-datamodel (models and syntaxes...) • dc-ac (reversing the brain drain?)

  5. Main activities • Make technical discussions visible outside dc-ac (eg. To RSS community, W3C groups etc) • Roadmap: visible tasklist and plans for deployability • ongoing development and documentation activities (more on this later...) • Focus on implementability: what to say to developers who want to ‘use DC’

  6. Topics for discussion • How to make sure the work gets done? • Small practical steps, not a grand architecture • admit possibility of failure - some things may be too hard, or research topics • DCMI as community: explore IRC channels etc., as aid to progress tracking • Implementation focus: we all need this stuff to do our ‘day jobs’

  7. For discussion today... • What resources do we have? Who can spare time to... • report on implementation experience • developer FAQs, issue lists • work on specs, proof of concept implementations • What experience do we have? How consistent an ‘architecture’ can we expect to have? How can developers for use (X)HTML but be ‘RDF friendly...’ etc

  8. A lot of work to do • Can we live with the proposed charter? • Does the draft tasklist look ok? • Do we want to talk details now? • Possible time-consuming topics: • updating our RDF representation of DC-Q • principles of good qualification: is this an architecture question, Usage group, DC-AC?

  9. notes • Roland – update of rdf model spec • Discussion Haspart etc. – useful to represent nested structure. Hard in html, but rdf and xml allow this. Implementing the lego metaphor.

  10. Discussion… • In addition to nesting, also need `linking • Once we had URIs as possible values for all 15; qualifiers don`t reflect this. • This requirement came out of several groups at dc8, need for pointers, eg. To authority records.

  11. … • Old (current) rdf and dc doc was designed before rdf schema was designed; it does work that can be done with schemas. • Linking: what to point to; issue of exchanging authority records, granularity of those. Is there scope for DC advise on this… or engage in discussion with potential authority file providers (eg. Syntax…)

  12. … • Missing out on potential of rdf for representing hierarchical structure… not made good use of rdf to date • Agents – representing separately avoiding duplication • Do we have a requirement to represent dc-education structure… what does this amount to…

  13. Limits of a flat datamodel and cramming everything into the 15… Should extensions be qualifiers to 15 or additional A technical bumping into political issues. Namespace vs namespace… Pidgins vs complex languages; needing a name for those richer multi-namespace languages. We expect, hope, want additional constructs beyond the 15. Dc-education, agents…

  14. … • Can we avoid verbosity of multiple namespaces… why import 6 or more namespaces to get simple job done. • Granularity: versioning at element level, at namespace level, both, either etc confusion… • How can we mix for eg dublin core with Biztalk • Resolve the painful versioning discussion • (is this an engineering or policy question)

  15. Terminology mess: what do we mean by namespace… • Do we mean xml namespaces, ie modularity construct, unique names

More Related