Class,Type,Subtype,URI Scheme(s),Functional Specification,Security Considerations,Intended Usage,Enumservice Specification(s),Requester(s),Further Information
"Application-Based, Ancillary",acct,N/A,acct,"This Enumservice indicates that the resource
can be identified by the associated 'acct' URI [RFC7565].","For DNS considerations in avoiding loops when
searching for ""acct"" NAPTRs,
see [RFC7566], Section 6.
For security considerations,
see [RFC7566], Section 7.",COMMON,[RFC7566],[Laurent_Walter_Goix],
"Application-Based, Common",email,mailto,mailto,"This Enumservice indicates that the resource can be
addressed by the associated URI in order to send an
email.","See [RFC4355], Section 6.",COMMON,"[RFC4355]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]",
"Application-Based, Common",ems,mailto,mailto,"This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol. EMS content is sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4, as an MMS message. Within
such a message, EMS content is carried as either a
text or application/octet-stream MIME sub-part (see
TS 26.140 [16], Section 4.1). For references see [RFC4355].","There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of [RFC4355] apply.",COMMON,"[RFC4355]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]",
"Application-Based, Common",ems,tel,tel,"This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Enhanced Message
Service (EMS) [14] (For reference see
[RFC4355]).","There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of [RFC4355] apply.",COMMON,"[RFC4355]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]","Note that an indication of EMS can be taken as
implying that the recipient is capable of receiving
SMS messages at this address as well."
"Application-Based, Subset",fax,tel,tel,"This Enumservice indicates that the resource
identified by the associated URI is capable
of being contacted to provide a communication
session during which facsimile documents can be
sent. A client selecting this NAPTR will have support
for generating and sending facsimile documents to
the recipient using the PSTN session and transfer
protocols specified in [12] and [13] in
[RFC4355] -
in short, they will have a fax program with a local
or shared PSTN access over which they can send
faxes. References are contained in [RFC4355].","See [RFC4355], Section 6.",COMMON,"[RFC4355]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]",
"Application-Based, Subset",ft,ftp,ftp,"This Enumservice indicates that the resource
identified by the associated URI is a file
service from which a file or file listing can be
retrieved.","See [RFC4002], Section 5.",COMMON,"[RFC4002]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]",
Protocol-Based,h323,N/A,h323,"See [RFC3762], Section 3.","See [RFC3762], Section 5.",COMMON,"[RFC3762]
[RFC6118]",[Orit_Levin],
Protocol-Based,iax,N/A,iax,"The 'iax' Enumservice is used to map E.164 numbers to
IAX URIs. Such URIs identify resources capable of being
contacted to provide a communication session using the
IAX protocol [RFC5456]. A client selecting this NAPTR needs to be able to support
communication utilizing the IAX protocol.","See [RFC6315], Section 4.",COMMON,[RFC6315],"[Ed_Guy]
[Klaus_Darilion]",
"Application-Based, Common",ical-access,http,http,"This Enumservice indicates that the resource identified
can be addressed by the associated URI in order to access
a user's calendar (for example free/busy status) using
the CalDAV [7] protocol for Internet calendaring. References are contained in [RFC5333].","See [RFC5333], Section 4.",COMMON,"[RFC5333]
[RFC6118]",[Rohan_Mahy],
"Application-Based, Common",ical-access,https,https,"This Enumservice indicates that the resource identified
can be addressed by the associated URI in order to access
a user's calendar (for example free/busy status) using
the CalDAV [7] protocol for Internet calendaring. References are contained in [RFC5333].","See [RFC5333], Section 4.",COMMON,"[RFC5333]
[RFC6118]",[Rohan_Mahy],
"Application-Based, Common",ical-sched,mailto,mailto,"This Enumservice indicates that the resource identified
can be addressed by the associated URI used for
scheduling using Internet calendaring via Internet mail
with the iMIP [6] protocol. References are contained in [RFC5333].","See [RFC5333], Section 4.",COMMON,"[RFC5333]
[RFC6118]",[Rohan_Mahy],
"Application-Based, Subset",ifax,mailto,mailto,"See [RFC4143], Section 1.","See [RFC4143], Section 3.",COMMON,"[RFC4143]
[RFC6118]","[Kiyoshi_Toyoda]
[Dave_Crocker]","The URI Scheme is 'mailto' because facsimile is a
profile of standard Internet mail and uses standard
Internet mail addressing."
"Application-Based, Common",im,N/A,im,"This Enumservice indicates that the resource
identified is an 'im:' URI. The 'im:' URI scheme
does not identify any particular protocol that will
be used to handle instant messaging receipt or
delivery, rather the mechanism in RFC3861 [4] is
used to discover whether an IM protocol supported by
the party querying ENUM is also supported by the
target resource. References are contained in [RFC5028].","See [RFC5028], Section 3.",COMMON,"[RFC5028]
[RFC6118]",[Rohan_Mahy],
"Application-Based, Common",mms,mailto,mailto,"This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol. MMS messages are sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4. Within and between MMS Environments (MMSE,
network infrastructures that support the MultiMedia
Service), other pieces of state data (for example,
charging-significant information) are exchanged
between MMS Relay Servers. Thus, although these
servers use SMTP as the ""bearer"" for their
application exchanges, they map their internal state
to specialized header fields carried in the SMTP message
exchanges. The header fields used in such MMSE are
described in detail in [17]. For references see [RFC4355].","There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of [RFC4355] apply.",COMMON,"[RFC4355]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]","The MMS Architecture describes an interface
between the MMSE and ""legacy messaging systems""
(labelled as MM3) which accepts ""standard"" SMTP
messages. Thus although the MMS Relay Server that
supports this interface appears as a standard SMTP
server from the perspective of an Internet-based
mail server, it acts as a gateway and translator,
adding the internal state data that is used within
and between the MMS Environments. This mechanism is
described in [17], which also includes references to
the specifications agreed by those bodies
responsible for the design of the MMS. References are contained in [RFC4355]."
"Application-Based, Common",mms,tel,tel,"This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Multimedia
Messaging Service (MMS) [15]. For references see [RFC4355].","There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of [RFC4355] apply.",COMMON,"[RFC4355]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]","Note that MMS can be used as an alternative to
deliver an SMS RP-DATA RPDU if, for example, the
SMS bearer is not supported. If an entry includes
this Enumservice, then in effect this can be taken
as implying that the recipient is capable of
receiving EMS or SMS messages at this address. Such
choices on the end system de do have two small
caveats; whilst in practice all terminals supporting
MMS today support SMS as well, it might not
necessarily be the case in the future, and there may
be tariff differences in using the MMS rather than
using the SMS or EMS."
"Application-Based, Common",pres,N/A,pres,"See [RFC3953], Section 4.","See [RFC3953], Section 6.",COMMON,"[RFC3953]
[RFC6118]",[Jon_Peterson],"See [RFC3953], Section 3."
"Application-Based, Common",pstn,sip,sip,"These Enumservices indicate that the
resource identified can be addressed by the
associated URI in order to initiate a
telecommunication session, which may include two-way
voice or other communications, to the PSTN.","See [RFC4769], Section 7.",COMMON,"[RFC4769]
[RFC6118]","[Jason_Livingood]
[Richard_Shockey]","A Number Portability Dip Indicator (npdi) should
be used in practice
(see [RFC4769], Section 4)."
"Application-Based, Ancillary",pstn,tel,tel,"These Enumservices indicate that the
resource identified can be addressed by the
associated URI in order to initiate a
telecommunication session, which may include two-way
voice or other communications, to the PSTN. These
URIs may contain number portability data as
specified in RFC4694 [10]. References are contained in [RFC4769].","See [RFC4769], Section 7.",COMMON,"[RFC4769]
[RFC6118]","[Jason_Livingood]
[Richard_Shockey]","A Number Portability Dip Indicator (npdi) should
be used in practice
(see [RFC4769], Section 4)."
Protocol-Based,sip,N/A,"sip, sips","See [RFC3764], Section 4.","See [RFC3764], Section 6.",COMMON,"[RFC3764]
[RFC6118]",[Jon_Peterson],"See [RFC3764], Section 3."
"Application-Based, Common",sms,mailto,mailto,"This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol. SMS content is sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4, as an MMS message. Within
such a message, SMS content is carried as either a
text or application/octet-stream MIME sub-part (see
TS 26.140 [16], Section 4.1) For references see [RFC4355]","There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of [RFC4355] apply.",COMMON,"[RFC4355]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]",
"Application-Based, Common",sms,tel,tel,"This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Short Message
Service (SMS) [14] in [RFC4355].","There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of [RFC4355] apply.",COMMON,"[RFC4355]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]",
"Application-Based, Common",unifmsg,http,http,"This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information. Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource. References are contained in [RFC5278].","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",unifmsg,https,https,"This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol. Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource. References are contained in [RFC5278].","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",unifmsg,sip,sip,"This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a unified communication session to a unified
messaging system.","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",unifmsg,sips,sips,"This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a unified communication session to a unified
messaging system.","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
Data Type-Based,vcard,N/A,"http, https","This Enumservice indicates that the resource
identified is a plain vCard, according to RFC2426,
which may be accessed using HTTP / HTTPS [7]. Clients fetching the vCard from the resource
indicated should expect access to be
restricted. Additionally, the comprehension of the
data provided may vary depending on the client's
identity. References are contained in [RFC4969].","See [RFC4969], Section 5.",COMMON,"[RFC4969]
[RFC6118]",[Alexander_Mayrhofer],
"Application-Based, Common",videomsg,http,http,"This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information. Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource. References are contained in [RFC5278].","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",videomsg,https,https,"This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol. Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource. References are contained in [RFC5278].","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",videomsg,sip,sip,"This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a video communication session to a video messaging
system.","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",videomsg,sips,sips,"This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a video communication session to a video messaging
system.","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",voice,tel,tel,"The kind of communication indicated by this
Enumservice is ""Interactive Voice"". From a protocol
perspective, this communication is expected to
involve bidirectional media streams carrying audio
data. A client may imply that the person controlling
population of a NAPTR holding this Enumservice
indicates their capability to engage in an
interactive voice session when contacted using the
URI generated by this NAPTR.","See [RFC4415], Section 5.",COMMON,"[RFC4415]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]","This Enumservice indicates that the person
responsible for the NAPTR is accessible via the PSTN
(Public Switched Telephone Network) or PLMN (Public
Land Mobile Network) using the value of the
generated URI. The kind of subsystem required to initiate a
Voice Enumservice with this Subtype is a ""Dialler"".
This is a subsystem that either provides a local
connection to the PSTN or PLMN, or that provides an
indirect connection to those networks. The
subsystem will use the telephone number held in the
generated URI to place a voice call. The voice call
is placed to a network that uses E.164 numbers to
route calls to an appropriate destination. Note that the PSTN/PLMN connection may be
indirect. The end user receiving this NAPTR may
have a relationship with a Communications Service
Provider that accepts call initiation requests from
that subsystem using an IP-based protocol such as
SIP or H.323, and places the call to the PSTN using
a remote gateway service. In this case the Provider
may either accept requests using ""tel:"" URIs or has
a defined mechanism to convert ""tel:"" URI values
into a ""protocol-native"" form. The ""tel:"" URI value SHOULD be fully qualified
(using the ""global phone number"" form of RFC3966
[10]). A ""local phone number"" as defined in that
document SHOULD NOT be used unless the controller of
the zone in which the NAPTR appears is sure that it
can be distinguished unambiguously by all clients
that can access the resource record and that a call
from their network access points can be routed to
that destination. References are contained in [RFC4415]."
"Application-Based, Common",voicemsg,http,http,"This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information. Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even voice message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource. References are contained in [RFC5278].","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",voicemsg,https,https,"This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol. Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even voice message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource. References are contained in [RFC5278].","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",voicemsg,sip,sip,"This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",voicemsg,sips,sips,"This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
"Application-Based, Common",voicemsg,tel,tel,"This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.","See [RFC5278], Section 3.",COMMON,"[RFC5278]
[RFC6118]","[Jason_Livingood]
[Don_Troshynski]","Implementers should review a non-exclusive list of examples
in Section 7 of [RFC5278]."
Data Type-Based,vpim,ldap,ldap,"See [RFC4238], Section 3.2 - 3.3.","Malicious Redirection:
One of the fundamental dangers related to any
service such as this is that a malicious entry in a
resolver's database will cause clients to resolve
the E.164 into the wrong LDAP URI. The possible
intent may be to cause the client to connect to a
rogue LDAP server and retrieve (or fail to retrieve)
a resource containing fraudulent or damaging
information. Denial of Service:
By removing the URI to which the E.164 maps, a
malicious intruder may remove the client's ability
to access the LDAP directory server.",COMMON,"[RFC4238]
[RFC6118]",[Greg_Vaudreuil],
Data Type-Based,vpim,mailto,mailto,"See [RFC4238], Section 4.2 - 4.4.","Malicious Redirection:
One of the fundamental dangers related to any
service such as this is that a malicious entry in a
resolver's database will cause clients to resolve
the E.164 into the wrong email URI. The possible
intent may be to cause the client to send the
information to an incorrect destination. Denial of Service:
By removing the URI to which the E.164 maps, a
malicious intruder may remove the client's ability
to access the resource. Unsolicited Bulk Email:
The exposure of email addresses through the ENUM
service provides a bulk mailer access to large
numbers of email addresses where only the telephone
number was previously known.",COMMON,"[RFC4238]
[RFC6118]",[Greg_Vaudreuil],"Error Conditions: E.164 number not in the numbering plan E.164 number in the numbering plan, but no
URIs exist for that number E2U+vpim:mailto Service unavailable of email
addresses where only the telephone number was
previously known."
"Application-Based, Common",web,http,http,"This Enumservice indicates that the resource
identified by the associated URI is capable
of being a source of information. It has to be
noted that the kind of information retrieved can be
manifold. Usually, contacting a resource by an
""http:"" URI provides a document. This document can
contain references that will trigger download of
many different kinds of information, like audio or
video or executable code. Thus, one can not be more
specific about the kind of information that can be
expected when contacting the resource.","See [RFC4002], Section 5.",COMMON,"[RFC4002]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]",
"Application-Based, Common",web,https,https,"This Enumservice indicates that the resource
identified by the associated URI is capable
of being a source of information, which can be
contacted by using TLS or Secure Socket Layer
protocol. It has to be noted that the kind of
information retrieved can be manifold. Usually,
contacting a resource by an ""https:"" URI provides a
document. This document can contain all different
kind of information, like audio or video or
executable code. Thus, one can not be more specific
what information to expect when contacting the
resource.","See [RFC4002], Section 5.",COMMON,"[RFC4002]
[RFC6118]","[Rudolf_Brandner]
[Lawrence_Conroy]
[Richard_Stastny]",
Protocol-Based,xmpp,N/A,xmpp,"This Enumservice indicates that the resource
identified is an XMPP entity.","See [RFC4979], Section 6.",COMMON,"[RFC4979]
[RFC6118]",[Alexander_Mayrhofer],
Presently we were in a very dark road, and at a point where it dropped suddenly between steep sides we halted in black shadow. A gleam of pale sand, a whisper of deep flowing waters, and a farther glimmer of more sands beyond them challenged our advance. We had come to a "grapevine ferry." The scow was on the other side, the water too shoal for the horses to swim, and the bottom, most likely, quicksand. Out of the blackness of the opposite shore came a soft, high-pitched, quavering, long-drawn, smothered moan of woe, the call of that snivelling little sinner the screech-owl. Ferry murmured to me to answer it and I sent the same faint horror-stricken tremolo back. Again it came to us, from not farther than one might toss his cap, and I followed Ferry down to the water's edge. The grapevine guy swayed at our side, we heard the scow slide from the sands, and in a few moments, moved by two videttes, it touched our shore. Soon we were across, the two videttes riding with us, and beyond a sharp rise, in an old opening made by the swoop of a hurricane, we entered the silent unlighted bivouac of Ferry's scouts. Ferry got down and sat on the earth talking with Quinn, while the sergeants quietly roused the sleepers to horse. Plotinus is driven by this perplexity to reconsider the whole theory of Matter.477 He takes Aristotle¡¯s doctrine as the groundwork of his investigation. According to this, all existence is divided into Matter and Form. What we know of things¡ªin other words, the sum of their differential characteristics¡ªis their Form. Take away this, and the unknowable residuum is their Matter. Again, Matter is the vague indeterminate something out of which particular Forms are developed. The two are related as Possibility to Actuality, as the more generic to the more specific substance through every grade of classification and composition. Thus there are two Matters, the one sensible and the other intelligible. The former constitutes the common substratum of bodies, the other the common element of ideas.478 The general distinction between Matter and Form was originally suggested to Aristotle by Plato¡¯s remarks on the same subject; but he differs325 from his master in two important particulars. Plato, in his Timaeus, seems to identify Matter with space.479 So far, it is a much more positive conception than the ?λη of the Metaphysics. On the other hand, he constantly opposes it to reality as something non-existent; and he at least implies that it is opposed to absolute good as a principle of absolute evil.480 Thus while the Aristotelian world is formed by the development of Power into Actuality, the Platonic world is composed by the union of Being and not-Being, of the Same and the Different, of the One and the Many, of the Limit and the Unlimited, of Good and Evil, in varying proportions with each other. The Lawton woman had heard of an officer's family at Grant, which was in need of a cook, and had gone there. [See larger version] On the 8th of July an extraordinary Privy Council was summoned. All the members, of whatever party, were desired to attend, and many were the speculations as to the object of their meeting. The general notion was that it involved the continuing or the ending of the war. It turned out to be for the announcement of the king's intended marriage. The lady selected was Charlotte, the second sister of the Duke of Mecklenburg-Strelitz. Apart from the narrowness of her education, the young princess had a considerable amount of amiability, good sense, and domestic taste. These she shared with her intended husband, and whilst they made the royal couple always retiring, at the same time they caused them to give, during their lives, a moral air to their court. On the 8th of September Charlotte arrived at St. James's, and that afternoon the marriage took place, the ceremony being performed by the Archbishop of Canterbury. On the 22nd the coronation took place with the greatest splendour. Mother and girls were inconsolable, for each had something that they were sure "Si would like," and would "do him good," but they knew Josiah Klegg, Sr., well enough to understand what was the condition when he had once made up his mind. CHAPTER V. THE YOUNG RECRUITS Si proceeded to deftly construct a litter out of the two guns, with some sticks that he cut with a knife, and bound with pawpaw strips. His voice had sunk very low, almost to sweetness. A soft flurry of pink went over her face, and her eyelids drooped. Then suddenly she braced herself, pulled herself taut, grew combative again, though her voice shook. HoME²Ô¾®Ïè̫ʲôÐÇ×ù
ENTER NUMBET 0016idwnet.com.cn
www.jxylw888.org.cn
kbchain.com.cn
liaomai.org.cn
kxotki.com.cn
hping.com.cn
www.kdamen.com.cn
pwlxex.com.cn
www.qhchain.com.cn
www.vxnews.com.cn