The XML Security Working Group has agreed not to progress this XML Signature Streaming Profile of XPath 1.0 specification further as a Recommendation track document, electing to publish it as an informative Working Group Note.

This Note was once published on 6 August 2015 as a First Public Working Group Note. However, after the publication we got comments that the Note's having a shortname of "xpath-dm" was misleading since the Note describes not the whole XPath data model but the XPath data model for SCXML. Therefore this Note is now republished with a clearer shortname of "scxml-xpath-dm" to avoid confusion.

This Note was once published on 6 August 2015 as a First Public Working Group Note. However, after the publication we got comments that the Note's having a shortname of "dom-iop" was misleading since the Note does not belog to the core set of the DOM specifications but describes the DOM I/O processor for SCXML. Therefore this Note is now republished with a clearer shortname of "scxml-dom-iop" to avoid confusion.

XPath_query - 構造化データで実行する XPath クエリです。

XPath について詳しくは、http://www.w3schools.com/xsl/xpath_intro.asp(英語)をご覧ください。

2.3.1.1 XPathPointer Class

XPath Pointer - An expression pointer that makes use of XPath [XPath] expressions to point out parts of a document.

Another common method of selecting elements and content within a resource that supports the Document Object Model (DOM), such as documents in XML or HTML, is to use an XPath selection [DOM-Level-3-XPath]. XPath allows a great deal of flexibility when describing the path through the structure to the selected content. Results are not defined for when an XPath Selector is applied to a representation that does not conform to the DOM.

NOTE

Implementers should note that the HTML5 specification allows parsers to add elements into the DOM that are considered to be missing. XPaths should be constructed to include these elements, rather than from the element structure in the document.

NOTE

Implementers should use only commonly supported features of XPath that directly contribute to selection of an element or content in order to maximize interoperability between systems.

Instance

An element of a group of Resources represented by a particular Class.

YANG relies on XML Path Language (XPath) 1.0 [XPATH] as a notation

for specifying many inter-node references and dependencies. NETCONF

clients and servers are not required to implement an XPath

interpreter, but MUST ensure that the requirements encoded in the

data model are enforced. The manner of enforcement is an

implementation decision. The XPath expressions MUST be syntactically

correct, and all prefixes used MUST be present in the XPath context

(see Section 6.4.1). An implementation may choose to implement them

by hand, rather than using the XPath expression directly.

The mechanism for handling unprefixed names is adopted from XPath 2.0

[XPATH2.0], and helps simplify XPath expressions in YANG. No

ambiguity may ever arise because YANG node identifiers are always

qualified names with a non-null namespace URI.

Document type declarations (see Section 2.8 of

[W3C.REC-xml-20001006]) MUST NOT appear in NETCONF content.

<condition> (optional)

An XPath boolean expression along with a conditional interval of time, in minutes, that must elapse between updates if the expression evaluates to true.