<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" version="2.0">
  <channel>
    <title>Matevž Gačnik's Weblog - Articles</title>
    <link>https://www.request-response.com/blog/</link>
    <description>Technology Philanthropy</description>
    <image>
      <url>http://www.request-response.com/blog/images/favicon.jpg</url>
      <title>Matevž Gačnik's Weblog - Articles</title>
      <link>https://www.request-response.com/blog/</link>
    </image>
    <language>en-us</language>
    <copyright>Matevz Gacnik</copyright>
    <lastBuildDate>Thu, 05 Mar 2026 07:02:09 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.1.8102.813</generator>
    <managingEditor>matevz.gacnik@gmail.com</managingEditor>
    <webMaster>matevz.gacnik@gmail.com</webMaster>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=93b456f5-4db8-478b-9420-215a0e6e4157</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,93b456f5-4db8-478b-9420-215a0e6e4157.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,93b456f5-4db8-478b-9420-215a0e6e4157.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=93b456f5-4db8-478b-9420-215a0e6e4157</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Apple’s M‑series processors have historically followed a monolithic design philosophy.
Each generation from M1 through M4 relied on a single die that integrated CPU cores,
GPU cores, memory controllers, and specialized accelerators into a unified system
on chip. With the introduction of the M5 Pro and M5 Max processors, Apple has fundamentally
altered this approach.
</p>
        <p>
The company has introduced a modular design methodology now, in 2026, known as <b>Fusion
Architecture</b>.
</p>
        <img border="0" src="https://www.request-response.com/blog/content/binary/Apple-M5-Pro-M5-Max-chips-260303_big.jpg.large.jpg" />
        <p>
Fusion Architecture represents the first structural redesign of Apple Silicon since
the debut of <b>the M1 in 2020</b>. Instead of manufacturing one large die, Apple
now constructs high‑end processors from multiple silicon dies bonded together into
a single logical system. This shift reflects broader trends in semiconductor engineering
driven by manufacturing limits, cost constraints, and the rapidly growing computational
requirements of artificial intelligence workloads.
</p>
        <b>Historical Context: The Monolithic Apple Silicon Strategy</b>
        <p>
When Apple introduced the M1 processor in 2020, the company redefined personal computing
processor architecture. The M1 integrated CPU, GPU, Neural Engine, and memory controllers
onto a single die while introducing the unified memory architecture. This architecture
allowed all compute components to access a shared memory pool without copying data
between discrete subsystems.
</p>
        <p>
This design delivered several advantages including reduced memory latency, improved
energy efficiency, higher effective bandwidth between compute units, and simplified
software optimization. The M1 architecture quickly proved successful and subsequent
generations including M2, M3, and M4 followed the same structural model while incrementally
improving process nodes, core counts, and bandwidth.
</p>
        <p>
However, this design philosophy carried a significant limitation. As workloads increased,
particularly those related to large language models and machine learning inference,
chip complexity and die size began to scale rapidly. Larger dies are significantly
harder to manufacture reliably because even a single defect renders the entire chip
unusable.
</p>
        <b>The Semiconductor Industry Shift Toward Chiplets</b>
        <p>
Apple is not alone in confronting the physical limits of monolithic chips. The semiconductor
industry has broadly transitioned toward chiplet architectures where processors are
composed of several smaller dies interconnected <b>within a single package</b>.
</p>
        <p>
Major vendors have already adopted this strategy. AMD employs chiplet designs in Ryzen
and EPYC processors. Intel uses advanced packaging techniques such as embedded multi‑die
interconnect bridge and Foveros stacking. NVIDIA constructs its largest AI accelerators
using multi‑die packaging.
</p>
        <p>
The economic rationale behind chiplets is straightforward. Manufacturing several smaller
dies is more cost efficient than producing one extremely large die because yield rates
improve significantly. Industry analyses indicate that modular chiplet designs can
deliver comparable computational capability at dramatically lower manufacturing cost.
</p>
        <p>
This transition marks the gradual decline of the traditional monolithic processor
model.
</p>
        <i>Apple’s Approach: Fusion Architecture</i>
        <p>
Apple’s response to these constraints is Fusion Architecture.
</p>
        <p>
Rather than simply replicating existing dies and connecting them together, Apple has
designed a modular structure where individual dies perform distinct functional roles.
These dies are physically bonded using high bandwidth interconnect technology and
presented to the operating system as a single logical processor.
</p>
        <p>
The critical design requirement Apple preserved is unified memory. Even though the
processor now spans multiple dies, Apple maintains a shared memory architecture that
allows all compute units to operate on the same dataset without explicit data transfers.
</p>
        <p>
While Apple has not publicly disclosed the full technical implementation of cross
die memory coherence, the company claims the architecture preserves the same software
model as earlier M series chips. From the perspective of applications and operating
systems, the processor behaves as a single unified system.
</p>
        <i>Structural Design of the M5 Pro and M5 Max</i>
        <p>
The first processors implementing Fusion Architecture are the <b>M5 Pro</b> and <b>M5
Max</b>. Both chips consist of two separate dies connected through high speed packaging
technology. The first die is identical in both processors and contains the majority
of the system control components.
</p>
        <i>Primary Die</i>
        <p>
The first die includes an 18 core CPU cluster, a 16 core Neural Engine, the SSD controller,
and Thunderbolt I O controllers. This die effectively functions as the computational
and system management foundation of the processor.
</p>
        <i>Secondary Die</i>
        <p>
The second die differentiates the two processors.
</p>
        <p>
The M5 Pro configuration includes up to 20 GPU cores, a single media engine, and a
memory controller delivering up to 307 GB per second bandwidth. The M5 Max configuration
includes up to 40 GPU cores, dual media engines, and a memory controller delivering
up to 614 GB per second bandwidth.
</p>
        <p>
This design enables Apple <b>to scale GPU and media performance independently from
the CPU subsystem</b>. In principle, additional GPU focused dies could be added in
future designs to extend compute capacity without redesigning the entire processor.
</p>
        <b>Architectural Changes in CPU Design</b>
        <p>
