XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Musings on the fundamental nature of data

Hi Roger,
 
I think you might have missed an important aspect: - change.
Usually the focus is very narrow - on something which changes.
The changes can be modelled as a series of states and the purpose
of the sending / receiving is to synchronise those states, so as to
allow the changing 'worldview' to be synchronised - at least re that
narrow scope which is the focus of the synchronisation.
 
Cheers

----
Stephen D Green


On 29 April 2013 18:26, Costello, Roger L. <costello@mitre.org> wrote:
Hi Folks,

The subject line is the short title. Here is the longer title:

    Musings on the fundamental nature of the knowledge
    that is captured from a domain expert and the subsequent
    exchange of that knowledge as data

Consider this scenario: You conduct multiple in-depth discussions/interviews with someone who is a Subject Matter Expert (SME) and you capture that person's knowledge by encoding it as data using some syntax such as XML.

What knowledge do you deem important for encoding as data?

Presumably the data will be shared -- exchanged -- with others. What data do you want others to have?

This knowledge might be worth encoding as data:

    If there are geometric shapes, then it might be
    worthwhile to encode knowledge about the shapes
    so that others can reconstruct the shapes, should
    that be desired.

    If there is a need to control something, then it might
    be worthwhile to encode knowledge about how to
    control the "thing" so that others with access to a
    "thing" can control it, should that be desired.

    If there are places involved, then it might be worthwhile
    to encode knowledge about the location of the place so
    that others can go to that place (or send something to
    that place), should that be desired.

    If there is an item for which there are many occurrences,
    then it might be worthwhile to encode knowledge that
    identifies the item so that others can obtain their own
    copy of the item, should that be desired.

Observe the recurring pattern. The knowledge that is worth encoding as data is that data which, when exchanged, allows the recipient to replicate, to some extent, the sender's worldview:

    The sender has a shape. Upon receipt of the shape data
    the recipient can replicate the shape.

    The sender is controlling some "thing". Upon receipt of
    the control data the recipient can replicate controlling
    a "thing".

    The sender is at some location. Upon receipt of the location
    data the recipient can replicate the experience of being
    at the same location.

    The sender has an item. Upon receipt of the identifying
    data the recipient can replicate the item by obtaining his
    own copy of the item.

Assertion: The most fundamental issue with data exchange is:

    What worldview do you want replicated?

I welcome your insights on this subject.

/Roger

_______________________________________________________________________

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@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS