ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> xml-dev
xml-dev
RE: [xml-dev] Can RDDL and RDF coexist?
by =?iso-8859-1?Q?Bill_de_h=D3ra?= other posts by this author
Jun 5 2002 5:47PM messages near this date
RE: [xml-dev] Can RDDL and RDF coexist? | Re: [xml-dev] Can RDDL and RDF coexist?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>  -----Original Message-----
>  From: Bullard, Claude L (Len) [mailto:clbullar@[...].com] 
>  
>  If it embeds the authority, there are two 
>  pieces of information there and how to 
>  reconcile which is in effect or both is 
>  still a processing issue.  You are saying 
>  that there is no RDF System specification 
>  and that interoperability of such systems 
>  is left to the vendors to imagine.

I am saying as far as RDF is concerned, no meaning is embedded in a
URI ref. 


>  Once again, given the rules of the game, 
>  the biggest vendor wins.  If the vendor 
>  chooses not to support it, the Semantic 
>  Web based on RDF processing collapses or 
>  remains a niche.   Ok.

Well on this point any vendor who looks for meaning in the URI ref,
rather than the RDF graph, and makes decisions or entailments based
on that structure, is doing something other than RDF. That's not
exactly left unspecified and the one RDF construct that did
something like it is gone. If it's not crystal clear now, I'm sure
it can be made so before any of the new drafts go to
recommendation. That doesn't stop anyone doing their own thing, no
spec does, but you can do say things that make it clear that a
certain practice is not ok, via "must not".

There's a distributed systems best practice re naming that names
should be opaque, i.e. you don't go parsing into names to discover
something about who is named. That makes sense if you're using
something Java's VMID, I'm not sure how it'll work out for URIs as
they do have internal structure.

Bill de hÓra

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA/AwUBPP5OruaWiFwg2CH4EQLy/ACg5KnnH+36QkmaDUwJ85SFNsdcQyUAnA+l
BwoMIEElqU9qE2fqetmweD9d
=mmc1
-----END PGP SIGNATURE-----


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl> 
Thread:
Bullard, Claude L (Len)
=?iso-8859-1?Q?Bill_de_h=D3ra?=
Thomas B. Passin
Paul Prescod
=?iso-8859-1?Q?Bill_de_h=D3ra?=
Paul Prescod
=?iso-8859-1?Q?Bill_de_h=D3ra?=


Peter V. Mikhalenko

Ronald Bourret

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved