Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] What is Data?

From: Uche Ogbuji <uche@------.--->
To: Frank Manola <fmanola@---.--->
Date: 9/2/2009 5:25:00 PM
Sorry for top-post.  I've written a huge deal on on all these topics for
over 10 years, and I'm sorry that at present I'm not very disposed to spend
a lot of time in close discussion.  If I'm able to grab a few cycles this
week, I can provide no end of pointers to my articles expanding on the bits
you picked out.

--Uche

On Wed, Sep 2, 2009 at 9:47 AM, Frank Manola <fmanola@a...> wrote:

>
> On Sep 2, 2009, at 11:03 AM, Peter Hunsberger wrote:
>
>  Went off list, by mistake.  Uche comments on RDF  got me to ask what
>> he meant and it seems relevant to the general question....
>>
>>
>> ---------- Forwarded message ----------
>> From: Peter Hunsberger <peter.hunsberger@g...>
>> Date: Tue, Sep 1, 2009 at 8:45 PM
>> Subject: Re: [xml-dev] What is Data?
>> To: Uche Ogbuji <uche@o...>
>>
>>
>> On Tue, Sep 1, 2009 at 6:37 PM, Uche Ogbuji<uche@o...> wrote:
>>
>>>
>>> In my opinion RDF should have been about expressing context across the
>>> narrative aspects of content, including XML documents (or at least XML
>>> without the mess that is  PSVI and all that).  Instead RDF makes mixed
>>> content and such a pain, and focuses too much on granular data typing,
>>> and
>>> relies on a basic statement model (triples) far too limited to express
>>> useful nuance.
>>>
>>
> I'm still not sure what some of this means.  I could read my own
> interpretation into these things, but specifically, could we have some
> examples of what is meant by:
>
> "expressing context across the narrative aspects of content"
>
> "mixed content"
>
> "granular data typing"
>
> "useful nuance"
>
>
>> The last part (triples) was my first frustration and I've definitely
>> run into the pain of fitting mixed content into it.  Hadn't thought
>> about the granular types that much, but you're right on that one too.
>>  Shame, really.  Wouldn't it be nice to be able to answer Rogers
>> original question by simply pointing at RDF and saying "anything that
>> fits in there" with the fit, for well, everything, being obvious....
>>
>>
> A variant on this might be a good way to tease out some of the issues
> people have with RDF (or with definitions of data in general).  Suppose we
> answered Roger's original question by saying that data is anything that can
> fit into a relational DBMS.  The fit isn't always obvious (hence issues of
> database design), but take that as a starting point.  Now lets discuss the
> problems folks have with that definition.  Since anything you can fit into a
> relational DBMS you can fit into RDF (with its own issues of "database
> design"), presumably many of the problems will be the same.
>
> --Frank
>
>  --
>> Peter Hunsberger
>>
>>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>


-- 
Uche Ogbuji                       http://uche.ogbuji.net
Founding Partner, Zepheira        http://zepheira.com
Linked-in profile: http://www.linkedin.com/in/ucheogbuji
Articles: http://uche.ogbuji.net/tech/publications/
Friendfeed: http://friendfeed.com/uche
Twitter: http://twitter.com/uogbuji
Join me at Balisage:
* http://www.balisage.net/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent