跳至主要内容

XSD Tutorial (3): Mis

In last blog, we have some problems and their solution, in this thread, we are going to solve more specific problems.

Define id Like Attribute?

<xs:attribute name="id" type="xs:ID"/>

Define ref Like Attribute?

<xs:attribute name="ref" type="xs:IDREF"/>

Default Value for Element?

Short answer is no, xsd doesn’t provide this functionality.

Attributes can be set with a default value because it is relative simple, while elements can nested and combined, which is much more complex and hard to provide a default content.

As far as we know, there also exists no alternatives to provide a default value for a missing element. In order to provide this functionality, we add much more code when combined with jaxb.

Define key & keyref

We define them in following steps:

  • First, we must define key & keyref in element body;
  • Second, definekey in following format:
<key
  id = ID
  name = NCName
  {any attributes with non-schema namespace . . .}>
  Content: (annotation?, (selector, field+))
</key>


<xs:key name="key">
    <xs:selector xpath=".//state"/>
    <xs:field xpath="code"/>
</xs:key>
  • Then, simple XPath syntax rule:
Expression Description
nodename Selects all nodes with the name “nodename”
/ Selects from the root node
// Selects nodes in the document from the current node that match the selection no matter where they are
. Selects the current node
.. Selects the parent of the current node
@ Selects attributes

A simple key & keyref example (in which vehicle reference it’s father node):

<xs:element name="vehicle">
    <xs:complexType>
        <xs:attribute name="state" type="xs:integer"/>
    </xs:complexType>
</xs:element>

<xs:element name="state">
    <xs:complexType>
        <xs:sequence>
            <xs:element name="code" type="xs:integer"/>
            <xs:element ref="vehicle"/>
        </xs:sequence>
    </xs:complexType>
</xs:element>

<xs:element name="root">
    <xs:complexType>
        <xs:sequence>
            <xs:element ref="state"/>
        </xs:sequence>
    </xs:complexType>

    <xs:key name="state">
        <!-- states are keyed by their code -->
        <xs:selector xpath=".//state"/>
        <xs:field xpath="code"/>
    </xs:key>

    <xs:keyref name="vehicleState" refer="state">
        <!-- every vehicle refers to its state -->
        <xs:selector xpath=".//vehicle"/>
        <xs:field xpath="@state"/>
    </xs:keyref>
</xs:element>
<state>
    <code>12</code>
    <vehicle state="12"/>
</state>

A more complicated xsd/xml code can be found in my git repo.

Ref

Written with StackEdit.

评论

发表评论

此博客中的热门博文

Spring Boot: Customize Environment

Spring Boot: Customize Environment Environment variable is a very commonly used feature in daily programming: used in init script used in startup configuration used by logging etc In Spring Boot, all environment variables are a part of properties in Spring context and managed by Environment abstraction. Because Spring Boot can handle the parse of configuration files, when we want to implement a project which uses yml file as a separate config file, we choose the Spring Boot. The following is the problems we met when we implementing the parse of yml file and it is recorded for future reader. Bind to Class Property values can be injected directly into your beans using the @Value annotation, accessed via Spring’s Environment abstraction or bound to structured objects via @ConfigurationProperties. As the document says, there exists three ways to access properties in *.properties or *.yml : @Value : access single value Environment : can access multi
5 条评论
阅读全文

Elasticsearch: Join and SubQuery

Elasticsearch: Join and SubQuery Tony was bothered by the recent change of search engine requirement: they want the functionality of SQL-like join in Elasticsearch! “They are crazy! How can they think like that. Didn’t they understand that Elasticsearch is kind-of NoSQL 1 in which every index should be independent and self-contained? In this way, every index can work independently and scale as they like without considering other indexes, so the performance can boost. Following this design principle, Elasticsearch has little related supports.” Tony thought, after listening their requirements. Leader notice tony’s unwillingness and said, “Maybe it is hard to do, but the requirement is reasonable. We need to search person by his friends, didn’t we? What’s more, the harder to implement, the more you can learn from it, right?” Tony thought leader’s word does make sense so he set out to do the related implementations Application-Side Join “The first implementation
发表评论
阅读全文

Implement isdigit

It is seems very easy to implement c library function isdigit , but for a library code, performance is very important. So we will try to implement it and make it faster. Function So, first we make it right. int isdigit ( char c) { return c >= '0' && c <= '9' ; } Improvements One – Macro When it comes to performance for c code, macro can always be tried. #define isdigit (c) c >= '0' && c <= '9' Two – Table Upper version use two comparison and one logical operation, but we can do better with more space: # define isdigit(c) table[c] This works and faster, but somewhat wasteful. We need only one bit to represent true or false, but we use a int. So what to do? There are many similar functions like isalpha(), isupper ... in c header file, so we can combine them into one int and get result by table[c]&SOME_BIT , which is what source do. Source code of ctype.h : # define _ISbit(bit) (1 << (
发表评论
阅读全文