[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [legalxml-econtracts] Agenda for upcoming meeting from the OASIS Legal XML Member Section Electronic Contracts Technical Committee Secretary (File id: @@2204)
The referenced URL (for the DC Requirements) for todays meeting contains href's that were inappropriately inserted whenever that file was posted to the LegalXML website. I have attached a version that removes those, and makes for easy hyperlinking within the document. >-----Original Message----- >From: Dr. Laurence Leff [mailto:D-Leff@wiu.edu] >Sent: Sunday, July 13, 2003 3:25 PM >To: legalxml-econtracts@lists.oasis-open.org >Subject: [legalxml-econtracts] Agenda for upcoming meeting from the >OASIS Legal XML Member Section Electronic Contracts Technical Committee >Secretary (File id: @@2204) > > ><H1><CENTER>Agenda for Conference Call</CENTER></H1> ><H1><Center>Electronic Contracts Technical Committee of the</CENTER></H1> ><H1><Center>OASIS Legal XML Member Section</CENTER></H1> > > <H1><CENTER>July 16th </CENTER></H1> > <H1><CENTER>18:00 Eastern</CENTER></H1> > <H1><CENTER>Dial 512 225 3050 - Use 84759# for Pin >Code</CENTER></H1> > ><P> >18:00:00 Wed Jul 16 2003 in America/New_York converts to >22:00:00 Wed Jul 16 2003 in GMT ></P> ><OL> ><LI> >Welcome and Roll Call ><LI> >Approval of draft Minutes for the meetings of June 18th and July 2nd ><BR> >Discuss the Scenario ><A >href="http://www.oasis-open.org/apps/org/workgroup/legalxml-econtracts/ >download.php/2037/dataconsortium.html"> >Data Consortium Contract Schema ></A> ><LI> >Discuss the Clause Model (no more than fifteen minutes) ><LI> >New Business ></OL> > >You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/legalxml-econtracts/members/leave_w orkgroup.phpTitle: OASIS LEGALXML ECONTRACTS TC - DATA CONSORTIUM REQUIREMENTS
OASIS LegalXML eContracts TC RequirementsScenario - Contract Information Requirements
IntroductionThis document contains requirements from the Data Consortium (http://www.dataconsortium.org/) that we request be implemented by the initial standard being crafted by the OASIS LegalXML eContracts Technical Committee. The Data Consortium represents the commercial real estate industry in the United States, and is allied with the PISCES organization, a similar group of commercial real estate stakeholders in the United Kingdom and Europe. The Data Consortium also has extensive ties within the United States to fraternal groups, most notably the Appraisal Institute and the National Council of Real Estate Investment Fiduciaries. All members of the Data Consortium have a strong interest in the standards being developed by the OASIS LegalXML eContract Technical Committee because significant savings and new services are expected in our industry as a direct result of creating a standard that supports an arms-length exchange of contract documents. Our request for consideration of our requirements is made as a fellow OASIS organization and, accordingly, we offer our services and industry experience to the Technical Committee as it moves forward from the requirements process through implementation and standardization. We expect to submit a companion "use case scenario" which is concerned with the extraction of information from a legal contract. As per the requirements process, contributions to this scenario are welcome. Please send your contributions to John McClure. The preferred format for comments is a marked-up version of this document, using <ins> and <del> elements to identify text changes you'd like to see. Scenario StatementThe objective of this scenario is to identify the information in a contract which the Data Consortium wants to extract, usually for reason of updating databases concerned with the management of real estate properties and facilities. The information elements identified here are those contained within the contracts themselves, that is, this document has merely a passing interest in process-related information as it occurrs during the formation and administration of the contract. Rather, the focus here is entirely on the content of the contract as agreed to by the parties. There are numerous legal documents involved with the daily conduct of commercial real estate operations. Our focus here is on our two bedrock documents — leases and purchase contracts — which we believe would herald the industry's greatest and most immediate benefit from following a standardization process. We are interested in standards that relate to not only the original contract but, in the case of leases, also to contract renewals. In fact, leases themselves can be considered almost to be an archetype for most other contracts, because (a) leases detail a recurring relationship over time between the parties, not just a to a specific action, as in a transfer of property (b) leases do often include purchases or expectations of goods and services between lessor and lessee (c) leases do involve the specification of rights that are granted by the lessor to the lessee (e) leases can include debt instruments such as promissory notes (f) leases have discernible contract execution, performance, settlement, renewal, and default terms and (g) many lease contracts include options to purchase, or a grant of purchase. What does the real estate professional do, today, with the executed lease contract? The most common answer is that the scope of information then abstracted from the contract is dependent on the schema of the databases that are to be updated. Most databases in the commercial real estate industry today are relational databases, that is, they are a rigid information structure which do not accommodate the flowed text which this group expects to annotate with XML markup. In short, the industry transfers selected fields of information from the contract to databases that drive facilities management and accounting functions. Clearly, this process can be improved by converting the contract into a database itself that drives the facilities management and accounting functions of a commercial real estate management company. In order for this to happen, however, all information in the contract must be annotated with XML tags. Often, certain information in the contract serves multiple purposes and, hence, this information must be simultaneously tagged with multiple XML tags. By doing so, introduction of new or improved services will no longer depend on the information abstracted from a contract, because that step will have been eliminated. Table of SchemaeAppurtenance ContingencyTerm ContingentEvent Goodwill UnitPricing UnitPricingTerm UnitQuantity UnitQuantityTerm Tax TaxTerm TermsOfEvidence TermsOfLiability TermsOfRestriction AcceptanceEvent AcceptanceFailure AcceptanceFailureTerm AcceptanceTerm ActualValue AddendedContract Addendum Address AddressLine AfterDate AfterDateTime AfterTime Agent AsOfDateTime Attachment Author BackMatter BeforeDate BeforeDateTime BeforeTime BeginTextTerm BillingEvent BillingFailure BillingFailureTerm BillingTerm Body BusinessName CancellationEvent CancellationFailure CancellationFailureTerm CancellationTerm Caption CaptionHeading CaptionNumber CaptionNumberHeading Carrier Cell Charge ChargeTerm CityName Claimant Claimee Clause CollectionEvent CollectionFailure CollectionFailureTerm CollectionTerm Column Contact Content Contract ContractDate ContractDateTime ContractCancellationEvent ContractCancellationTerm ContractExecutionEvent ContractExecutionTerm ContractLitigationEvent ContractLitigationTerm ContractRenewalEvent ContractRenewalTerm ContractSettlementEvent ContractSettlementTerm ContractTime CreateDateTime CreditEvent CreditFailure CreditFailureTerm CreditTerm Customer Date DeliveryEvent DeliveryFailure DeliveryFailureTerm DeliveryTerm Description Discount DiscountTerm Distributor Editor EffectiveDate EffectiveDateTime EffectiveTime EmailAddress EndTextTerm Escalation EscalationTerm EscrowEvent EscrowFailure EscrowFailureTerm EscrowTerm EstimatedValue ExchangeEvent ExchangeFailure ExchangeFailureTerm ExchangeTerm ExpirationDate ExpirationDateTime ExpirationTime FamilyName Figure FirstFigure FirstName Folder Frequency FrontMatter FullName GivenName Goods Grantee Grantor GroupItem GroupName HomeAddress IndexTable InstallationEvent InstallationFailure InstallationFailureTerm InstallationTerm InstitutionName Installer Invoicee Invoicer Landlord LastEditDateTime LastFigure LastName LegalName LegalParty MaintenanceEvent MaintenanceFailure MaintenanceFailureTerm MaintenanceTerm MajorItem Manager Manufacturer Metadata MinorItem ModificationEvent ModificationFailure ModificationFailureTerm ModificationTerm Name NamePrefix NameSuffix NotAfterDate NotAfterDateTime NotAfterTime NotBeforeDate NotBeforeDateTime NotBeforeTime Offeree Offerer OrdinalBaseDate OrdinalDay OrdinalMonth OrdinalYear OrganizationName OtherName Page PageArea PageNumberHeading PageOrientation Pagination Paragraph Payee Payer PerformanceEvent PerformanceFailure PerformanceFailureTerm PerformanceTerm Premises PreviousValue PrePaymentEvent PrePaymentFailure PrePaymentFailureTerm PrePaymentTerm ProcurementEvent ProcurementFailure ProcurementFailureTerm ProcurementTerm ProductionEvent ProductionFailure ProductionFailureTerm ProductionTerm PurchaseEvent PurchaseFailure PurchaseFailureTerm PurchaseTerm Purchaser Recipient ReimbursementEvent ReimbursementFailure ReimbursementFailureTerm ReimbursementTerm RemittanceEvent RemittanceFailure RemittanceFailureTerm RemittanceTerm Renter RequisitionEvent RequisitionFailure RequisitionFailureTerm RequisitionTerm Retailer Row ScheduledAcceptance ScheduledBilling ScheduledCancellation ScheduledCollection ScheduledCredit ScheduledDelivery ScheduledEscrow ScheduledEvent ScheduledExchange ScheduledInstallation ScheduledMaintenance ScheduledModification ScheduledPrePayment ScheduledProcurement ScheduledProduction ScheduledPurchase ScheduledReimbursement ScheduledRemittance ScheduledRequisition ScheduledSurrender ScheduledUse Section Seller Service ServiceProvder StateName StatePostalCode SubAmount SubClause SubParagraph SubPart SubSection SubTotal Superior Supplier SurrenderEvent SurrenderFailure SurrenderFailureTerm SurrenderTerm Table Time Title TotalAmount Type UnorderedContent UseEvent UseFailure UseFailureTerm UseTerm Watermark Wholesaler WorkAddress ZipCode amount date dateTime duration integer gDay gMonth gYear integer name nameRef text time uriContract Information RequirementsThe following requirements have been determined from analysis of the structure and content of commercial real estate leases. Contract SchemaContracts range from simple memoranda of renewals to multi-section, multi-addendum, masterpieces of legal artistry. One important aim of the schema for a Contract is to avoid forcing drafters of simple contracts to structure their contracts in a manner appropriate only to complex contracts. Complex contracts require a higher degree of normalization (of "nesting") of their information, primarily to facilitate formatting the document for printing and viewing. Simple contracts however, have little need other than to directly identify the parameters of the contract, without the "nesting". For instance, the Body of a Contract can be explicitly stated, complete with embedded text, or it can be implied for text embedded at the level of the contract itself.
amount SchemaAn amount string is a decimal string that is to be interpreted as an amount of currency. The specific currency is indicated either by the currency associated with the item's container or the datastream itself. A more specific set of elements indicating a specific currency, is provided at http://www.hypergrove.com/Publications/Symbols.html. For example, amounts in US Dollars would use "usd" rather than "amount". date SchemaA date string, as defined by XML Schema, is a string conforming to CCYY-MM-DD format. dateTime SchemaA dateTime string, as defined by XML Schema, is a string conforming to CCYY-MM-DDTHH:MM:SS format. gDay SchemaA gDay string, as defined by XML Schema, is a string whose content ranges from 1 through 31. gMonth SchemaA gDay string, as defined by XML Schema, is a string whose content ranges from 1 through 12. gYear SchemaA gYear string, as defined by XML Schema, is a string whose content ranges from 1 through 9999. name SchemaA name string identifies the "name" associated with an information object.
For instance, to show that "Mr. Jones (defined as 'Agent.2') is the agent for
Mr. Smith (who is defined as 'Purchaser.1'), and Mr. Smith's agent is Mr. Jones"
would be coded as: Similarly, to show that a Payee is Mr. Jones:
nameRef SchemaA string that identifies the "name" associated with a referenced information object. See name for more information. text SchemaA text string contains a separately addressable set of text characters. The specific language of the text string is indicated either by the language associated with the container or the datastream itself. A more specific set of elements indicating a specific language, is provided at http://www.hypergrove.com/Publications/Symbols.html. For example, strings of English text would use "en" or "eng" rather than "text". time SchemaA time string, as defined by XML Schema, is a string conforming to HH:MM:SS format. uri SchemaA uri string identifies the Universal Resource Identifier of an information object. AcceptanceTerm SchemaAn AcceptanceTerm describes an acceptance of goods or service that is contemplated by a Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a successful Acceptance. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
AcceptanceEvent SchemaIn the context of a Contract or Addendum, An AcceptanceEvent describes an acceptance of goods or service. The charges, discounts, escalations, and taxes specified by an AcceptanceEvent are those levied as a result of the acceptance. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Purchaser SchemaA Purchaser is a type of Contact, and inherits all its characteristics. Additional items are noted here. AcceptanceFailure SchemaAn AcceptanceFailure describes an Acceptance of goods or service that was not made by a Recipient. The charges, discounts, escalations, and taxes are levied as a result of the failure to perform the Acceptance or render the service. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
AcceptanceFailureTerm SchemaAn AcceptanceFailureTerm describes a term concerning the failure of an acceptance of delivered goods or services that is contemplated by a Contract or Addendum. The charges, discounts, escalations, and taxes are to be levied should a failure of acceptance occur. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledAcceptance SchemaA ScheduledAcceptance identifies a schedule for one or more acceptances of delivered goods or service. A ScheduledAcceptance can be described in the context of a Contract or Addendum; or in the context of a AcceptanceTerm within a Contract or Addendum. This term is a sub-type of ScheduledEvent and inherits all its characteristics. Addendum SchemaAn Addendum is located either within BackMatter or the Body of a Contract; within the Contract itself; or within another Addendum. Often an addendum is separately paginated from its surrounding material. Functionally, an Addendum can be either a "container" for another contract, or it may be itself a contract. As a contract itself, it is composed of all the information specified for a Contract, and as a container, it would merely contain a (single) Contract within it. When the Addendum contains a Contract, it may not simultaneously contain other information.
Address Schema
AddressLine1, AddressLine2, and AddressLine3 SchemaAn AddressLine contains a text string. CityName SchemaA CityName contains a text string. StateName SchemaA StateName contains a text string. StatePostalCode SchemaA StatePostalCode contains a text string. ZipCode SchemaA ZipCode contains a text string. Attachment SchemaAn Attachment is located either within BackMatter of a Contract or an Addendum to the Contract; or within the Contract itself. Often an attachment is separately paginated from its surrounding material. Functionally, an Attachment contains material that may be germaine to the contract, but is not part of the contract between its parties. An Attachment can be a legal exhibit such as a Certificate of Occupancy or it can be a non-legal exhibit such as a drawing. Because the attachment is not a part of the contract, no attempt is made here to identify contractual terms or contractually-relevant declarations within it. Nevertheless, for the purposes of formatting the contract with its included attachments, its document parts are identified.
BackMatter SchemaBackMatter in a Contract, Addendum, or Attachment identifies material that is often separately paginated from its FrontMatter and Body.
BillingTerm SchemaA BillingTerm describes an invoicing of goods or services that are contemplated by a Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those that can be levied within an invoice. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
BillingEvent SchemaIn the context of a Contract or Addendum, a BillingEvent describes an invoicing (for goods and services) that has been made or attempted. The charges, discounts, escalations, and taxes specified by a BillingEvent are those levied by a specific invoice. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Invoicee SchemaAn Invoicee is a type of Contact, and inherits all its characteristics. Additional items are noted here. Invoicer SchemaAn Invoicer is a type of Contact, and inherits all its characteristics. Additional items are noted here. BillingFailure SchemaA BillingFailure describes the goods and services not invoiced that are contemplated by a Contract or Addendum. The charges, discounts, escalations, and taxes are those that would have been invoiced. This term is a sub-type of PerformanceFailure and inherits all its characteristics. BillingFailureTerm SchemaA BillingFailureTerm concerns the failure of invoicing for received goods and services that are contemplated by a Contract or Addendum. The meaning of charges, discounts, escalations, and taxes in this context are unclear. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledBilling SchemaA ScheduledBilling provides the schedule of invoicing for goods and services contemplated by the Contract or Addendum or in the context of a BillingTerm within a Contract or Addendum. Charges, discounts, escalations, and taxes in this context are as-yet unbilled invoice items. This term is a sub-type of ScheduledEvent and inherits all its characteristics. Body SchemaA Body in a Contract, Addendum, or Attachment identifies material that is often separately paginated from its FrontMatter and BackMatter.
CancellationTerm SchemaA CancellationTerm describes procedures for cancelling requisitions for goods or service contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a cancellation. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
CancellationEvent SchemaIn the context of a Contract or Addendum, A CancellationEvent describes a cancellation of goods or services. The charges, discounts, escalations, and taxes specified by in a CancellationEvent are those levied as a result of the cancellation. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
CancellationFailure SchemaA CancellationFailure describes a cancellation of goods or service that was not made by a Recipient. The charges, discounts, escalations, and taxes are levied as a result of the failure to perform the cancellation or render the service. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
CancellationFailureTerm SchemaA CancellationFailureTerm concerns the failure to cancel requisitions for goods or services contemplated by a Contract or Addendum. The charges, discounts, escalations, and taxes are to be levied should a failure occur. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledCancellation SchemaA ScheduledCancellation identifies a schedule for cancellation of requisitioned goods or services, whether explicit said in the contract or not. A ScheduledCancellation can be described in the context of a Contract or Addendum; or in the context of a CancellationTerm within a Contract or Addendum. This term is a sub-type of ScheduledEvent and inherits all its characteristics. Charge SchemaA Charge can be specified using (a) UnitPrice and UnitQuantity (b) a Formula, represented using MathML (c) a TotalAmount that can be further described as SubTotal amounts or SubAmounts or (d) a BaseAmount, BaseAdjustment, BasePercentage, and AdjustmentPercentage.
Clause SchemaA Clause is located in a Contract, Attachment or Addendum; in a Section of a Contract, Attachment, or Addendum; or within a SubSection of a Section.
Author SchemaAn Author is a type of Contact, and inherits all its characteristics. Additional items are noted here. Caption SchemaA Caption normally contains a single text string, but can contain multiple text strings, each in a different language. CaptionNumber SchemaA CaptionNumber contains a single text string. Editor SchemaAn Editor is a type of Contact, and inherits all its characteristics. Additional items are noted here. SubClause SchemaA SubClause is located in a Clause within a Contract, Attachment; Addendum; Section or SubSection.
CollectionTerm SchemaA CollectionTerm describes the collection of payments for invoices of goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a sending the transaction to a collections agency, or similar. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
CollectionEvent SchemaIn the context of a Contract or Addendum, a CollectionEvent describes a settlement of funds for goods or services received under contract. The charges, discounts, escalations, and taxes specified by in a CollectionEvent are those collected by settlement. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
CollectionFailure SchemaA CollectionFailure describes a payment that was rendered, but which did not clear settlement. The charges, discounts, escalations, and taxes are levied as a result of the failure to complete the collection of funds. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
CollectionFailureTerm SchemaA CollectionFailureTerm concerns failures to collect funds due from payments for invoiced goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes are those to be levied should collection failure occur. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledCollection SchemaA ScheduledCollection identifies payments received for which collection is yet to occur. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
Contact SchemaA Contact is located within a Contract, Addendum, or Attachment. This schema applies to all roles in general.
Agent SchemaAn Agent is a type of Contact, and inherits all its characteristics. Additional items are noted here. EmailAddress SchemaAn EmailAddress contains a text string. HomeAddress SchemaA HomeAddress contains the same items as an Address. LegalParty SchemaA LegalParty is a type of Contact, and inherits all its characteristics. Additional items are noted here. WorkAddress SchemaA WorkAddress contains the same items as an Address. Content SchemaContent is located within a Clause, UnOrderedContent, Paragraph, or Section; or within a SubClause, SubParagraph, SubPart, or SubSection. Its primary function is to hold text strings that comprise the "body" of the text block.
ContractCancellationEvent SchemaA ContractCancellationEvent describes the Cancellation of a Contract or Addendum.
ContractCancellationTerm SchemaA ContractCancellationTerm describes the requirements for cancelling the effect of a Contract or Addendum.
ContractExecutionEvent SchemaA ContractExecutionEvent describes the execution of a Contract or Addendum.
Offeree SchemaAn Offeree is a type of Contact, and inherits all its characteristics. Additional items are noted here. Offerer SchemaAn Offerer is a type of Contact, and inherits all its characteristics. Additional items are noted here. ContractExecutionTerm SchemaA ContractExecutionTerm describes a commercial event within the scope of the Contract or Addendum which, when performed, signifies the execution of the contract or addemdum.
ContractRenewalEvent SchemaA ContractRenewalEvent describes a renewal of a Contract or Addendum.
ContractRenewalTerm SchemaA ContractRenewalTerm describes the requirements for renewing the effect of a Contract or Addendum.
ContractSettlementEvent SchemaA ContractSettlementEvent describes the settlement of a Contract or Addendum.
ContractSettlementTerm SchemaA ContractSettlementTerm describes a commercial event within the scope of the Contract or Addendum which, when performed, signifies the (partial) settlement or expiration of the contract or addemdum.
CreditTerm SchemaA CreditTerm describes the extension of credit for the purchase of goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of the credit rather than immediate payments for the goods or services. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
CreditEvent SchemaA CreditEvent describes a credit arrangement already in place for the purchase of goods or services received under Contract or Addendum. The charges, discounts, escalations, and taxes specified by in a CreditEvent are those levied for the credit event, that is, financing charges. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
CreditFailure SchemaA CreditFailure describes an attempt to procure credit for goods and services contemplated by the contract or addendum. The charges, discounts, escalations, and taxes are levied as a result of the failure to procure the credit. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
CreditFailureTerm SchemaA CreditFailureTerm concerns the charges, discounts, escalations, and taxes to be levied should credit as envisioned by the Contract or Addendum not be procured. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledCredit SchemaA ScheduledCredit identifies credit anticipated to be extended. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
Date and Time SchemaA Date includes a year, month, day. Subtypes of a simple date include AsOfDateTime, ContractDateTime, CreateDateTime, LastEditDateTime, BeginDate, EndDate, BeforeDate, NotBeforeDate, AfterDate, and NotAfterDate. AfterDate SchemaAn AfterDateTime inherits items from Date. AfterDateTime SchemaAn AfterDateTime inherits items from DateTime. AfterTime SchemaAn AfterTime inherits items from Time. AsOfDateTime SchemaAn AsOfDateTime inherits items from DateTime. BeforeDate SchemaA BeforeDate inherits items from Date. BeforeDateTime SchemaA BeforeDateTime inherits items from DateTime. BeforeTime SchemaA BeforeTime inherits items from Time. ContractDate SchemaA ContractDate inherits items from Date. ContractDateTime SchemaA ContractDateTime inherits items from DateTime. ContractTime SchemaA ContractTime inherits items from Time. CreateDateTime SchemaA CreateDateTime inherits items from DateTime. Date Schema
EffectiveDate SchemaA EffectiveDate inherits items from Date. EffectiveDateTime SchemaA EffectiveDateTime inherits items from DateTime. EffectiveTime SchemaA EffectiveTime inherits items from Time. ExpirationDate SchemaAn ExpirationDate inherits items from Date. ExpirationDateTime SchemaAn ExpirationDateTime inherits items from DateTime. ExpirationTime SchemaAn ExpirationTime inherits items from Time. LastEditDateTime SchemaA LastEditDateTime inherits items from DateTime. NotAfterDate SchemaA NotAfterDateTime inherits items from Date. NotAfterDateTime SchemaA NotAfterDateTime inherits items from DateTime. NotAfterTime SchemaAn NotAfterTime inherits items from Time. NotBeforeDate SchemaA NotBeforeDate inherits items from Date. NotBeforeDateTime SchemaA NotBeforeDateTime inherits items from DateTime. NotBeforeTime SchemaA NotBeforeTime inherits items from Time. OrdinalBaseDate SchemaAn OrdinalBaseDate is the base against which an OrdinalDay, OrdinalMonth, or OrdinalYear is to be applied. It inherits its items from Date. OrdinalDay SchemaAn OrdinalDay is the number of days to be added to a OrdinalBaseDate. Its content is an integer or a text string that is converted to an integer. OrdinalMonth SchemaAn OrdinalMonth is the number of months to be added to a OrdinalBaseDate. Its content is an integer or a text string that is converted to an integer. OrdinalYear SchemaAn OrdinalYear is the number of years to be added to a OrdinalBaseDate. Its content is an integer or a text string that is converted to an integer. Time SchemaDeliveryTerm SchemaA DeliveryTerm describes a delivery of goods or a rendering of service that is contemplated by a Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a successful delivery. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
DeliveryEvent SchemaIn the context of a Contract or Addendum, a DeliveryEvent describes a delivery of goods that has been made or attempted, or a service that has been rendered. The charges, discounts, escalations, and taxes specified by a DeliveryEvent are those levied as a result of the attempted or successful delivery. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Recipient SchemaA Recipient is a type of Contact, and inherits all its characteristics. Additional items are noted here. Carrier SchemaA Carrier is a type of Contact, and inherits all its characteristics. Additional items are noted here. ServiceProvider SchemaA ServiceProvider is a type of Contact, and inherits all its characteristics. Additional items are noted here. DeliveryFailure SchemaA DeliveryFailure describes a delivery that was not made or attempted, or a service that has not been rendered. The charges, discounts, escalations, and taxes are levied as a result of the failure to perform the delivery or render the service. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
DeliveryFailureTerm SchemaA DeliveryFailureTerm describes a term concerning the failure of a delivery of goods that is contemplated by a Contract or Addendum. The charges, discounts, escalations, and taxes are to be levied should a failure of delivery occur. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledDelivery SchemaA ScheduledDelivery identifies a schedule for one or more deliveries of goods or renderings of service. A ScheduledDelivery can be described in the context of a Contract or Addendum; or in the context of a DeliveryTerm within a Contract or Addendum. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
EscrowTerm SchemaA EscrowTerm describes the Escrow of deposits and prepayments for goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied due to escrow fund accounting. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
EscrowEvent SchemaAn EscrowEvent describes an escrow of deposits or prepayments received for goods or services to be delivered under the Contract or Addendum. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
EscrowFailure SchemaA EscrowFailure describes an escrow of funds that was scheduled but not accomplished. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
EscrowFailureTerm SchemaAn EscrowFailureTerm concerns failures to collect deposits and prepaymentsfor goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes are those to be levied should the deposits or prepayments not occur. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledEscrow SchemaA ScheduledEscrow identifies deposits and other prepayments to be received in escrow. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
ExchangeTerm SchemaAn ExchangeTerm describes required or optional procedures for exchanging goods delivered under the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a exchange. The goods identified are those that are subjects of this term. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
ExchangeEvent SchemaAn ExchangeEvent describes an exchange of goods or services. The charges, discounts, escalations, and taxes specified by the ExchangeEvent are those levied as a result of the Exchange. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
ExchangeFailure SchemaAn ExchangeFailure describes an exchange of goods or service that were mandated by the Contract or Addendum, but not performed by a recipient. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
ExchangeFailureTerm SchemaAn ExchangeFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods not be exchanged as required by an ExchangeTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledExchange SchemaA ScheduledExchange identifies a schedule for Exchange of delivered and accepted goods or services. A ScheduledExchange can be described in the context of a Contract or Addendum; or in the context of a ExchangeTerm within a Contract or Addendum. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
Figure SchemaA Figure is located within a Clause, UnOrderedContent, Paragraph, or Section; or within a SubClause, SubParagraph, SubPart, or SubSection.
FrontMatter SchemaFrontMatter in a Contract identifies material that is often separately paginated from the Body of the Contract.
Goods SchemaGoods describe a tract of land with the buildings thereon, or a building or part of a building, usually with its grounds and other appurtenances thereon.
IndexTable SchemaAn IndexTable is used to represent tables of contents, attachments, addenda, authorities, footnotes, keywords, references, and related documents, using the Type element.
CaptionHeading Schema
CaptionNumberHeading Schema
GroupItem Schema
MajorItem Schema
MinorItem Schema
InstallationTerm SchemaAn InstallationTerm describes required or optional installations of goods, or an installation service contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of the installation. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
InstallationEvent SchemaAn InstallationEvent describes nn installation of goods, or of an installation service rendered. The charges, discounts, escalations, and taxes specified by the InstallationEvent are those levied as a result of the installation. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Installer SchemaAn Installer is a type of Contact, and inherits all its characteristics. Additional items are noted here. InstallationFailure SchemaAn InstallationFailure describes an installation of goods or an installation service mandated by the Contract or Addendum, but not performed to acceptance. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
InstallationFailureTerm SchemaAn InstallationFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods or premises not be installed as required by an InstallationTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledInstallation SchemaA ScheduledInstallation identifies a schedule for installation of goods or of an installation service to be rendered under the contract or addendum. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
MaintenanceTerm SchemaA MaintenanceTerm describes maintenance requirements for goods or premises, or as part of services, delivered under the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a maintenance. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
MaintenanceEvent SchemaA MaintenanceEvent describes a maintenance of goods or premises, or the rendering of maintenance services. The charges, discounts, escalations, and taxes specified by the MaintenanceEvent are those levied as a result of the maintenance. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
MaintenanceFailure SchemaA MaintenanceFailure describes a maintenance of goods or premises, or a maintenance service, that were mandated by the Contract or Addendum, but not performed by a caretaker. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
MaintenanceFailureTerm SchemaA MaintenanceFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods not be maintained as required by a MaintenanceTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledMaintenance SchemaA ScheduledMaintenance identifies a schedule for maintenance of goods or premises or, or the rendering of a maintenance service, as contemplated by the Contract or Addendum. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
ModificationTerm SchemaA ModificationTerm describes required or optional modifications to goods, goodwill, or premises delivered, or services rendered, under the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a modification. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
ModificationEvent SchemaA ModificationEvent describes a modification of goods or premises, or of services rendered. The charges, discounts, escalations, and taxes specified by the ModificationEvent are those levied as a result of the modification. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
ModificationFailure SchemaA ModificationFailure describes a modification of goods or service that were mandated by the Contract or Addendum, but not performed. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
ModificationFailureTerm SchemaA ModificationFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods or premises not be modified as required by a ModificationTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledModification SchemaA ScheduledModification identifies a schedule for modification of goods or premises to be delivered for acceptance, or of services to be rendered for acceptance. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
Metadata SchemaMetadata in a Contract, Addendum, or Attachment identifies material that is normally not formatted into the web page or printable view. Dublin Core information items are placed here.
Name SchemaA Name identifies a simple name for something. Subtypes of simple names are included here.
FullName SchemaA FullName is used to name a person.
LegalName SchemaA LegalName is used to name a person or other legal entity.
BusinessName SchemaA BusinessName contains a single text string. FamilyName SchemaA FamilyName contains a single text string. FirstName SchemaA FirstName contains a single text string. GivenName SchemaA GivenName contains a single text string. GroupName SchemaA GroupName contains a single text string. InstitutionName SchemaAn InstitutionName contains a single text string. LastName SchemaA LastName contains a single text string. MiddleName SchemaA MiddleName contains a single text string. NamePrefix SchemaA NamePrefix contains a single text string. NameSuffix SchemaA NameSuffix contains a single text string. OrganizationName SchemaAn OrganizationName contains a single text string. OtherName SchemaAn OtherName contains a single text string. Page SchemaA Page is located within a Contract, Addendum, Attachment; or within BackMatter, Body or FrontMatter of a Contract, Attachment, or Addendum.
BeginTextItem SchemaEndTextItem SchemaFirstFigure SchemaLastFigure SchemaPageArea SchemaA PageArea is located on a Page.
Paragraph SchemaA Paragraph is located in a Contract, Attachment or Addendum; or in a Section or SubSection, Clause, or SubClause of a Contract, Attachment, or Addendum.
SubParagraph SchemaA SubParagraph is located in a Paragraph, Section or SubSection within a Contract, Attachment, or Addendum.
PerformanceEvent SchemaA PerformanceEvent describes an event that has occurred that is related to the Contract or Addendum, but which is not related to either its initial execution or its settlement. The characteristics of a PerformanceEvent applies to all its sub-types, for instance, a DeliveryEvent or RemittanceEvent, and will not be repeated for each of those.
ScheduledEvent SchemaA ScheduledEvent describes an event that is anticipated to occur within the scope of the Contract or Addendum. The characteristics of a ScheduledEvent applies to all its sub-types, for instance, a ScheduledDelivery or ScheduledRemittance, and will not be repeated for each of those.
PerformanceFailure SchemaA PerformanceFailure describes a default event, that is, an event that did not occur, that is related to the Contract or Addendum. The characteristics of a ContractDefaultEvent applies to all its sub-types, for instance, a DeliveryFailure or a RemittanceFailure, and will not be repeated for each of those.
PerformanceFailureTerm SchemaA PerformanceFailureTerm describes the consequences of failure to satisfy a term of a Contract or Addendum. The characteristics of a PerformanceFailureTerm applies to all its sub-types, and will not be repeated for each of those.
PerformanceTerm SchemaA PerformanceTerm describes a commercial event within the scope of the Contract or Addendum, which is not related to either its initial execution or its settlement. The characteristics of a PerformanceTerm applies to all its sub-types, and will not be repeated for each of those.
Premises SchemaPremises describe a tract of land with the buildings thereon, or a building or part of a building, usually with its grounds and other appurtenances thereon.
Landlord SchemaA Landlord is a type of Contact, and inherits all its characteristics. Additional items are noted here. Manager SchemaA Manager is a type of Contact, and inherits all its characteristics. Additional items are noted here. Occupant SchemaAn Occupant is a type of Contact, and inherits all its characteristics. Additional items are noted here. Owner SchemaAn Owner is a type of Contact, and inherits all its characteristics. Additional items are noted here. Renter SchemaA Renter is a type of Contact, and inherits all its characteristics. Additional items are noted here. PrePaymentTerm SchemaA PrePaymentTerm describes pre-payments for invoices of goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be paid. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
PrePaymentEvent SchemaA PrePaymentEvent describes a pre-payment for goods or services received under the Contract or Addendum. The charges, discounts, escalations, and taxes specified by the PrePaymentEvent are those paid. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
PrePaymentFailure SchemaA PrePaymentFailure describes a pre-payment that was not received. The charges, discounts, escalations, and taxes are levied as a result of the failure to remit a prepayment. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
PrePaymentFailureTerm SchemaA PrePaymentFailureTerm concerns pre-payments not received for invoiced goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes are those to be levied should PrePayment failure occur. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledPrePayment SchemaA ScheduledPrePayment identifies pre-payments yet to occur. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
ProcurementTerm SchemaA ProcurementTerm describes the procurement and inventorying of goods under the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a procurement or inventory. The goods identified are those that are subjects of this term. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
ProcurementEvent SchemaA ProcurementEvent describes the receipt of goods that are then placed into inventory. The charges, discounts, escalations, and taxes specified by the ProcurementEvent are those levied as a result of the procurement/inventory. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Distributor SchemaA Distributor is a type of Contact, and inherits all its characteristics. Additional items are noted here. Wholesaler SchemaA Wholesaler is a type of Contact, and inherits all its characteristics. Additional items are noted here. ProcurementFailure SchemaA ProcurementFailure describes a procurement of goods that were mandated by the Contract or Addendum, but not performed by a supplier. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
ProcurementFailureTerm SchemaA ProcurementFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods not be procured/inventoried as required by a procurementTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledProcurement SchemaA ScheduledProcurement identifies a schedule for procurement of goods. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
ProductionTerm SchemaA ProductionTerm describes the production of goods under the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of the manufacture. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
ProductionEvent SchemaA ProductionEvent describes an incidence of manufacture. The charges, discounts, escalations, and taxes specified by the ProductionEvent are those levied as a result of the manufacture. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Manufacturer SchemaA Manufacturer is a type of Contact, and inherits all its characteristics. Additional items are noted here. ProductionFailure SchemaA ProductionFailure describes a manufacture of goods that was mandated by the Contract or Addendum, but not performed. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
ProductionFailureTerm SchemaA ProductionFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods not be manufacture as required by a ProductionTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledProduction SchemaA ScheduledProduction identifies a schedule for manufacture of goods. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
PurchaseTerm SchemaA PurchaseTerm describes requiremetns concerning the purchase of goods, goodwill, premises, or services under the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of the purchase. The goods identified are those that are subjects of this term. This term is a sub-type of ContractSettlementTerm and inherits all its characteristics.
PurchaseEvent SchemaA PurchaseEvent describes a purchase of goods or services that has occurred. The charges, discounts, escalations, and taxes specified by the PurchaseEvent are those levied as a result of the purchase. This term is a sub-type of ContractSettlementEvent and inherits all its characteristics.
PurchaseFailure SchemaA PurchaseFailure describes a purchase of goods or services that were mandated by the Contract or Addendum, but not performed by a purchaser. This term is a sub-type of ContractSettlementFailure and inherits all its characteristics.
PurchaseFailureTerm SchemaA PurchaseFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods or services not be purchased as required by A PurchaseTerm in the Contract or Addendum. This term is a sub-type of ContractSettlementFailureTerm and inherits all its characteristics.
ScheduledPurchase SchemaA ScheduledPurchase identifies a schedule for purchase of goods or services. A ScheduledPurchase can be described in the context of a Contract or Addendum; or in the context of a PurchaseTerm within a Contract or Addendum. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
ReimbursementTerm SchemaA ReimbursementTerm describes the reimbursement terms of financing received for payment of invoices for goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be billed as a result of a financing. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
ReimbursementEvent SchemaA ReimbursementEvent describes a re-payment of overage amounts. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
ReimbursementFailure SchemaA ReimbursementFailure describes a payment that was scheduled, but which did not occur. The charges, discounts, escalations, and taxes are levied as a result of the failure to perform the reimbursement of funds. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
ReimbursementFailureTerm SchemaA ReimbursementFailureTerm concerns failures to collect funds due for financings. The terms of charges, discounts, escalations, and taxes are those to be levied should Reimbursement failure occur. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledReimbursement SchemaA ScheduledReimbursement identifies one-time and recurring payments to be made for debt. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
RemittanceTerm SchemaA RemittanceTerm describes payments for invoices of goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be paid. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
RemittanceEvent SchemaA RemittanceEvent describes a payment for goods or services received under the Contract or Addendum. The charges, discounts, escalations, and taxes specified by the RemittanceEvent are those paid. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Payee SchemaA Payee is a type of Contact, and inherits all its characteristics. Additional items are noted here. Payer SchemaA Payer is a type of Contact, and inherits all its characteristics. Additional items are noted here. RemittanceFailure SchemaA RemittanceFailure describes a payment that was not received. The charges, discounts, escalations, and taxes are levied as a result of the Remittance failure. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
RemittanceFailureTerm SchemaA RemittanceFailureTerm concerns a payment not received for invoiced goods or services contemplated by the Contract or Addendum. The terms of charges, discounts, escalations, and taxes are those to be levied should Remittance failure occur. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledRemittance SchemaA ScheduledRemittance identifies payments yet to occur. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
RequisitionTerm SchemaA RequisitionTerm describes the requisition or ordering of goods involved with the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of the requisition or order. The goods identified are those that are subjects of this term. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
RequisitionEvent SchemaA RequisitionEvent describes the ordering of goods that are then delivered to a recipient. The charges, discounts, escalations, and taxes specified by the RequisitionEvent are those levied as a result of the Requisition/inventory. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Customer SchemaA Customer is a type of Contact, and inherits all its characteristics. Additional items are noted here. Seller SchemaA Seller is a type of Contact, and inherits all its characteristics. Additional items are noted here. Supplier SchemaA Supplier is a type of Contact, and inherits all its characteristics. Additional items are noted here. RequisitionFailure SchemaA RequisitionFailure describes a requisition of goods that were mandated by the Contract or Addendum, but not performed by a recipient. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
RequisitionFailureTerm SchemaA RequisitionFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods not be procured/ordered as required by a RequisitionTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledRequisition SchemaA ScheduledRequisition identifies a future one-time or recurring requisition of goods and services. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
Section SchemaA Section is located in a Contract, Attachment or Addendum.
SubSection SchemaA SubSection is located in a Section within a Contract, Attachment, or Addendum.
SurrenderTerm SchemaA SurrenderTerm describes the surrender of goods under the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of a surrender of goods. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
SurrenderEvent SchemaA SurrenderEvent describes the claim of goods between claimant and claimee. The charges, discounts, escalations, and taxes specified by the SurrenderEvent are those levied as a result of the surrender event. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
Claimant SchemaA Claimant is a type of Contact, and inherits all its characteristics. Additional items are noted here. Claimee SchemaA Claimee is a type of Contact, and inherits all its characteristics. Additional items are noted here. SurrenderFailure SchemaA SurrenderFailure describes a surrender of goods mandated by the Contract or Addendum, but not performed by a claimee. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
SurrenderFailureTerm SchemaA SurrenderFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods not be procured/inventoried as required by a SurrenderTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledSurrender SchemaA ScheduledSurrender identifies a schedule for Surrender of goods. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
Table SchemaA Table is basic content like Content, which holds string data, Figure, which holds image data, and List, which holds a set of strings.
Cell SchemaA Cell occurs within a Column, Row, or Row. Within the context of a Table, it is to be flowed.
Column SchemaA Column occurs within a Table.
Row SchemaA Row occurs within a Table.
TotalAmount Schema
ActualValue Schema
EstimatedValue Schema
PreviousValue Schema
SubAmount Schema
SubTotal Schema
UnOrderedContent SchemaUnOrderedContent is located within a Clause, Paragraph, or Section; or within a SubClause, SubParagraph, SubPart, or SubSection. Its primary function is to hold text strings that comprise the "body" of the text block. UseTerm SchemaA UseTerm describes the use of goods under the Contract or Addendum. The terms of charges, discounts, escalations, and taxes describe those to be levied as a result of the use of goods. This term is a sub-type of PerformanceTerm and inherits all its characteristics.
UseEvent SchemaA UseEvent describes an incidence of use of goods. The charges, discounts, escalations, and taxes specified by the UseEvent are those levied as a result of the use. This term is a sub-type of PerformanceEvent and inherits all its characteristics.
UseFailure SchemaA UseFailure describes a use of goods that were mandated by the Contract or Addendum, but not performed. This term is a sub-type of PerformanceFailure and inherits all its characteristics.
UseFailureTerm SchemaA UseFailureTerm concerns the charges, discounts, escalations, and taxes that are to be levied should goods not be used as required by a UseTerm in the Contract or Addendum. This term is a sub-type of PerformanceFailureTerm and inherits all its characteristics.
ScheduledUse SchemaA ScheduledUse identifies a schedule for use of goods. This term is a sub-type of ScheduledEvent and inherits all its characteristics.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]