The CPU configuration of the M5 generation introduces another major structural change.
Earlier M series chips relied on a hybrid architecture combining performance cores
with efficiency cores.
</p>
        <p>
The M5 Pro and M5 Max abandon efficiency cores entirely and instead implement a two
tier high performance structure.
</p>
        <p>
The CPU cluster consists of six super cores optimized for peak single thread performance
and twelve performance cores optimized for high multithread throughput. This creates
an all performance architecture designed for sustained computational workloads rather
than energy optimized background processing.
</p>
        <p>
The naming scheme has also evolved. What were previously called performance cores
in earlier M series chips are now referred to as super cores. The new performance
cores represent an intermediate tier that prioritizes throughput while maintaining
strong efficiency characteristics.
</p>
        <p>
This structure closely resembles the strategy used by AMD in its Zen 5 and Zen 5c
core architecture.
</p>
        <i>GPU Evolution and AI Acceleration</i>
        <p>
Another significant development is the integration of neural accelerators within each
GPU core.
</p>
        <p>
Although the GPU core counts remain unchanged from the previous generation, each core
now includes dedicated hardware for machine learning computation. This allows the
GPU to perform both graphics processing and AI inference tasks.
</p>
        <p>
Apple claims this architecture enables up to four times the AI compute capability
without increasing the overall GPU core count.
</p>
        <p>
This reflects a broader shift in processor design. GPUs are evolving into general
purpose parallel compute engines <b>where graphics workloads represent only one category
of computation</b>.
</p>
        <i>Memory Bandwidth Scaling</i>
        <p>
Large AI models require extremely high memory bandwidth to deliver acceptable inference
performance. Apple has continued to increase bandwidth across successive M series
generations. The M5 generation extends this trend. The M5 Pro reaches 307 GB per second
memory bandwidth while the M5 Max reaches 614 GB per second. Both figures represent
improvements over the M4 generation.
</p>
        <p>
Bandwidth scaling is particularly important for local inference of large language
models. High bandwidth allows large parameter sets to be accessed efficiently by GPU
and neural compute units. This suggests Apple is designing these processors with the
expectation that laptops will increasingly run advanced AI models locally rather than
relying solely on cloud infrastructure.
</p>
        <i>Strategic Implications of Fusion Architecture</i>
        <p>
Fusion Architecture is not revolutionary in the sense that multi die packaging already
exists across the semiconductor industry. However, it represents a critical strategic
transition for Apple Silicon. The key significance lies in scalability. By demonstrating
that unified memory and high performance interconnects can function across multiple
dies, Apple removes the traditional constraint of die size. Future processors can
scale horizontally by combining additional specialized dies <b>rather than enlarging
a single monolithic chip</b>.
</p>
        <p>
This opens several potential directions for future development including additional
GPU dies for AI acceleration, specialized machine learning dies, and advanced multi
package configurations for workstation and server workloads. The packaging technology
used to bond these dies is similar to the interconnect technologies used in modern
AI servers. Apple has effectively brought data center class packaging techniques into
consumer laptop processors.
</p>
        <b>So..</b>
        <p>
The M1 generation introduced a radical rethinking of personal computing processors
through unified memory and system level integration. Subsequent generations refined
that architecture while maintaining the monolithic design.
</p>
        <p>
Fusion Architecture represents the next phase of <b>Apple Silicon (r)evolution</b>.
Author notes the reader to remember 2020 and how revolutionary the <b>M1</b> Apple
Silicon architecture actually was.
</p>
        <p>
Instead of competing with the physical limits of monolithic chips, Apple is adopting
a modular strategy that preserves its core architectural principles while enabling
future scalability. Multi die packaging allows the company <b>to expand computational
capability without incurring the manufacturing penalties</b> associated with extremely
large silicon dies.
</p>
        <p>
The immediate performance gains of the M5 generation are important but the more significant
development is architectural. Fusion Architecture establishes the structural foundation
upon which future Apple processors will be built.
</p>
        <p>
In practical terms, the question is no longer how large a single Apple Silicon chip
can become. The real question is how many modular components Apple can connect together
while maintaining the unified architecture that has defined the platform since the
M1.
</p>
        <img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=93b456f5-4db8-478b-9420-215a0e6e4157" />
      </body>
      <title>Apple Fusion Architecture: The Structural Evolution of Apple Silicon</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,93b456f5-4db8-478b-9420-215a0e6e4157.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,93b456f5-4db8-478b-9420-215a0e6e4157.aspx</link>
      <pubDate>Thu, 05 Mar 2026 07:02:09 GMT</pubDate>
      <description>&lt;p&gt;
