top - previous - this is slide 1 - next
ISSUE-63: Metadata Architecture for the Web
Outline
Goal: determine next steps on interoperability issue
JAR 2011-02-09
top - previous - this is slide 2 - next
Generic approach to TAG issues
top - previous - this is slide 3 - next
Background
top - previous - this is slide 4 - next
Received wisdom (webarch)
<http://example/cheese> dc:creator "Jiang Yuhe".
top - previous - this is slide 5 - next
Deployment
top - previous - this is slide 6 - next
Consensus at risk - syntactic space threatened
Because Web URIs are reserved for their IRs, other URIs have to be used for other things. Those who find this difficult have their eyes on Web URIs.
HH: "It [303]'s not a standard. It's on no W3C Recs. It's a W3C TAG finding, and primarily something Tim wrote in a design note that got put forth by SWEO as Note. So there's no process to go through to change it to begin with."
"... people forget to put it [the #] there when writing and cut and pasting URIs, and it's applied inconsistently across the XML and RDF universes. It puts a magic redirect in where one isn't necessary to begin with."
top - previous - this is slide 7 - next
The interoperability issue
top - previous - this is slide 8 - next
The interoperability issue (2)
top - previous - this is slide 9 - next
Notational approaches, webarch vs. alternative
where you see U, pretend that you see http://example/e
webarch | alternative | |
refer to document at U | <U> yielding 200 the document | [wa:isAccessedFrom "U"^^xsd:anyURI] <U#description> <doc:U> &<U> <U> yielding non-description |
refer to subject of document at U | [foaf:isPrimaryTopicOf <U>] <U#subject> <tdb:U> *<U> <V> yielding 303 Location: U <V> yielding 200 other IR | <U> yielding description |
top - previous - this is slide 10 - next
Can we maintain consensus?
top - previous - this is slide 11 - next
[Discuss process here. Echoes, TAG purview, important, fatigue, etc. More technical stuff follows.]
top - previous - this is slide 12 - next
Deeper issues (AWWSW)
top - previous - this is slide 13 - next
What does metadata express - intent or truth?
Robin Berjon: "There shouldn't be a way of specifying dependencies external to the content or it's authoritative metadata all over again."
Media type and dependencies express intent: You can't hold me responsible if my content is interpreted in some other way.
Other metadata is objective - e.g. authorship, size.
top - previous - this is slide 14 - next
How is metadata true?
A: Check it using GET/200.
top - previous - this is slide 15 - next
Why would I let myself be held accountable for my referential use of someone else's http: URI, if GET/200 has authority over reference and the URI owner is in control of GET/200?
top - previous - this is slide 16 - next
WRONG QUESTIONS:
top - previous - this is slide 17 - next
Segue to persistence discussion
Actionable persistence = a way to hold services accountable, and a system for obtaining universal consensus on what they're accountable for
Persistent Reference Interventions