[
Lists Home |
Date Index |
Thread Index
]
> Bill de hÓra wrote:
> > Throw an exception to the application, let the application figure
> > out what to do (ie try a GET, page an admin), let it stream back
> > triples to the graph. But do not have an RDF processor parsing into
> > the URI refs, leave that to web code.
>
> You haven't answered my question. Some piece of software stumbles upon
> "eg:Document". It doesn't know about eg:Document yet. It knows a bunch
> about eg:Work. eg:Document is a subclass of eg:Work, so everything it
> knows about eg:Work should apply to eg:Document. How does it discover
> the subclass relationship? I don't care how you segment it into rdf
> processor and application.
I think I've become quite confused about what you're asking.
I'm not the best person to talk about RDF as a series of disconnected models, since every use I have made of RDF is in unified models, with merging applied where necessary.
However, my guess is that in the federated RDF model, you had better rely on isDefinedBy properties rather than namespaces in the serialization.
Of course, the bad news is that isDefinedBy is not used nearly as often as it should be.
Aside (and this thought probably more properly belongs on www-rdf-interest):
I have come recently to believe that RDF will require some concept of scopes to be successful in any distributed model. Even though we only use RDF in closed models, 4RDF's basic implementation of scopes ("domains" as we call them) are already essential in many maintenance and administrative tasks for such models.
If RDF had the idea of scopes, here is how I would answer your question:
People who publish RDF should indicate the scope of the statements in the published RDF. This can be as simple as signalling the agent that it should treat the URI from which it retrieved the serialization as the scope. Let us call this scope S.
The publisher could then provide one or more statements assigning governing schemata for the scope. The agent can then retrieve those schemata as needed.
--
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Track chair, XML/Web Services One (San Jose, Boston): http://www.xmlconference.com/
DAML Reference - http://www.xml.com/pub/a/2002/05/01/damlref.html
The Languages of the Semantic Web - http://www.newarchitectmag.com/documents/s=2453/new1020218556549/index.html
XML, The Model Driven Architecture, and RDF @ XML Europe - http://www.xmleurope.com/2002/kttrack.asp#themodel
|