Apple’s M‑series processors have historically followed a monolithic design philosophy.
Each generation from M1 through M4 relied on a single die that integrated CPU cores,
GPU cores, memory controllers, and specialized accelerators into a unified system
on chip. With the introduction of the M5 Pro and M5 Max processors, Apple has fundamentally
altered this approach.
&lt;/p&gt;
&lt;p&gt;
The company has introduced a modular design methodology now, in 2026, known as &lt;b&gt;Fusion
Architecture&lt;/b&gt;.
&lt;/p&gt;
&lt;img border="0" src="https://www.request-response.com/blog/content/binary/Apple-M5-Pro-M5-Max-chips-260303_big.jpg.large.jpg"&gt; 
&lt;p&gt;
Fusion Architecture represents the first structural redesign of Apple Silicon since
the debut of &lt;b&gt;the M1 in 2020&lt;/b&gt;. Instead of manufacturing one large die, Apple
now constructs high‑end processors from multiple silicon dies bonded together into
a single logical system. This shift reflects broader trends in semiconductor engineering
driven by manufacturing limits, cost constraints, and the rapidly growing computational
requirements of artificial intelligence workloads.
&lt;/p&gt;
&lt;b&gt;Historical Context: The Monolithic Apple Silicon Strategy&lt;/b&gt; 
&lt;p&gt;
When Apple introduced the M1 processor in 2020, the company redefined personal computing
processor architecture. The M1 integrated CPU, GPU, Neural Engine, and memory controllers
onto a single die while introducing the unified memory architecture. This architecture
allowed all compute components to access a shared memory pool without copying data
between discrete subsystems.
&lt;/p&gt;
&lt;p&gt;
This design delivered several advantages including reduced memory latency, improved
energy efficiency, higher effective bandwidth between compute units, and simplified
software optimization. The M1 architecture quickly proved successful and subsequent
generations including M2, M3, and M4 followed the same structural model while incrementally
improving process nodes, core counts, and bandwidth.
&lt;/p&gt;
&lt;p&gt;
However, this design philosophy carried a significant limitation. As workloads increased,
particularly those related to large language models and machine learning inference,
chip complexity and die size began to scale rapidly. Larger dies are significantly
harder to manufacture reliably because even a single defect renders the entire chip
unusable.
&lt;/p&gt;
&lt;b&gt;The Semiconductor Industry Shift Toward Chiplets&lt;/b&gt; 
&lt;p&gt;
Apple is not alone in confronting the physical limits of monolithic chips. The semiconductor
industry has broadly transitioned toward chiplet architectures where processors are
composed of several smaller dies interconnected &lt;b&gt;within a single package&lt;/b&gt;.
&lt;/p&gt;
&lt;p&gt;
Major vendors have already adopted this strategy. AMD employs chiplet designs in Ryzen
and EPYC processors. Intel uses advanced packaging techniques such as embedded multi‑die
interconnect bridge and Foveros stacking. NVIDIA constructs its largest AI accelerators
using multi‑die packaging.
&lt;/p&gt;
&lt;p&gt;
The economic rationale behind chiplets is straightforward. Manufacturing several smaller
dies is more cost efficient than producing one extremely large die because yield rates
improve significantly. Industry analyses indicate that modular chiplet designs can
deliver comparable computational capability at dramatically lower manufacturing cost.
&lt;/p&gt;
&lt;p&gt;
This transition marks the gradual decline of the traditional monolithic processor
model.
&lt;/p&gt;
&lt;i&gt;Apple’s Approach: Fusion Architecture&lt;/i&gt; 
&lt;p&gt;
Apple’s response to these constraints is Fusion Architecture.
&lt;/p&gt;
&lt;p&gt;
Rather than simply replicating existing dies and connecting them together, Apple has
designed a modular structure where individual dies perform distinct functional roles.
These dies are physically bonded using high bandwidth interconnect technology and
presented to the operating system as a single logical processor.
&lt;/p&gt;
&lt;p&gt;
The critical design requirement Apple preserved is unified memory. Even though the
processor now spans multiple dies, Apple maintains a shared memory architecture that
allows all compute units to operate on the same dataset without explicit data transfers.
&lt;/p&gt;
&lt;p&gt;
While Apple has not publicly disclosed the full technical implementation of cross
die memory coherence, the company claims the architecture preserves the same software
model as earlier M series chips. From the perspective of applications and operating
systems, the processor behaves as a single unified system.
&lt;/p&gt;
&lt;i&gt;Structural Design of the M5 Pro and M5 Max&lt;/i&gt; 
&lt;p&gt;
The first processors implementing Fusion Architecture are the &lt;b&gt;M5 Pro&lt;/b&gt; and &lt;b&gt;M5
Max&lt;/b&gt;. Both chips consist of two separate dies connected through high speed packaging
technology. The first die is identical in both processors and contains the majority
of the system control components.
&lt;/p&gt;
&lt;i&gt;Primary Die&lt;/i&gt; 
&lt;p&gt;
The first die includes an 18 core CPU cluster, a 16 core Neural Engine, the SSD controller,
and Thunderbolt I O controllers. This die effectively functions as the computational
and system management foundation of the processor.
&lt;/p&gt;
&lt;i&gt;Secondary Die&lt;/i&gt; 
&lt;p&gt;
The second die differentiates the two processors.
&lt;/p&gt;
&lt;p&gt;
The M5 Pro configuration includes up to 20 GPU cores, a single media engine, and a
memory controller delivering up to 307 GB per second bandwidth. The M5 Max configuration
includes up to 40 GPU cores, dual media engines, and a memory controller delivering
up to 614 GB per second bandwidth.
&lt;/p&gt;
&lt;p&gt;
This design enables Apple &lt;b&gt;to scale GPU and media performance independently from
the CPU subsystem&lt;/b&gt;. In principle, additional GPU focused dies could be added in
future designs to extend compute capacity without redesigning the entire processor.
&lt;/p&gt;
&lt;b&gt;Architectural Changes in CPU Design&lt;/b&gt; 
&lt;p&gt;
The CPU configuration of the M5 generation introduces another major structural change.
Earlier M series chips relied on a hybrid architecture combining performance cores
with efficiency cores.
&lt;/p&gt;
&lt;p&gt;
The M5 Pro and M5 Max abandon efficiency cores entirely and instead implement a two
tier high performance structure.
&lt;/p&gt;
&lt;p&gt;
The CPU cluster consists of six super cores optimized for peak single thread performance
and twelve performance cores optimized for high multithread throughput. This creates
an all performance architecture designed for sustained computational workloads rather
than energy optimized background processing.
&lt;/p&gt;
&lt;p&gt;
The naming scheme has also evolved. What were previously called performance cores
in earlier M series chips are now referred to as super cores. The new performance
cores represent an intermediate tier that prioritizes throughput while maintaining
strong efficiency characteristics.
&lt;/p&gt;
&lt;p&gt;
This structure closely resembles the strategy used by AMD in its Zen 5 and Zen 5c
core architecture.
&lt;/p&gt;
&lt;i&gt;GPU Evolution and AI Acceleration&lt;/i&gt; 
&lt;p&gt;
Another significant development is the integration of neural accelerators within each
GPU core.
&lt;/p&gt;
&lt;p&gt;
Although the GPU core counts remain unchanged from the previous generation, each core
now includes dedicated hardware for machine learning computation. This allows the
GPU to perform both graphics processing and AI inference tasks.
&lt;/p&gt;
&lt;p&gt;
Apple claims this architecture enables up to four times the AI compute capability
without increasing the overall GPU core count.
&lt;/p&gt;
&lt;p&gt;
This reflects a broader shift in processor design. GPUs are evolving into general
purpose parallel compute engines &lt;b&gt;where graphics workloads represent only one category
of computation&lt;/b&gt;.
&lt;/p&gt;
&lt;i&gt;Memory Bandwidth Scaling&lt;/i&gt; 
&lt;p&gt;
Large AI models require extremely high memory bandwidth to deliver acceptable inference
performance. Apple has continued to increase bandwidth across successive M series
generations. The M5 generation extends this trend. The M5 Pro reaches 307 GB per second
memory bandwidth while the M5 Max reaches 614 GB per second. Both figures represent
improvements over the M4 generation.
&lt;/p&gt;
&lt;p&gt;
Bandwidth scaling is particularly important for local inference of large language
models. High bandwidth allows large parameter sets to be accessed efficiently by GPU
and neural compute units. This suggests Apple is designing these processors with the
expectation that laptops will increasingly run advanced AI models locally rather than
relying solely on cloud infrastructure.
&lt;/p&gt;
&lt;i&gt;Strategic Implications of Fusion Architecture&lt;/i&gt; 
&lt;p&gt;
Fusion Architecture is not revolutionary in the sense that multi die packaging already
exists across the semiconductor industry. However, it represents a critical strategic
transition for Apple Silicon. The key significance lies in scalability. By demonstrating
that unified memory and high performance interconnects can function across multiple
dies, Apple removes the traditional constraint of die size. Future processors can
scale horizontally by combining additional specialized dies &lt;b&gt;rather than enlarging
a single monolithic chip&lt;/b&gt;.
&lt;/p&gt;
&lt;p&gt;
This opens several potential directions for future development including additional
GPU dies for AI acceleration, specialized machine learning dies, and advanced multi
package configurations for workstation and server workloads. The packaging technology
used to bond these dies is similar to the interconnect technologies used in modern
AI servers. Apple has effectively brought data center class packaging techniques into
consumer laptop processors.
&lt;/p&gt;
&lt;b&gt;So..&lt;/b&gt; 
&lt;p&gt;
The M1 generation introduced a radical rethinking of personal computing processors
through unified memory and system level integration. Subsequent generations refined
that architecture while maintaining the monolithic design.
&lt;/p&gt;
&lt;p&gt;
Fusion Architecture represents the next phase of &lt;b&gt;Apple Silicon (r)evolution&lt;/b&gt;.
Author notes the reader to remember 2020 and how revolutionary the &lt;b&gt;M1&lt;/b&gt; Apple
Silicon architecture actually was.
&lt;/p&gt;
&lt;p&gt;
Instead of competing with the physical limits of monolithic chips, Apple is adopting
a modular strategy that preserves its core architectural principles while enabling
future scalability. Multi die packaging allows the company &lt;b&gt;to expand computational
capability without incurring the manufacturing penalties&lt;/b&gt; associated with extremely
large silicon dies.
&lt;/p&gt;
&lt;p&gt;
The immediate performance gains of the M5 generation are important but the more significant
development is architectural. Fusion Architecture establishes the structural foundation
upon which future Apple processors will be built.
&lt;/p&gt;
&lt;p&gt;
In practical terms, the question is no longer how large a single Apple Silicon chip
can become. The real question is how many modular components Apple can connect together
while maintaining the unified architecture that has defined the platform since the
M1.
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=93b456f5-4db8-478b-9420-215a0e6e4157" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,93b456f5-4db8-478b-9420-215a0e6e4157.aspx</comments>
      <category>AI</category>
      <category>Apple</category>
      <category>Articles</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=0810e768-87db-427f-9c26-8668c34348bd</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,0810e768-87db-427f-9c26-8668c34348bd.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,0810e768-87db-427f-9c26-8668c34348bd.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=0810e768-87db-427f-9c26-8668c34348bd</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Terence Tao is another remarkable figure who deserves a Nobel Prize. However, since
