Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed #511 and a few minor markup errors #912

Merged
merged 1 commit into from
Nov 17, 2019
Merged

Fixed #511 and a few minor markup errors #912

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions xproc/src/main/xml/specification.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -472,7 +472,7 @@ remove the <code>serialization</code> property
<para>XProc 3.0 has been designed to make it possible to process any kind of
document. Each document has a representation in the <biblioref linkend="xpath-datamodel"/>.
This is necessary so that any kind of document can be passed as an argument to XPath functions,
such as <tag>p:document-properties</tag>.
such as <function>p:document-properties</function>.
Practically speaking, there are five kinds of documents:</para>

<orderedlist>
Expand Down Expand Up @@ -1692,6 +1692,19 @@ of a document as a map.</para>
associated with the <parameter>doc</parameter> specified. If the item
is not associated with a document, the resulting map will be empty.</para>

<para>Document properties are associated with documents that flow out
of steps. Documents loaded with XPath functions or through other
out-of-band means may not have properties associated with them. In
order to provide a consistent interface for pipeline authors, the
base URI of a node is always returned in the <code>base-uri</code>
property and the <code>content-type</code> property always contains at
least the most general appropriate content type
(<code>application/xml</code> for any XML node,
<code>text/plain</code> for any text node, and
<code>application/octet-stream</code> if no more specific type is
known).
</para>

<para>The <function>p:document-properties</function> function behaves
normally during static analysis.</para>
</section>
Expand Down Expand Up @@ -6261,7 +6274,7 @@ draft:</para>

<itemizedlist>
<listitem>
<para>The <function>p:document-properties-document()</function> function was removed</para>
<para>The <code>p:document-properties-document()</code> function was removed</para>
</listitem>
<listitem>
<para>The semantics of <tag>p:if</tag> have been changed. If the test expression is false, <tag>p:if</tag>
Expand Down