Main

related bits

0

processing priority

4

site type

3 (personal blog or private political site, e.g. Blogspot, Substack, also small blogs on own domains)

review version

11

html import

20 (imported)

Events

first seen date

2025-01-15 00:46:11

expired found date

-

created at

2025-01-15 00:46:10

updated at

2025-07-26 20:26:56

Domain name statistics

length

20

crc

30471

tld

2211

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

69893241 (blogspot.com)

previous id

0

replaced with id

0

related id

-

dns primary id

0

dns alternative id

0

lifecycle status

0 (unclassified, or currently active)

Subdomains and pages

deleted subdomains

0

page imported products

0

page imported random

0

page imported parking

0

Error counters

count skipped due to recent timeouts on the same server IP

0

count content received but rejected due to 11-799

0

count dns errors

0

count cert errors

0

count timeouts

0

count http 429

0

count http 404

0

count http 403

0

count http 5xx

0

next operation date

-

Server

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

65531

mp size raw text

28780

mp inner links count

58

mp inner links status

10 (links queued, awaiting import)

Open Graph

title

description

image

site name

author

updated

2026-03-01 21:12:29

raw text

Making SOA Real Making SOA Real An SOA odyssey Thursday, June 21, 2007 Integrated Concepts This posting passed on by a colleague I find particularly interesting as it relates to our SOA implementation. The idea is that the four concepts: Enterprise Canonical Data Model Canonical Message Schema Event Driven Architecture Business Event Ontology are intimately related and the post goes through the touch points for each. What I appreciate here is the separation of the canonical data model from the canonical message schema. In our implementation we create XSD to represent the business entities (analogous to the enterprise canonical data model) and then wrap various parts of these in XSD when creating the response, request, and acknowledgement message contracts (canonical message schemas). But although we have a handle on these concepts I think it's important to really keep an eye on raising the visibility of the canonical data model from within the project team ...

Text analysis

redirect type

35 (location.replace)

block type

0 (no issues)

detected language

1 (English)

category id

SEC and Crypto [en] (228)

index version

2026022801

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

22982

text words

4768

text unique words

1387

text lines

254

text sentences

143

text paragraphs

44

text words per sentence

33

text matched phrases

2

text matched dictionaries

8

RSS

rss status

32 (unknown)

rss found date

2025-01-15 00:46:12

rss size orig

160551

rss items

25

rss spam phrases

0

rss detected language

1 (English)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap status

40 (completed successful import of reports.txt file to table in_pages)

sitemap review version

2

sitemap urls count

49

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

0

sitemap found date

2025-01-15 00:46:11

sitemap process date

2025-03-24 15:20:55

sitemap first import date

-

sitemap last import date

2025-07-26 20:26:56