there isn't a Nobel Prize for mathematics, the highest honor he can receive is the
Fields Medal, which he has already won. 
<br /><br />
Amadeus #Mozart, go Bob Dylan!
</p>
[1] <a href="https://en.wikipedia.org/wiki/Fields_Medal&#xA;" target="_blank">https://en.wikipedia.org/wiki/Fields_Medal</a><br /><br />
His: <a href="https://terrytao.wordpress.com" target="_blank">BLOG</a> | <a href="https://www.math.ucla.edu/~tao" target="_blank">OFFICIAL</a> | <a href="https://ww3.math.ucla.edu/professor-terence-tao-receives-2022-grand-medaille-of-the-french-academy-of-sciences/" target="_blank">AWARD</a><br /><br /><img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=0810e768-87db-427f-9c26-8668c34348bd" /></body>
      <title>Terence Tao</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,0810e768-87db-427f-9c26-8668c34348bd.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,0810e768-87db-427f-9c26-8668c34348bd.aspx</link>
      <pubDate>Fri, 28 Jun 2024 03:56:50 GMT</pubDate>
      <description>&lt;p&gt;
Terence Tao is another remarkable figure who deserves a Nobel Prize. However, since
there isn't a Nobel Prize for mathematics, the highest honor he can receive is the
Fields Medal, which he has already won. 
&lt;br /&gt;
&lt;br /&gt;
Amadeus #Mozart, go Bob Dylan!
&lt;/p&gt;
[1] &lt;a href="https://en.wikipedia.org/wiki/Fields_Medal
" target="_blank"&gt;https://en.wikipedia.org/wiki/Fields_Medal&lt;/a&gt; 
&lt;br /&gt;
&lt;br /&gt;
His: &lt;a href="https://terrytao.wordpress.com" target="_blank"&gt;BLOG&lt;/a&gt; | &lt;a href="https://www.math.ucla.edu/~tao" target="_blank"&gt;OFFICIAL&lt;/a&gt; | &lt;a href="https://ww3.math.ucla.edu/professor-terence-tao-receives-2022-grand-medaille-of-the-french-academy-of-sciences/" target="_blank"&gt;AWARD&lt;/a&gt; 
&lt;br /&gt;
&lt;br /&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=0810e768-87db-427f-9c26-8668c34348bd" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,0810e768-87db-427f-9c26-8668c34348bd.aspx</comments>
      <category>Articles</category>
      <category>Personal</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=27ffb21b-3123-4f8c-b8b6-69151629e81c</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,27ffb21b-3123-4f8c-b8b6-69151629e81c.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,27ffb21b-3123-4f8c-b8b6-69151629e81c.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=27ffb21b-3123-4f8c-b8b6-69151629e81c</wfw:commentRss>
      <title>On Bosons and Morons</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,27ffb21b-3123-4f8c-b8b6-69151629e81c.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,27ffb21b-3123-4f8c-b8b6-69151629e81c.aspx</link>
      <pubDate>Sat, 10 Feb 2024 11:10:30 GMT</pubDate>
      <description>&lt;p&gt;
