Revision [99]
Last edited on 2009-09-19 06:08:56 by DavidLeeAdditions:
- Serialized XDM will not retain information about node identity: that is, the recipient of the serialized XDM will not be able to determine whether two serialized elements originated from the same node or merely from two nodes that were deep-equal to each other.
- Schema and Type information. XDM Serialization does NOT transfer type **defininitions**. The consumer of the serialized XDM is assumed to have access to the same schema as the producer of the serialized XDM: that is, a QName identifying a type is assumed to have the same meaning to both the producer and consumer.
- Schema and Type information. XDM Serialization does NOT transfer type **defininitions**. The consumer of the serialized XDM is assumed to have access to the same schema as the producer of the serialized XDM: that is, a QName identifying a type is assumed to have the same meaning to both the producer and consumer.
Deletions:
the recipient of the serialized XDM will not be able to determine whether
two serialized elements originated from the same node or merely from two
nodes that were deep-equal to each other.
- Schema and Type information. XDM Serialization does NOT transfer type **defininitions**. The consumer of the serialized XDM is assumed to have access to the same
schema as the producer of the serialized XDM: that is, a QName identifying a
type is assumed to have the same meaning to both the producer and consumer.
Revision [98]
Edited on 2009-09-19 06:07:37 by DavidLeeAdditions:
- Sequences should **not** be normalized. Sequences should preserve the individuality, count and type of items. Adjacent atomic item should not be contented (normalized).
- Serialized XDM will retain information about the descendants of nodes in the sequence being serialized, but it will not retain information about their ancestors.
- Serialized XDM will retain information about the descendants of nodes in the sequence being serialized, but it will not retain information about their ancestors.
Deletions:
- Serialized XDM will retain information about the descendants of nodes in
the sequence being serialized, but it will not retain information about
their ancestors.
Revision [97]
Edited on 2009-09-19 06:02:33 by DavidLeeAdditions:
-Individuality of sequence items
- Types of atomic items
- Sequences should **not** be normalized. Sequences of should preserve the individuality, count and type of items. For example a sequence of 3 xs:integer should be able to be reconstituted as 3 xs:integer items. Text nodes should not be concatenated.
- Types of atomic items
- Sequences should **not** be normalized. Sequences of should preserve the individuality, count and type of items. For example a sequence of 3 xs:integer should be able to be reconstituted as 3 xs:integer items. Text nodes should not be concatenated.
Deletions:
Revision [96]
Edited on 2009-09-18 19:01:21 by DavidLeeAdditions:
====Goals====
Deletions:
Revision [95]
Edited on 2009-09-18 19:00:52 by DavidLeeNo differences.
Revision [94]
Edited on 2009-09-18 19:00:29 by DavidLeeAdditions:
====Goals=====
- Serialized XDM will retain information about the descendants of nodes in
the sequence being serialized, but it will not retain information about
their ancestors.
==XDM Information NOT preserved==
- Ancester information. An XDM Node serialized will NOT maintain information about its ancestors. For example if a node $a is serliazed then $a/.. is NOT maintained.
- Serialized XDM will not retain information about node identity: that is,
the recipient of the serialized XDM will not be able to determine whether
two serialized elements originated from the same node or merely from two
nodes that were deep-equal to each other.
- Schema and Type information. XDM Serialization does NOT transfer type **defininitions**. The consumer of the serialized XDM is assumed to have access to the same
schema as the producer of the serialized XDM: that is, a QName identifying a
type is assumed to have the same meaning to both the producer and consumer.
- Serialized XDM will retain information about the descendants of nodes in
the sequence being serialized, but it will not retain information about
their ancestors.
==XDM Information NOT preserved==
- Ancester information. An XDM Node serialized will NOT maintain information about its ancestors. For example if a node $a is serliazed then $a/.. is NOT maintained.
- Serialized XDM will not retain information about node identity: that is,
the recipient of the serialized XDM will not be able to determine whether
two serialized elements originated from the same node or merely from two
nodes that were deep-equal to each other.
- Schema and Type information. XDM Serialization does NOT transfer type **defininitions**. The consumer of the serialized XDM is assumed to have access to the same
schema as the producer of the serialized XDM: that is, a QName identifying a
type is assumed to have the same meaning to both the producer and consumer.
Deletions:
Revision [93]
Edited on 2009-09-18 18:48:54 by DavidLeeAdditions:
- document, element,attribute, text, namespace, processing , instruction, comment.
Each type has a value. Atomic types have string values, and node types have XML values.
An XDM serialization format should preserve the following attributes
- Sequences
- Sequences should **not** be normalized. Sequences of should preserve the count and type of items
- Atomic Types and values
- Atomic types are preserved with the expanded QName for the type and the string value
- Nodes
- Nodes values are preserved for each 8 of the XDM Node types
Each type has a value. Atomic types have string values, and node types have XML values.
An XDM serialization format should preserve the following attributes
- Sequences
- Sequences should **not** be normalized. Sequences of should preserve the count and type of items
- Atomic Types and values
- Atomic types are preserved with the expanded QName for the type and the string value
- Nodes
- Nodes values are preserved for each 8 of the XDM Node types
Deletions:
- element
- attribute
- text
- namespace
- processing
- instruction
- comment
Revision [82]
Edited on 2009-09-18 17:52:26 by DavidLeeNo differences.
Revision [81]
Edited on 2009-09-18 17:45:07 by DavidLeeAdditions:
The XDM Model defines values as a sequence of zero or more items. Each item is one of the following types
- Atomic Type
- Node type
- document
- element
- attribute
- text
- namespace
- processing
- instruction
- comment
- Atomic Type
- Node type
- document
- element
- attribute
- text
- namespace
- processing
- instruction
- comment
Deletions:
Revision [80]
Edited on 2009-09-18 17:40:41 by DavidLeeAdditions:
The XDM Model defines the following types
Revision [79]
Edited on 2009-09-18 17:26:58 by DavidLeeAdditions:
====XDM Information Preserved and Lost====
Preserving all of the information in the XDM is very difficult, and likely why a serialization model for XDM has not been specified. This proposal recognizes that not all XDM information is equally important. In the context of the Use Cases, and with the goals of reasonable implementation with existing vendor libraries this proposal aims at preserving some XDM information at the expense of others.
==XDM Information preserved==
Preserving all of the information in the XDM is very difficult, and likely why a serialization model for XDM has not been specified. This proposal recognizes that not all XDM information is equally important. In the context of the Use Cases, and with the goals of reasonable implementation with existing vendor libraries this proposal aims at preserving some XDM information at the expense of others.
==XDM Information preserved==
Revision [78]
Edited on 2009-09-18 14:06:24 by DavidLeeAdditions:
Real Soon Now !
Deletions:
Revision [58]
Edited on 2009-09-18 08:40:02 by DavidLeeAdditions:
- Exchange of XDM Data between XDM Tools and tools which are not XDM capable, or with limited XDM capability.
Deletions:
Revision [53]
Edited on 2009-09-18 06:46:38 by DavidLeeAdditions:
- Standardization of a format for use in XML Pipeline Processors so that steps can be implemented by different vendors or in different languages.
- [[XDMSerializeUseCase7 Use Case 7]] Standardization of a format for use in XML Pipeline Processors so that steps can be implemented by different vendors or in different languages.
- [[XDMSerializeUseCase7 Use Case 7]] Standardization of a format for use in XML Pipeline Processors so that steps can be implemented by different vendors or in different languages.
Revision [50]
Edited on 2009-09-18 06:30:43 by DavidLeeAdditions:
- [[XDMSerializeUseCase2 Use Case 2]] Exchange of XDM data between XDM Tools from different vendors in the same environment
Deletions:
Revision [49]
Edited on 2009-09-18 06:30:27 by DavidLeeAdditions:
- [[XDMSerializeUseCase4 Use Case 4]] Exchange of XDM Data between XDM Tools and tools which are not XDM capible.
Deletions:
Revision [48]
Edited on 2009-09-18 06:30:09 by DavidLeeAdditions:
Use cases are concrete examples that demonstrate the goals.
- [[XDMSerializeUseCase1 Use Case 1]] Exchange of XDM data between XDM Tools in different environments
- [[XDMSerializeUseCase2 Use Case 2]] [Exchange of XDM data between XDM Tools from different vendors in the same environment
- [[XDMSerializeUseCase3 Use Case 3]] Exchange of XDM data between XDM Tools from the same vendor in the same environment where it is difficult to preserve the vendors native data structure
- [[XDMSerializeUseCase4Use Case 4]] Exchange of XDM Data between XDM Tools and tools which are not XDM capible.
- [[XDMSerializeUseCase5 Use Case 5]] Provide a human readable output of XDM data
- [[XDMSerializeUseCase6 Use Case 6]] Output of XDM data from test cases using XDM Tools with the purposes of validation and compare
- [[XDMSerializeUseCase1 Use Case 1]] Exchange of XDM data between XDM Tools in different environments
- [[XDMSerializeUseCase2 Use Case 2]] [Exchange of XDM data between XDM Tools from different vendors in the same environment
- [[XDMSerializeUseCase3 Use Case 3]] Exchange of XDM data between XDM Tools from the same vendor in the same environment where it is difficult to preserve the vendors native data structure
- [[XDMSerializeUseCase4Use Case 4]] Exchange of XDM Data between XDM Tools and tools which are not XDM capible.
- [[XDMSerializeUseCase5 Use Case 5]] Provide a human readable output of XDM data
- [[XDMSerializeUseCase6 Use Case 6]] Output of XDM data from test cases using XDM Tools with the purposes of validation and compare
Deletions:
Revision [47]
Edited on 2009-09-18 06:18:16 by DavidLeeAdditions:
- Exchange of XDM data between XDM Tools in different environments
- Exchange of XDM data between XDM Tools from different vendors in the same environment
- Exchange of XDM data between XDM Tools from the same vendor in the same environment where it is difficult to preserve the vendors native data structure
- Exchange of XDM Data between XDM Tools and tools which are not XDM capible.
- Provide a human readable output of XDM data
- Output of XDM data from test cases using XDM Tools with the purposes of validation and compare
- Exchange of XDM data between XDM Tools from different vendors in the same environment
- Exchange of XDM data between XDM Tools from the same vendor in the same environment where it is difficult to preserve the vendors native data structure
- Exchange of XDM Data between XDM Tools and tools which are not XDM capible.
- Provide a human readable output of XDM data
- Output of XDM data from test cases using XDM Tools with the purposes of validation and compare
Deletions:
Revision [46]
Edited on 2009-09-18 05:20:16 by DavidLeeAdditions:
- XDM Consumer An XDM Tool which can consume (allow as input, arguments) XDM Data.
- XDM Producer An XDM Tool which can produce XDM data (on output, return or output variables)
This proposal expresses multiple goals, not all of which may be possible to achieve. The use cases describe concrete examples of many of the goals, while this summary provides the intent.
- A standardized text representation of XDM data preserving as much of the XDM model as reasonable.
- A representation that can be easily implemented using existing vendors XML technology.
Some purposes for which this standard could be used include
- Exchange of XDM data
- XDM Producer An XDM Tool which can produce XDM data (on output, return or output variables)
This proposal expresses multiple goals, not all of which may be possible to achieve. The use cases describe concrete examples of many of the goals, while this summary provides the intent.
- A standardized text representation of XDM data preserving as much of the XDM model as reasonable.
- A representation that can be easily implemented using existing vendors XML technology.
Some purposes for which this standard could be used include
- Exchange of XDM data