It finally happened. Pfeew!
&lt;/p&gt;
Article link: &lt;a href="content/binary/bosonsmorons.pdf" target="_blank"&gt;On Bosons
and Morons&lt;/a&gt; 
&lt;p&gt;
&lt;img width="500" src="images/bosonsmorons.png" border: 5px solid #444&gt;&gt;&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=27ffb21b-3123-4f8c-b8b6-69151629e81c" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,27ffb21b-3123-4f8c-b8b6-69151629e81c.aspx</comments>
      <category>AI</category>
      <category>Articles</category>
      <category>Parody</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=0dc65305-0d10-4ddd-b07c-a5a6150a61fc</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,0dc65305-0d10-4ddd-b07c-a5a6150a61fc.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,0dc65305-0d10-4ddd-b07c-a5a6150a61fc.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=0dc65305-0d10-4ddd-b07c-a5a6150a61fc</wfw:commentRss>
      <slash:comments>2</slash:comments>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Having dropped all my current articles, this post is intended to sum it all up.
</p>
        <p>
XML and XML Schema territory:
</p>
        <ul>
          <li>
Type Systems Compared - XML &lt;&gt; CLR (XML, XML Schema, CLR) [<a href="http://www.request-response.com/blog/PermaLink,guid,baaf6646-162a-4557-9d7e-10e4953ab627.aspx">Preview</a>, <a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmlclrtypesystem.doc">Download</a>]</li>
          <li>
The Importance of XML Typization (XML, XML Schema) [<a href="http://www.request-response.com/blog/PermaLink,guid,d6531997-2522-4136-ae25-2c4ec349fa27.aspx">Preview</a>, <a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmltypization.doc">Download</a>]</li>
          <li>
XML Namespaces and PSVI Problems (XML, XML Schema) [<a href="http://www.request-response.com/blog/PermaLink,guid,ae74f150-da30-4ea0-a944-cd70daef0025.aspx">Preview</a>, <a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmlnamespacespsvi.doc">Download</a>]</li>
          <li>
XML Schema - Specification Primer (I/II) (XML, XML Schema) [<a href="http://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx">Preview</a>, <a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmlschema1.doc">Download</a>]</li>
          <li>
XML Schema - Specification Primer (II/II) (XML, XML Schema) [<a href="http://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx">Preview</a>, <a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmlschema2.doc">Download</a>]</li>
        </ul>
        <p>
WinFX territory:
</p>
        <ul>
          <li>
Concepts and Semantics of Service Contracts (WCF) [<a href="http://www.request-response.com/blog/PermaLink,guid,25e8d68b-09ff-46e8-b360-ecd5128aa90c.aspx">Preview</a>, <a href="http://www.request-response.com/blog/content/binary/matevzgacnik-servicecontracts.doc">Download</a>]</li>
          <li>
Transactional Semantics in Loosely Coupled Distributed Systems (WCF) [<a href="http://www.request-response.com/blog/PermaLink,guid,a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620.aspx">Preview</a>, <a href="http://www.request-response.com/blog/content/binary/matevzgacnik-transactionalservices.doc">Download</a>]</li>
          <li>
Cooperation Between Workflows and Services (WCF, ASMX, WF) [<a href="http://www.request-response.com/blog/PermaLink,guid,86bd92f2-13fd-4454-ab88-272a4a8be875.aspx">Preview</a>, <a href="http://www.request-response.com/blog/content/binary/matevzgacnik-workflowsservices.doc">Download</a>]</li>
        </ul>
        <p>
Article language: <strong>Slovenian</strong></p>
        <img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=0dc65305-0d10-4ddd-b07c-a5a6150a61fc" />
      </body>
      <title>Article Summary: May 2006</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,0dc65305-0d10-4ddd-b07c-a5a6150a61fc.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,0dc65305-0d10-4ddd-b07c-a5a6150a61fc.aspx</link>
      <pubDate>Wed, 07 Jun 2006 09:47:53 GMT</pubDate>
      <description>&lt;p&gt;
Having dropped all my current articles, this post is intended to sum it all up.
&lt;/p&gt;
&lt;p&gt;
XML and XML Schema territory:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
Type Systems Compared - XML &amp;lt;&amp;gt; CLR (XML, XML Schema, CLR) [&lt;a href="http://www.request-response.com/blog/PermaLink,guid,baaf6646-162a-4557-9d7e-10e4953ab627.aspx"&gt;Preview&lt;/a&gt;, &lt;a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmlclrtypesystem.doc"&gt;Download&lt;/a&gt;]&lt;/li&gt;
&lt;li&gt;
The Importance of XML Typization (XML, XML Schema) [&lt;a href="http://www.request-response.com/blog/PermaLink,guid,d6531997-2522-4136-ae25-2c4ec349fa27.aspx"&gt;Preview&lt;/a&gt;, &lt;a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmltypization.doc"&gt;Download&lt;/a&gt;]&lt;/li&gt;
&lt;li&gt;
XML Namespaces and PSVI Problems&amp;nbsp;(XML, XML Schema) [&lt;a href="http://www.request-response.com/blog/PermaLink,guid,ae74f150-da30-4ea0-a944-cd70daef0025.aspx"&gt;Preview&lt;/a&gt;, &lt;a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmlnamespacespsvi.doc"&gt;Download&lt;/a&gt;]&lt;/li&gt;
&lt;li&gt;
XML Schema - Specification Primer (I/II) (XML, XML Schema) [&lt;a href="http://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx"&gt;Preview&lt;/a&gt;, &lt;a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmlschema1.doc"&gt;Download&lt;/a&gt;]&lt;/li&gt;
&lt;li&gt;
XML Schema&amp;nbsp;- Specification Primer (II/II) (XML, XML Schema) [&lt;a href="http://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx"&gt;Preview&lt;/a&gt;, &lt;a href="http://www.request-response.com/blog/content/binary/matevzgacnik-xmlschema2.doc"&gt;Download&lt;/a&gt;]&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
WinFX territory:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
Concepts and Semantics of Service Contracts&amp;nbsp;(WCF) [&lt;a href="http://www.request-response.com/blog/PermaLink,guid,25e8d68b-09ff-46e8-b360-ecd5128aa90c.aspx"&gt;Preview&lt;/a&gt;, &lt;a href="http://www.request-response.com/blog/content/binary/matevzgacnik-servicecontracts.doc"&gt;Download&lt;/a&gt;]&lt;/li&gt;
&lt;li&gt;
Transactional Semantics in Loosely Coupled Distributed Systems (WCF)&amp;nbsp;[&lt;a href="http://www.request-response.com/blog/PermaLink,guid,a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620.aspx"&gt;Preview&lt;/a&gt;, &lt;a href="http://www.request-response.com/blog/content/binary/matevzgacnik-transactionalservices.doc"&gt;Download&lt;/a&gt;]&lt;/li&gt;
&lt;li&gt;
Cooperation&amp;nbsp;Between Workflows and Services (WCF, ASMX, WF)&amp;nbsp;[&lt;a href="http://www.request-response.com/blog/PermaLink,guid,86bd92f2-13fd-4454-ab88-272a4a8be875.aspx"&gt;Preview&lt;/a&gt;, &lt;a href="http://www.request-response.com/blog/content/binary/matevzgacnik-workflowsservices.doc"&gt;Download&lt;/a&gt;]&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
Article language: &lt;strong&gt;Slovenian&lt;/strong&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=0dc65305-0d10-4ddd-b07c-a5a6150a61fc" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,0dc65305-0d10-4ddd-b07c-a5a6150a61fc.aspx</comments>
      <category>Articles</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=86bd92f2-13fd-4454-ab88-272a4a8be875</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,86bd92f2-13fd-4454-ab88-272a4a8be875.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,86bd92f2-13fd-4454-ab88-272a4a8be875.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=86bd92f2-13fd-4454-ab88-272a4a8be875</wfw:commentRss>
      <slash:comments>2</slash:comments>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Last article discusses service-workflow cooperation options in <a href="http://msdn.microsoft.com/winfx/">WinFX</a> and
dives into communication scenarios for <a href="http://www.windowsworkflow.net/">Windows
Workflow Foundation</a>.
</p>
        <p>
Language: <strong><em>Slovenian</em></strong></p>
        <hr />
        <p>
Naslov:
</p>
        <p>
          <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-WorkflowsServices.doc">Sodelovanje
storitev in delovnih tokov</a>
        </p>
        <p>
          <em>
            <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-WorkflowsServices.doc">
              <img alt="Sodelovanje storitev in delovnih tokov" hspace="0" src="http://www.request-response.com/blog/images/matevzgacnik-workflowsservices.jpg" align="baseline" border="1" />
            </a>
          </em>
        </p>
        <img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=86bd92f2-13fd-4454-ab88-272a4a8be875" />
      </body>
      <title>Article: Cooperation Between Workflows and Services</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,86bd92f2-13fd-4454-ab88-272a4a8be875.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,86bd92f2-13fd-4454-ab88-272a4a8be875.aspx</link>
      <pubDate>Wed, 07 Jun 2006 09:29:02 GMT</pubDate>
      <description>&lt;p&gt;
Last article discusses&amp;nbsp;service-workflow cooperation&amp;nbsp;options in &lt;a href="http://msdn.microsoft.com/winfx/"&gt;WinFX&lt;/a&gt; and
dives into communication scenarios for &lt;a href="http://www.windowsworkflow.net/"&gt;Windows
Workflow Foundation&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Language:&amp;nbsp;&lt;strong&gt;&lt;em&gt;Slovenian&lt;/em&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;
Naslov:
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-WorkflowsServices.doc"&gt;Sodelovanje
storitev in delovnih tokov&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-WorkflowsServices.doc"&gt;&lt;img alt="Sodelovanje storitev in delovnih tokov" hspace=0 src="http://www.request-response.com/blog/images/matevzgacnik-workflowsservices.jpg" align=baseline border=1&gt;&lt;/a&gt;&lt;/em&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=86bd92f2-13fd-4454-ab88-272a4a8be875" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,86bd92f2-13fd-4454-ab88-272a4a8be875.aspx</comments>
      <category>Articles</category>
      <category>.NET 3.0 - WCF</category>
      <category>.NET 3.0 - WF</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <a href="http://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx">Last
article</a> finished my XML series. This one focuses on transactional semantics in
a service oriented universe.
</p>
        <p>
Language: <strong><em>Slovenian</em></strong></p>
        <hr />
        <p>
Naslov:
</p>
        <p>
          <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-TransactionalServices.doc">Transakcijska
semantika v šibko sklopljenih, porazdeljenih sistemih</a>
        </p>
        <p>
          <em>
            <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-TransactionalServices.doc">
              <img alt="Transakcijska semantika v šibko sklopljenih, porazdeljenih sistemih" hspace="0" src="http://www.request-response.com/blog/images/matevzgacnik-TransactionalServices.jpg" align="baseline" border="1" />
            </a>
          </em>
        </p>
        <img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620" />
      </body>
      <title>Article: Transactional Semantics in Loosely Coupled Distributed Systems</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620.aspx</link>
      <pubDate>Tue, 06 Jun 2006 08:59:30 GMT</pubDate>
      <description>&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx"&gt;Last
article&lt;/a&gt; finished my XML series. This one focuses on transactional semantics in
a service oriented universe.
&lt;/p&gt;
&lt;p&gt;
Language:&amp;nbsp;&lt;strong&gt;&lt;em&gt;Slovenian&lt;/em&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;
Naslov:
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-TransactionalServices.doc"&gt;Transakcijska
semantika v šibko sklopljenih, porazdeljenih sistemih&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-TransactionalServices.doc"&gt;&lt;img alt="Transakcijska semantika v šibko sklopljenih, porazdeljenih sistemih" hspace=0 src="http://www.request-response.com/blog/images/matevzgacnik-TransactionalServices.jpg" align=baseline border=1&gt;&lt;/a&gt;&lt;/em&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,a40bf4fb-fea6-42c5-a2f2-f0e7dafa3620.aspx</comments>
      <category>.NET 3.0 - WCF</category>
      <category>Architecture</category>
      <category>Articles</category>
      <category>Transactions</category>
      <category>Web Services</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=e77d7831-b76f-4750-a650-1503b425467e</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=e77d7831-b76f-4750-a650-1503b425467e</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Next article in XML series is discussing XML Schema. This is a two part article.
</p>
        <p>
Language: <strong><em>Slovenian</em></strong></p>
        <hr />
        <p>
Naslov:
</p>
        <p>
          <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLSchema1.doc">XML
Schema (1/2)</a>
        </p>
        <p>
          <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLSchema2.doc">XML
Schema (2/2)</a>
        </p>
        <p>
          <img alt="XML Schema" hspace="0" src="http://www.request-response.com/blog/images/matevzgacnik-xmlschema.jpg" align="baseline" border="1" />
        </p>
        <img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=e77d7831-b76f-4750-a650-1503b425467e" />
      </body>
      <title>Article: XML Schema - Specification Primer</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx</link>
      <pubDate>Sun, 04 Jun 2006 07:50:18 GMT</pubDate>
      <description>&lt;p&gt;
Next article in XML series is discussing XML Schema. This is a two part article.
&lt;/p&gt;
&lt;p&gt;
Language:&amp;nbsp;&lt;strong&gt;&lt;em&gt;Slovenian&lt;/em&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;
Naslov:
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLSchema1.doc"&gt;XML
Schema (1/2)&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLSchema2.doc"&gt;XML
Schema (2/2)&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;img alt="XML Schema" hspace=0 src="http://www.request-response.com/blog/images/matevzgacnik-xmlschema.jpg" align=baseline border=1&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=e77d7831-b76f-4750-a650-1503b425467e" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,e77d7831-b76f-4750-a650-1503b425467e.aspx</comments>
      <category>Articles</category>
      <category>XML</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=ae74f150-da30-4ea0-a944-cd70daef0025</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,ae74f150-da30-4ea0-a944-cd70daef0025.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,ae74f150-da30-4ea0-a944-cd70daef0025.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=ae74f150-da30-4ea0-a944-cd70daef0025</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Next article in XML series is discussing XML Namespaces and PSVI problems.
</p>
        <p>
Language: <strong><em>Slovenian</em></strong></p>
        <hr />
        <p>
Naslov:
</p>
        <p>
          <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLNamespacesPSVI.doc">Imenski
prostori XML in problemi v PSVI</a>
        </p>
        <p>
          <em>
            <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLNamespacesPSVI.doc">
              <img alt="Imenski prostori XML in problemi v PSVI" hspace="0" src="http://www.request-response.com/blog/images/matevzgacnik-xmlnamespacespsvi.jpg" align="baseline" border="1" />
            </a>
          </em>
        </p>
        <img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=ae74f150-da30-4ea0-a944-cd70daef0025" />
      </body>
      <title>Article: XML Namespaces and PSVI Problems</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,ae74f150-da30-4ea0-a944-cd70daef0025.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,ae74f150-da30-4ea0-a944-cd70daef0025.aspx</link>
      <pubDate>Sat, 03 Jun 2006 10:50:01 GMT</pubDate>
      <description>&lt;p&gt;
Next article in XML series is discussing XML Namespaces and PSVI problems.
&lt;/p&gt;
&lt;p&gt;
Language:&amp;nbsp;&lt;strong&gt;&lt;em&gt;Slovenian&lt;/em&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;
Naslov:
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLNamespacesPSVI.doc"&gt;Imenski
prostori XML in problemi v PSVI&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLNamespacesPSVI.doc"&gt;&lt;img alt="Imenski prostori XML in problemi v PSVI" hspace=0 src="http://www.request-response.com/blog/images/matevzgacnik-xmlnamespacespsvi.jpg" align=baseline border=1&gt;&lt;/a&gt;&lt;/em&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=ae74f150-da30-4ea0-a944-cd70daef0025" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,ae74f150-da30-4ea0-a944-cd70daef0025.aspx</comments>
      <category>Articles</category>
      <category>XML</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=d6531997-2522-4136-ae25-2c4ec349fa27</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,d6531997-2522-4136-ae25-2c4ec349fa27.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,d6531997-2522-4136-ae25-2c4ec349fa27.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=d6531997-2522-4136-ae25-2c4ec349fa27</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
This article is starting the XML series. First we dive into XML typization importance
and XML Infoset.
</p>
        <p>
Language: <strong><em>Slovenian</em></strong></p>
        <hr />
        <p>
Naslov:
</p>
        <p>
          <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLTypization.doc">Pomembnost
tipizacije XML</a>
        </p>
        <p>
          <em>
            <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLTypization.doc">
              <img alt="Pomembnost tipizacije XML" hspace="0" src="http://www.request-response.com/blog/images/matevzgacnik-xmltypization.jpg" align="baseline" border="1" />
            </a>
          </em>
        </p>
        <img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=d6531997-2522-4136-ae25-2c4ec349fa27" />
      </body>
      <title>Article: The Importance of XML Typization</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,d6531997-2522-4136-ae25-2c4ec349fa27.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,d6531997-2522-4136-ae25-2c4ec349fa27.aspx</link>
      <pubDate>Sat, 03 Jun 2006 09:29:29 GMT</pubDate>
      <description>&lt;p&gt;
This article is starting the XML series. First we dive into XML typization importance
and XML Infoset.
&lt;/p&gt;
&lt;p&gt;
Language:&amp;nbsp;&lt;strong&gt;&lt;em&gt;Slovenian&lt;/em&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;
Naslov:
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLTypization.doc"&gt;Pomembnost
tipizacije XML&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLTypization.doc"&gt;&lt;img alt="Pomembnost tipizacije XML" hspace=0 src="http://www.request-response.com/blog/images/matevzgacnik-xmltypization.jpg" align=baseline border=1&gt;&lt;/a&gt;&lt;/em&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=d6531997-2522-4136-ae25-2c4ec349fa27" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,d6531997-2522-4136-ae25-2c4ec349fa27.aspx</comments>
      <category>Articles</category>
      <category>XML</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=25e8d68b-09ff-46e8-b360-ecd5128aa90c</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,25e8d68b-09ff-46e8-b360-ecd5128aa90c.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,25e8d68b-09ff-46e8-b360-ecd5128aa90c.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=25e8d68b-09ff-46e8-b360-ecd5128aa90c</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
The second article is about concepts and semantics of service contracts. It deals
with WCF (<a href="http://www.windowscommunication.net">Windows Communication Foundation</a>)
contract definition and its behavioral aspects.
</p>
        <p>
Language: <strong><em>Slovenian</em></strong></p>
        <hr />
        <p>
Naslov:
</p>
        <p>
          <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-ServiceContracts.doc">Koncepti
in semantike storitvenih pogodb</a>
        </p>
        <p>
          <em>
            <a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-ServiceContracts.doc">
              <img alt="Koncepti in semantike storitvenih pogodb" hspace="0" src="http://www.request-response.com/blog/images/matevzgacnik-servicecontracts.jpg" align="baseline" border="1" />
            </a>
          </em>
        </p>
        <img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=25e8d68b-09ff-46e8-b360-ecd5128aa90c" />
      </body>
      <title>Article: Concepts and Semantics of Service Contracts</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,25e8d68b-09ff-46e8-b360-ecd5128aa90c.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,25e8d68b-09ff-46e8-b360-ecd5128aa90c.aspx</link>
      <pubDate>Fri, 02 Jun 2006 18:19:45 GMT</pubDate>
      <description>&lt;p&gt;
The second article is about concepts and semantics of service contracts. It deals
with WCF (&lt;a href="http://www.windowscommunication.net"&gt;Windows Communication Foundation&lt;/a&gt;)
contract definition and its behavioral aspects.
&lt;/p&gt;
&lt;p&gt;
Language:&amp;nbsp;&lt;strong&gt;&lt;em&gt;Slovenian&lt;/em&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;
Naslov:
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-ServiceContracts.doc"&gt;Koncepti
in semantike storitvenih pogodb&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-ServiceContracts.doc"&gt;&lt;img alt="Koncepti in semantike storitvenih pogodb" hspace=0 src="http://www.request-response.com/blog/images/matevzgacnik-servicecontracts.jpg" align=baseline border=1&gt;&lt;/a&gt;&lt;/em&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=25e8d68b-09ff-46e8-b360-ecd5128aa90c" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,25e8d68b-09ff-46e8-b360-ecd5128aa90c.aspx</comments>
      <category>.NET 3.0 - WCF</category>
      <category>Architecture</category>
      <category>Articles</category>
      <category>Web Services</category>
    </item>
    <item>
      <trackback:ping>https://www.request-response.com/blog/Trackback.aspx?guid=baaf6646-162a-4557-9d7e-10e4953ab627</trackback:ping>
      <pingback:server>https://www.request-response.com/blog/pingback.aspx</pingback:server>
      <pingback:target>https://www.request-response.com/blog/PermaLink,guid,baaf6646-162a-4557-9d7e-10e4953ab627.aspx</pingback:target>
      <dc:creator>Matevz Gacnik</dc:creator>
      <wfw:comment>https://www.request-response.com/blog/CommentView,guid,baaf6646-162a-4557-9d7e-10e4953ab627.aspx</wfw:comment>
      <wfw:commentRss>https://www.request-response.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=baaf6646-162a-4557-9d7e-10e4953ab627</wfw:commentRss>
      <slash:comments>1</slash:comments>
      <title>Article: Type Systems Compared, XML, CLR</title>
      <guid isPermaLink="false">https://www.request-response.com/blog/PermaLink,guid,baaf6646-162a-4557-9d7e-10e4953ab627.aspx</guid>
      <link>https://www.request-response.com/blog/PermaLink,guid,baaf6646-162a-4557-9d7e-10e4953ab627.aspx</link>
      <pubDate>Thu, 01 Jun 2006 13:38:54 GMT</pubDate>
      <description>&lt;p&gt;
I'm going to publish a series of my articles, which went out the door a couple of
months ago.
&lt;/p&gt;
&lt;p&gt;
All articles are in &lt;strong&gt;&lt;em&gt;Slovene language&lt;/em&gt;&lt;/strong&gt;.
&lt;/p&gt;
&lt;p&gt;
Here goes the first one.
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;
Naslov:
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLCLRTypeSystem.doc"&gt;Tipski
sistem XML &amp;lt;&amp;gt; Tipski sistem CLR&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;&lt;a href="http://www.request-response.com/blog/content/binary/MatevzGacnik-XMLCLRTypeSystem.doc"&gt;&lt;img alt="Tipski sistem XML &lt;&gt; Tipski sistem CLR" hspace=0 src="http://www.request-response.com/blog/images/matevzgacnik-xmlclrtypesystem.jpg" align=baseline border=1&gt;&lt;/a&gt;&lt;/em&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="https://www.request-response.com/blog/aggbug.ashx?id=baaf6646-162a-4557-9d7e-10e4953ab627" /&gt;</description>
      <comments>https://www.request-response.com/blog/CommentView,guid,baaf6646-162a-4557-9d7e-10e4953ab627.aspx</comments>
      <category>Articles</category>
      <category>CLR</category>
      <category>XML</category>
    </item>
  </channel>
</rss>